- Users - oVirt List Archives

Hossted Engine Setup Fails - Failed to execute stage 'Misc configuration': [Errno 1] Operation not permitted:
by Jeremy Tourville 03 Dec '17

03 Dec '17

--_000_CY4PR1301MB216687DC6A8BA816D8544850FA3E0CY4PR1301MB2166_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The full on-screen message is: Failed to execute stage 'Misc configuration': [Errno 1] Operation not permi= tted: '/var/run/vdsm/storage/a3964421-dc4a-45d9-ac24-3ce4e5972d1e/50178ece-= 273e-47fe-8083-be10923c0c74' Hosted Engine deployment failed: this system is not reliable, please check = the issue,fix and redeploy I have tried deploying the self hosted engine using both the UI as well as = CLI (even though not recommended) to see if there was any difference. Ther= e was not, both methods fail with the same error message. I was able however, to deploy the engine on a separate host and complete my= setup. This proved to me that there was nothing wrong with my NFS storage= setup AFAIK. It is my goal to have an all in one setup so the self hosted method would b= e my preferred solution. I have attached a log for review: https://pastebin.com/CfZzAm4P <https://pastebin.com/CfZzAm4P> Many thanks in advance for your assistance! <https://pastebin.com/CfZzAm4P> <https://pastebin.com/CfZzAm4P> <https://pastebin.com/CfZzAm4P> [https://pastebin.com/i/facebook.png]<https://pastebin.com/CfZzAm4P> 2017-12-02 14:33:39 DEBUG otopi.context context.dumpEnvironment:760 ENVIRON= MENT - Pastebin.com<https://pastebin.com/CfZzAm4P> pastebin.com --_000_CY4PR1301MB216687DC6A8BA816D8544850FA3E0CY4PR1301MB2166_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style type=3D"text/css" style=3D"display:none;"></style> </head> <body dir=3D"ltr"> <div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font= -family:Calibri,Helvetica,sans-serif;" dir=3D"ltr"> <p style=3D"margin-top:0;margin-bottom:0"></p> <div>The full on-screen message is:<br> </div> <div><br> </div> <div>Failed to execute stage 'Misc configuration': [Errno 1] Operation not = permitted: '/var/run/vdsm/storage/a3964421-dc4a-45d9-ac24-3ce4e5972d1e/5017= 8ece-273e-47fe-8083-be10923c0c74'<br> Hosted Engine deployment failed: this system is not reliable, please check = the issue,fix and redeploy <br> </div> <div><br> </div> <div>I have tried deploying the self hosted engine using both the UI as wel= l as CLI (even though not recommended) to see if there was any difference.&= nbsp; There was not, both methods fail with the same error message.</div> <div><br> </div> <div>I was able however, to deploy the engine on a separate host and comple= te my setup.  This proved to me that there was nothing wrong with my N= FS storage setup AFAIK.<br> </div> <p></p> <p style=3D"margin-top:0;margin-bottom:0"><br> </p> <p style=3D"margin-top:0;margin-bottom:0">It is my goal to have an all in o= ne setup so the self hosted method would be my preferred solution.  I = have attached a log for review:</p> <p style=3D"margin-top:0;margin-bottom:0"><a href=3D"https://pastebin.com/C= fZzAm4P" class=3D"OWAAutoLink" id=3D"LPlnk43233" previewremoved=3D"true" ta= bindex=3D"-1" disabled=3D"true">https://pastebin.com/CfZzAm4P</a></p> <p style=3D"margin-top:0;margin-bottom:0"><a href=3D"https://pastebin.com/C= fZzAm4P" class=3D"OWAAutoLink" id=3D"LPlnk43233" previewremoved=3D"true" ta= bindex=3D"-1" disabled=3D"true"><br> </a></p> <p style=3D"margin-top:0;margin-bottom:0"><a href=3D"https://pastebin.com/C= fZzAm4P" class=3D"OWAAutoLink" id=3D"LPlnk43233" previewremoved=3D"true" ta= bindex=3D"-1" disabled=3D"true">Many thanks in advance for your assistance! <br> </a></p> <p style=3D"margin-top:0;margin-bottom:0"><a href=3D"https://pastebin.com/C= fZzAm4P" class=3D"OWAAutoLink" id=3D"LPlnk43233" previewremoved=3D"true" ta= bindex=3D"-1" disabled=3D"true"><br> </a></p> <p style=3D"margin-top:0;margin-bottom:0"><a href=3D"https://pastebin.com/C= fZzAm4P" class=3D"OWAAutoLink" id=3D"LPlnk43233" previewremoved=3D"true" ta= bindex=3D"-1" disabled=3D"true"><br> </a></p> <div id=3D"LPBorder_GT_15122582569030.36195870517000817" style=3D"margin-bo= ttom: 20px; overflow: auto; width: 100%; text-indent: 0px;"> <table id=3D"LPContainer_15122582568940.6784679520832382" style=3D"width: 9= 0%; background-color: rgb(255, 255, 255); position: relative; overflow: aut= o; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1= px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);= " role=3D"presentation" cellspacing=3D"0"> <tbody> <tr style=3D"border-spacing: 0px;" valign=3D"top"> <td id=3D"ImageCell_15122582568960.3892562072564215" style=3D"width: 250px;= position: relative; display: table-cell; padding-right: 20px;" colspan=3D"= 1"> <div id=3D"LPImageContainer_15122582568960.5164700832438345" style=3D"backg= round-color: rgb(255, 255, 255); height: 250px; position: relative; margin:= auto; display: table; width: 250px;"> <a id=3D"LPImageAnchor_15122582568980.3615641635618033" style=3D"display: t= able-cell; text-align: center;" href=3D"https://pastebin.com/CfZzAm4P" targ= et=3D"_blank" tabindex=3D"-1" disabled=3D"true"><img style=3D"display: inli= ne-block; max-width: 250px; max-height: 250px; height: 250px; width: 250px;= border-width: 0px; vertical-align: bottom;" id=3D"LPThumbnailImageID_15122= 582568980.7836388114170441" width=3D"250" height=3D"250" src=3D"https://pas= tebin.com/i/facebook.png"></a></div> </td> <td id=3D"TextCell_15122582568990.4546592956780994" style=3D"vertical-align= : top; position: relative; padding: 0px; display: table-cell;" colspan=3D"2= "> <div id=3D"LPRemovePreviewContainer_15122582568990.73254787290038"></div> <div id=3D"LPTitle_15122582568990.6337056475782945" style=3D"top: 0px; colo= r: rgb(0, 120, 215); font-weight: 400; font-size: 21px; font-family: "= wf_segoe-ui_light", "Segoe UI Light", "Segoe WP Light&q= uot;, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif= ; line-height: 21px;"> <a id=3D"LPUrlAnchor_15122582569000.7185941393110225" style=3D"text-decorat= ion: none;" href=3D"https://pastebin.com/CfZzAm4P" target=3D"_blank" tabind= ex=3D"-1" disabled=3D"true">2017-12-02 14:33:39 DEBUG otopi.context context= .dumpEnvironment:760 ENVIRONMENT - Pastebin.com</a></div> <div id=3D"LPMetadata_15122582569020.37104493943227146" style=3D"margin: 10= px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: &quo= t;wf_segoe-ui_normal", "Segoe UI", "Segoe WP", Tah= oma, Arial, sans-serif; font-size: 14px; line-height: 14px;"> pastebin.com</div> </td> </tr> </tbody> </table> </div> <br> <p></p> </div> </body> </html> --_000_CY4PR1301MB216687DC6A8BA816D8544850FA3E0CY4PR1301MB2166_--

2 1

Convert local storage domain to shared
by Demeter Tibor 03 Dec '17

03 Dec '17

--=_345563be-5719-4ca3-a875-90e8c94299c9 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Dear Users, We have an old ovirt3.5 install with a local and a shared clusters. Meanwhile we created a new data center, that based on 4.1 and it use only shared infrastructure. I would like to migrate an big VM from the old local datacenter to our new, but I don't have enough downtime. Is it possible to convert the old local storage to shared (by share via NFS) and attach that as new storage domain to the new cluster? I just want to import VM and copy (while running) with live storage migration function. I know, the official way for move vms between ovirt clusters is the export domain, but it has very big disks. What can I do? Thanks Tibor --=_345563be-5719-4ca3-a875-90e8c94299c9 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div id=3D"zimbraEditorContainer" style=3D"font-family: arial, = helvetica, sans-serif; font-size: 12pt; color: #000000" class=3D"403"><div>= <br></div><div>Dear Users,</div><div><br data-mce-bogus=3D"1"></div><div>We= have an old ovirt3.5 install with a local and a shared clusters. Meanwhile= we created a new data center, that based on 4.1 and it use only shared inf= rastructure.</div><div>I would like to migrate an big VM from the old local= datacenter to our new, but I don't have enough downtime. </div><div><= br data-mce-bogus=3D"1"></div><div>Is it possible to convert the old local = storage to shared (by share via NFS) and attach that as new storage domain = to the new cluster?</div><div></div><div>I just want to import VM and copy = (while running) with live storage migration function.</div><div><br data-mc= e-bogus=3D"1"></div><div>I know, the official way for move vms between ovir= t clusters is the export domain, but it has very big disks.</div><div><br d= ata-mce-bogus=3D"1"></div><div>What can I do?</div><div><br data-mce-bogus= =3D"1"></div><div>Thanks </div><div><br data-mce-bogus=3D"1"></div><di= v>Tibor</div><div data-marker=3D"__SIG_PRE__"><p style=3D"font-family: 'Tim= es New Roman'; font-size: medium; margin: 0px;" data-mce-style=3D"font-fami= ly: 'Times New Roman'; font-size: medium; margin: 0px;"><strong><span style= =3D"font-size: medium;" data-mce-style=3D"font-size: medium;"><span style= =3D"color: #2d67b0;" data-mce-style=3D"color: #2d67b0;"></span></span></str= ong></p><p></p></div></div></body></html> --=_345563be-5719-4ca3-a875-90e8c94299c9--

4 5

Efficient networks API for external OVN provider
by Roman Bolshakov 02 Dec '17

02 Dec '17

Hi, We're using for OVN provider for half a year and noticed a few performance issues when networks are created programmatically: 1. Network listing on external provider takes around a second with ~1000 OVN networks on bare oVirt cluster (engine + 2 hosts) with no VMs 2. Network import from external provider takes around 1,6 second on the cluster 3. External network provider API doesn't allow to query specific network by name. 4. System networks don't have external id field. Without it we need to list all external networks to delete one, which is slow due to #3. In the end, we get a few seconds to delete/create an external network end-to-end. We're using oVirt 4.1.7. Which of the issues are going to be fixed in 4.2? Thanks, Roman

2 3

Strange drive performance over 10Gb
by Wesley Stewart 02 Dec '17

02 Dec '17

I was curious if anyone else has seen this or had any suggestions. I have recently began playing around with my two servers (Freenas Box and oVirt box) and their 10Gb Ethernet ports. I can access the Freenas SMB share over the 10Gb port without issue and I have been playing around with the capabilities. After finding out that my Linux Raid (MDADM) mirror is having horrible write performance, I decided to plug in an NVMe drive that I had lying around and check out its performance. *For my first test*,I added the NVMe drive as a passthrough device to a Windows guest and was able to transfer to and from Freenas box without issue. Speeds were typically ~350-400 MB/s but could drop down to 250 MB/s or so, and would top out around 525 MB/s, pretty slick! *For my second test*, I decided to mount the NVMe drive on the CentOS ovirt host and make it a local datastore. I migrated my Windows Guest to it, and decided to test and see what sort of transfer speeds I got and saw some weird results... Writing TOO the NAS worked about the same. Perhaps a little slower but at least had a steady 250-300 MB/s. Writing to the Windows Guest had a very "Fast and then slow, fast and then slow" type of throughput. I took a few screenshots: (Writing TO the NAS was fairly consistent) [image: Inline image 1] https://i.imgur.com/jWNNvfp.png (Writing TO the Windows Guest on NVMe storage) Sometimes these hit the *low 10-20 MB/s* during the transfer. [image: Inline image 2] https://i.imgur.com/aizG6n0.png [image: Inline image 3] https://i.imgur.com/AjRpR0K.png

2 2

Migration from Proxmox
by Gabriel Stein 02 Dec '17

02 Dec '17

Hi again! well, I'm trying to migrate all my VMs from Proxmox to oVirt. Proxmox doesn't have libvirt and I can dump the files using vzdump <vm-id> <directory> and the output is a *.vma file I think from Proxmox. I can't even find the files, Proxmox create Logical Volumes for every VM. I converted that to *.qcow2 using qemu-img convert, the conversion worked(at least no errors) but I can't import it using a script that I found on web* and the export storage domain(oVirt didn't found it). I would like to know if there is a way to do that. I read a lot about and found that one could build a conversion server and use virt-v2v to import. But it will require a RH Enterprise for that, right? I don't have a subscription and I would like to know if is possible without the subscription? And sorry for the offtopic question, if there is a "redhat" which would like to answer me privately, if I buy a subscription for 1 Server and I have NN CentOS Servers, it will be possible to use all benefits since I have a valid subscription(of course, support just for the RH Server)? * https://rwmj.wordpress.com/2015/09/18/importing-kvm- guests-to-ovirt-or-rhev/ Thanks in Advance! All the best Gabriel Gabriel Stein ------------------------------ Gabriel Ferraz Stein Tel.: +49 (0) 170 2881531

2 4

Re: [ovirt-users] Method to easily verify version of host
by Sandro Bonazzola 02 Dec '17

02 Dec '17

Il 01 Dic 2017 10:41, "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com> ha scritto: Hello, currently in web admin gui one can easily verify the exact version of its engine. In my case I see oVirt Engine Version: 4.1.7.6-1.el7.centos Supposing you fully update your hosts with yum update at every upgrade you do, ovirt-release41 package gives you exact release installed on your host. But the same it seems doesn't happen for hypervisors. Eg in my case I see that they are not aligned with my engine level because of the "Update available" icon in side of them in Hosts tab and the related event of type " Check for available updates on host ov300 was completed successfully with message 'found updates for packages ... qemu-img-ev-2.9.0-16.el7_4.8.1 ... vdsm-4.19.37-1.el7.centos ... " One can crosscheck vdsm version for each hypervisor, but it is suboptimal if you have many hosts and it is not immediate to see the potentially different levels of misalignment, in case you have many hosts... Is there anything or do you think it worth's while to open an RFE for it? Gianluca _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

1 0

[ANN] oVirt 4.1.8 Fourth Release Candidate is now available
by Simone Tiraboschi 01 Dec '17

01 Dec '17

The oVirt Project is pleased to announce the availability of the Fourth Release Candidate of oVirt 4.1.8, as of November 30th, 2017 This update is the eighth in a series of stabilization updates to the 4.1 series. Starting from 4.1.5 oVirt supports libgfapi [5]. Using libgfapi provides a real performance boost for ovirt when using GlusterFS . Due to a known issue [6], using this will break live storage migration. This is expected to be fixed soon. If you do not use live storage migration you can give it a try. Use [7] for more details on how to enable it. This release is available now for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.1 See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * oVirt Appliance is already available * oVirt Live is already available[4] * oVirt Node is already available[4] Additional Resources: * Read more about the oVirt 4.1.8 release highlights: http://www.ovirt.org/release/4.1.8/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.8/ [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/ [5] http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/lib… [6] https://bugzilla.redhat.com/show_bug.cgi?id=1306562 [7] http://www.ovirt.org/develop/release-management/features/storage/glusterfs-…

4 4

Re: [ovirt-users] oVirt Node ng upgrade failed
by Yuval Turgeman 01 Dec '17

01 Dec '17

Great, thanks! we already have a patch in POST ready here: https://gerrit.ovirt.org/#/c/84957/ Thanks, Yuval On Dec 1, 2017 15:04, "Kilian Ries" <mail(a)kilian-ries.de> wrote: Bug is opened: https://bugzilla.redhat.com/show_bug.cgi?id=1519784 Ok, i try to fix my host next week. Thanks for your help ;) ------------------------------ *Von:* Yuval Turgeman <yuvalt(a)redhat.com> *Gesendet:* Donnerstag, 30. November 2017 09:22:39 *An:* Kilian Ries *Cc:* users *Betreff:* Re: [ovirt-users] oVirt Node ng upgrade failed Looks like it, yes - we try to add setfiles_t to permissive, because we assume selinux is on, and if it's disabled, semanage fails with the error you mentioned. Can you open a bug on this ? If you would like to fix the system, you will need to clean the unused LVs, remove the relevant boot entries from grub (if they exist) and /boot/ovirt-node-ng-4.1.7-0.20171108.0+1 (if it exists), then reinstall the rpm. On Thu, Nov 30, 2017 at 10:16 AM, Kilian Ries <mail(a)kilian-ries.de> wrote: > Yes, selinux is disabled via /etc/selinux/config; Is that the problem? :/ > ------------------------------ > *Von:* Yuval Turgeman <yuvalt(a)redhat.com> > *Gesendet:* Donnerstag, 30. November 2017 09:13:34 > *An:* Kilian Ries > *Cc:* users > > *Betreff:* Re: [ovirt-users] oVirt Node ng upgrade failed > > Kilian, did you disable selinux by any chance ? (selinux=0 on boot) ? > > On Thu, Nov 30, 2017 at 9:57 AM, Yuval Turgeman <yuvalt(a)redhat.com> wrote: > >> Looks like selinux is broken on your machine for some reason, can you >> share /etc/selinux ? >> >> Thanks, >> Yuval. >> >> On Tue, Nov 28, 2017 at 6:31 PM, Kilian Ries <mail(a)kilian-ries.de> wrote: >> >>> @Yuval Turgeman >>> >>> >>> ### >>> >>> >>> [17:27:10][root@vm5:~]$semanage permissive -a setfiles_t >>> >>> SELinux: Could not downgrade policy file /etc/selinux/targeted/policy/policy.30, >>> searching for an older version. >>> >>> SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.30: >>> No such file or directory >>> >>> /sbin/load_policy: Can't load policy: No such file or directory >>> >>> libsemanage.semanage_reload_policy: load_policy returned error code 2. >>> (No such file or directory). >>> >>> SELinux: Could not downgrade policy file /etc/selinux/targeted/policy/policy.30, >>> searching for an older version. >>> >>> SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.30: >>> No such file or directory >>> >>> /sbin/load_policy: Can't load policy: No such file or directory >>> >>> libsemanage.semanage_reload_policy: load_policy returned error code 2. >>> (No such file or directory). >>> >>> OSError: No such file or directory >>> >>> >>> ### >>> >>> >>> @Ryan Barry >>> >>> >>> Manual yum upgrade finished without any error but imgbased.log still >>> shows me the following: >>> >>> >>> ### >>> >>> >>> 2017-11-28 17:25:28,372 [DEBUG] (MainThread) Returned: >>> >>> 2017-11-28 17:25:28,434 [DEBUG] (MainThread) Creating /home as >>> {'attach': True, 'size': '1G'} >>> >>> 2017-11-28 17:25:28,434 [DEBUG] (MainThread) Calling binary: (['vgs', >>> '--noheadings', '@imgbased:volume', '-o', 'lv_full_name'],) {'stderr': >>> <open file '/dev/null', mode 'w' at 0x7fa2d1ad8ed0>} >>> >>> 2017-11-28 17:25:28,434 [DEBUG] (MainThread) Calling: (['vgs', >>> '--noheadings', '@imgbased:volume', '-o', 'lv_full_name'],) {'close_fds': >>> True, 'stderr': <open file '/dev/null', mode 'w' at 0x7fa2d1ad8ed0>} >>> >>> 2017-11-28 17:25:28,533 [DEBUG] (MainThread) Returned: onn/home >>> >>> onn/tmp >>> >>> onn/var_log >>> >>> onn/var_log_audit >>> >>> 2017-11-28 17:25:28,533 [DEBUG] (MainThread) Calling binary: (['umount', >>> '-l', '/etc'],) {} >>> >>> 2017-11-28 17:25:28,534 [DEBUG] (MainThread) Calling: (['umount', '-l', >>> '/etc'],) {'close_fds': True, 'stderr': -2} >>> >>> 2017-11-28 17:25:28,539 [DEBUG] (MainThread) Returned: >>> >>> 2017-11-28 17:25:28,540 [DEBUG] (MainThread) Calling binary: (['umount', >>> '-l', u'/tmp/mnt.tuHU8'],) {} >>> >>> 2017-11-28 17:25:28,540 [DEBUG] (MainThread) Calling: (['umount', '-l', >>> u'/tmp/mnt.tuHU8'],) {'close_fds': True, 'stderr': -2} >>> >>> 2017-11-28 17:25:28,635 [DEBUG] (MainThread) Returned: >>> >>> 2017-11-28 17:25:28,635 [DEBUG] (MainThread) Calling binary: (['rmdir', >>> u'/tmp/mnt.tuHU8'],) {} >>> >>> 2017-11-28 17:25:28,635 [DEBUG] (MainThread) Calling: (['rmdir', >>> u'/tmp/mnt.tuHU8'],) {'close_fds': True, 'stderr': -2} >>> >>> 2017-11-28 17:25:28,640 [DEBUG] (MainThread) Returned: >>> >>> 2017-11-28 17:25:28,641 [ERROR] (MainThread) Failed to migrate etc >>> >>> Traceback (most recent call last): >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py", >>> line 109, in on_new_layer >>> >>> check_nist_layout(imgbase, new_lv) >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py", >>> line 179, in check_nist_layout >>> >>> v.create(t, paths[t]["size"], paths[t]["attach"]) >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/volume.py", >>> line 48, in create >>> >>> "Path is already a volume: %s" % where >>> >>> AssertionError: Path is already a volume: /home >>> >>> 2017-11-28 17:25:28,642 [DEBUG] (MainThread) Calling binary: (['umount', >>> '-l', u'/tmp/mnt.bEW2k'],) {} >>> >>> 2017-11-28 17:25:28,642 [DEBUG] (MainThread) Calling: (['umount', '-l', >>> u'/tmp/mnt.bEW2k'],) {'close_fds': True, 'stderr': -2} >>> >>> 2017-11-28 17:25:29,061 [DEBUG] (MainThread) Returned: >>> >>> 2017-11-28 17:25:29,061 [DEBUG] (MainThread) Calling binary: (['rmdir', >>> u'/tmp/mnt.bEW2k'],) {} >>> >>> 2017-11-28 17:25:29,061 [DEBUG] (MainThread) Calling: (['rmdir', >>> u'/tmp/mnt.bEW2k'],) {'close_fds': True, 'stderr': -2} >>> >>> 2017-11-28 17:25:29,067 [DEBUG] (MainThread) Returned: >>> >>> 2017-11-28 17:25:29,067 [DEBUG] (MainThread) Calling binary: (['umount', >>> '-l', u'/tmp/mnt.UB5Yg'],) {} >>> >>> 2017-11-28 17:25:29,067 [DEBUG] (MainThread) Calling: (['umount', '-l', >>> u'/tmp/mnt.UB5Yg'],) {'close_fds': True, 'stderr': -2} >>> >>> 2017-11-28 17:25:29,625 [DEBUG] (MainThread) Returned: >>> >>> 2017-11-28 17:25:29,625 [DEBUG] (MainThread) Calling binary: (['rmdir', >>> u'/tmp/mnt.UB5Yg'],) {} >>> >>> 2017-11-28 17:25:29,626 [DEBUG] (MainThread) Calling: (['rmdir', >>> u'/tmp/mnt.UB5Yg'],) {'close_fds': True, 'stderr': -2} >>> >>> 2017-11-28 17:25:29,631 [DEBUG] (MainThread) Returned: >>> >>> Traceback (most recent call last): >>> >>> File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main >>> >>> "__main__", fname, loader, pkg_name) >>> >>> File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code >>> >>> exec code in run_globals >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/__main__.py", >>> line 53, in <module> >>> >>> CliApplication() >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/__init__.py", >>> line 82, in CliApplication >>> >>> app.hooks.emit("post-arg-parse", args) >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/hooks.py", >>> line 120, in emit >>> >>> cb(self.context, *args) >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/plugins/update.py", >>> line 56, in post_argparse >>> >>> base_lv, _ = LiveimgExtractor(app.imgbase).extract(args.FILENAME) >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/plugins/update.py", >>> line 118, in extract >>> >>> "%s" % size, nvr) >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/plugins/update.py", >>> line 99, in add_base_with_tree >>> >>> new_layer_lv = self.imgbase.add_layer(new_base) >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/imgbase.py", >>> line 191, in add_layer >>> >>> self.hooks.emit("new-layer-added", prev_lv, new_lv) >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/hooks.py", >>> line 120, in emit >>> >>> cb(self.context, *args) >>> >>> File "/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py", >>> line 123, in on_new_layer >>> >>> raise ConfigMigrationError() >>> >>> imgbased.plugins.osupdater.ConfigMigrationError >>> >>> >>> ### >>> ------------------------------ >>> *Von:* Yuval Turgeman <yuvalt(a)redhat.com> >>> *Gesendet:* Sonntag, 26. November 2017 17:23:55 >>> *An:* Kilian Ries >>> *Cc:* Ryan Barry; Lev Veyde; users >>> >>> *Betreff:* Re: [ovirt-users] oVirt Node ng upgrade failed >>> >>> Hi, >>> >>> Can you try to run on your 4.1.1 `semanage permissive -a setfiles_t` and >>> share your output ? >>> >>> Thanks, >>> Yuval >>> >>> On Fri, Nov 24, 2017 at 11:01 AM, Kilian Ries <mail(a)kilian-ries.de> >>> wrote: >>> >>>> This is the imgbased.log: >>>> >>>> >>>> https://www.dropbox.com/s/v9dmgz14cpzfcsn/imgbased.log.tar.gz?dl=0 >>>> >>>> Ok, i'll try your steps and come back later ... >>>> >>>> >>>> ------------------------------ >>>> *Von:* Ryan Barry <rbarry(a)redhat.com> >>>> *Gesendet:* Donnerstag, 23. November 2017 23:33:34 >>>> *An:* Kilian Ries; Lev Veyde; users >>>> *Betreff:* Re: [ovirt-users] oVirt Node ng upgrade failed >>>> >>>> Can you grab imgbased.log? >>>> >>>> To retry, "rpm -e ovirt-node-ng-image-update" and remove the new LVs. >>>> "yum install ovirt-node-ng-image-update" from the CLI instead of engine so >>>> we can get full logs would be useful >>>> >>>> On Thu, Nov 23, 2017 at 16:01 Lev Veyde <lveyde(a)redhat.com> wrote: >>>> >>>>> >>>>> ---------- Forwarded message ---------- >>>>> From: Kilian Ries <mail(a)kilian-ries.de> >>>>> Date: Thu, Nov 23, 2017 at 5:16 PM >>>>> Subject: [ovirt-users] oVirt Node ng upgrade failed >>>>> To: "Users(a)ovirt.org" <Users(a)ovirt.org> >>>>> >>>>> >>>>> Hi, >>>>> >>>>> >>>>> just tried to upgrade from >>>>> >>>>> >>>>> ovirt-node-ng-4.1.1.1-0.20170504.0+1 >>>>> >>>>> >>>>> to >>>>> >>>>> >>>>> ovirt-node-ng-4.1.7-0.20171108.0+1 >>>>> >>>>> >>>>> but it failed: >>>>> >>>>> >>>>> ### >>>>> >>>>> >>>>> 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.info:80 Yum Verify: 1/4: ovirt-node-ng-image-update.noarch >>>>> 0:4.1.7-1.el7.centos - u >>>>> >>>>> 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.info:80 Yum Verify: 2/4: ovirt-node-ng-image-update-placeholder.noarch >>>>> 0:4.1.1.1-1.el7.centos - od >>>>> >>>>> 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.info:80 Yum Verify: 3/4: ovirt-node-ng-image.noarch >>>>> 0:4.1.1.1-1.el7.centos - od >>>>> >>>>> 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.info:80 Yum Verify: 4/4: ovirt-node-ng-image-update.noarch >>>>> 0:4.1.1.1-1.el7.centos - ud >>>>> >>>>> 2017-11-23 10:19:21 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Transaction processed >>>>> >>>>> 2017-11-23 10:19:21 DEBUG otopi.context context._executeMethod:142 >>>>> method exception >>>>> >>>>> Traceback (most recent call last): >>>>> >>>>> File "/tmp/ovirt-3JI9q14aGS/pythonlib/otopi/context.py", line 132, >>>>> in _executeMethod >>>>> >>>>> method['method']() >>>>> >>>>> File "/tmp/ovirt-3JI9q14aGS/otopi-plugins/otopi/packagers/yumpackager.py", >>>>> line 261, in _packages >>>>> >>>>> self._miniyum.processTransaction() >>>>> >>>>> File "/tmp/ovirt-3JI9q14aGS/pythonlib/otopi/miniyum.py", line 1049, >>>>> in processTransaction >>>>> >>>>> _('One or more elements within Yum transaction failed') >>>>> >>>>> RuntimeError: One or more elements within Yum transaction failed >>>>> >>>>> 2017-11-23 10:19:21 ERROR otopi.context context._executeMethod:151 >>>>> Failed to execute stage 'Package installation': One or more elements within >>>>> Yum transaction failed >>>>> >>>>> 2017-11-23 10:19:21 DEBUG otopi.transaction transaction.abort:119 >>>>> aborting 'Yum Transaction' >>>>> >>>>> 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.info:80 Yum Performing yum transaction rollback >>>>> >>>>> 2017-11-23 10:19:21 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_64/filelists_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:21 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_64/filelists_db >>>>> 374 k(100%) >>>>> >>>>> 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_64/other_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_64/other_db >>>>> 53 k(100%) >>>>> >>>>> 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db (0%) >>>>> >>>>> 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 55 k(4%) >>>>> >>>>> 2017-11-23 10:19:23 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 201 k(17%) >>>>> >>>>> 2017-11-23 10:19:23 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 648 k(56%) >>>>> >>>>> 2017-11-23 10:19:23 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 1.1 M(99%) >>>>> >>>>> 2017-11-23 10:19:23 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 1.1 M(100%) >>>>> >>>>> 2017-11-23 10:19:25 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db (0%) >>>>> >>>>> 2017-11-23 10:19:25 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db 45 k(14%) >>>>> >>>>> 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db 207 k(66%) >>>>> >>>>> 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db 311 k(100%) >>>>> >>>>> 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-centos-gluster38/x86_64/filelists_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-centos-gluster38/x86_64/filelists_db >>>>> 18 k(100%) >>>>> >>>>> 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-centos-gluster38/x86_64/other_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-centos-gluster38/x86_64/other_db >>>>> 7.6 k(100%) >>>>> >>>>> 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/filelists_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:27 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/filelists_db >>>>> 7.5 M(76%) >>>>> >>>>> 2017-11-23 10:19:27 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/filelists_db >>>>> 9.9 M(100%) >>>>> >>>>> 2017-11-23 10:19:29 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/other_db (0%) >>>>> >>>>> 2017-11-23 10:19:29 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/other_db 2.9 >>>>> M(100%) >>>>> >>>>> 2017-11-23 10:19:30 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_64/filelists_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:30 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_64/filelists_db >>>>> 6.5 k(100%) >>>>> >>>>> 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_64/other_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_64/other_db >>>>> 851 (100%) >>>>> >>>>> 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-centos-ovirt41/7/x86_64/filelists_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-centos-ovirt41/7/x86_64/filelists_db >>>>> 312 k(100%) >>>>> >>>>> 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-centos-ovirt41/7/x86_64/other_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: ovirt-centos-ovirt41/7/x86_64/other_db >>>>> 84 k(100%) >>>>> >>>>> 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/filelists_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/filelists_db >>>>> 4.5 k(100%) >>>>> >>>>> 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/other_db >>>>> (0%) >>>>> >>>>> 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/other_db >>>>> 1.4 k(100%) >>>>> >>>>> 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: virtio-win-stable/filelists_db (0%) >>>>> >>>>> 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: virtio-win-stable/filelists_db 3.9 >>>>> k(100%) >>>>> >>>>> 2017-11-23 10:19:33 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: virtio-win-stable/other_db (0%) >>>>> >>>>> 2017-11-23 10:19:33 DEBUG otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.verbose:76 Yum Downloading: virtio-win-stable/other_db 4.3 >>>>> k(100%) >>>>> >>>>> 2017-11-23 10:19:33 ERROR otopi.plugins.otopi.packagers.yumpackager >>>>> yumpackager.error:85 Yum Transaction close failed: Traceback (most recent >>>>> call last): >>>>> >>>>> File "/tmp/ovirt-3JI9q14aGS/pythonlib/otopi/miniyum.py", line 761, >>>>> in endTransaction >>>>> >>>>> if self._yb.history_undo(transactionCurrent): >>>>> >>>>> File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 6086, >>>>> in history_undo >>>>> >>>>> if self.install(pkgtup=pkg.pkgtup): >>>>> >>>>> File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4910, >>>>> in install >>>>> >>>>> raise Errors.InstallError, _('No package(s) available to install') >>>>> >>>>> InstallError: Kein(e) Paket(e) zum Installieren verfügbar. >>>>> >>>>> >>>>> ### >>>>> >>>>> >>>>> >>>>> Some more information on my system: >>>>> >>>>> >>>>> ### >>>>> >>>>> >>>>> $ mount >>>>> >>>>> ... >>>>> >>>>> /dev/mapper/onn-ovirt--node--ng--4.1.1.1--0.20170504.0+1 on / type >>>>> ext4 (rw,relatime,discard,stripe=128,data=ordered) >>>>> >>>>> >>>>> >>>>> $ imgbase layout >>>>> >>>>> ovirt-node-ng-4.1.1.1-0.20170406.0 >>>>> >>>>> ovirt-node-ng-4.1.1.1-0.20170504.0 >>>>> >>>>> +- ovirt-node-ng-4.1.1.1-0.20170504.0+1 >>>>> >>>>> ovirt-node-ng-4.1.7-0.20171108.0 >>>>> >>>>> +- ovirt-node-ng-4.1.7-0.20171108.0+1 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> $ rpm -q ovirt-node-ng-image >>>>> >>>>> Das Paket ovirt-node-ng-image ist nicht installiert >>>>> >>>>> >>>>> >>>>> $ nodectl check >>>>> >>>>> Status: OK >>>>> >>>>> Bootloader ... OK >>>>> >>>>> Layer boot entries ... OK >>>>> >>>>> Valid boot entries ... OK >>>>> >>>>> Mount points ... OK >>>>> >>>>> Separate /var ... OK >>>>> >>>>> Discard is used ... OK >>>>> >>>>> Basic storage ... OK >>>>> >>>>> Initialized VG ... OK >>>>> >>>>> Initialized Thin Pool ... OK >>>>> >>>>> Initialized LVs ... OK >>>>> >>>>> Thin storage ... OK >>>>> >>>>> Checking available space in thinpool ... OK >>>>> >>>>> Checking thinpool auto-extend ... OK >>>>> >>>>> vdsmd ... OK >>>>> >>>>> >>>>> ### >>>>> >>>>> >>>>> I can restart my Node and VMs are running, but oVirt Engine tells me >>>>> no update is available. It seems 4.1.7 is installed, but Node still boots >>>>> the old 4.1.1 image. >>>>> >>>>> >>>>> Can i force run the upgrade again or is there another way to fix this? >>>>> >>>>> >>>>> Thanks >>>>> >>>>> Greets >>>>> >>>>> Kilian >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Users mailing list >>>>> Users(a)ovirt.org >>>>> http://lists.ovirt.org/mailman/listinfo/users >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Lev Veyde >>>>> >>>>> Software Engineer, RHCE | RHCVA | MCITP >>>>> >>>>> Red Hat Israel >>>>> >>>>> <https://www.redhat.com> >>>>> >>>>> lev(a)redhat.com | lveyde(a)redhat.com >>>>> <https://red.ht/sig> >>>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >>>>> >>>> -- >>>> >>>> RYAN BARRY >>>> >>>> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR >>>> >>>> Red Hat NA <https://www.redhat.com/> >>>> >>>> rbarry(a)redhat.com M: +1-651-815-9306 IM: rbarry >>>> <https://red.ht/sig> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> >

1 0

Re: [ovirt-users] oVirt Node ng upgrade failed
by Ryan Barry 01 Dec '17

01 Dec '17

Can you grab imgbased.log? To retry, "rpm -e ovirt-node-ng-image-update" and remove the new LVs. "yum install ovirt-node-ng-image-update" from the CLI instead of engine so we can get full logs would be useful On Thu, Nov 23, 2017 at 16:01 Lev Veyde <lveyde(a)redhat.com> wrote: > > ---------- Forwarded message ---------- > From: Kilian Ries <mail(a)kilian-ries.de> > Date: Thu, Nov 23, 2017 at 5:16 PM > Subject: [ovirt-users] oVirt Node ng upgrade failed > To: "Users(a)ovirt.org" <Users(a)ovirt.org> > > > Hi, > > > just tried to upgrade from > > > ovirt-node-ng-4.1.1.1-0.20170504.0+1 > > > to > > > ovirt-node-ng-4.1.7-0.20171108.0+1 > > > but it failed: > > > ### > > > 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager > yumpackager.info:80 Yum Verify: 1/4: ovirt-node-ng-image-update.noarch > 0:4.1.7-1.el7.centos - u > > 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager > yumpackager.info:80 Yum Verify: 2/4: > ovirt-node-ng-image-update-placeholder.noarch 0:4.1.1.1-1.el7.centos - od > > 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager > yumpackager.info:80 Yum Verify: 3/4: ovirt-node-ng-image.noarch > 0:4.1.1.1-1.el7.centos - od > > 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager > yumpackager.info:80 Yum Verify: 4/4: ovirt-node-ng-image-update.noarch > 0:4.1.1.1-1.el7.centos - ud > > 2017-11-23 10:19:21 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Transaction processed > > 2017-11-23 10:19:21 DEBUG otopi.context context._executeMethod:142 method > exception > > Traceback (most recent call last): > > File "/tmp/ovirt-3JI9q14aGS/pythonlib/otopi/context.py", line 132, in > _executeMethod > > method['method']() > > File > "/tmp/ovirt-3JI9q14aGS/otopi-plugins/otopi/packagers/yumpackager.py", line > 261, in _packages > > self._miniyum.processTransaction() > > File "/tmp/ovirt-3JI9q14aGS/pythonlib/otopi/miniyum.py", line 1049, in > processTransaction > > _('One or more elements within Yum transaction failed') > > RuntimeError: One or more elements within Yum transaction failed > > 2017-11-23 10:19:21 ERROR otopi.context context._executeMethod:151 Failed > to execute stage 'Package installation': One or more elements within Yum > transaction failed > > 2017-11-23 10:19:21 DEBUG otopi.transaction transaction.abort:119 aborting > 'Yum Transaction' > > 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager > yumpackager.info:80 Yum Performing yum transaction rollback > > 2017-11-23 10:19:21 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > centos-opstools-release/7/x86_64/filelists_db (0%) > > 2017-11-23 10:19:21 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > centos-opstools-release/7/x86_64/filelists_db 374 k(100%) > > 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > centos-opstools-release/7/x86_64/other_db (0%) > > 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > centos-opstools-release/7/x86_64/other_db 53 k(100%) > > 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db (0%) > > 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 55 k(4%) > > 2017-11-23 10:19:23 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 201 k(17%) > > 2017-11-23 10:19:23 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 648 k(56%) > > 2017-11-23 10:19:23 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 1.1 M(99%) > > 2017-11-23 10:19:23 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 1.1 M(100%) > > 2017-11-23 10:19:25 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db (0%) > > 2017-11-23 10:19:25 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db 45 k(14%) > > 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db 207 k(66%) > > 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db 311 k(100%) > > 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-4.1-centos-gluster38/x86_64/filelists_db (0%) > > 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-4.1-centos-gluster38/x86_64/filelists_db 18 k(100%) > > 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-4.1-centos-gluster38/x86_64/other_db (0%) > > 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-4.1-centos-gluster38/x86_64/other_db 7.6 k(100%) > > 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/filelists_db > (0%) > > 2017-11-23 10:19:27 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/filelists_db > 7.5 M(76%) > > 2017-11-23 10:19:27 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/filelists_db > 9.9 M(100%) > > 2017-11-23 10:19:29 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/other_db (0%) > > 2017-11-23 10:19:29 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/other_db 2.9 > M(100%) > > 2017-11-23 10:19:30 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-4.1-patternfly1-noarch-epel/x86_64/filelists_db (0%) > > 2017-11-23 10:19:30 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-4.1-patternfly1-noarch-epel/x86_64/filelists_db 6.5 k(100%) > > 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-4.1-patternfly1-noarch-epel/x86_64/other_db (0%) > > 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-4.1-patternfly1-noarch-epel/x86_64/other_db 851 (100%) > > 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-centos-ovirt41/7/x86_64/filelists_db (0%) > > 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-centos-ovirt41/7/x86_64/filelists_db 312 k(100%) > > 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-centos-ovirt41/7/x86_64/other_db (0%) > > 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > ovirt-centos-ovirt41/7/x86_64/other_db 84 k(100%) > > 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > rnachimu-gdeploy/x86_64/filelists_db (0%) > > 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: > rnachimu-gdeploy/x86_64/filelists_db 4.5 k(100%) > > 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/other_db > (0%) > > 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/other_db > 1.4 k(100%) > > 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: virtio-win-stable/filelists_db (0%) > > 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: virtio-win-stable/filelists_db 3.9 > k(100%) > > 2017-11-23 10:19:33 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: virtio-win-stable/other_db (0%) > > 2017-11-23 10:19:33 DEBUG otopi.plugins.otopi.packagers.yumpackager > yumpackager.verbose:76 Yum Downloading: virtio-win-stable/other_db 4.3 > k(100%) > > 2017-11-23 10:19:33 ERROR otopi.plugins.otopi.packagers.yumpackager > yumpackager.error:85 Yum Transaction close failed: Traceback (most recent > call last): > > File "/tmp/ovirt-3JI9q14aGS/pythonlib/otopi/miniyum.py", line 761, in > endTransaction > > if self._yb.history_undo(transactionCurrent): > > File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 6086, in > history_undo > > if self.install(pkgtup=pkg.pkgtup): > > File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4910, in > install > > raise Errors.InstallError, _('No package(s) available to install') > > InstallError: Kein(e) Paket(e) zum Installieren verfügbar. > > > ### > > > > Some more information on my system: > > > ### > > > $ mount > > ... > > /dev/mapper/onn-ovirt--node--ng--4.1.1.1--0.20170504.0+1 on / type ext4 > (rw,relatime,discard,stripe=128,data=ordered) > > > > $ imgbase layout > > ovirt-node-ng-4.1.1.1-0.20170406.0 > > ovirt-node-ng-4.1.1.1-0.20170504.0 > > +- ovirt-node-ng-4.1.1.1-0.20170504.0+1 > > ovirt-node-ng-4.1.7-0.20171108.0 > > +- ovirt-node-ng-4.1.7-0.20171108.0+1 > > > > > > $ rpm -q ovirt-node-ng-image > > Das Paket ovirt-node-ng-image ist nicht installiert > > > > $ nodectl check > > Status: OK > > Bootloader ... OK > > Layer boot entries ... OK > > Valid boot entries ... OK > > Mount points ... OK > > Separate /var ... OK > > Discard is used ... OK > > Basic storage ... OK > > Initialized VG ... OK > > Initialized Thin Pool ... OK > > Initialized LVs ... OK > > Thin storage ... OK > > Checking available space in thinpool ... OK > > Checking thinpool auto-extend ... OK > > vdsmd ... OK > > > ### > > > I can restart my Node and VMs are running, but oVirt Engine tells me no > update is available. It seems 4.1.7 is installed, but Node still boots the > old 4.1.1 image. > > > Can i force run the upgrade again or is there another way to fix this? > > > Thanks > > Greets > > Kilian > > > > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > > > -- > > Lev Veyde > > Software Engineer, RHCE | RHCVA | MCITP > > Red Hat Israel > > <https://www.redhat.com> > > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > -- RYAN BARRY SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR Red Hat NA <https://www.redhat.com/> rbarry(a)redhat.com M: +1-651-815-9306 <javascript:void(0);> IM: rbarry <https://red.ht/sig>

3 9

Method to easily verify version of host
by Gianluca Cecchi 01 Dec '17

01 Dec '17

Hello, currently in web admin gui one can easily verify the exact version of its engine. In my case I see oVirt Engine Version: 4.1.7.6-1.el7.centos But the same it seems doesn't happen for hypervisors. Eg in my case I see that they are not aligned with my engine level because of the "Update available" icon in side of them in Hosts tab and the related event of type " Check for available updates on host ov300 was completed successfully with message 'found updates for packages ... qemu-img-ev-2.9.0-16.el7_4.8.1 ... vdsm-4.19.37-1.el7.centos ... " One can crosscheck vdsm version for each hypervisor, but it is suboptimal if you have many hosts and it is not immediate to see the potentially different levels of misalignment, in case you have many hosts... Is there anything or do you think it worth's while to open an RFE for it? Gianluca

1 0

ovirt-node-ng-update
by Nathanaël Blanchet 30 Nov '17

30 Nov '17

Hi all, I didn't find any explicit howto about upgrade of ovirt-node, but I may mistake... However, here is what I guess: after installing a fresh ovirt-node-ng iso, the engine check upgrade finds an available update "ovirt-node-ng-image-update" But, the available update is the same as the current one. If I choose installing it succeeds, but after rebooting, ovirt-node-ng-image-update is not still part of installed rpms so that engine tells me an update of ovirt-node is still available. -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 4

Configuring LDAP backend in non interactive mode
by Luca 'remix_tj' Lorenzetto 30 Nov '17

30 Nov '17

Hello, i'm looking for some examples on how to configure LDAP authn and authz in non interactive mode. I'd like to add some authentication sources immediately after hosted-engine deployment. I've seen that ovirt-engine-extension-aaa-ldap-setup has an option config-append. Help refers to an answer file, but i can't find out how to generate it. All the servers i'm deploying should use the same configurations to access to 3 different active directory servers. Anyone has experiences about this? Luca -- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet è la più grande biblioteca del mondo. Ma il problema è che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <lorenzetto.luca(a)gmail.com>

1 0

Migration from Proxmox to oVirt
by Gabriel Stein 30 Nov '17

30 Nov '17

Hi again! well, I'm trying to migrate all my VMs from Proxmox to oVirt. Proxmox doesn't have libvirt and I can dump the files using vzdump <vm-id> <directory> and the output is a *.vma file I think from Proxmox. I can't even find the files, Proxmox create Logical Volumes for every VM. I converted that to *.qcow2 using qemu-img convert, the conversion worked(at least no errors) but I can't import it using a script that I found on web* and the export storage domain(oVirt didn't found it). I would like to know if there is a way to do that. I read a lot about and found that one could build a conversion server and use virt-v2v to import. But it will require a RH Enterprise for that, right? I don't have a subscription and I would like to know if is possible without the subscription? And sorry for the offtopic question, if there is a "redhat" which would like to answer me privately, if I buy a subscription for 1 Server and I have NN CentOS Servers, it will be possible to use all benefits since I have a valid subscription(of course, support just for the RH Server)? * https://rwmj.wordpress.com/2015/09/18/importing-kvm-guests-to-ovirt-or-rhev/ Thanks in Advance! All the best Gabriel Gabriel Stein ------------------------------ Gabriel Ferraz Stein Tel.: +49 (0) 170 2881531

1 0

Re: [ovirt-users] Convert local storage domain to shared
by Karli Sjöberg 29 Nov '17

29 Nov '17

1 0

[ANN] oVirt 4.2.0 Second Beta Release is now available for testing
by Sandro Bonazzola 29 Nov '17

29 Nov '17

The oVirt Project is pleased to announce the availability of the Second Beta Release of oVirt 4.2.0, as of November 15th, 2017 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the second beta release of the 4.2.0 version. This release brings more than 240 enhancements and more than one thousand bug fixes, including more than 430 high or urgent severity fixes, on top of oVirt 4.1 series. What's new in oVirt 4.2.0? - The Administration Portal has been completely redesigned using Patternfly, a widely adopted standard in web application design. It now features a cleaner, more intuitive design, for an improved user experience. - There is an all-new VM Portal for non-admin users. - A new High Performance virtual machine type has been added to the New VM dialog box in the Administration Portal. - Open Virtual Network (OVN) adds support for Open vSwitch software defined networking (SDN). - oVirt now supports Nvidia vGPU. - The ovirt-ansible-roles package helps users with common administration tasks. - Virt-v2v now supports Debian/Ubuntu based VMs. For more information about these and other features, check out the oVirt 4.2.0 blog post <https://ovirt.org/blog/2017/11/introducing-ovirt-4.2.0-beta/>. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.2 (available for x86_64 only) See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available. - An async release of oVirt Node will follow soon. Additional Resources: * Read more about the oVirt 4.2.0 release highlights: http://www.ovirt.org/release/4.2.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.2.0/ [4] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>

2 1

please test UI plugins in 4.2 beta
by Greg Sheremeta 29 Nov '17

29 Nov '17

Hi everyone, [I should have sent this message sooner -- apologies, and thanks to Martin Sivak for the reminder!] If you're trying out oVirt 4.2 Beta, please check that any existing UI plugins [1] you are using 1. still work (they should!), and 2. look good in the new UI. If something doesn't look quite right with a UI plugin [for example, if it doesn't quite match the new theme], please contact Alexander Wels and me and we can assist with getting it updated. [1] https://www.ovirt.org/develop/release-management/features/ux/uiplugins/ Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

1 0

FOSDEM 2018 - CFP is about to close!
by Doron Fediuck 29 Nov '17

29 Nov '17

Hi all, FOSDEM 18's Virt and IaaS CFP ends on Friday! This is your last chance to submit your session, so do not wait any longer. You can find more details in [1]. Thanks, Doron [1] https://www.ovirt.org/blog/2017/10/come-to-fosdem-event/

1 0

strange problems with engine
by alex＠rt14.ru 29 Nov '17

29 Nov '17

2 2

Update gluster HCI from 4.1.3 to 4.1.7
by Gianluca Cecchi 28 Nov '17

28 Nov '17

Hello, I have an environment with 3 hosts and gluster HCI on 4.1.3. I'm following this link to take it to 4.1.7 https://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-en… The hosts and engine were at 7.3 prior of beginning the update. All went ok for the engine that now is on 7.4 (not rebooted yet) Points 4. 5. 6. for the first updated host were substituted by rebooting it I'm at point: 7. Exit the global maintenance mode: in a few minutes the engine VM should migrate to the fresh upgraded host cause it will get an higher score One note: actually exiting from global maintenance doesn't imply that the host previously put into maintenance exiting from it, correct? So in my workflow, before point 7., actually I have selected the host and activated it. Currently the situation is this - engine running on ovirt02 - update happened on ovirt03 Then after exiting from global maintenance I don't see the engine vm migrating to it. And in fact (see below) the score of ovirt02 is the same (3400) as the one of ovirt03, so it seems it is correct that engine remains there...? Which kind of messages should I see inside logs of engine/hosts? [root@ovirt01 ~]# rpm -q vdsm vdsm-4.19.20-1.el7.centos.x86_64 [root@ovirt02 ~]# rpm -q vdsm vdsm-4.19.20-1.el7.centos.x86_64 [root@ovirt02 ~]# [root@ovirt03 ~]# rpm -q vdsm vdsm-4.19.37-1.el7.centos.x86_64 from host ovirt01: [root@ovirt01 ~]# hosted-engine --vm-status --== Host 1 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : ovirt01.localdomain.local Host ID : 1 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3352 stopped : False Local maintenance : False crc32 : 256f2128 local_conf_timestamp : 12251210 Host timestamp : 12251178 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=12251178 (Tue Nov 28 10:11:20 2017) host-id=1 score=3352 vm_conf_refresh_time=12251210 (Tue Nov 28 10:11:52 2017) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False --== Host 2 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : 192.168.150.103 Host ID : 2 Engine status : {"health": "good", "vm": "up", "detail": "up"} Score : 3400 stopped : False Local maintenance : False crc32 : 9b8c8a6c local_conf_timestamp : 12219386 Host timestamp : 12219357 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=12219357 (Tue Nov 28 10:11:23 2017) host-id=2 score=3400 vm_conf_refresh_time=12219386 (Tue Nov 28 10:11:52 2017) conf_on_shared_storage=True maintenance=False state=EngineUp stopped=False --== Host 3 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : ovirt03.localdomain.local Host ID : 3 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3400 stopped : False Local maintenance : False crc32 : 9f6399ef local_conf_timestamp : 2136 Host timestamp : 2136 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=2136 (Tue Nov 28 10:11:56 2017) host-id=3 score=3400 vm_conf_refresh_time=2136 (Tue Nov 28 10:11:56 2017) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False [root@ovirt01 ~]# Can I manually migrate engine vm to ovirt03? On ovirt03: [root@ovirt03 ~]# gluster volume info engine Volume Name: engine Type: Replicate Volume ID: 6e2bd1d7-9c8e-4c54-9d85-f36e1b871771 Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: ovirt01.localdomain.local:/gluster/brick1/engine Brick2: ovirt02.localdomain.local:/gluster/brick1/engine Brick3: ovirt03.localdomain.local:/gluster/brick1/engine (arbiter) Options Reconfigured: performance.strict-o-direct: on nfs.disable: on user.cifs: off network.ping-timeout: 30 cluster.shd-max-threads: 6 cluster.shd-wait-qlength: 10000 cluster.locking-scheme: granular cluster.data-self-heal-algorithm: full performance.low-prio-threads: 32 features.shard-block-size: 512MB features.shard: on storage.owner-gid: 36 storage.owner-uid: 36 cluster.server-quorum-type: server cluster.quorum-type: auto network.remote-dio: off cluster.eager-lock: enable performance.stat-prefetch: off performance.io-cache: off performance.read-ahead: off performance.quick-read: off performance.readdir-ahead: on transport.address-family: inet [root@ovirt03 ~]# [root@ovirt03 ~]# gluster volume heal engine info Brick ovirt01.localdomain.local:/gluster/brick1/engine Status: Connected Number of entries: 0 Brick ovirt02.localdomain.local:/gluster/brick1/engine Status: Connected Number of entries: 0 Brick ovirt03.localdomain.local:/gluster/brick1/engine Status: Connected Number of entries: 0 [root@ovirt03 ~]# Thanks, Gianluca

2 2

"Cannot acquire bridge address" / Failure in "hosted-engine --deploy" on 4.1.8
by Frank Wall 28 Nov '17

28 Nov '17

Hi, when running "hosted-engine --deploy" on a fresh CentOS 7.4 with pre-built network configuration (and ovirtmgmt bridge), the following error occurs: 2017-11-27 19:08:12 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/network/bridge.py", line 295, in _get_hostname_from_bridge_if raise RuntimeError(_('Cannot acquire bridge address')) RuntimeError: Cannot acquire bridge address While checking the source of bridge.py line 295 the root cause is interesting: Running "vdsClient -s $HOSTNAME getVdsCapabilities" works perfectly, all NICs and bridges are returned, but only "networks" is returned as empty list: {}. Clearly looks like a bug. How can I resolve this issue? ovirt-hosted-engine-setup-2.1.4-1.el7.centos.noarch vdsm-4.19.40-1.el7.centos.x86_64 Regards - Frank

2 3

Time management in self hosted engine vm
by Gianluca Cecchi 28 Nov '17

28 Nov '17

Hello, I have a self hosted engine HCI environment that was born in 4.0.5 through the ansible/gdeploy mechanism and then gradually updated to 4.1.7 Now the engine and host are at CentOS 7.4 level. Inside the gdeploy jobs the engine vm was installed through the appliance at the 4.0.5 time. I see in web admin gui that hw clock of engine vm is configured as UTC (so far so good) and the same is inside the OS. And I would like to change it to UTC+1 like the 3 hosts I also see that neither chronyd nor ntpd are installed on engine vm. Can I fix the situation the normal os level way: - timedatectl set-timezone "Europe/Rome" - install and configure chronyd or better not to configure time sync in engine vm? Thanks, Gianluca

2 1

HA on Non Responsive
by Arthur Melo 28 Nov '17

28 Nov '17

Hello, there! Is it possible to reduce time to auto migrate machines when node is non responsive? Atenciosamente, Arthur Melo Linux User #302250

3 5

Hosts been evacuated unnecessarily
by FERNANDO FREDIANI 28 Nov '17

28 Nov '17

This is a multi-part message in MIME format. --------------85B0C37C08377D8D314D9F67 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello folks. Ou oVirt (4.1.7.3-1.el7.centos) which runs in one Datacenter and controls Nodes locally and also remotelly lost communication with the remote Nodes in another Datacenter. To this point nothing wrong as the Nodes can continue working as expected and running their Virtual Machines each without dependency of the oVirt Engine. What happened at some point is that when the communication between Engine and Hosts came back Hosts in the remote Datacenter got confused and initiated a Live Migration of ALL VMs from one of the hosts to another. I had also to restart vdsmd agent on all Hosts in order to get sanity my environment. What adds up even more strangeness to this scenario is that one of the Hosts affected by the need of restarting VDSM doesn't belong to the same Cluster as the others and had to have the vdsmd restarted. I understand the Hosts can survive without the Engine online with reduced possibilities but can communicated between them, but without affecting the VMs or even needing to do what happened in this scenario. Am I wrong on any of the assumptions ? Fernando --------------85B0C37C08377D8D314D9F67 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <font face="arial, helvetica, sans-serif">Hello folks.<br> <br> </font><font face="arial, helvetica, sans-serif"><font face="arial, helvetica, sans-serif">Ou oVirt (</font></font><font face="arial, helvetica, sans-serif"><font face="arial, helvetica, sans-serif"><span class="version-text">4.1.7.3-1.el7.centos)</span> which runs in one Datacenter and controls Nodes locally and also remotelly lost communication with the remote Nodes in another Datacenter.<br> To this point nothing wrong as the Nodes can continue working as expected and running their Virtual Machines each without dependency of the oVirt Engine.<br> <br> What happened at some point is that when the communication between Engine and Hosts came back Hosts in the remote Datacenter got confused and initiated a Live Migration of ALL VMs from one of the hosts to another. I had also to restart vdsmd agent on all Hosts in order to get sanity my environment.<br> <br> What adds up even more strangeness to this scenario is that one of the Hosts affected by the need of restarting VDSM doesn't belong to the same Cluster as the others and had to have the vdsmd restarted.<br> <br> I understand the Hosts can survive without the Engine online with reduced possibilities but can communicated between them, but without affecting the VMs or even needing to do what happened in this scenario.<br> <br> Am I wrong on any of the assumptions ?<br> <br> Fernando</font></font> </body> </html> --------------85B0C37C08377D8D314D9F67--

1 0

OVS DPDK Performance
by FERNANDO FREDIANI 28 Nov '17

28 Nov '17

This is a multi-part message in MIME format. --------------BDE85DB92A8FD76EF257B82B Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello As some may have seen recently OVS DPDK has been introduced to oVirt (https://ovirt.org/blog/2017/09/ovs-dpdk/) This is very interesting feature which can make a huge performance difference in terms of network performance. Just wanted to ask if anyone has tested it in any environment and made any comparison, specially for packet forward (e.g: running Virtual Routers or Virtual Firewalls with virtio) or packet dropping as well. One doubt I have and if someone could clarify is: Should I enable DPDK in the Host any traffic forwarded to any VMs will automatically benefit from this performance gain of DPDK or there additional steps that need to be put in place inside the VM when sharing a physical Network Interface ? Thanks Fernando --------------BDE85DB92A8FD76EF257B82B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <font face="arial, helvetica, sans-serif">Hello<br> <br> As some may have seen recently OVS DPDK has been introduced to oVirt (<a class="moz-txt-link-freetext" href="https://ovirt.org/blog/2017/09/ovs-dpdk/">https://ovirt.org/blog/2017/09/ovs-dpdk/</a>). This is very interesting feature which can make a huge performance difference in terms of network performance.<br> <br> Just wanted to ask if anyone has tested it in any environment and made any comparison, specially for packet forward (e.g: running Virtual Routers or Virtual Firewalls with virtio) or packet dropping as well.<br> <br> One doubt I have and if someone could clarify is: Should I enable DPDK in the Host any traffic forwarded to any VMs will automatically benefit from this performance gain of DPDK or there additional steps that need to be put in place inside the VM when sharing a physical Network Interface ?<br> <br> Thanks<br> Fernando<br> </font> </body> </html> --------------BDE85DB92A8FD76EF257B82B--

2 2

Upgrading from Hosted Engine 3.6 to 4.X
by Cam Wright 28 Nov '17

28 Nov '17

Hi there, We're looking to upgrade our hosted engine setup from 3.6 to 4.0 (or 4.1)... We built the 3.6 setup a couple of years ago with Fedora 22 (we wanted the newer-at-the-time kernel 4.4) on the hosts and engine, but when we move to 4.X we'd like to move to EL7 on the engine (as that seems to be the supported version) and to the oVirt Node ISO installer on the hypervisors. We've got only four hosts in our oVirt datacentre, configured in two clusters. Our current idea is to take a backup of the oVirt database using the backup-restore tool, and to take a 'dd' of the virtual disk too, for good measure. Then upgrade the engine to 4.X and confirm that the 3.6 hosts will run, and then finally piecemeal upgrade the hosts to 4.X using the oVirt Node ISO installer. Looking at this page - https://www.ovirt.org/documentation/self-hosted/chap-Maintenance_and_Upgrad… - it seems the 'hosted-engine --upgrade-appliance' path is the best way to do this... but because our hosts are running Fedora instead of EL, I think that makes this option moot to us. Is what I've suggested a valid upgrade path, or is there a more sane way of going about this? -C Cam Wright - Systems and Technical Resource Administrator CUTTINGEDGE / 90 Victoria St, West End, Brisbane, QLD, 4101 T + 61 7 3013 6200 M 0420 827 007 E cwright(a)cuttingedge.com.au | W www.cuttingedge.com.au /SYD /BNE /TYO -- This email is confidential and solely for the use of the intended recipient. If you have received this email in error please notify the author and delete it immediately. This email is not to be distributed without the author's written consent. Unauthorised forwarding, printing, copying or use is strictly prohibited and may be a breach of copyright. Any views expressed in this email are those of the individual sender unless specifically stated to be the views of Cutting Edge Post Pty Ltd (Cutting Edge). Although this email has been sent in the belief that it is virus-free, it is the responsibility of the recipient to ensure that it is virus free. No responsibility is accepted by Cutting Edge for any loss or damage arising in any way from receipt or use of this email. This email may contain legally privileged information and privilege is not waived if you have received this email in error.

3 4