Re: [Users] single VM disappeared
Hi, This appears to affect VM's derived from the template clone task. http://lists.ovirt.org/pipermail/users/2013-September/016172.html On 13 Sep 2013, at 16:43, Hans-Joachim wrote: > Hi, > > it should be, as you will loose all your imported VMs by restarting the > engine. > > Hans-Joachim > > Date: Fri, 13 Sep 2013 11:19:09 -0400 (EDT) > From: Ofer Schreiber > To: Yair Zaslavsky > Cc: "users@ovirt.org" > Subject: Re: [Users] single VM disappeared > Message-ID: <54b23153-0a06-45e9-8417-c5f4df540...@redhat.com> > Content-Type: text/plain; charset="utf-8" > > Nothing actually. > Unless its a huge blocker, than we might rebuild the engine with it. > Otherwise, it will be in 3.3.1 which will be a month from now. > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] single VM disappeared
Thanks for the update. I'm hoping this can get fast tracked into the mainline beta, ready for release on Monday. This is a show stopper for many people - especially those migrating from previous community release; where an in place upgrade does not work. Since upgrading from 3.2 to 3.3, our VM estate is essentially useless. I understand the timing, and the possible uniqueness of the issue. Yet, to wait a month the facilitate an upgrade would see our oVirt estate dropped. This is essentially a non starter. I can replicate this issue consistently, so if I can assist in testing any builds, please let me know. Here's hoping for some good news! :) Thanks, James On 13 Sep 2013, at 16:19, Ofer Schreiber wrote: > Nothing actually. > Unless its a huge blocker, than we might rebuild the engine with it. > Otherwise, it will be in 3.3.1 which will be a month from now. > > > > ב-13 Sep 2013, בשעה 14:04, Yair Zaslavsky כתב/ה: > >> >> >> - Original Message - >>> From: "James Wilson" >>> To: users@ovirt.org >>> Cc: "Yair Zaslavsky" >>> Sent: Friday, September 13, 2013 2:00:31 PM >>> Subject: Re: [Users] single VM disappeared >>> >>> Hi, >>> >>> Absolutely correct - I imported a VM, manually modified the vdsmTaskIds >>> entry, which was set to null. Restarted ovirt-engine, and the VM remains. >>> >>> This is also successful, if post import, before restarting overt-engine, the >>> task is deleted completed form the async_tasks table. >>> >>> The VM remains. >>> >>> Will this patch make it into Beta? >> >> Ofer - what can be done so this patch makes it into beta? it is already >> merged on ovirt-engine-3.3 branch >> >>> >>> On 13 Sep 2013, at 11:53, Yair Zaslavsky wrote: >>> >>>> I managed to resolve these issues (import vm, restart, no vms) with the >>>> following patch >>>> >>>> http://gerrit.ovirt.org/#/c/17582/ >>>> >>>> >>>> >>>> - Original Message - >>>>> From: "Markus Stockhausen" >>>>> To: "Hans-Joachim" , users@ovirt.org >>>>> Sent: Friday, September 13, 2013 10:11:11 AM >>>>> Subject: Re: [Users] single VM disappeared >>>>> >>>>>> Von: users-boun...@ovirt.org [users-boun...@ovirt.org]" im Auftrag von >>>>>> "Hans-Joachim [r...@chef.net] >>>>>> Gesendet: Freitag, 13. September 2013 09:08 >>>>>> An: users@ovirt.org >>>>>> Betreff: Re: [Users] single VM disappeared >>>>>> >>>>>> Hi, >>>>>> >>>>>> Yesterday, I opened a ticket too... Sorry >>>>>> >>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1007427 >>>>>> >>>>>> Hans-Joachim >>>>> >>>>> No problem at all. The more reports the better. >>>>> >>>>> Markus >>>>> >>>>> >>>>> ___ >>>>> Users mailing list >>>>> Users@ovirt.org >>>>> http://lists.ovirt.org/mailman/listinfo/users >>>>> >>>> ___ >>>> Users mailing list >>>> Users@ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] single VM disappeared
Hi, Absolutely correct - I imported a VM, manually modified the vdsmTaskIds entry, which was set to null. Restarted ovirt-engine, and the VM remains. This is also successful, if post import, before restarting overt-engine, the task is deleted completed form the async_tasks table. The VM remains. Will this patch make it into Beta? On 13 Sep 2013, at 11:53, Yair Zaslavsky wrote: > I managed to resolve these issues (import vm, restart, no vms) with the > following patch > > http://gerrit.ovirt.org/#/c/17582/ > > > > - Original Message - >> From: "Markus Stockhausen" >> To: "Hans-Joachim" , users@ovirt.org >> Sent: Friday, September 13, 2013 10:11:11 AM >> Subject: Re: [Users] single VM disappeared >> >>> Von: users-boun...@ovirt.org [users-boun...@ovirt.org]" im Auftrag von >>> "Hans-Joachim [r...@chef.net] >>> Gesendet: Freitag, 13. September 2013 09:08 >>> An: users@ovirt.org >>> Betreff: Re: [Users] single VM disappeared >>> >>> Hi, >>> >>> Yesterday, I opened a ticket too... Sorry >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1007427 >>> >>> Hans-Joachim >> >> No problem at all. The more reports the better. >> >> Markus >> >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.3 Dependency Resolution
Hi Dave, I can replicate this consistently. The only repo I disabled was the Stable oVirt definition, to enable only the Beta: name=Stable builds of the oVirt project baseurl=http://ovirt.org/releases/updates-testing/rpm/EL/$releasever/ enabled=0 skip_if_unavailable=1 gpgcheck=0 priority=20 [ovirt-beta] name=Beta builds of the oVirt project baseurl=http://ovirt.org/releases/beta/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 priority=20 Otherwise, this is a vanilla install! Could it be a similar regression to this issue? http://list-archives.org/2013/07/31/users-ovirt-org/vdsm-v4-12-0-dependencies-for-el6-hosts/f/2841672598 Thanks, James On 12 Sep 2013, at 19:49, Dave Neary wrote: > Hi James, > > I didn't have the same issues - is that because I disabled one or more > of the repos, or purely luck in the order the repos were processed for me? > > Thanks, > Dave. > > On 09/12/2013 06:39 PM, James Wilson wrote: >> Hi, >> >> I've just performed a clean install of CentOS 6.4 x86_64 (Minimal) along >> with oVirt 3.3 from the official EL6 Beta repository. This resulted in >> dependency conflicts between the official oVirt repo and EPEL. >> >> The following repositories were installed and activated: >> >> # yum localinstall >> http://resources.ovirt.org/releases/ovirt-release-el6-8-1.noarch.rpm -y >> # yum localinstall >> http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm -y >> >> Followed by installation of the main oVirt engine and all-in-one >> configuration: >> >> # yum install ovirt-engine-setup-plugin-allinone -y >> >> This resulted in the following fatal error: >> >> Error: Package: vdsm-4.12.1-2.el6.x86_64 (ovirt-beta) >> Requires: mom >= 0.3.2-3 >> Available: mom-0.3.0-1.el6.noarch (epel) >> mom = 0.3.0-1.el6 >> Error: Package: glusterfs-api-3.4.0-8.el6.x86_64 (glusterfs-epel) >> Requires: glusterfs = 3.4.0-8.el6 >> Available: glusterfs-3.2.7-1.el6.i686 (epel) >> glusterfs = 3.2.7-1.el6 >> Error: Package: vdsm-4.12.1-2.el6.x86_64 (ovirt-beta) >> Requires: glusterfs >= 3.4.0 >> Available: glusterfs-3.2.7-1.el6.i686 (epel) >> glusterfs = 3.2.7-1.el6 >> You could try using --skip-broken to work around the problem >> You could try running: rpm -Va --nofiles --nodigest >> >> To resolve, priorities have to be set within the yum repository definitions: >> >> # yum install yum-priorities >> >> Adding arbitrary priorities to the oVirt and EPEL repositories rectified the >> issue - giving EPEL a lower value. For example: >> >> /etc/yum.repos.d/el6-ovirt.repo >> >> [ovirt-beta] >> name=Beta builds of the oVirt project >> baseurl=http://ovirt.org/releases/beta/rpm/EL/$releasever/ >> enabled=1 >> skip_if_unavailable=1 >> gpgcheck=0 >> priority=20 >> priority=20 >> >> /etc/yum.repos.d/epel.repo >> >> [epel] >> name=Extra Packages for Enterprise Linux 6 - $basearch >> #baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch >> mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=$basearch >> failovermethod=priority >> enabled=1 >> gpgcheck=1 >> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 >> priority=25 >> >> The priority setting must be enabled for each repo definition, Once >> complete, the installation succeeds without issue. >> >> Hope this helps! >> >> James >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > > -- > Dave Neary - Community Action and Impact > Open Source and Standards, Red Hat - http://community.redhat.com > Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] single VM disappeared
On 12 Sep 2013, at 21:27, Markus Stockhausen wrote: >> please provide the output of: >> >> psql engine postgres -c "select * from async_tasks;" > > Ok, this is going really crazy now. We are talking about two errors > that occured at nearly the same time. The first one is what you > described. The bug on the CPU pane prohibits me from starting the > VM because "Emulated machine" is empty. No problem with that > I have a workaround. > > But now to the other bug. Took me quite some time to reproduce > it. But the setup is very simple. > > 1) Import a VM from an export domain into the cluster. > 2) Wait for the successful finished message > 3) See the machine in the VM overview of the cluster >Everything looks fine (vm, disks, ...) > 4) stop and start cluster > 5) machine is missing > 6) cluster spits failure messages This exact thing is happening to me. I'm trying to import oVirt 3.2 VM's from an export domain. The import is successful, to the point I can fire up the VM's. Restart ovirt-engine and the VM is gone. Prior to the latest ovirt-engine update, only the VM container was removed and the disk remained. Since updating to ovirt-engine-3.3.0-3.el6.noarch a few moments ago, the container still gets removed, but now the disk is gone too! CentOS 6.4 x86_64 / oVirt 3.3 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] oVirt 3.3 Dependency Resolution
Hi, I've just performed a clean install of CentOS 6.4 x86_64 (Minimal) along with oVirt 3.3 from the official EL6 Beta repository. This resulted in dependency conflicts between the official oVirt repo and EPEL. The following repositories were installed and activated: # yum localinstall http://resources.ovirt.org/releases/ovirt-release-el6-8-1.noarch.rpm -y # yum localinstall http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm -y Followed by installation of the main oVirt engine and all-in-one configuration: # yum install ovirt-engine-setup-plugin-allinone -y This resulted in the following fatal error: Error: Package: vdsm-4.12.1-2.el6.x86_64 (ovirt-beta) Requires: mom >= 0.3.2-3 Available: mom-0.3.0-1.el6.noarch (epel) mom = 0.3.0-1.el6 Error: Package: glusterfs-api-3.4.0-8.el6.x86_64 (glusterfs-epel) Requires: glusterfs = 3.4.0-8.el6 Available: glusterfs-3.2.7-1.el6.i686 (epel) glusterfs = 3.2.7-1.el6 Error: Package: vdsm-4.12.1-2.el6.x86_64 (ovirt-beta) Requires: glusterfs >= 3.4.0 Available: glusterfs-3.2.7-1.el6.i686 (epel) glusterfs = 3.2.7-1.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest To resolve, priorities have to be set within the yum repository definitions: # yum install yum-priorities Adding arbitrary priorities to the oVirt and EPEL repositories rectified the issue - giving EPEL a lower value. For example: /etc/yum.repos.d/el6-ovirt.repo [ovirt-beta] name=Beta builds of the oVirt project baseurl=http://ovirt.org/releases/beta/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 priority=20 priority=20 /etc/yum.repos.d/epel.repo [epel] name=Extra Packages for Enterprise Linux 6 - $basearch #baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=$basearch failovermethod=priority enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 priority=25 The priority setting must be enabled for each repo definition, Once complete, the installation succeeds without issue. Hope this helps! James ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
