- Users - oVirt List Archives

4.2.8 and yum update
by carl langlois 06 Aug '20

06 Aug '20

Hi all, I am in the process of upgrading our cluster to 4.3. But first i need to update everything to 4.2.8 and update the os to the latest 7.x. I was able to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But when i tried to update the host yum update got broken gluster packages. The current host that i'm trying to update is on 7.5. If i look at the release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve this. Any suggestions?. Carl

2 6

[ANN] oVirt 4.4.2 Second Release Candidate is now available for testing
by Lev Veyde 06 Aug '20

06 Aug '20

oVirt 4.4.2 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.2 Second Release Candidate for testing, as of August 6th, 2020. This update is the second in a series of stabilization updates to the 4.4 series. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8.2 minimal from: https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8.2 from https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to the engine and let it be deployed. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.2 release highlights: http://www.ovirt.org/release/4.4.2/ * 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] http://www.ovirt.org/release/4.4.2/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior 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

Re: VDSM can't see StoragePool
by Nardus Geldenhuys 06 Aug '20

06 Aug '20

Hi Hope you are well. Did you find a solution for this? Think we have the same type of issue. Regards Nar

1 0

useful workaround for catch-22 situation with nic drivers and Windows
by i iordanov 06 Aug '20

06 Aug '20

Hello, I just wanted to post a nice workaround I came up with in case it helps anybody. The reason I needed it is that in oVirt 4.4, it appears I am unable to change the nic1 type when creating VMs (maybe that's a bug?) and I necessarily end up with the default nic1 type which needs a virtio driver in Windows which is obviously not present on a clean install. Also, since there is no networking, it can't be downloaded. I did think of mounting a USB stick via remote-viewer, but something is wonky there too - the USB device selection menu item is grayed out, and no, it's not permissions. So what i did was to create an .iso file with spice-guest-tools-latest.exe in it and copy the resulting iso file to the ISO domain. Then, I was easily able to attach the ISO to the Windows machine in question and install spice-guest-tools, which made the network adapter work. Quick snippet of how I created the .iso: $ find test test test/spice-guest-tools-latest.exe $ mkisofs -o spice-tools.iso test I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 116 Path table size(bytes): 10 Max brk space used 0 5124 extents written (10 MB) Hope it helps somebody :). Cheers! iordan -- The conscious mind has only one thread of execution.

2 1

Resize partition cause oVirt installation failed
by hkexdong＠yahoo.com.hk 06 Aug '20

06 Aug '20

I've 2 x 512GB SSD. Purely for oVirt 4.4.1 (CentOS 8.2) installation. Using auto partitioning will assign 800+ GB to root partition. I think that's too much so manually reduce it to 80 GB. As there are 2 disks. I want to form RAID too. So, I manually change all the partitions from "LVM thin provisioning" to "RAID" (with RAID 1). Eventually, cause the installation failed with a message "There was an error running the kickstart script at line ....." If I don't make any change to the partitions. The installation success. Is this a known issue? oVirt not allow resize partition and using Linux software RAID?

4 5

General Design question for oVirt set up between locations
by Holger Petrick 05 Aug '20

05 Aug '20

Hello, I'm looking to deploy oVirt for a company which has locations in different countries. As I know and also set up in my test environment, the oVirt Engine is the central place to manage different Data Center in a central place. But how to manage a location when the network connection between a Data Center and oVirt Engine is down? Is it possible to set up on each location a hosted engine and connect also the "local" engine / hosts to a "Central" Engine? What is the recommendation to deploy oVirt on multiple location? Thank you. Holger

2 2

Semi off-topic: invalid SPF record for ovirt.org
by Chris Adams 05 Aug '20

05 Aug '20

Not sure where to send this (so sending to the list); the ovirt.org SPF record is invalid: $ dig ovirt.org txt +short "v=spf1 a:mail.ovirt.org a:gerrit.ovirt.org 66.187.233.88 ~all" The bare IP address needs to be "ip4:66.187.233.88" instead. -- Chris Adams <cma(a)cmadams.net>

2 1

Subject: [ANN] Updated oVirt release 4.4.1.5
by Lev Veyde 05 Aug '20

05 Aug '20

The oVirt Team has just released a new version of oVirt Node package that fixes oVirt Hyperconverged deployment related issue: Bug 1862588 <https://bugzilla.redhat.com/show_bug.cgi?id=1862588> - Update to gluster-7.7 with ovirt-ng node 4.4.1 Updated ovirt-node-ng-installer had been built and a new torrent for this ISO is now available at https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.1… Relevant changes compared to previous version: - Gluster 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/ - Ansible 2.9.11: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Boot Hole vulnerability in grub2 (CVE-2020-1073) fix: https://blog.centos.org/2020/08/centos-community-newsletter-august-2020-200… -- Lev Veyde Senior 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

Unable to start vms in a specific host
by miguel.garcia＠toshibagcs.com 04 Aug '20

04 Aug '20

I had added a couple new hosts in my cluster (hyp16,hyp17) both followed the same procedure but at the moment to start vms all of them goes to hyp16, if I tried to migrate a vm to hyp 17 the migration task fails. Here is the log trying to do migration: 2020-07-22 17:19:12,352-04 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] Running command: MigrateVmToServerCommand internal: false. Entities affected : ID: 24939bc1-5359-4f9d-b742-b32143c02eb1 Type: VMAction group MIGRATE_VM with role type USER 2020-07-22 17:19:12,421-04 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='15466e1a-1f44-472c-94fc-84b132ff1c7d', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1', srcHost='172.16.99.12', dstVdsId='3663f46b-61db-4b4c-a6c0-03fedc90edf0', dstHost='172.16.99.19:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='625', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=ab ort, params=[]}}]]', dstQemu='172.16.99.19'}), log id: 4f624ae2 2020-07-22 17:19:12,423-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] START, MigrateBrokerVDSCommand(HostName = hyp10.infra, MigrateVDSCommandParameters:{hostId='15466e1a-1f44-472c-94fc-84b132ff1c7d', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1', srcHost='172.16.99.12', dstVdsId='3663f46b-61db-4b4c-a6c0-03fedc90edf0', dstHost='172.16.99.19:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='625', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntim e, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='172.16.99.19'}), log id: 7ead484c 2020-07-22 17:19:12,587-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] FINISH, MigrateBrokerVDSCommand, return: , log id: 7ead484c 2020-07-22 17:19:12,589-04 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 4f624ae2 2020-07-22 17:19:12,597-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: Test, Source: hyp10.infra, Destination: hyp17.infra, User: Miguel.Garcia@). 2020-07-22 17:19:14,050-04 INFO [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default task-2378) [] User antonio.acosta@ successfully logged out 2020-07-22 17:19:14,069-04 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-2380) [27d07a90] Running command: TerminateSessionsForTokenCommand internal: true. 2020-07-22 17:19:14,405-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] VM '24939bc1-5359-4f9d-b742-b32143c02eb1' was reported as Down on VDS '3663f46b-61db-4b4c-a6c0-03fedc90edf0'(hyp17.infra) 2020-07-22 17:19:14,406-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-12) [] START, DestroyVDSCommand(HostName = hyp17.infra, DestroyVmVDSCommandParameters:{hostId='3663f46b-61db-4b4c-a6c0-03fedc90edf0', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 7d54e8da 2020-07-22 17:19:14,823-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-12) [] Failed to destroy VM '24939bc1-5359-4f9d-b742-b32143c02eb1' because VM does not exist, ignoring 2020-07-22 17:19:14,823-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-12) [] FINISH, DestroyVDSCommand, return: , log id: 7d54e8da 2020-07-22 17:19:14,824-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] VM '24939bc1-5359-4f9d-b742-b32143c02eb1'(Test) was unexpectedly detected as 'Down' on VDS '3663f46b-61db-4b4c-a6c0-03fedc90edf0'(hyp17.infra) (expected on '15466e1a-1f44-472c-94fc-84b132ff1c7d') 2020-07-22 17:19:14,824-04 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] Migration of VM 'Test' to host 'hyp17.infra' failed: VM destroyed during the startup. 2020-07-22 17:19:14,824-04 WARN [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-3) [] skipping VM '24939bc1-5359-4f9d-b742-b32143c02eb1' from this monitoring cycle - the VM data has changed since fetching the data 2020-07-22 17:19:17,224-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [] VM '24939bc1-5359-4f9d-b742-b32143c02eb1'(Test) moved from 'MigratingFrom' --> 'Up' 2020-07-22 17:19:17,224-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [] Adding VM '24939bc1-5359-4f9d-b742-b32143c02eb1'(Test) to re-run list 2020-07-22 17:19:17,229-04 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [] Rerun VM '24939bc1-5359-4f9d-b742-b32143c02eb1'. Called from VDS 'hyp10.infra' 2020-07-22 17:19:17,310-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-12994) [] START, MigrateStatusVDSCommand(HostName = hyp10.infra, MigrateStatusVDSCommandParameters:{hostId='15466e1a-1f44-472c-94fc-84b132ff1c7d', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1'}), log id: 74cf526d 2020-07-22 17:19:17,533-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-12994) [] FINISH, MigrateStatusVDSCommand, return: , log id: 74cf526d 2020-07-22 17:19:17,587-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-12994) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed (VM: Test, Source: hyp10.infra, Destination: hyp17.infra). 2020-07-22 17:19:17,591-04 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (EE-ManagedThreadFactory-engine-Thread-12994) [] Lock freed to object 'EngineLock:{exclusiveLocks='[24939bc1-5359-4f9d-b742-b32143c02eb1=VM]', sharedLocks=''}'

2 2

4.4rc issue with attaching logical network to ib0
by Edward Berger 04 Aug '20

04 Aug '20

I'm trying to add a logical network to an omnipath (which appears as an infinband ib0 under centos kernel driver) and the attempt errors out, under 4.4RC. This used to work under 4.3 on the same hardware. 'Unexpected failure of libnm when running the mainloop: run execution'}, code = -32603 I want to use ib0 for network file systems and VM migrations.

2 3