- Users - oVirt List Archives

ovirt 4.1, hosted engine and hyperconvergence
by Gabriel Stein 27 Nov '17

27 Nov '17

Hi! I'm having problems to add new hosts on ovirt web interface and deploying the hosted engine. Everything works until yum try to install the needed packages. Error: Failed to install Host a.b.c. Yum ['qemu-kvm-tools-ev conflicts with 10:qemu-kvm-tools-1.5.3-141.el7_4.2.x86_64', 'qemu-kvm-tools conflicts with 10:qemu-kvm-tools-ev-2.9.0-16.el7_4.8.1.x86_64']. I already tried: - delete all repos and leave just ovirt and centos-base(doesn't works) - yum update(no updates) Some Data: CentOS Linux release 7.4.1708 (Core) oVirt Engine Version: 4.1.7.6-1.el7.centos Any Hints? Thanks! Best Regards, Gabriel Gabriel Stein ------------------------------ Gabriel Ferraz Stein Tel.: +49 (0) 170 2881531

2 1

Re: [ovirt-users] ovirt 4.2 - performance vm
by Sharon Gratch 26 Nov '17

26 Nov '17

+ ovirt-users On Thu, Nov 23, 2017 at 2:31 PM, Mark Hunt <Mark.Hunt(a)arm.com> wrote: > Sharon, > > > All working ok now , thank you. > Great! Thanks for the update. > When is the prod release for rhv 4.2 due to come out do you know ? > RHV 4.2 public beta which is also oVirt 4.2 GA is planned to be released soon. I'm not sure about dates for the prod release so please refer to RHV support for that. > Also I see migration for perf vm's won't be until version 4.3 , is there a > rough timeline on that ? > Still not I think..but again please refer to RHV support for that. Regards, Sharon > > Regards > > > Mark H. > > > > > > ------------------------------ > *From:* Sharon Gratch <sgratch(a)redhat.com> > *Sent:* 15 November 2017 15:04 > *To:* Mark Hunt > *Subject:* Re: ovirt 4.2 - performance vm > > Hi Mark, > > Thanks for the data you sent. > > There was a bug avoiding High Performance VMs with NUMA node pining from > start running (due to Null pointer exception, which is exactly what you > encountered). > This bug was already fixed in latest oVirt engine master versions. > > Can you please sync your engine to latest master version and re-check if > problem is not reproduced anymore? > > > > And regardless to that bug, just a small recommendation regarding the CPU > pinning settings for your high performance VM 'perf' running on host > euhpc-ovirt3.euhpc.arm.com: > For high performance results I recommend you to pin all 8 vCPUs and not > just the first one. > i.e. CPU pinning topology field should be set to something like: > 0#0_1#1_2#2_3#3_4#4_5#5_6#6_7#7 > > And then the NUMA pinning should be set accordingly, i.e. both vNUMAs 0, 1 > should be pinned to host NUMA 0 instead of 0->1 and 1->0 (since CPUs 0-7 > are part of NUMA 0). > > Regards, > Sharon > > > > > On Tue, Nov 14, 2017 at 11:26 AM, Mark Hunt <Mark.Hunt(a)arm.com> wrote: > > Hi Sharon, > > > > Output from lscpu attached > > > Regards > > > Mark H. > > > > > > > > > > ------------------------------ > *From:* Sharon Gratch <sgratch(a)redhat.com> > *Sent:* 13 November 2017 18:10 > *To:* Mark Hunt > *Subject:* Re: ovirt 4.2 - performance vm > > Hi, > > Sorry for the late response. > > It seems that NUMA pinning failed when running VM 'perf' on host: > euhpc-ovirt3.euhpc.arm.com. <http://euhpc-ovirt3.euhpc.arm.com> > Because whenever you cancel the NUMA pinning, the VM runs without any > error on this host. > But when you set the NUMA pinning, the VM failed to run on the host, then > the scheduler tries to rerun the VM on other host in the cluster but there > is no other host and that's why you get the error of "no available hosts". > > So for having a full picture of the problem, can you please send me the > NUMA settings of this host? > For that you just need to login to this host euhpc-ovirt3.euhpc.arm.com and > run from shell: > >> lscpu > > Can you please send me the result of this lscpu command? > > > Thanks, > Sharon > > > On Mon, Oct 30, 2017 at 12:50 PM, Mark Hunt <Mark.Hunt(a)arm.com> wrote: > > Hi Sharon, > > > Yes I did (numa + hp) , please find attached engine.log from the the > ovirt manager vm. One thing I did note was that the first time I pinned the > numa nodes they showed green in the gui , thereafter they were red !? > > > Regards > > > Mark H. > > > > > > ------------------------------ > *From:* Sharon Gratch <sgratch(a)redhat.com> > *Sent:* 24 October 2017 09:07 > *To:* Mark Hunt > *Subject:* Re: ovirt 4.2 - performance vm > > Hi, > > Sorry for the late response. > > Did you set huge-pages and/or NUMA pinning for this high-performance VM? > If so then maybe no host was found with appropriate settings for running > that VM. > Can you please send me the engine log with relevant errors/messages? > > Thanks, > Sharon > > > On Fri, Oct 20, 2017 at 7:39 PM, Mark Hunt <Mark.Hunt(a)arm.com> wrote: > > Hi Sharon, > > > Is there anything not mentioned on the performance vm page that needs to > be set for this to work ? I have tried starting one and all I get back is > there are no available hosts - when there are !? > > > Regards > > > Mark H. > > > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. >

1 0

Shared vs Local Storage for Datacenters
by Matt . 26 Nov '17

26 Nov '17

Hi Guys, I'm wondering at the moment what the actual difference is between Shared and Local Storage Datacenters. As far as I can see a Local DC supports NFS as well which makes it a more flexible DC in storage if you ask me, so why do both still exist ? Is it possible in a decent way to change a running Shared Storage DC to a Local one and Keep the NFS shares and add some local mounts for specific hosts ? I hope someone can clearify! Cheers, Matt

4 3

Why Node was rebooting?
by Jonathan Baecker 25 Nov '17

25 Nov '17

This is a multi-part message in MIME format. --------------D1D0407AE4CFA3C37FF62CF4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello community, yesterday evening one of our nodes was rebooted, but I have not found out why. The engine only reports this: 24.11.2017 22:01:43 Storage Pool Manager runs on Host onode-1 (Address: onode-1.worknet.lan). 24.11.2017 21:58:50 Failed to verify Host onode-1 power management. 24.11.2017 21:58:50 Status of host onode-1 was set to Up. 24.11.2017 21:58:41 Successfully refreshed the capabilities of host onode-1. 24.11.2017 21:58:37 VDSM onode-1 command GetCapabilitiesVDS failed: Client close 24.11.2017 21:58:37 VDSM onode-1 command HSMGetAllTasksStatusesVDS failed: Not SPM: () 24.11.2017 21:58:22 Host onode-1 is rebooting. 24.11.2017 21:58:22 Kdump flow is not in progress on host onode-1. 24.11.2017 21:57:51 Host onode-1 is non responsive. 24.11.2017 21:57:51 VM playout was set to the Unknown status. 24.11.2017 21:57:51 VM gogs was set to the Unknown status. 24.11.2017 21:57:51 VM Windows2008 was set to the Unknown status. [...] There is no crash report, and no relevant errors in dmesg. Does the engine send a reboot command to the node, when it gets no responds? Is there any other way to found out why the node was rebooting? The node hangs on a usv and all other servers was running well... In the time, when the reboot was happen, I had a bigger video compression job in one of the VMs, so maybe the CPUs got a bit stressed, but they are not over committed. Regards Jonathan --------------D1D0407AE4CFA3C37FF62CF4 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 text="#000000" bgcolor="#FFFFFF"> Hello community, yesterday evening one of our nodes was rebooted, but I have not found out why. The engine only reports this: <blockquote> <blockquote> 24.11.2017 22:01:43 Storage Pool Manager runs on Host onode-1 (Address: onode-1.worknet.lan). 24.11.2017 21:58:50 Failed to verify Host onode-1 power management. 24.11.2017 21:58:50 Status of host onode-1 was set to Up. 24.11.2017 21:58:41 Successfully refreshed the capabilities of host onode-1. 24.11.2017 21:58:37 VDSM onode-1 command GetCapabilitiesVDS failed: Client close 24.11.2017 21:58:37 VDSM onode-1 command HSMGetAllTasksStatusesVDS failed: Not SPM: () 24.11.2017 21:58:22 Host onode-1 is rebooting. 24.11.2017 21:58:22 Kdump flow is not in progress on host onode-1. 24.11.2017 21:57:51 Host onode-1 is non responsive. 24.11.2017 21:57:51 VM playout was set to the Unknown status. 24.11.2017 21:57:51 VM gogs was set to the Unknown status. 24.11.2017 21:57:51 VM Windows2008 was set to the Unknown status. [...] </blockquote> </blockquote> There is no crash report, and no relevant errors in dmesg. Does the engine send a reboot command to the node, when it gets no responds? Is there any other way to found out why the node was rebooting? The node hangs on a usv and all other servers was running well... In the time, when the reboot was happen, I had a bigger video compression job in one of the VMs, so maybe the CPUs got a bit stressed, but they are not over committed. Regards Jonathan </body> </html> --------------D1D0407AE4CFA3C37FF62CF4--

2 2

Cannot import copied Storage Domain
by Matt . 25 Nov '17

25 Nov '17

Hi Guys, I had a host with a local storage domain which was mounted using NFS and I was not able to deactivate and detach it from the Datacenter so I moved the folder like with content like: 728a7458-e1f9-4a67-8226-668cf3cc546e __DIRECT_IO_TEST__ to a seperate folder and destroyed the old storage domain. Now I want to import the storage domain again which does not work, userrights are ok but I get the message: There is no storage domain under the specified path. Check event pane for more details I also tried to create a new storage domain and put all my images in the images folder but also not working and I don't see my disks or Vm's in oVirt. I have doen such thing in the past and mostly it saved me but now I'm not lucky there. What is the best way to move my images back into oVirt or a new Storage domain ? Maybe someone has an idea here. Thanks! Matt

1 1

oVirt Remote Access
by Emerson Jr 24 Nov '17

24 Nov '17

Hi, I'm having a hard time understanding what happened after I configured oVirt network ("bridge" on the CentOS), it changed the routes metric and now I can't access my oVirt portal from another computer on the network (https:// <IP>/UserPortal). It was working before, I have two Lan interfaces on the network of the server, one of them the IP is bridged to the oVirt, the other one is not, I was using the not bridge IP to access it. Thanks.

2 1

Hosts flapping between non-responive and active
by Matt . 24 Nov '17

24 Nov '17

Hi guys, I have a problem with hosts tha are flapping between NON-responsive and Active. The network is performing well, the VM's are running fine when it happens all the time. I also move a host to a Local Storage DC only without any NFS share attached and even there it happens. In the logs, vdsm.log on the hosts and the engine.log on the engine does not show anything wrong what refers to this behaviour. Where can I look for more information ? My hosts are on the latest 4.1 VDSM versions: Engine: oVirt Engine Version: 4.1.7.6-1.el7.centos Cheers, Matt

2 2

Huge Glsuter Issues - oVirt 4.1.7
by Sven Achtelik 24 Nov '17

24 Nov '17

--_000_BFAB40933B3367488CE6299BAF8592D1014E5314F510SOCRATESasl_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I'm experiencing huge issues when working with big VMs on Gluster volumes. = Doing a Snapshot or removing a big Disk lead to the effect that the SPM nod= e is getting non responsive. Fencing is than kicking in and taking the node= down with the hard reset/reboot. My setup has three nodes with 10Gbit/s NICs for the Gluster network. The Br= icks are on Raid-6 with a 1GB cache on the raid controller and the volumes = are setup as follows: Volume Name: data Type: Replicate Volume ID: c734d678-91e3-449c-8a24-d26b73bef965 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 =3D 3 Transport-type: tcp Bricks: Brick1: ovirt-node01-gfs.storage.lan:/gluster/brick2/data Brick2: ovirt-node02-gfs.storage.lan:/gluster/brick2/data Brick3: ovirt-node03-gfs.storage.lan:/gluster/brick2/data Options Reconfigured: features.barrier: disable cluster.granular-entry-heal: enable performance.readdir-ahead: on performance.quick-read: off performance.read-ahead: off performance.io-cache: off performance.stat-prefetch: on cluster.eager-lock: enable network.remote-dio: off cluster.quorum-type: auto cluster.server-quorum-type: server storage.owner-uid: 36 storage.owner-gid: 36 features.shard: on features.shard-block-size: 512MB performance.low-prio-threads: 32 cluster.data-self-heal-algorithm: full cluster.locking-scheme: granular cluster.shd-wait-qlength: 10000 cluster.shd-max-threads: 6 network.ping-timeout: 30 user.cifs: off nfs.disable: on performance.strict-o-direct: on server.event-threads: 4 client.event-threads: 4 It feel like the System looks up during snapshotting or removing of a big d= isk and this delay triggers things to go wrong. Is there anything that is n= ot setup right on my gluster or is this behavior normal with bigger disks (= 50GB+) ? Is there a reliable option for caching with SSDs ? Thank you, Sven --_000_BFAB40933B3367488CE6299BAF8592D1014E5314F510SOCRATESasl_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content= =3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros= oft Word 15 (filtered medium)"><style></style></head><body lang=3DDE link=3D"#0563C1" v= link=3D"#954F72"><div class=3DWordSection1>Hi All, <o:= p></o:p><o:p> </o:p>= I’m experiencing huge issues when working with big= VMs on Gluster volumes. Doing a Snapshot or removing a big Disk lead to th= e effect that the SPM node is getting non responsive. Fencing is than kicki= ng in and taking the node down with the hard reset/reboot. <o:p></o:p></spa= n><o:p> </o:p><= p class=3DMsoNormal>My setup has three nodes with 10Gbit= /s NICs for the Gluster network. The Bricks are on Raid-6 with a 1GB cache = on the raid controller and the volumes are setup as follows:<o:p></o:p></sp= an><o:p> </o:p>= Volume Name: data<o:p></o:p>= Type: Replicate<o:p></o:p></spa= n>Volume ID: c734d678-91e3-449c= -8a24-d26b73bef965<o:p></o:p>Status: Started<o:p></o:p>Snapshot Count: 0<o:p></o:p>Number of Bricks: 1 x 3 =3D 3<o:p></o:p>Transport-type: tcp<o:p></o:p>Bricks:<o:p></o:p>Brick1: ovirt-node01-gfs.storage.lan:/gluster/= brick2/data<o:p></o:p>Br= ick2: ovirt-node02-gfs.storage.lan:/gluster/brick2/data<o:p></o:p></= p>Brick3: ovirt-node03-gfs.storage.= lan:/gluster/brick2/data<o:p></o:p>Options Reconfigured:<o:p></o:p>= features.barrier: disable<o:p></o:p>cluster.granular-entry-heal: enable<o:p></o= :p>performance.readdir-a= head: on<o:p></o:p>perfo= rmance.quick-read: off<o:p></o:p>performance.read-ahead: off<o:p></o:p>performance.io-cache: off<o:p></o:p>performance.stat-prefetch: on<o:p></o:p>= cluster.eager-lock: enab= le<o:p></o:p>network.rem= ote-dio: off<o:p></o:p>c= luster.quorum-type: auto<o:p></o:p>cluster.server-quorum-type: server<o:p></o:p>storage.owner-uid: 36<o:p></o:p>= storage.owner-gid: 36<o:p></o:p></s= pan>features.shard: on<o:p></o:= p>features.shard-block-s= ize: 512MB<o:p></o:p>per= formance.low-prio-threads: 32<o:p></o:p><sp= an lang=3DEN-US>cluster.data-self-heal-algorithm: full<o:p></o:p></p= >cluster.locking-scheme: granular<o= :p></o:p>cluster.shd-wai= t-qlength: 10000<o:p></o:p>cluster.shd-max-threads: 6<o:p></o:p><sp= an lang=3DEN-US>network.ping-timeout: 30<o:p></o:p>user.cifs: off<o:p></o:p>nfs.disable: on<o:p></o:p>performance.strict-o-direct: on<o:p></o:p><= /span>server.event-threads: 4<o= :p></o:p>client.event-th= reads: 4<o:p></o:p><o:p>=  </o:p>It feel like= the System looks up during snapshotting or removing of a big disk and this= delay triggers things to go wrong. Is there anything that is not setup rig= ht on my gluster or is this behavior normal with bigger disks (50GB+) ? Is = there a reliable option for caching with SSDs ?<o:p></o:p><o:p> </o:p>Thank you, <o:p></o:p>Sven <o:p></o:p></div></body></html>= --_000_BFAB40933B3367488CE6299BAF8592D1014E5314F510SOCRATESasl_--

3 3

[ANN] oVirt 4.1.8 Second Release Candidate is now available
by Lev Veyde 23 Nov '17

23 Nov '17

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 4.1.8, as of November 23rd, 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. <http://www.ovirt.org/release/4.1.8/>8 <http://www.ovirt.org/release/4.1.8/>/ <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. <http://www.ovirt.org/release/4.1.8/>8 <http://www.ovirt.org/release/4.1.8/>/ <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-… -- 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>

1 0

oVirt Node ng upgrade failed
by Kilian Ries 23 Nov '17

23 Nov '17

--_000_929ab90080cf4ff889fcaf0133fb78d8kilianriesde_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 yumpacka= ger.info:80 Yum Verify: 1/4: ovirt-node-ng-image-update.noarch 0:4.1.7-1.el= 7.centos - u 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager yumpacka= ger.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 yumpacka= ger.info:80 Yum Verify: 3/4: ovirt-node-ng-image.noarch 0:4.1.1.1-1.el7.cen= tos - od 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager yumpacka= ger.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 yumpack= ager.verbose:76 Yum Transaction processed 2017-11-23 10:19:21 DEBUG otopi.context context._executeMethod:142 method e= xception Traceback (most recent call last): File "/tmp/ovirt-3JI9q14aGS/pythonlib/otopi/context.py", line 132, in _ex= ecuteMethod 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 pr= ocessTransaction _('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 t= o execute stage 'Package installation': One or more elements within Yum tra= nsaction 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 yumpacka= ger.info:80 Yum Performing yum transaction rollback 2017-11-23 10:19:21 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.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 yumpack= ager.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 yumpack= ager.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 yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db (0%) 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.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 yumpack= ager.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 yumpack= ager.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 yumpack= ager.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 yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db (0%) 2017-11-23 10:19:25 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.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 yumpack= ager.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 yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1-centos-gluster38/x86_64/filelist= s_db (0%) 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1-centos-gluster38/x86_64/filelist= s_db 18 k(100%) 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.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 yumpack= ager.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 yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/filelists_db 7.5 M(7= 6%) 2017-11-23 10:19:27 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/filelists_db 9.9 M(1= 00%) 2017-11-23 10:19:29 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.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 yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_64/f= ilelists_db (0%) 2017-11-23 10:19:30 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_64/f= ilelists_db 6.5 k(100%) 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_64/o= ther_db (0%) 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_64/o= ther_db 851 (100%) 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.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 yumpack= ager.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 yumpack= ager.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 yumpack= ager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/filelists_db (0%) 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/other_db (0%) 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.verbose:76 Yum Downloading: virtio-win-stable/filelists_db (0%) 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.verbose:76 Yum Downloading: virtio-win-stable/other_db (0%) 2017-11-23 10:19:33 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpack= ager.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 yumpack= ager.error:85 Yum Transaction close failed: Traceback (most recent call las= t): File "/tmp/ovirt-3JI9q14aGS/pythonlib/otopi/miniyum.py", line 761, in end= Transaction if self._yb.history_undo(transactionCurrent): File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 6086, in hi= story_undo if self.install(pkgtup=3Dpkg.pkgtup): File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4910, in in= stall raise Errors.InstallError, _('No package(s) available to install') InstallError: Kein(e) Paket(e) zum Installieren verf=FCgbar. ### 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=3D128,data=3Dordered) $ 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 upd= ate 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 --_000_929ab90080cf4ff889fcaf0133fb78d8kilianriesde_ 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,Arial,Helvetica,sans-serif;"> 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 yumpa= ckager.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 yumpa= ckager.info:80 Yum Verify: 2/4: ovirt-node-ng-image-update-placeholder.noar= ch 0:4.1.1.1-1.el7.centos - od 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager yumpa= ckager.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 yumpa= ckager.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 yump= ackager.verbose:76 Yum Transaction processed 2017-11-23 10:19:21 DEBUG otopi.context context._executeMethod:142 metho= d 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/yu= mpackager.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')</p= > RuntimeError: One or more elements within Yum transaction failed 2017-11-23 10:19:21 ERROR otopi.context context._executeMethod:151 Faile= d 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 aborti= ng 'Yum Transaction' 2017-11-23 10:19:21 INFO otopi.plugins.otopi.packagers.yumpackager yumpa= ckager.info:80 Yum Performing yum transaction rollback 2017-11-23 10:19:21 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_64/fileli= sts_db (0%) 2017-11-23 10:19:21 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_64/fileli= sts_db 374 k(100%) 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.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 yump= ackager.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 yump= ackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db (0%) 2017-11-23 10:19:22 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.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 yump= ackager.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 yump= ackager.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 yump= ackager.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 yump= ackager.verbose:76 Yum Downloading: ovirt-4.1/7/filelists_db 1.1 M(100%)</p= > 2017-11-23 10:19:25 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: ovirt-4.1/7/other_db (0%) 2017-11-23 10:19:25 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.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 yump= ackager.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 yump= ackager.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 yump= ackager.verbose:76 Yum Downloading: ovirt-4.1-centos-gluster38/x86_64/filel= ists_db (0%) 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: ovirt-4.1-centos-gluster38/x86_64/filel= ists_db 18 k(100%) 2017-11-23 10:19:26 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.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 yump= ackager.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 yump= ackager.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 yump= ackager.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 yump= ackager.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 yump= ackager.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 yump= ackager.verbose:76 Yum Downloading: ovirt-4.1-epel/x86_64/other_db 2.9 M(10= 0%) 2017-11-23 10:19:30 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_6= 4/filelists_db (0%) 2017-11-23 10:19:30 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_6= 4/filelists_db 6.5 k(100%) 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_6= 4/other_db (0%) 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: ovirt-4.1-patternfly1-noarch-epel/x86_6= 4/other_db 851 (100%) 2017-11-23 10:19:31 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.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 yump= ackager.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 yump= ackager.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 yump= ackager.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 yump= ackager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/filelists_db (0= %) 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.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 yump= ackager.verbose:76 Yum Downloading: rnachimu-gdeploy/x86_64/other_db (0%)</= p> 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.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 yump= ackager.verbose:76 Yum Downloading: virtio-win-stable/filelists_db (0%) 2017-11-23 10:19:32 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: virtio-win-stable/filelists_db 3.9 k(10= 0%) 2017-11-23 10:19:33 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: virtio-win-stable/other_db (0%) 2017-11-23 10:19:33 DEBUG otopi.plugins.otopi.packagers.yumpackager yump= ackager.verbose:76 Yum Downloading: virtio-win-stable/other_db 4.3 k(100%)<= /p> 2017-11-23 10:19:33 ERROR otopi.plugins.otopi.packagers.yumpackager yump= ackager.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=3Dpkg.pkgtup):   File "/usr/lib/python2.7/site-packages/yum/__init__.py"= , line 4910, in install     raise Errors.InstallError, _('No package(s) available to i= nstall') InstallError: Kein(e) Paket(e) zum Installieren verf=FCgbar. ### Some more information on my system: ### $ mount ... /dev/mapper/onn-ovirt--node--ng--4.1.1.1--0.20170504.0+1 on / type e= xt4 (rw,relatime,discard,stripe=3D128,data=3Dordered) $ 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?</= p> Thanks Greets Kilian </div> </body> </html> --_000_929ab90080cf4ff889fcaf0133fb78d8kilianriesde_--

1 0