On 10/01/2013 03:04 PM, Yair Zaslavsky wrote:
> >
>>> > >>I think I have an idea about what happended now.
>>> > >>
>>> > >>The 2 disappeared VMs have been imported into oVirt using
virt-v2v. The
>>> > >>3rd one that's now missing a disk volume was not, but I have
been
>>> > >>playing with storage migration in the past.
>> > >
>> > >Then this is the reason, other users have complained about it at
>> > >users(a)ovirt.org
> >
> >I have read the thread about disappearing VMs from August and indeed it
> >sounds like this might me the same problem.
> >
>> > >Upgrade I just talked with Ofer (CC'ed), our release engineer, and
he
>> > >said that all packages should be 3.3.0-4 (notice ovirt-engine is
>> > >not) I hope this helps you out,
> >
> >There are no updates, at least Yum doesn't give me any. I enabled the
> >beta channel just now, but that doesn't make a difference. 3.3.0-1 is
> >the latest version. What am I missing?
> >
> >martijn@ovirt:~> sudo yum list all|grep ovirt-engine.noarch
> >ovirt-engine.noarch 3.3.0-1.el6 @ovirt-beta
I'll let ofer answer that.
you should run ovirt-check-update and ovirt-engine-upgrade (or
ovirt-engine-setup) to get updates for engine. we use version lock to
prevent yum for updating the rpm without proper sync of db/backup/rollback.