- Users - oVirt List Archives

Re: Time Drift Issues
by dhanaraj.ramesh＠yahoo.com 07 Sep '21

07 Sep '21

change the host and engine time to local Time zone and ensure NTP client pointed to same NTP server

2 1

Re: Upgrading Node that use Local Storage Domain
by Roman Bednar 07 Sep '21

07 Sep '21

Hello, it's always better to share logs showing the error message, that way we can look at what exactly went wrong. But in general there is a guide [1] on upgrading from 4.3 when using local storage. If that's not the case there's also a chance your local storage domain is not placed correctly [2]. If neither of those two help you resolve the issue please share the logs with us and we'll look further. -Roman [1] https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_hypervisor_pre… [2] https://lists.ovirt.org/archives/list/users@ovirt.org/thread/CPG7H7J7C44TN3… On Tue, Sep 7, 2021 at 6:22 AM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > Hi, > > > > Currently we have a several node (using oVirt Node) that configured using > Local Storage Domain. How do I appropriately update the node ? Using yum > update always failed while installing ovirt image update. (scriptlet > failed). Is there any specific step to do the update for node that using > local storage ? > > Thanks before. > > > > Regards, > > > > Nur Imam Febrianto > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/RPSGOMH3N2PCM… >

1 0

Hostedengine Database broken
by marcel＠deheureu.se 07 Sep '21

07 Sep '21

Hi ovirt list, in our test system is the engine crashed and the database is broken. Of cause it was a test system which has no database backup but there are three importent VMs there. Our Plan is to deploy a new hosted engine and connect it to the old datacenter and glusterfs. if i am remember right, the vms will be stopped but we will not lose them. So if i connect the existing data center and click of one VM he will ask me to import it right? Or did you have an better idea? Br Marcel

2 2

Upgrading Node that use Local Storage Domain
by Nur Imam Febrianto 07 Sep '21

07 Sep '21

Hi, Currently we have a several node (using oVirt Node) that configured using Local Storage Domain. How do I appropriately update the node ? Using yum update always failed while installing ovirt image update. (scriptlet failed). Is there any specific step to do the update for node that using local storage ? Thanks before. Regards, Nur Imam Febrianto Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

1 0

Time Drift Issues
by Nur Imam Febrianto 07 Sep '21

07 Sep '21

Hi All, Recently I got an warning in our cluster about time drift : Host xxxxx has time-drift of 672 seconds while maximum configured value is 300 seconds. What should I do to address this issue ? Should I reconfigure / configure ntp client on all host ? Thanks before. Regards, Nur Imam Febrianto Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

1 0

Change Cluster CPU type
by Andrey Rusakov 06 Sep '21

06 Sep '21

We are using oVirt for several years. And we start with Xeon v2 CPUs. At this moment of time we got all v3 aтв we will chnage them to v4 in a month. So i would like to change Cluster default CPU to Haswell, But got error with custom cpu on HostedEngine. HostedEngine config is locked. Is there a solution to chnage HostedEngine cpu type? P.S. some problem with Cluster compability version (4.5 4.6)

4 7

Correct way to install VDSM hooks
by Shantur Rathore 06 Sep '21

06 Sep '21

Hi all, I am trying to install vdsm hooks (scratchpad) specifically. I can see that there are rpms available in https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/noarch/ but when I try to install using yum it says it cannot find it. Do I have to manually select the hook rpm and install it or am I missing something? Kind regards, Shantur

2 3

Update to 4.4.8 leaves cluster in a circular error-state
by Paul-Erik Törrönen 06 Sep '21

06 Sep '21

Having updated rpm-packages for a DC with a cluster containing 2 hosts (and executed the engine-setup on the engine machine), I now face the following issue: One of the VMs had a couple of snapshots and apparently this interferes with the upgrade of the cluster version, which currently is 4.4. The 4.4 has become incompatible with the chosen CPU architecture (Intel Westmere Family, the hosts are both Dell x10-series with Xeon X56xx CPUs) and requires an upgrade to newer compatibility version, 4.6 presumably, so the DC/Cluster state is "unknown". However I can't do this because the snapshots exists. I get the "Cannot change cluster version since following VMs are previewing snapshots:" listing a VM with snapshots. The snapshots in turn can not be Commit/Undo because: "Cannot revert to Snapshot. Unknown Data Center status.". So how do I break this circular error? The VM itself is not essential, it can be removed if that solves the case. However this can not be completed from the UI because: "Cannot remove VM. Unknown Data Center status.". Poltsi

2 3

Getting issue in finalize section after disk successfully uploaded
by avishek.sarkar＠broadcom.com 04 Sep '21

04 Sep '21

I have used upload-disk.py to upload qcow2 image to data center...however getting below errror ./upload-disk.py --engine-url 'https://xyz.net' --username='xyz(a)abc.net' --password-file=password --sd-name='SEC-ABC' --cafile='/home/jenkins/crt/ca.crt' --disk-format="qcow2" --disk-sparse image-XYZ Checking image... Image format: qcow2 Disk format: cow Disk content type: data Disk provisioned size: 10737418240 Disk initial size: 5526847488 Disk name: image-avishek.qcow2 Connecting... Creating disk... Creating transfer session... Uploading image... [ 100.00% ] 10.00 GiB, 11.34 seconds, 903.09 MiB/s Finalizing transfer session... Traceback (most recent call last): File "./upload-disk.py", line 300, in <module> transfer_service.finalize() File "/usr/lib64/python3.6/site-packages/ovirtsdk4/services.py", line 13971, in finalize return self._internal_action(action, 'finalize', None, headers, query, wait) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error ovirtsdk4.AuthError: Fault reason is "Operation Failed". Fault detail is "[User is not authorized to perform this action.]". HTTP response code is 403.

1 0

NFS storage was locked for 45 minutes after I attempted a clone operation
by David White 03 Sep '21

03 Sep '21

I have an HCI cluster running on Gluster storage. I exposed an NFS share into oVirt as a storage domain so that I could clone all of my VMs (I'm preparing to move physically to a new datacenter). I got 3-4 VMs cloned perfectly fine yesterday. But then this evening, I tried to clone a big VM, and it caused the disk to lock up. The VM went totally unresponsive, and I didn't see a way to cancel the clone. Nagios NRPE (on the client VM) was reporting server load over 65+, but I was never able to establish an SSH connection. Eventually, I tried restarting the ovirt-engine, per https://access.redhat.com/solutions/396753. When that didn't work, I powered down the VM completely. But the disks were still locked. So I then tried to put the storage domain into maintenance mode, but that wound up putting the entire domain into a "locked" state. Finally, eventually, the disks unlocked, and I was able to power the VM back online. From start to finish, my VM was down for about 45 minutes, including the time when NRPE was still sending data to Nagios. What logs should I look at, and how can I troubleshoot what went wrong here, and hopefully avoid this from happening again? Sent with ProtonMail Secure Email.

3 6

oVirt Node 4.4.8.3 Async update
by Sandro Bonazzola 03 Sep '21

03 Sep '21

oVirt Node 4.4.8.3 Async update On September 3rd 2021 the oVirt project released an async update for oVirt Node consuming the following packages: - ovirt-release44 4.4.8.3 - ovirt-node-ng-image-update 4.4.8.3 oVirt Node respin also consumed most recent CentOS Stream and Advanced Virtualization content. It also includes fixes for: - Bug 1996602 <https://bugzilla.redhat.com/show_bug.cgi?id=1996602> - VM remains in paused state when trying to write on a resized disk resides on iscsi - Via qemu-kvm-6.0.0-29.el8s which shipped live. Here’s the full list of changes: --- ovirt-node-ng-image-4.4.8.2.manifest-rpm 2021-09-01 12:59:05.195037688 +0200 +++ ovirt-node-ng-image-4.4.8.3.manifest-rpm 2021-09-03 13:27:52.006368887 +0200 @@ -47 +46,0 @@ -boost-iostreams-1.66.0-10.el8.x86_64 @@ -112 +111 @@ -device-mapper-persistent-data-0.9.0-1.el8.x86_64 +device-mapper-persistent-data-0.9.0-4.el8.x86_64 @@ -355 +354 @@ -libcap-2.26-4.el8.x86_64 +libcap-2.26-5.el8.x86_64 @@ -637 +636 @@ -osinfo-db-20210215-1.el8.noarch +osinfo-db-20210809-1.el8.noarch @@ -648 +647 @@ -ovirt-node-ng-image-update-placeholder-4.4.8.2-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.8.3-1.el8.noarch @@ -656,2 +655,2 @@ -ovirt-release-host-node-4.4.8.2-1.el8.noarch -ovirt-release44-4.4.8.2-1.el8.noarch +ovirt-release-host-node-4.4.8.3-1.el8.noarch +ovirt-release44-4.4.8.3-1.el8.noarch @@ -768 +767 @@ -python3-eventlet-0.25.2-3.el8.noarch +python3-eventlet-0.25.2-3.1.el8.noarch @@ -814 +813 @@ -python3-os-brick-4.0.3-1.el8.noarch +python3-os-brick-4.0.3-2.el8.noarch @@ -890,14 +889,14 @@ -qemu-guest-agent-6.0.0-27.el8s.x86_64 -qemu-img-6.0.0-27.el8s.x86_64 -qemu-kvm-6.0.0-27.el8s.x86_64 -qemu-kvm-block-curl-6.0.0-27.el8s.x86_64 -qemu-kvm-block-gluster-6.0.0-27.el8s.x86_64 -qemu-kvm-block-iscsi-6.0.0-27.el8s.x86_64 -qemu-kvm-block-rbd-6.0.0-27.el8s.x86_64 -qemu-kvm-block-ssh-6.0.0-27.el8s.x86_64 -qemu-kvm-common-6.0.0-27.el8s.x86_64 -qemu-kvm-core-6.0.0-27.el8s.x86_64 -qemu-kvm-docs-6.0.0-27.el8s.x86_64 -qemu-kvm-hw-usbredir-6.0.0-27.el8s.x86_64 -qemu-kvm-ui-opengl-6.0.0-27.el8s.x86_64 -qemu-kvm-ui-spice-6.0.0-27.el8s.x86_64 +qemu-guest-agent-6.0.0-29.el8s.x86_64 +qemu-img-6.0.0-29.el8s.x86_64 +qemu-kvm-6.0.0-29.el8s.x86_64 +qemu-kvm-block-curl-6.0.0-29.el8s.x86_64 +qemu-kvm-block-gluster-6.0.0-29.el8s.x86_64 +qemu-kvm-block-iscsi-6.0.0-29.el8s.x86_64 +qemu-kvm-block-rbd-6.0.0-29.el8s.x86_64 +qemu-kvm-block-ssh-6.0.0-29.el8s.x86_64 +qemu-kvm-common-6.0.0-29.el8s.x86_64 +qemu-kvm-core-6.0.0-29.el8s.x86_64 +qemu-kvm-docs-6.0.0-29.el8s.x86_64 +qemu-kvm-hw-usbredir-6.0.0-29.el8s.x86_64 +qemu-kvm-ui-opengl-6.0.0-29.el8s.x86_64 +qemu-kvm-ui-spice-6.0.0-29.el8s.x86_64 @@ -934,2 +933,2 @@ -selinux-policy-3.14.3-78.el8.noarch -selinux-policy-targeted-3.14.3-78.el8.noarch +selinux-policy-3.14.3-79.el8.noarch +selinux-policy-targeted-3.14.3-79.el8.noarch @@ -1007 +1006 @@ -virt-v2v-1.42.0-14.el8s.x86_64 +virt-v2v-1.42.0-15.el8s.x86_64 -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

posix storage mount path error when creating volumes
by Sketch 03 Sep '21

03 Sep '21

My cluster was originally built on 4.3, and things were working as long as my SPM was on 4.3. I just killed off the last 4.3 host and rebuilt it as 4.4, and upgraded my cluster and DC to compatibility level 4.6. We had cephfs mounted as a posix FS which worked fine, but oddly in 4.3 we would end up with two mounts for the same volume. The configuration had a comma separated list of IPs as that is how ceph was configured for redundancy, and this is the mount that shows up on both 4.3 and 4.4 hosts (/rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/). But the 4.3 hosts would also have a duplicate mount which had the FQDN of one of the servers instead of the comma separated list. In 4.4, there's only a single mount and existing VMs will start just fine, but you can't create new disks or migrate existing disks onto the posix storage volume. My suspicion is this is an issue with the mount parser not liking the comma in the name of the mount from the error that I get on the SPM host when it tries to create a volume (migration would also fail on the volume creation task): 2021-08-31 19:34:07,767-0700 INFO (jsonrpc/6) [vdsm.api] START createVolume(sdUUID='e8ec5645-fc1b-4d64-a145-44aa8ac5ef48', spUUID='2948c860-9bdf-11e8-a6b3-00163e0419f0', imgUUID='7d704b4d-1ebe-462f-b11e-b91039f43637', size='1073741824', volFormat=5, preallocate=1, diskType='DATA', volUUID='be6cb033-4e42-4bf5-a4a3-6ab5bf03edee', desc='{"DiskAlias":"test","DiskDescription":""}', srcImgUUID='00000000-0000-0000-0000-000000000000', srcVolUUID='00000000-0000-0000-0000-000000000000', initialSize=None, addBitmaps=False) from=::ffff:10.1.2.37,43490, flow_id=bb137995-1ffa-429f-b6eb-5b9ca9f8dfd7, task_id=2ddfd1bc-d7e1-4a1e-877a-68e1c2a897ed (api:48) 2021-08-31 19:34:07,767-0700 INFO (jsonrpc/6) [IOProcessClient] (Global) Starting client (__init__:340) 2021-08-31 19:34:07,782-0700 INFO (ioprocess/3193398) [IOProcess] (Global) Starting ioprocess (__init__:465) 2021-08-31 19:34:07,803-0700 INFO (jsonrpc/6) [vdsm.api] FINISH createVolume return=None from=::ffff:10.1.2.37,43490, flow_id=bb137995-1ffa-429f-b6eb-5b9ca9f8dfd7, task_id=2ddfd1bc-d7e1-4a1e-877a-68e1c2a897ed (api:54) 2021-08-31 19:34:07,844-0700 INFO (tasks/5) [storage.ThreadPool.WorkerThread] START task 2ddfd1bc-d7e1-4a1e-877a-68e1c2a897ed (cmd=<bound method Task.commit of <vdsm.storage.task.Task object at 0x7f4894279860>>, args=None) (threadPool:146) 2021-08-31 19:34:07,869-0700 INFO (tasks/5) [storage.StorageDomain] Create placeholder /rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/7d704b4d-1ebe-462f-b11e-b91039f43637 for image's volumes (sd:1718) 2021-08-31 19:34:07,869-0700 ERROR (tasks/5) [storage.TaskManager.Task] (Task='2ddfd1bc-d7e1-4a1e-877a-68e1c2a897ed') Unexpected error (task:877) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 884, in _run return fn(*args, **kargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 350, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/lib/python3.6/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 1945, in createVolume initial_size=initialSize, add_bitmaps=addBitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 1216, in createVolume initial_size=initial_size, add_bitmaps=add_bitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 1174, in create imgPath = dom.create_image(imgUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 1721, in create_image "create_image_rollback", [image_dir]) File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 385, in __init__ self.params = ParamList(argslist) File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 298, in __init__ raise ValueError("ParamsList: sep %s in %s" % (sep, i)) ValueError: ParamsList: sep , in /rhev/data-center/mnt/10.1.88.75,10.1.88.76,10.1.88.77:_vmstore/e8ec5645-fc1b-4d64-a145-44aa8ac5ef48/images/7d704b4d-1ebe-462f-b11e-b91039f43637 2021-08-31 19:34:07,964-0700 INFO (tasks/5) [storage.ThreadPool.WorkerThread] FINISH task 2ddfd1bc-d7e1-4a1e-877a-68e1c2a897ed (threadPool:148) This is a pretty major issue since we can no longer create new VMs. As a workaround, I could change the mount path of the volume to only reference a single IP, but oVirt won't let me edit the mount. I wonder if I could manually edit in the database, then reboot the hosts one by one to make the change take effect without having to shut down hundreds of VMs at once?

3 3

Template for Ubuntu 18.04 Server Issues
by jeremy_tourville＠hotmail.com 02 Sep '21

02 Sep '21

I have built a system as a template on oVirt. Specifically, Ubuntu 18.04 server. I am noticing an issue when creating new vms from that template. I used the check box for "seal template" when creating the template. When I create a new Ubuntu VM I am getting duplicate IP addresses for all the machines created from the template. It seems like the checkbox doesn't fully function as intended. I would need to do further manual steps to clear up this issue. Has anyone else noticed this behavior? Is this expected or have I missed something? Thanks for your input!

6 7

oVirt Monitoring with Grafana: Use Cases Blog
by Aviv Litman 02 Sep '21

02 Sep '21

Hi all, Happy to share my new oVirt blog with you: oVirt Monitoring with Grafana: Use Cases Blog <https://blogs.ovirt.org/2021/09/ovirt-monitoring-with-grafana-use-cases-blo…> . This blog presents some very helpful use cases that can help you identify actionable insights. That can help you free unused resources and balance them. Feedback, comments and suggestions are more than welcome! -- Aviv Litman BI Associate Software Engineer Red Hat <https://www.redhat.com/> alitman(a)redhat.com <https://www.redhat.com/>

1 0

Re: Import OVA problem
by Dominique Deschênes 02 Sep '21

02 Sep '21

Hi Saif, Here the error in engine.log 2021-08-31 10:22:26,536-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Query OVA info. Run query script. 2021-08-31 10:22:29,640-04 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] Error parsing OVF due to Error loading ovf, message The element type "SpecParams" must be terminated by the matching end-tag "</SpecParams>". 2021-08-31 10:22:29,662-04 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] Error parsing OVF due to Error loading ovf, message The element type "SpecParams" must be terminated by the matching end-tag "</SpecParams>". 2021-08-31 10:22:30,694-04 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] Error parsing OVF due to Error loading ovf, message XML document structures must start and end within the same entity. And my ansible log file https://drive.google.com/file/d/1qnd-Ut1tHr5X3jrKcsPsxOz8ObPTuQ7v/view?usp=… Dominique ----- Original Message ----- From: Saif Abu Saleh (sabusale(a)redhat.com) Date: 31/08/21 09:54 To: Dominique D (dominique.deschenes(a)gcgenicom.com) Cc: users(a)ovirt.org Subject: Re: [ovirt-users] Import OVA problem Hi Dominique, Hope you are doing well In order to investigate this, we need to check the log files Can you please try to do import again and provide the following log files after the import: - engine.log, from location: <deployment_location>/var/log/ovirt-engine/engine.log - ansible log file (depending on the time of the import), from location: <deployment_location>/var/log/ovirt-engine/ova Thanks, Saif On Sun, Aug 29, 2021 at 6:08 PM Dominique D <dominique.deschenes(a)gcgenicom.com> wrote: I have tried exporting 4 VMs (2 centos and 2 Windows) to an nfs mount (export OVA) and importing from ova and I can't see all the files. Here are the files in the directory -rw-------+ 1 root root 10739331584 Aug 29 10:27 linux2.ova -rw-------+ 1 root root 1784370176 Aug 28 12:00 linuxtest.ova -rw-------+ 1 root root 64434655232 Aug 28 13:57 vdiw10-2004v1C.ova -rw-------+ 1 vdsm kvm 49040712192 Aug 27 17:21 vdiw10rg06.ova The only file I see in virtual machine on source is linuxtest.ova and linux2.ova. Do you know why ? ovirt 4.4.6 _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3TX6YKUG56OLC…

2 1

Re: Ovirt-4.4.7 Adding host to existing cluster will attempt to run ovirt-hosted-engine-setup
by Paul-Erik Törrönen 01 Sep '21

01 Sep '21

On 2021-08-17 11:12, Dana Elfassy wrote: > The execution of the task itself is fine - we're always installing this > package because of dependencies. > As for its failure- looks like an issue with the repositories. > Please run $ yum repolist > on the host and copy the output Sorry for replying so late, was on a 2-week road-trip. $ yum repolist repo id repo name appstream CentOS Stream 8 - AppStream baseos CentOS Stream 8 - BaseOS elasticsearch-7.x Elasticsearch repository for 7.x packages epel-next Extra Packages for Enterprise Linux 8 - Next - x86_64 extras CentOS Stream 8 - Extras ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-centos-ceph-pacific Ceph packages for x86_64 ovirt-4.4-centos-gluster8 CentOS-8 - Gluster 8 ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-stream-advanced-virtualization Advanced Virtualization CentOS Stream packages for x86_64 ovirt-4.4-centos-stream-nfv-openvswitch CentOS-8 - NFV OpenvSwitch ovirt-4.4-centos-stream-ovirt44 CentOS-8 Stream - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp Copr repo for ovsdbapp owned by mdbarroso ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-openstack-train OpenStack Train Repository ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL powertools CentOS Stream 8 - PowerTools Then there's also this: $ dnf update Last metadata expiration check: 0:28:17 ago on Tue 31 Aug 2021 12:45:32 PM EEST. Error: Problem 1: cannot install the best update candidate for package ovirt-host-dependencies-4.4.7-1.el8.x86_64 - nothing provides python3-os-brick needed by ovirt-host-dependencies-4.4.8-1.el8.x86_64 Problem 2: package ovirt-host-4.4.8-1.el8.x86_64 requires ovirt-host-dependencies = 4.4.8-1.el8, but none of the providers can be installed - cannot install the best update candidate for package ovirt-host-4.4.7-1.el8.x86_64 - nothing provides python3-os-brick needed by ovirt-host-dependencies-4.4.8-1.el8.x86_64 Poltsi

3 3

[ANN] oVirt 4.4.8 Async update #2
by Sandro Bonazzola 01 Sep '21

01 Sep '21

oVirt 4.4.8 Async update #2 On September 1st 2021 the oVirt project released an async update to the following packages: - ovirt-release44 4.4.8.2 - vdsm 4.40.80.6 Fixing the following bugs: - Bug 1999032 <https://bugzilla.redhat.com/show_bug.cgi?id=1999032> - Failed to add rhel host to rhv engine server with error - VDSM host-38 command Get Host Capabilities failed: Internal JSON-RPC error: {'reason': "'libvirt'"} - Bug 1998865 <https://bugzilla.redhat.com/show_bug.cgi?id=1998865> - Host installation fails due to missing bond file - Bug 1996602 <https://bugzilla.redhat.com/show_bug.cgi?id=1996602> - VM remains in paused state when trying to write on a resized disk resides on iscsi oVirt Node respin is waiting for latest Advanced Virtualization build to land on mirrors providing: - hivex-1.3.18-22.el8s - libvirt-7.6.0-2.el8s - libvirt-python-7.6.0-1.el8s - qemu-kvm-6.0.0-27.el8s A separate announcement will be sent when the oVirt Node build will be available. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 1

oVirt Node 4.4.8.2 Async update
by Sandro Bonazzola 01 Sep '21

01 Sep '21

oVirt Node 4.4.8.2 Async update On September 1st 2021 the oVirt project released an async update for oVirt Node consuming the following packages: - ovirt-release44 4.4.8.2 - vdsm 4.40.80.6 oVirt Node respin also consumed most recent CentOS Stream and Advanced Virtualization content. It also includes fixes for: - CVE-2021-31535 <https://access.redhat.com/security/cve/CVE-2021-31535> libX11: missing request length checks - CVE-2021-3564 <https://access.redhat.com/security/cve/CVE-2021-3564> kernel: double free in bluetooth subsystem when the HCI device initialization fails - CVE-2021-3573 <https://access.redhat.com/security/cve/CVE-2021-3573> kernel: use-after-free in function hci_sock_bound_ioctl() - CVE-2021-29155 <https://access.redhat.com/security/cve/CVE-2021-29155> kernel: protection for sequences of pointer arithmetic operations against speculatively out-of-bounds loads can be bypassed to leak content of kernel memory - CVE-2021-31829 <https://access.redhat.com/security/cve/CVE-2021-31829> kernel: protection of stack pointer against speculative pointer arithmetic can be bypassed to leak content of kernel memory - CVE-2021-33200 <https://access.redhat.com/security/cve/CVE-2021-33200> kernel: out-of-bounds reads and writes due to enforcing incorrect limits for pointer arithmetic operations by BPF verifier - CVE-2021-3679 <https://access.redhat.com/security/cve/CVE-2021-3679> kernel: DoS in rb_per_cpu_empty() - CVE-2020-26144 <https://access.redhat.com/security/cve/CVE-2020-26144> kernel: accepting unencrypted A-MSDU frames that start with RFC1042 header - CVE-2020-26145 <https://access.redhat.com/security/cve/CVE-2020-26145> kernel: accepting plaintext broadcast fragments as full frames - CVE-2020-24587 <https://access.redhat.com/security/cve/CVE-2020-24587> kernel: Reassembling fragments encrypted under different keys - CVE-2020-26141 <https://access.redhat.com/security/cve/CVE-2020-26141> kernel: not verifying TKIP MIC of fragmented frames - CVE-2020-24586 <https://access.redhat.com/security/cve/CVE-2020-24586> kernel: Fragmentation cache not cleared on reconnection - CVE-2020-26147 <https://access.redhat.com/security/cve/CVE-2020-26147> kernel: reassembling mixed encrypted/plaintext fragments - CVE-2021-3653 <https://access.redhat.com/security/cve/CVE-2021-3653> kernel: SVM nested virtualization issue in KVM (AVIC support) - CVE-2021-3656 <https://access.redhat.com/security/cve/CVE-2021-3656> kernel: SVM nested virtualization issue in KVM (VMLOAD/VMSAVE) Here’s the full list of changes: --- ovirt-node-ng-image-4.4.8.1.manifest-rpm 2021-08-27 08:11:54.863736688 +0200 +++ ovirt-node-ng-image-4.4.8.2.manifest-rpm 2021-09-01 12:59:05.195037688 +0200 @@ -3,6 +3,6 @@ -NetworkManager-1.32.8-1.el8.x86_64 -NetworkManager-config-server-1.32.8-1.el8.noarch -NetworkManager-libnm-1.32.8-1.el8.x86_64 -NetworkManager-ovs-1.32.8-1.el8.x86_64 -NetworkManager-team-1.32.8-1.el8.x86_64 -NetworkManager-tui-1.32.8-1.el8.x86_64 +NetworkManager-1.32.10-2.el8.x86_64 +NetworkManager-config-server-1.32.10-2.el8.noarch +NetworkManager-libnm-1.32.10-2.el8.x86_64 +NetworkManager-ovs-1.32.10-2.el8.x86_64 +NetworkManager-team-1.32.10-2.el8.x86_64 +NetworkManager-tui-1.32.10-2.el8.x86_64 @@ -24 +24 @@ -ansible-2.9.24-2.el8.noarch +ansible-2.9.25-1.el8.noarch @@ -39,5 +39,5 @@ -bind-export-libs-9.11.26-4.el8_4.x86_64 -bind-libs-9.11.26-4.el8_4.x86_64 -bind-libs-lite-9.11.26-4.el8_4.x86_64 -bind-license-9.11.26-4.el8_4.noarch -bind-utils-9.11.26-4.el8_4.x86_64 +bind-export-libs-9.11.26-6.el8.x86_64 +bind-libs-9.11.26-6.el8.x86_64 +bind-libs-lite-9.11.26-6.el8.x86_64 +bind-license-9.11.26-6.el8.noarch +bind-utils-9.11.26-6.el8.x86_64 @@ -46 +46 @@ -blivet-data-3.4.0-4.el8.noarch +blivet-data-3.4.0-5.el8.noarch @@ -68,2 +68,2 @@ -cockpit-250-1.el8.x86_64 -cockpit-bridge-250-1.el8.x86_64 +cockpit-251-1.el8.x86_64 +cockpit-bridge-251-1.el8.x86_64 @@ -71,3 +71,3 @@ -cockpit-storaged-250-1.el8.noarch -cockpit-system-250-1.el8.noarch -cockpit-ws-250-1.el8.x86_64 +cockpit-storaged-251-1.el8.noarch +cockpit-system-251-1.el8.noarch +cockpit-ws-251-1.el8.x86_64 @@ -94 +94 @@ -curl-7.61.1-18.el8_4.1.x86_64 +curl-7.61.1-21.el8.x86_64 @@ -118,2 +118,2 @@ -dnf-4.7.0-2.el8.noarch -dnf-data-4.7.0-2.el8.noarch +dnf-4.7.0-3.el8.noarch +dnf-data-4.7.0-3.el8.noarch @@ -123,5 +123,5 @@ -dracut-049-188.git20210802.el8.x86_64 -dracut-config-generic-049-188.git20210802.el8.x86_64 -dracut-live-049-188.git20210802.el8.x86_64 -dracut-network-049-188.git20210802.el8.x86_64 -dracut-squash-049-188.git20210802.el8.x86_64 +dracut-049-190.git20210811.el8.x86_64 +dracut-config-generic-049-190.git20210811.el8.x86_64 +dracut-live-049-190.git20210811.el8.x86_64 +dracut-network-049-190.git20210811.el8.x86_64 +dracut-squash-049-190.git20210811.el8.x86_64 @@ -138 +138 @@ -ethtool-5.8-6.el8.x86_64 +ethtool-5.8-7.el8.x86_64 @@ -184 +184 @@ -fontconfig-2.13.1-3.el8.x86_64 +fontconfig-2.13.1-4.el8.x86_64 @@ -188 +188 @@ -fstrm-0.6.0-3.el8.1.x86_64 +fstrm-0.6.1-2.el8.x86_64 @@ -206,3 +206,3 @@ -glibc-2.28-162.el8.x86_64 -glibc-common-2.28-162.el8.x86_64 -glibc-langpack-en-2.28-162.el8.x86_64 +glibc-2.28-164.el8.x86_64 +glibc-common-2.28-164.el8.x86_64 +glibc-langpack-en-2.28-164.el8.x86_64 @@ -240 +240 @@ -grubby-8.40-41.el8.x86_64 +grubby-8.40-42.el8.x86_64 @@ -249 +249 @@ -hivex-1.3.18-21.module_el8.5.0+821+97472045.x86_64 +hivex-1.3.18-22.el8s.x86_64 @@ -251 +251 @@ -hwdata-0.314-8.9.el8.noarch +hwdata-0.314-8.10.el8.noarch @@ -265,2 +265,2 @@ -iproute-5.12.0-2.el8.x86_64 -iproute-tc-5.12.0-2.el8.x86_64 +iproute-5.12.0-3.el8.x86_64 +iproute-tc-5.12.0-3.el8.x86_64 @@ -270,3 +270,3 @@ -iptables-1.8.4-19.el8.x86_64 -iptables-ebtables-1.8.4-19.el8.x86_64 -iptables-libs-1.8.4-19.el8.x86_64 +iptables-1.8.4-20.el8.x86_64 +iptables-ebtables-1.8.4-20.el8.x86_64 +iptables-libs-1.8.4-20.el8.x86_64 @@ -301,6 +301,6 @@ -kernel-4.18.0-331.el8.x86_64 -kernel-core-4.18.0-331.el8.x86_64 -kernel-modules-4.18.0-331.el8.x86_64 -kernel-tools-4.18.0-331.el8.x86_64 -kernel-tools-libs-4.18.0-331.el8.x86_64 -kexec-tools-2.0.20-56.el8.x86_64 +kernel-4.18.0-338.el8.x86_64 +kernel-core-4.18.0-338.el8.x86_64 +kernel-modules-4.18.0-338.el8.x86_64 +kernel-tools-4.18.0-338.el8.x86_64 +kernel-tools-libs-4.18.0-338.el8.x86_64 +kexec-tools-2.0.20-57.el8.x86_64 @@ -313,2 +313,2 @@ -krb5-libs-1.18.2-13.el8.x86_64 -krb5-workstation-1.18.2-13.el8.x86_64 +krb5-libs-1.18.2-14.el8.x86_64 +krb5-workstation-1.18.2-14.el8.x86_64 @@ -318,3 +318,3 @@ -libX11-1.6.8-4.el8.x86_64 -libX11-common-1.6.8-4.el8.noarch -libX11-xcb-1.6.8-4.el8.x86_64 +libX11-1.6.8-5.el8.x86_64 +libX11-common-1.6.8-5.el8.noarch +libX11-xcb-1.6.8-5.el8.x86_64 @@ -353 +353 @@ -libbpf-0.3.0-1.el8.x86_64 +libbpf-0.4.0-1.el8.x86_64 @@ -363 +363 @@ -libcurl-7.61.1-18.el8_4.1.x86_64 +libcurl-7.61.1-21.el8.x86_64 @@ -407 +407 @@ -libkadm5-1.18.2-13.el8.x86_64 +libkadm5-1.18.2-14.el8.x86_64 @@ -418 +418 @@ -libmodulemd-2.12.1-1.el8.x86_64 +libmodulemd-2.13.0-1.el8.x86_64 @@ -465 +465 @@ -libsepol-2.9-2.el8.x86_64 +libsepol-2.9-3.el8.x86_64 @@ -503,24 +503,24 @@ -libvirt-7.5.0-1.el8s.x86_64 -libvirt-client-7.5.0-1.el8s.x86_64 -libvirt-daemon-7.5.0-1.el8s.x86_64 -libvirt-daemon-config-network-7.5.0-1.el8s.x86_64 -libvirt-daemon-config-nwfilter-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-interface-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-network-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-nodedev-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-nwfilter-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-qemu-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-secret-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-core-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-disk-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-gluster-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-direct-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-logical-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-mpath-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-rbd-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-scsi-7.5.0-1.el8s.x86_64 -libvirt-daemon-kvm-7.5.0-1.el8s.x86_64 -libvirt-libs-7.5.0-1.el8s.x86_64 -libvirt-lock-sanlock-7.5.0-1.el8s.x86_64 +libvirt-7.6.0-2.el8s.x86_64 +libvirt-client-7.6.0-2.el8s.x86_64 +libvirt-daemon-7.6.0-2.el8s.x86_64 +libvirt-daemon-config-network-7.6.0-2.el8s.x86_64 +libvirt-daemon-config-nwfilter-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-interface-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-network-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-nodedev-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-nwfilter-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-qemu-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-secret-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-core-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-disk-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-gluster-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-iscsi-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-iscsi-direct-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-logical-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-mpath-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-rbd-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-scsi-7.6.0-2.el8s.x86_64 +libvirt-daemon-kvm-7.6.0-2.el8s.x86_64 +libvirt-libs-7.6.0-2.el8s.x86_64 +libvirt-lock-sanlock-7.6.0-2.el8s.x86_64 @@ -546,2 +546,2 @@ -lldpad-1.0.1-14.git036e314.el8.x86_64 -llvm-libs-12.0.0-1.module_el8.5.0+840+21214faf.x86_64 +lldpad-1.0.1-16.git036e314.el8.x86_64 +llvm-libs-12.0.1-1.module_el8.5.0+892+54d791e1.x86_64 @@ -553 +553 @@ -lsscsi-0.32-2.el8.x86_64 +lsscsi-0.32-3.el8.x86_64 @@ -555 +555 @@ -lua-libs-5.3.4-11.el8.x86_64 +lua-libs-5.3.4-12.el8.x86_64 @@ -603 +603 @@ -nftables-0.9.3-20.el8.x86_64 +nftables-0.9.3-21.el8.x86_64 @@ -605 +605 @@ -nmap-ncat-7.70-5.el8.x86_64 +nmap-ncat-7.70-6.el8.x86_64 @@ -609 +609 @@ -nspr-4.31.0-1.el8_4.x86_64 +nspr-4.32.0-1.el8_4.x86_64 @@ -636 +636 @@ -os-prober-1.74-6.el8.x86_64 +os-prober-1.74-9.el8.x86_64 @@ -648 +648 @@ -ovirt-node-ng-image-update-placeholder-4.4.8.1-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.8.2-1.el8.noarch @@ -656,2 +656,2 @@ -ovirt-release-host-node-4.4.8.1-1.el8.noarch -ovirt-release44-4.4.8.1-1.el8.noarch +ovirt-release-host-node-4.4.8.2-1.el8.noarch +ovirt-release44-4.4.8.2-1.el8.noarch @@ -664,3 +664,3 @@ -pacemaker-cluster-libs-2.1.0-6.el8.x86_64 -pacemaker-libs-2.1.0-6.el8.x86_64 -pacemaker-schemas-2.1.0-6.el8.noarch +pacemaker-cluster-libs-2.1.0-8.el8.x86_64 +pacemaker-libs-2.1.0-8.el8.x86_64 +pacemaker-schemas-2.1.0-8.el8.noarch @@ -715 +715 @@ -platform-python-3.6.8-39.el8.x86_64 +platform-python-3.6.8-40.el8.x86_64 @@ -718,3 +718,3 @@ -plymouth-0.9.4-9.20200615git1e36e30.el8.x86_64 -plymouth-core-libs-0.9.4-9.20200615git1e36e30.el8.x86_64 -plymouth-scripts-0.9.4-9.20200615git1e36e30.el8.x86_64 +plymouth-0.9.4-10.20200615git1e36e30.el8.x86_64 +plymouth-core-libs-0.9.4-10.20200615git1e36e30.el8.x86_64 +plymouth-scripts-0.9.4-10.20200615git1e36e30.el8.x86_64 @@ -744,2 +744,2 @@ -python3-bind-9.11.26-4.el8_4.noarch -python3-blivet-3.4.0-4.el8.noarch +python3-bind-9.11.26-6.el8.noarch +python3-blivet-3.4.0-5.el8.noarch @@ -753 +753 @@ -python3-cloud-what-1.28.20-1.el8.x86_64 +python3-cloud-what-1.28.21-2.el8.x86_64 @@ -762 +762 @@ -python3-dnf-4.7.0-2.el8.noarch +python3-dnf-4.7.0-3.el8.noarch @@ -797 +797 @@ -python3-libs-3.6.8-39.el8.x86_64 +python3-libs-3.6.8-40.el8.x86_64 @@ -800 +800 @@ -python3-libvirt-7.5.0-1.el8s.x86_64 +python3-libvirt-7.6.0-1.el8s.x86_64 @@ -811 +811 @@ -python3-nftables-0.9.3-20.el8.x86_64 +python3-nftables-0.9.3-21.el8.x86_64 @@ -834 +834 @@ -python3-perf-4.18.0-331.el8.x86_64 +python3-perf-4.18.0-338.el8.x86_64 @@ -864 +864 @@ -python3-rpm-4.14.3-15.el8.x86_64 +python3-rpm-4.14.3-18.el8.x86_64 @@ -876 +876 @@ -python3-subscription-manager-rhsm-1.28.20-1.el8.x86_64 +python3-subscription-manager-rhsm-1.28.21-2.el8.x86_64 @@ -878 +878 @@ -python3-syspurpose-1.28.20-1.el8.x86_64 +python3-syspurpose-1.28.21-2.el8.x86_64 @@ -889,15 +889,15 @@ -python36-3.6.8-37.module_el8.5.0+771+e5d9a225.x86_64 -qemu-guest-agent-6.0.0-26.el8s.x86_64 -qemu-img-6.0.0-26.el8s.x86_64 -qemu-kvm-6.0.0-26.el8s.x86_64 -qemu-kvm-block-curl-6.0.0-26.el8s.x86_64 -qemu-kvm-block-gluster-6.0.0-26.el8s.x86_64 -qemu-kvm-block-iscsi-6.0.0-26.el8s.x86_64 -qemu-kvm-block-rbd-6.0.0-26.el8s.x86_64 -qemu-kvm-block-ssh-6.0.0-26.el8s.x86_64 -qemu-kvm-common-6.0.0-26.el8s.x86_64 -qemu-kvm-core-6.0.0-26.el8s.x86_64 -qemu-kvm-docs-6.0.0-26.el8s.x86_64 -qemu-kvm-hw-usbredir-6.0.0-26.el8s.x86_64 -qemu-kvm-ui-opengl-6.0.0-26.el8s.x86_64 -qemu-kvm-ui-spice-6.0.0-26.el8s.x86_64 +python36-3.6.8-38.module_el8.5.0+895+a459eca8.x86_64 +qemu-guest-agent-6.0.0-27.el8s.x86_64 +qemu-img-6.0.0-27.el8s.x86_64 +qemu-kvm-6.0.0-27.el8s.x86_64 +qemu-kvm-block-curl-6.0.0-27.el8s.x86_64 +qemu-kvm-block-gluster-6.0.0-27.el8s.x86_64 +qemu-kvm-block-iscsi-6.0.0-27.el8s.x86_64 +qemu-kvm-block-rbd-6.0.0-27.el8s.x86_64 +qemu-kvm-block-ssh-6.0.0-27.el8s.x86_64 +qemu-kvm-common-6.0.0-27.el8s.x86_64 +qemu-kvm-core-6.0.0-27.el8s.x86_64 +qemu-kvm-docs-6.0.0-27.el8s.x86_64 +qemu-kvm-hw-usbredir-6.0.0-27.el8s.x86_64 +qemu-kvm-ui-opengl-6.0.0-27.el8s.x86_64 +qemu-kvm-ui-spice-6.0.0-27.el8s.x86_64 @@ -912,4 +912,4 @@ -rpm-4.14.3-15.el8.x86_64 -rpm-build-libs-4.14.3-15.el8.x86_64 -rpm-libs-4.14.3-15.el8.x86_64 -rpm-plugin-selinux-4.14.3-15.el8.x86_64 +rpm-4.14.3-18.el8.x86_64 +rpm-build-libs-4.14.3-18.el8.x86_64 +rpm-libs-4.14.3-18.el8.x86_64 +rpm-plugin-selinux-4.14.3-18.el8.x86_64 @@ -928,3 +928,3 @@ -sbd-1.4.2-2.el8.x86_64 -scap-security-guide-0.1.57-1.el8.noarch -scrub-2.5.2-14.el8.x86_64 +sbd-1.5.0-2.el8.x86_64 +scap-security-guide-0.1.57-4.el8.noarch +scrub-2.5.2-16.el8.x86_64 @@ -934,2 +934,2 @@ -selinux-policy-3.14.3-76.el8.noarch -selinux-policy-targeted-3.14.3-76.el8.noarch +selinux-policy-3.14.3-78.el8.noarch +selinux-policy-targeted-3.14.3-78.el8.noarch @@ -961 +961 @@ -subscription-manager-rhsm-certificates-1.28.20-1.el8.x86_64 +subscription-manager-rhsm-certificates-1.28.21-2.el8.x86_64 @@ -973,5 +973,5 @@ -systemd-239-49.el8.x86_64 -systemd-container-239-49.el8.x86_64 -systemd-libs-239-49.el8.x86_64 -systemd-pam-239-49.el8.x86_64 -systemd-udev-239-49.el8.x86_64 +systemd-239-50.el8.x86_64 +systemd-container-239-50.el8.x86_64 +systemd-libs-239-50.el8.x86_64 +systemd-pam-239-50.el8.x86_64 +systemd-udev-239-50.el8.x86_64 @@ -993,11 +993,11 @@ -vdo-6.2.5.65-14.el8.x86_64 -vdsm-4.40.80.5-1.el8.x86_64 -vdsm-api-4.40.80.5-1.el8.noarch -vdsm-client-4.40.80.5-1.el8.noarch -vdsm-common-4.40.80.5-1.el8.noarch -vdsm-gluster-4.40.80.5-1.el8.x86_64 -vdsm-http-4.40.80.5-1.el8.noarch -vdsm-jsonrpc-4.40.80.5-1.el8.noarch -vdsm-network-4.40.80.5-1.el8.x86_64 -vdsm-python-4.40.80.5-1.el8.noarch -vdsm-yajsonrpc-4.40.80.5-1.el8.noarch +vdo-6.2.5.74-14.el8.x86_64 +vdsm-4.40.80.6-1.el8.x86_64 +vdsm-api-4.40.80.6-1.el8.noarch +vdsm-client-4.40.80.6-1.el8.noarch +vdsm-common-4.40.80.6-1.el8.noarch +vdsm-gluster-4.40.80.6-1.el8.x86_64 +vdsm-http-4.40.80.6-1.el8.noarch +vdsm-jsonrpc-4.40.80.6-1.el8.noarch +vdsm-network-4.40.80.6-1.el8.x86_64 +vdsm-python-4.40.80.6-1.el8.noarch +vdsm-yajsonrpc-4.40.80.6-1.el8.noarch @@ -1021 +1021 @@ -yum-4.7.0-2.el8.noarch +yum-4.7.0-3.el8.noarch -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Re: [ovirt-devel] VM timezone typo
by Arik Hadas 01 Sep '21

01 Sep '21

On Wed, Sep 1, 2021 at 5:09 AM luwen.zhang <luwen.zhang(a)vinchin.com> wrote: > > Hello team, > > We found a minor issue on oVirt 4.4.8 version, it seems like a typo of the > VM timezone, it should be “GMT+01:00 Central European Standard Time” but on > 4.4.8 it’s “GMT+01:00 Central European Standard Tim”. > This lead to Vinchin VM restoration fail at VM creation stage if using VM > backups from previous oVirt versions. > > > We had adjusted our programing to deal with this specific issue, but hope > it can be fix soon. > Thanks for reporting this issue We've already merged a fix for that ( https://gerrit.ovirt.org/#/c/ovirt-engine/+/116260/) A possible way to resolve this before the aforementioned fix is available is to fix the typo in /usr/share/ovirt-engine/conf/timezones-defaults.properties (changes will be overridden when updating ovirt-engine) or adding "Europe/Warsaw=Central European Standard Time" to a new configuration in /etc/ovirt-engine/timezones/ (see https://github.com/oVirt/ovirt-site/pull/2554/files) > Thanks & regards! > > > *Luwen Zhang* | Product Manager > > *Mobile*: +8613880424687 | *Skype*: luwen.zhang_cn > > *WhatsApp*: +8613880424687 | *WeChat*: +8613880424687 > > *Website*: www.vinchin.com > > *Address*: F5, Block 8, National Information Security Industry Park, > > No.333 Yunhua Road, Hi-tech Zone, Chengdu, China | *Zip*: 610015 > > *INNOVATIVE VM BACKUP EXPERT* > > VMware Backup <https://www.vinchin.com/en/hypervisor/vmware-backup.html> > | XenServer/Citrix Hypervisor/XCP-ng Backup > <https://www.vinchin.com/en/hypervisor/xcp-ng-xenserver-backup.html> | Hyper-V > Backup <https://www.vinchin.com/en/hypervisor/hyper-v-backup.html> > > RHEV/oVirt Backup > <https://www.vinchin.com/en/hypervisor/red-hat-virtualization-ovirt-backup.h…> > | OLVM Backup > <https://www.vinchin.com/en/hypervisor/oracle-linux-virtualization-manager-b…> > | Sangfor HCI Backup > <https://www.vinchin.com/en/hypervisor/sangfor-hci-backup.html> | OpenStack > Backup <https://www.vinchin.com/en/hypervisor/openstack-backup.html> > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/42KMIMK6CKK25… >

2 1

Extending iSCSI storage domain
by Répás Péter 01 Sep '21

01 Sep '21

Hello, I have an oVirt 4.1.1 installion with 2 nodes and an ovirt manager on a serpate machine. I have multiple storage domain on an external storage, one contains the disk images of VMs, and another is a huge storage domain dedicated to store mediafiles. The mediafile storage domain has only one disk image, attached to a linux vm, no other disk image on this mediafile storage domain. The mediafile storage domain is attached and available to both ovirt nodes. This media storage domain has to be extended. The storage device has the capacity, so it is going to be extended. What should be done on the oVirt side to extend the media storage domain? Sorry for the lame question but the docs and tips from the web are ambiguous for me, some say it cannot be extended, just add a new lun to this storage domain. Does this operation need the full cluster to be put maintenance and stop all vms? Or just the linux vm to that is the disk image is attached to? Thank you for your help! Regards, Peter

1 0

ovirt go sdk
by Nikita Zubarev 01 Sep '21

01 Sep '21

Hello. I need help creating a virtual machine using https://github.com/oVirt/go-ovirt I need set cmdline vm , Please help me my create vm configuration, but cmd not set [image: image.png] Vm( ovirtsdk4.NewVmBuilder(). Name(*name). Console( ovirtsdk4.NewConsoleBuilder(). Enabled(true). MustBuild()). Memory(ram2 * int64(1<<30)). MemoryPolicy( ovirtsdk4.NewMemoryPolicyBuilder(). Guaranteed(int64(ram2) * int64(1<<30)). Max(int64(ram2) * 2 * int64(1<<30)). Ballooning(true). MustBuild()). // Memory(int64(ram2) * int64(1<<30)). Os( ovirtsdk4.NewOperatingSystemBuilder(). CustomKernelCmdline("qemu_cmdline").Cmdline("qemu_cmdline").Boot( ovirtsdk4.NewBootBuilder(). DevicesOfAny( ovirtsdk4.BOOTDEVICE_NETWORK, ovirtsdk4.BOOTDEVICE_HD). MustBuild()). MustBuild()). HighAvailability( ovirtsdk4.NewHighAvailabilityBuilder(). Enabled(true). MustBuild()). Cpu( ovirtsdk4.NewCpuBuilder(). Topology( ovirtsdk4.NewCpuTopologyBuilder(). Cores(cpu2). Sockets(1). MustBuild()). MustBuild()). Cluster( ovirtsdk4.NewClusterBuilder(). Name(Cluster). MustBuild()). Template( ovirtsdk4.NewTemplateBuilder(). Name("Blank"). MustBuild()). MustBuild()). Send()

2 1

mount options change
by Jiří Sléžka 01 Sep '21

01 Sep '21

Hi, is there any way to change mount options on active storage? I started using my gluster volume in replica 3, arbiter 1 configuration with 10.0.4.11:/vms mount point and mount options backup-volfile-servers=10.0.4.13 I would like to add also 10.0.4.12 as backup volfile as I am on full replica 3 now. Yes, I suppose I can shut down all vms, switch domain to maintenance and then change mount options but is there any other way? For example change it directly in db and then restart all hosts one by one (while vms are running)? Cheers, Jiri

1 0

Re: [External] : Re: about the hugepage setting of the KVM server
by Tommy Sway 01 Sep '21

01 Sep '21

I use the ovirt-node, and I configured HUGEPAGE on the VM, and does not configure the HUGEPAGE on the KVM host. The THP I don't configure anything about it, and after configure the HUGEPAGE on the vm, there is no report. I don't know which method is the best. From: Marcos Sungaila <marcos.sungaila(a)oracle.com> Sent: Thursday, August 26, 2021 9:13 PM To: Tommy Sway <sz_cuitao(a)163.com>; users(a)ovirt.org Subject: RE: [External] : [ovirt-users] Re: about the hugepage setting of the KVM server Hi Tommy, I have no simple answer to your question since I did not need this before, but some questions may help us understand how it is currently working. 1st- Are you using an ovirt-node or an OS+vdsm as a hypervisor? 2nd- Did you enabled huge pages on the VM OS? 3rd- Did you check on the hypervisor OS if transparent hugepages (THP) is enabled? And if, after enabling/configuring hugepages in the VM, it is reporting hugepages are in use in the host? Marcos From: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Sent: quinta-feira, 26 de agosto de 2021 04:49 To: users(a)ovirt.org <mailto:users@ovirt.org> Subject: [External] : [ovirt-users] Re: about the hugepage setting of the KVM server Anyone can help me ? From: users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> <users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> > On Behalf Of Tommy Sway Sent: Thursday, August 26, 2021 12:27 AM To: users(a)ovirt.org <mailto:users@ovirt.org> Subject: [ovirt-users] about the hugepage setting of the KVM server Hi: I am running virtual machines on the KVM servers of oVirt env. The virtual machine is running database, which needs to set the memory huge page on the OPERATING system of the virtual machine. If I need to set the huge page on the VIRTUAL machine, do I also need to set huge page on the KVM physical machine? Or just on the virtual machine? What best practices do you recommend? Thank you very much!

2 1

Unable to export VM from data storage domain.
by Diggy Mc 01 Sep '21

01 Sep '21

I'm running oVirt 4.4.4 with two data storage domains. One domain is where the production VMs run. The second domain is where I make backup copies of the VMs in the event of problems with the main production VMs. I make backups using the export option from the GUI's dropdown list. I just now tried to "restore" a backup copy via the export function and get an error. In fact, I get errors trying to export (import to my original data domain) any of the VMs that were exported to my backup data domain. My backup domain is a DATA domain and not an EXPORT domain. The exact error is: Export VM Failed [Cannot add VM. Cannot find a disk profile defined on storage domain 246c69e9-6f16-489f-8022-8613f6c1c22a.] Is this a bug or am I doing something wrong? Help is needed urgently. In advance, thank you.

2 4

Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'libvirt'"}]
by marek 31 Aug '21

31 Aug '21

hi, i have problem adding host to ovirt 4.4.8 standalone engine host is centos 8 stream (migrated from centos 8) on engine /var/log/ovirt-engine/engine.log 2021-08-30 10:32:43,422+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-69) [] Failed in 'Get Host Capabilities' method 2021-08-30 10:32:43,422+02 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-69) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'libvirt'"}] 2021-08-30 10:32:43,423+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-69) [] Unable to RefreshCapabilities beforeFirstRefreshTreatment: VDSErrorException: VDSGenericException: VDSErrorException: Failed to Get Host Capabilities, error = Internal JSON-RPC error: {'reason': "'libvirt'"}, code = -32603 any tips/ideas? Marek

3 3