[ovirt-users] ovirt 4.2 and hosted-engine storage migration
Does it exist any supported procedure to migrate the hosted-engine from one NFS storage to another NFS storage? I would appreciate any clue regarding this matter. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Odp: Re: ERROR Failed extracting VM OVF from the OVF_STORE volume
I have 2 nodes. The problem was temporarily solved after ovirt-ha-agent restart but then it came back but just on the one node. Do you know how to troubleshoot it? Gabriel Dnia 26 września 2017 13:13 gabriel_skup...@o2.plnapisał(a): And it started again ;/ Any idea? Regards, G. Dnia 26 września 2017 11:53 gabriel_skup...@o2.pl napisał(a): Dnia 26 września 2017 09:27 Gianluca Cecchi napisał(a): On Tue, Sep 26, 2017 at 9:14 AM, gabriel_skup...@o2.pl wrote: After a fresh installation of oVirt Node 4.1.5 and self-hosted engine I can see hundreds of logs like below. What is this about? How to mitigate it? 07:08 ovirt-ha-agent ovirt_hosted_engine_ha.agent. hosted_engine.HostedEngine. config ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agentHello, I had a recent experience with the same messages, but on RHV-H image, with a version comparable with oVirt node 4.1.5. In my case the messages disappeared after executing: systemctl restart ovirt-ha-agent I confirm, that solved the problem. ps. when you get such problems at the beginning it does not encourage you for further diving in it :)I didn't investigate more on the real cause though. HIH, Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Odp: Re: ERROR Failed extracting VM OVF from the OVF_STORE volume
And it started again ;/ Any idea? Regards, G. Dnia 26 września 2017 11:53 gabriel_skup...@o2.pl napisał(a): Dnia 26 września 2017 09:27 Gianluca Cecchinapisał(a): On Tue, Sep 26, 2017 at 9:14 AM, gabriel_skup...@o2.pl < gabriel_skup...@o2.pl > wrote: After a fresh installation of oVirt Node 4.1.5 and self-hosted engine I can see hundreds of logs like below. What is this about? How to mitigate it? 07:08 ovirt-ha-agent ovirt_hosted_engine_ha.agent. hosted_engine.HostedEngine. config ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agentHello, I had a recent experience with the same messages, but on RHV-H image, with a version comparable with oVirt node 4.1.5. In my case the messages disappeared after executing: systemctl restart ovirt-ha-agent I confirm, that solved the problem. ps. when you get such problems at the beginning it does not encourage you for further diving in it :)I didn't investigate more on the real cause though. HIH, Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Odp: Re: ERROR Failed extracting VM OVF from the OVF_STORE volume
Dnia 26 września 2017 09:27 Gianluca Cecchinapisał(a): On Tue, Sep 26, 2017 at 9:14 AM,gabriel_skup...@o2.pl < gabriel_skup...@o2.pl > wrote: After a fresh installation of oVirt Node 4.1.5 and self-hosted engine I can see hundreds of logs like below. What is this about? How to mitigate it? 07:08 ovirt-ha-agent ovirt_hosted_engine_ha.agent. hosted_engine.HostedEngine. config ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agentHello, I had a recent experience with the same messages, but on RHV-H image, with a version comparable with oVirt node 4.1.5. In my case the messages disappeared after executing: systemctl restart ovirt-ha-agent I confirm, that solved the problem. ps. when you get such problems at the beginning it does not encourage you for further diving in it :)I didn't investigate more on the real cause though. HIH, Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Odp: Re: ERROR Failed extracting VM OVF from the OVF_STORE volume
Dnia 26 września 2017 09:36 Gianluca Cecchinapisał(a):Il 26 Set 2017 09:31, "Martin Sivak" < msi...@redhat.com > ha scritto: Hi guys, do you see the hosted engine VM and the storage domain in the webadmin console? Yes. Hosted engine will prepare all the necessary files after a master storage domain is added and OVF is generated within one hour after webadmin starts (or when hosted engine VM is edited). It was installed yesterday. The logs I provided are from today. Regards, G. Best regards Martin Sivak On Tue, Sep 26, 2017 at 9:27 AM, Gianluca Cecchi < gianluca.cec...@gmail.com > wrote: > On Tue, Sep 26, 2017 at 9:14 AM,gabriel_skup...@o2.pl > < gabriel_skup...@o2.pl > wrote: >> >> After a fresh installation of oVirt Node 4.1.5 and self-hosted engine I >> can see hundreds of logs like below. What is this about? How to mitigate it? >> >> 07:08 >> ovirt-ha-agent >> ovirt_hosted_engine_ha.agent. hosted_engine.HostedEngine. config ERROR Failed >> extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf >> ovirt-ha-agent >> > > Hello, > I had a recent experience with the same messages, but on RHV-H image, with a > version comparable with oVirt node 4.1.5. > In my case the messages disappeared after executing: > > systemctl restart ovirt-ha-agent > > I didn't investigate more on the real cause though. > > HIH, > Gianluca > > __ _ > Users mailing list >Users@ovirt.org > lists.ovirt.org lists.ovirt.org mailman/listinfo/users > Yes, when I had this problem some days ago, all was ok from self hosted engine point of view. In webadmin gui I saw the hosted engine storage as up, I saw the engine VM line between the VMs and could also connect to its console from the GUI. My storage is FC if it can help debugging ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] ERROR Failed extracting VM OVF from the OVF_STORE volume
After a fresh installation of oVirt Node 4.1.5 and self-hosted engine I can see hundreds of logs like below. What is this about? How to mitigate it? 07:08 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:08 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:07 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:07 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:07 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:07 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:06 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:06 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:06 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:06 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:06 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:06 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:05 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:05 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:05 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:05 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:04 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:04 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:04 ovirt-ha-agent ovirt_hosted_engine_ha.agent.h ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf ovirt-ha-agent 07:04 ovirt-ha-agent ovirt_hosted_engine_ha.lib.ovf ERROR Unable to extract HEVM OVF ovirt-ha-agent 07:04 Regards, Gabriel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Odp: Re: How to upgrade self-hosted engine?
Dnia 21 września 2017 13:20 Johan Bernhardssonnapisał(a): 2017-09-21 13:08 skrev gabriel_skup...@o2.pl: Dnia 20 września 2017 15:54 Kasturi Narra napisał(a): Hi, upgrade HE (Hosted Engine ) by doing the steps below. 1) Move HE to global maintenance by running the command 'hosted-engine --set-maintenance --mode=global' 2) Add the required repos which has higher package versions. 3) Run 'yum update ovirt\*setup\*' What if we upgrade all packages by 'yum update'?That will break the engine most probably. Since engine-setup does more than just installing the package. To ensure a safe upgrade follow these steps. Clear. G./Johan -- Security all the way ... Linux/CMS/Network/Print/Virtua Consultant Kafit AB Orgnr: 556792-5945 Mobile: +46705111751 Sweden: +46101993005 Seychelles: +2486478105 Uk: +448701821792 Email: jo...@kafit.se Web: www.kafit.se www.kafit.se Connect with me on LinkedIn: www.linkedin.com www.linkedin.com About me: about.me about.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Odp: Re: How to upgrade self-hosted engine?
Dnia 20 września 2017 15:54 Kasturi Narranapisał(a): Hi, upgrade HE (Hosted Engine ) by doing the steps below. 1) Move HE to global maintenance by running the command 'hosted-engine --set-maintenance --mode=global' 2) Add the required repos which has higher package versions. 3) Run 'yum update ovirt\*setup\*' What if we upgrade all packages by 'yum update'? 4) engine-setup 5) Once the setup is done successfully please move HE out of global maintenance mode by running the command 'hosted-engine --set-maintenance --mode=none' For upgrade node you can do the steps below: 1) If there is an upgrade link present in the 'General' tab of the UI, (if ovirt node) click upgrade from UI which will move the host to maintenance and run upgrade on the system, reboots and brings it back up to Normal state. 2) If you do not see the upgrade link, then add the repos to which you would want to update the node. 3) Run 'yum update' 4) Reboot the system. 5) make sure that you are on the latest image by running 'imgbase w' if it is a ovirt node. 6)otherwise just make sure that you are on the latest kernel once your upgrade finishes. THANK YOU!Hope this helps Thanks kasturi On Wed, Sep 20, 2017 at 6:34 PM,gabriel_skup...@o2.pl < gabriel_skup...@o2.pl > wrote: To be honest, I don't see consistency regarding all that upgrade procedures. Have a look here: www.ovirt.org www.ovirt.org documentation/upgrade-guide/ chap-Updating_the_oVirt_ Environment/ It asks to update the system too :) I will appreciate if somebody clearly explains: -to upgrade the Node - please do this and this -to upgrade the Hosted-Engine - please do this and this. G. Dnia 20 września 2017 14:52 Johan Bernhardsson < jo...@kafit.se > napisał(a): If you follow that guide it will update everything on the virtual server running the engine. You should not run yum to upgrade the packages (correct me anyone if i am wrong about this) The engine-setup will download and install the packages for you. And on the nodes upgrade first via the web interface and after that you can upgrade with yum on the nodes. Don't forget to have the node in maintence mode when you run yum update /Johan 2017-09-20 14:39 skrevgabriel_skup...@o2.pl : Thanks. What about the system itself? Is yum update enough? Dnia 20 września 2017 13:25 Johan Bernhardsson < jo...@kafit.se > napisał(a): Follow this guide if it is between minor releaseswww.ovirt.org www.ovirt.org documentation/upgrade-guide/ chap-Updates_between_Minor_ Releases/Don't forget to send the hosted-engine to global maintenance /Johan On September 20, 2017 13:11:41gabriel_skup...@o2.pl wrote: In oVirt Engine Web Administration portal I can see option to upgrade the nodes but can't see any option to upgrade hosted-engine itself? What is the recommended procedure for it? __ _ Users mailing listUsers@ovirt.org lists.ovirt.org lists.ovirt.org mailman/listinfo/users -- Security all the way ... Linux/CMS/Network/Print/ Virtualisation/VoIP Consultant Kafit AB Orgnr: 556792-5945 Mobile: +46705111751 Sweden: +46101993005 Seychelles: +2486478105 Uk: +448701821792 Email: jo...@kafit.se Web: www.kafit.se www.kafit.se Connect with me on LinkedIn: www.linkedin.com www.linkedin.com smallone About me: about.me about.me __ _ Users mailing list Users@ovirt.orglists.ovirt.org lists.ovirt.org mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Odp: Re: How to upgrade self-hosted engine?
To be honest, I don't see consistency regarding all that upgrade procedures. Have a look here: www.ovirt.org www.ovirt.org It asks to update the system too :) I will appreciate if somebody clearly explains: -to upgrade the Node - please do this and this -to upgrade the Hosted-Engine - please do this and this. G. Dnia 20 września 2017 14:52 Johan Bernhardssonnapisał(a): If you follow that guide it will update everything on the virtual server running the engine. You should not run yum to upgrade the packages (correct me anyone if i am wrong about this) The engine-setup will download and install the packages for you. And on the nodes upgrade first via the web interface and after that you can upgrade with yum on the nodes. Don't forget to have the node in maintence mode when you run yum update /Johan 2017-09-20 14:39 skrev gabriel_skup...@o2.pl: Thanks. What about the system itself? Is yum update enough? Dnia 20 września 2017 13:25 Johan Bernhardsson napisał(a): Follow this guide if it is between minor releases www.ovirt.org www.ovirt.org Don't forget to send the hosted-engine to global maintenance /Johan On September 20, 2017 13:11:41 gabriel_skup...@o2.pl wrote: In oVirt Engine Web Administration portal I can see option to upgrade the nodes but can't see any option to upgrade hosted-engine itself? What is the recommended procedure for it? __ Users mailing list Users@ovirt.org lists.ovirt.org lists.ovirt.org -- Security all the way ... Linux/CMS/Network/Print/Virtua Consultant Kafit AB Orgnr: 556792-5945 Mobile: +46705111751 Sweden: +46101993005 Seychelles: +2486478105 Uk: +448701821792 Email: jo...@kafit.se Web: www.kafit.se www.kafit.se Connect with me on LinkedIn: www.linkedin.com www.linkedin.com About me: about.me about.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Odp: Re: How to upgrade self-hosted engine?
Thanks. What about the system itself?Is yum update enough? Dnia 20 września 2017 13:25 Johan Bernhardssonnapisał(a): Follow this guide if it is between minor releases www.ovirt.org www.ovirt.org Don't forget to send the hosted-engine to global maintenance /Johan On September 20, 2017 13:11:41 gabriel_skup...@o2.pl wrote: In oVirt Engine Web Administration portal I can see option to upgrade the nodes but can't see any option to upgrade hosted-engine itself? What is the recommended procedure for it? _ Users mailing list Users@ovirt.org lists.ovirt.org lists.ovirt.org ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] How to upgrade self-hosted engine?
In oVirt Engine Web Administration portal I can see option to upgrade the nodes but can't see any option to upgrade hosted-engine itself? What is the recommended procedure for it? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Odp: How to import OVA file into oVirt
Dnia 20 września 2017 11:25 Arik Hadasnapisał(a): On Wed, Sep 20, 2017 at 11:59 AM,gabriel_skup...@o2.pl < gabriel_skup...@o2.pl > wrote: Dnia 19 września 2017 16:03 Arik Hadas < aha...@redhat.com > napisał(a):On Tue, Sep 19, 2017 at 4:52 PM, gabriel_skup...@o2.pl wrote: I also tried to use the Import Virtual Machines option, there is an option to set the source to Vmware Virtual Appliance (OVA) but I don't know how to fill in the Path box. Tried domanin ip_address but did not work. Yes, that's the right way of doing that. In the path you should specify the local path to the file on the host, for example if you placed in the export domain it will be something like: /rhev/data-center/ /< domain_id>/.../file.ova but you can put it also in /tmp in some specific host and select that host as a proxy. Thanks, it works but now. I am getting: -Failed to convert Vm ASAv and then -Failed to import Vm ASAv to Data Center Default, Cluster Default.Do you know how to troubleshoot it? So you managed to reach the conversion phase - that's a good progress. We'll need the VDSM log that covers the time of the conversion on the host that was selected as proxy in order to investigate the failure. Could you please file a bug [1] and attach the log to that bug? [1] bugzilla.redhat.com bugzilla.redhat.com bugzilla.redhat.com bugzilla.redhat.com G. Dnia 19 września 2017 15:40 gabriel_skup...@o2.pl napisał(a): I am trying to import OVA file into my test oVirt env. I already have the export domain configured but when I go to the "VM Import" tab the "Import" button in inactive. oVirt 4.1.5/4.1.6 Any clue? G. __ _ Users mailing list Users@ovirt.org lists.ovirt.org lists.ovirt.org /listinfo/users __ _ Users mailing list Users@ovirt.org lists.ovirt.org lists.ovirt.org /listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Odp: How to import OVA file into oVirt
Dnia 19 września 2017 16:03 Arik Hadasnapisał(a): On Tue, Sep 19, 2017 at 4:52 PM,gabriel_skup...@o2.pl < gabriel_skup...@o2.pl > wrote: I also tried to use the Import Virtual Machines option, there is an option to set the source to Vmware Virtual Appliance (OVA) but I don't know how to fill in the Path box. Tried domanin ip_address but did not work. Yes, that's the right way of doing that. In the path you should specify the local path to the file on the host, for example if you placed in the export domain it will be something like: /rhev/data-center/ / napisał(a): I am trying to import OVA file into my test oVirt env. I already have the export domain configured but when I go to the "VM Import" tab the "Import" button in inactive. oVirt 4.1.5/4.1.6 Any clue? G. __ _ Users mailing list Users@ovirt.org lists.ovirt.org lists.ovirt.org mailman/listinfo/users __ _ Users mailing list Users@ovirt.orglists.ovirt.org lists.ovirt.org mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Odp: How to import OVA file into oVirt
I also tried to use the Import Virtual Machines option, there is an option to set the source to Vmware Virtual Appliance (OVA) but I don't know how to fill in the Path box. Tried domanin ip_address but did not work. G. Dnia 19 września 2017 15:40 gabriel_skup...@o2.plnapisał(a): I am trying to import OVA file into my test oVirt env. I already have the export domain configured but when I go to the "VM Import" tab the "Import" button in inactive. oVirt 4.1.5/4.1.6 Any clue? G. __ Users mailing list Users@ovirt.org lists.ovirt.org lists.ovirt.org ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] How to import OVA file into oVirt
I am trying to import OVA file into my test oVirt env. I already have the export domain configured but when I go to the "VM Import" tab the "Import" button in inactive. oVirt 4.1.5/4.1.6 Any clue? G. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Odp: Re: ovirt upgrade problem
Dnia 19 września 2017 09:48 Simone Tiraboschinapisał(a):On Mon, Sep 18, 2017 at 12:19 PM,gabriel_skup...@o2.pl < gabriel_skup...@o2.pl > wrote: Hi, While trying to upgrade my ovirt node from 4.1.5 to 4.1.6 I get the below errors. Can you help? . . . 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4. 1.6-0.2.rc2.20170830082757. gite10769f.el7.centos.noarch. rpm 550 M(99%) 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4. 1.6-0.2.rc2.20170830082757. gite10769f.el7.centos.noarch. rpm 551 M(99%) 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4. 1.6-0.2.rc2.20170830082757. gite10769f.el7.centos.noarch. rpm 551 M(99%) 2017-09-18 09:25:31 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum Download/Verify: ovirt-node-ng-image-update-4. 1.6-0.2.rc2.20170830082757. gite10769f.el7.centos.noarch 2017-09-18 09:25:35 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4. 1.6-0.2.rc2.20170830082757. gite10769f.el7.centos.noarch. rpm 551 M(100%) 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum Status: Check Package Signatures 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum Status: Running Test Transaction Running Transaction Check 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum Status: Running Transaction 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum obsoleting: 1/3: ovirt-node-ng-image-update-4. 1.6-0.2.rc2.20170830082757. gite10769f.el7.centos.noarch 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Script sink: warning: %post(ovirt-node-ng-image- update-4.1.6-0.2.rc2. 20170830082757.gite10769f.el7. centos.noarch) scriptlet failed, exit status 1 The upgrade issue seams here but from this log is not really clear. Could you please check /var/log/messages, yum logs and /tmp/imgbased.log ? By the way ovirt-node-ng-image-update-4.1 is just a pre-release package which shouldn't be there and the stable one for 4.1.6 is still waiting for qemu-kvm-ev 2.9.So, why did the notification appear saying that the new update is available to install? My initial Node version was 4.1.2017082211.iso After a few tries and reboots it finally worked. No idea why ;/ 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update. noarch 0:4.1.6-0.2.rc2. 20170830082757.gite10769f.el7. centos - u 2017-09-18 09:32:11 ERROR otopi.plugins.otopi.packagers. yumpackager yumpackager.error:85 Yum Non-fatal POSTIN scriptlet failure in rpm package ovirt-node-ng-image-update-4. 1.6-0.2.rc2.20170830082757. gite10769f.el7.centos.noarch 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4. 1.6-0.2.rc2.20170830082757. gite10769f.el7.centos.noarch 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4. 1.6-0.2.rc2.20170830082757. gite10769f.el7.centos.noarch 2017-09-18 09:32:11 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum erase: 2/3: ovirt-node-ng-image-update- placeholder 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update- placeholder-4.1.5-1.el7. centos.noarch 2017-09-18 09:32:11 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum updated: 3/3: ovirt-node-ng-image-update 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4. 1.5-1.el7.centos.noarch 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum Verify: 1/3: ovirt-node-ng-image-update. noarch 0:4.1.6-0.2.rc2. 20170830082757.gite10769f.el7. centos - u 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum Verify: 2/3: ovirt-node-ng-image-update- placeholder.noarch 0:4.1.5-1.el7.centos - od 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers. yumpackager yumpackager.info:80 yumpackager.info:80 Yum Verify: 3/3: ovirt-node-ng-image-update. noarch 0:4.1.5-1.el7.centos - ud 2017-09-18 09:32:12 DEBUG otopi.plugins
[ovirt-users] ovirt-node-ng-installer vs. ovirt-node-ng-installer-ovirt
I will appreciate if somebody explains me the difference between ovirt-node-ng-installer and ovirt-node-ng-installer-ovirt IOS files? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] ovirt upgrade problem
Hi, While trying to upgrade my ovirt node from 4.1.5 to 4.1.6 I get the below errors. Can you help? . . . 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.1 550 M(99%) 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.1 551 M(99%) 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.1 551 M(99%) 2017-09-18 09:25:31 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Download/Verify: ovirt-node-ng-image-update-4.1 2017-09-18 09:25:35 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.1 551 M(100%) 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Status: Check Package Signatures 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Status: Running Test Transaction Running Transaction Check 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Status: Running Transaction 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum obsoleting: 1/3: ovirt-node-ng-image-update-4.1 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Script sink: warning: %post(ovirt-node-ng-image-upda scriptlet failed, exit status 1 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update.noa 0:4.1.6-0.2.rc2.20170830082757 - u 2017-09-18 09:32:11 ERROR otopi.plugins.otopi.packagers. yumpackager.error:85 Yum Non-fatal POSTIN scriptlet failure in rpm package ovirt-node-ng-image-update-4.1 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4.1 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4.1 2017-09-18 09:32:11 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum erase: 2/3: ovirt-node-ng-image-update-pla 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-pla 2017-09-18 09:32:11 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum updated: 3/3: ovirt-node-ng-image-update 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4.1 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Verify: 1/3: ovirt-node-ng-image-update.noa 0:4.1.6-0.2.rc2.20170830082757 - u 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Verify: 2/3: ovirt-node-ng-image-update-pla 0:4.1.5-1.el7.centos - od 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Verify: 3/3: ovirt-node-ng-image-update.noa 0:4.1.5-1.el7.centos - ud 2017-09-18 09:32:12 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Transaction processed 2017-09-18 09:32:12 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/tmp/ovirt-kRPMlHbiO5/pythonl line 132, in _executeMethod method['method']() File "/tmp/ovirt-kRPMlHbiO5/otopi-p line 261, in _packages self._miniyum.processTransacti File "/tmp/ovirt-kRPMlHbiO5/pythonl line 1049, in processTransaction _('One or more elements within Yum transaction failed') RuntimeError: One or more elements within Yum transaction failed 2017-09-18 09:32:12 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Package installation': One or more elements within Yum transaction failed 2017-09-18 09:32:12 DEBUG otopi.transaction transaction.abort:119 aborting 'Yum Transaction' 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Performing yum transaction rollback 2017-09-18 09:32:12 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_ (0%) 2017-09-18 09:32:12 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_ 300 k(84%) 2017-09-18 09:32:13 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_ 355 k(100%) 2017-09-18 09:32:13 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_ (0%) 2017-09-18 09:32:13 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_ 50 k(100%) 2017-09-18 09:32:14 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db (0%) 2017-09-18 09:32:14 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 41 k(4%) 2