Fwd: oVirt 4.4.8 is now generally available
by Sandro Bonazzola
---------- Forwarded message ----------
From: *Sandro Bonazzola* <sbonazzo(a)redhat.com>
Date: Thursday, August 19, 2021
Subject: oVirt 4.4.8 is now generally available
To: oVirt Users <users(a)ovirt.org>
oVirt 4.4.8 is now generally available
The oVirt project is excited to announce the general availability of oVirt
4.4.8 , as of August 19th, 2021.
This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics, as compared to oVirt 4.3.
Important notes before you install / upgrade
Please note that oVirt 4.4 only supports clusters and data centers with
compatibility version 4.2 and above. If clusters or data centers are
running with an older compatibility version, you need to upgrade them to at
least 4.2 (4.3 is recommended).
Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
are no longer supported.
For example, the megaraid_sas driver is removed. If you use Enterprise
Linux 8 hosts you can try to provide the necessary drivers for the
deprecated hardware using the DUD method (See the users’ mailing list
thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/
thread/NDSVUZSESOXEFJNPHOXUH4HOOWRIRSB4/ )
Documentation
-
If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-
For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-
For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-
For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.
What’s new in oVirt 4.4.8 Release?
This update is the eighth in a series of stabilization updates to the 4.4
series.
This release is available now on x86_64 architecture for:
-
Red Hat Enterprise Linux 8.4
-
CentOS Linux (or similar) 8.4
-
CentOS Stream 8
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
-
Red Hat Enterprise Linux 8.4
-
CentOS Linux (or similar) 8.4
-
oVirt Node NG (based on CentOS Stream 8)
-
CentOS Stream 8
Some of the RFEs with high user impact are listed below:
-
Bug 1691696 <https://bugzilla.redhat.com/show_bug.cgi?id=1691696> -
[RFE] multipath events notifications
-
Bug 1939286 <https://bugzilla.redhat.com/show_bug.cgi?id=1939286> -
[RFE] Expose broken Affinity Groups via API too
-
Bug 1963083 <https://bugzilla.redhat.com/show_bug.cgi?id=1963083> -
[RFE] Support storing user data in VM checkpoint entity
-
Bug 1971185 <https://bugzilla.redhat.com/show_bug.cgi?id=1971185> -
[RFE] Report zero status in dirty extents response
-
Bug 1981297 <https://bugzilla.redhat.com/show_bug.cgi?id=1981297> -
[RFE] Add new backup phases and disable backup/image transfers DB instant
cleanup
-
Bug 1971317 <https://bugzilla.redhat.com/show_bug.cgi?id=1971317> -
[RFE][API] Import OVA template as a clone
-
Bug 1941507 <https://bugzilla.redhat.com/show_bug.cgi?id=1941507> -
[RFE] Implement rotation mechanism for /var/log/ovirt-engine/host-deploy
-
Bug 1962563 <https://bugzilla.redhat.com/show_bug.cgi?id=1962563> -
[RFE] Use nmstate for source routing
Some of the Bugs with high user impact are listed below:
-
Bug 1770027 <https://bugzilla.redhat.com/show_bug.cgi?id=1770027> - Live
Merge completed on the host, but not on the engine, which just waited for
it to complete until the operation was terminated.
-
Bug 1977689 <https://bugzilla.redhat.com/show_bug.cgi?id=1977689> -
Download backup disk command failes in sdk/examples/backup_vm.py
-
Bug 1987295 <https://bugzilla.redhat.com/show_bug.cgi?id=1987295> -
Setting host to 'maintenance' will be blocked when there are image
transfers with status different then 'paused'
-
Bug 1983414 <https://bugzilla.redhat.com/show_bug.cgi?id=1983414> -
Disks are locked forever when copying VMs' disks after snapshot
-
Bug 1982065 <https://bugzilla.redhat.com/show_bug.cgi?id=1982065> -
Invalid amount of memory is allowed to be hot plugged
-
Bug 1966535 <https://bugzilla.redhat.com/show_bug.cgi?id=1966535> -
NullPointerException when trying to delete uploaded disks with using
transfer_url
-
Bug 1985876 <https://bugzilla.redhat.com/show_bug.cgi?id=1985876> -
Cannot set 0.0.0.0 as gateway
-
Bug 1932392 <https://bugzilla.redhat.com/show_bug.cgi?id=1932392> -
engine-setup fails after 'engine-backup --mode=restore' if the backup was
taken on a newer version
-
Bug 1989794 <https://bugzilla.redhat.com/show_bug.cgi?id=1989794> -
engine still generates duplicate address for hotplug disk
oVirt Node and Appliance have been updated, including:
-
oVirt 4.4.8: https://www.ovirt.org/release/4.4.8/
-
CentOS Stream 8 latest updates
-
Ansible 2.9.24: https://github.com/ansible/ansible/blob/stable-2.9/
changelogs/CHANGELOG-v2.9.rst#v2-9-24
<https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v...>
We also included updates for the following CVEs:
cockpit-ovirt:
-
CVE-2020-28500 <https://access.redhat.com/security/cve/CVE-2020-28500> -
Moderate - nodejs-lodash: ReDoS via the toNumber, trim and trimEnd functions
-
CVE-2021-23337 <https://access.redhat.com/security/cve/CVE-2021-23337> -
Moderate - nodejs-lodash: command injection via template
oVirt Node consumed fixes for:
-
CVE-2021-3621 <https://access.redhat.com/security/cve/CVE-2021-3621> -
Important - sssd: shell command injection in sssctl
-
CVE-2021-33034 <https://access.redhat.com/security/cve/CVE-2021-33034> -
Important - kernel: use-after-free in net/bluetooth/hci_event.c when
destroying an hci_chan
-
CVE-2021-3501 <https://access.redhat.com/security/cve/CVE-2021-3501> -
Important - kernel: userspace applications can misuse the KVM API to cause
a write of 16 bytes at an offset up to 32 GB from vcpu->run
-
CVE-2021-3609 <https://access.redhat.com/security/cve/CVE-2021-3609> -
Important - kernel: race condition in net/can/bcm.c leads to local
privilege escalation
-
CVE-2021-25217 <https://access.redhat.com/security/cve/CVE-2021-25217> -
Important - dhcp: stack-based buffer overflow when parsing statements with
colon-separated hex digits in config or lease files in dhcpd and dhclient
-
CVE-2021-3623 <https://access.redhat.com/security/cve/CVE-2021-3623> -
Moderate - libtpms: out-of-bounds access when trying to resume the state of
the vTPM
-
CVE-2021-3565 <https://access.redhat.com/security/cve/CVE-2021-3565> -
Moderate - tpm2-tools: fixed AES wrapping key in tpm2_import
-
CVE-2021-3580 <https://access.redhat.com/security/cve/CVE-2021-3580> -
Moderate - nettle: Remote crash in RSA decryption via manipulated
ciphertext
-
CVE-2021-36222 <https://access.redhat.com/security/cve/CVE-2021-36222> -
Moderate - krb5: sending a request containing a PA-ENCRYPTED-CHALLENGE
padata element without using FAST could result in null dereference in the
KDC which leads to DoS
-
CVE-2020-24504 <https://access.redhat.com/security/cve/CVE-2020-24504> -
Moderate - kernel: Uncontrolled resource consumption in some Intel(R)
Ethernet E810 Adapter drivers
-
CVE-2020-24503 <https://access.redhat.com/security/cve/CVE-2020-24503> -
Moderate - kernel: Insufficient access control in some Intel(R) Ethernet
E810 Adapter drivers
-
CVE-2020-24502 <https://access.redhat.com/security/cve/CVE-2020-24502> -
Moderate - kernel: Improper input validation in some Intel(R) Ethernet E810
Adapter drivers
-
CVE-2021-35942 <https://access.redhat.com/security/cve/CVE-2021-35942> -
Moderate - glibc: Arbitrary read in wordexp()
-
CVE-2021-3448 <https://access.redhat.com/security/cve/CVE-2021-3448> -
Moderate - dnsmasq: fixed outgoing port used when --server is used with an
interface name
-
CVE-2021-20266 <https://access.redhat.com/security/cve/CVE-2021-20266> -
Low - rpm: missing length checks in hdrblobInit()
-
CVE-2020-29368 <https://access.redhat.com/security/cve/CVE-2020-29368> -
Low - kernel: the copy-on-write implementation can grant unintended write
access because of a race condition in a THP mapcount check
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 Stream 8
-
oVirt Node NG is already available for CentOS Stream 8
Additional resources:
-
Read more about the oVirt 4.4.8 release highlights:
https://www.ovirt.org/release/4.4.8/
<https://www.ovirt.org/release/4.4.8/>
-
Get more oVirt project updates on Twitter: https://twitter.com/ovirt
-
Check out the latest project news on the oVirt blog:
https://blogs.ovirt.org/
[1] https://www.ovirt.org/release/4.4.8/
[2] https://resources.ovirt.org/pub/ovirt-4.4/iso/
--
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.*
--
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.
<https://mojo.redhat.com/docs/DOC-1199578>*
3 years, 4 months
Injecting VirtIO drivers : Query
by KK CHN
Hi,
I am in the process of importing multi disk Windows VMs from HyperV
environment to my OpenStack Setup( Ussuri version, glance and QEMU-KVM
)
I am referring online documents as in the trailing lines. But Is this
relevant to inject VirtIO drivers to the Windows VMs ( as the articles
date back to 2015) . Some where it mentions when you perform P2V
migration its necessary.
Is this VirtIO injection is necessary in my case ? I am exporting from
HyperV and importing to OpenStack.
1. Kindly advise me the relevance of VirtIO injection and is it applicable
to my requirements.
2. Is there any uptodate reference materials link for performing Windows
Multidisk VM importing to OpenStack(ussurin, glance and KVM) . Or Am I
doing an impossible thing by beat around the bush ?
These are the links which I referred but it too old : So the relevance of
the contents still applicable ? ( Windows VMs are Windows 2012 Server,
2008 and 2003 which I need to import to OpenStack)
https://superuser.openstack.org/articles/how-to-migrate-from-vmware-and-h...
https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e00000...
Kris
3 years, 4 months
glusterfs not starting
by eevans＠digitaldatatechs.com
I have an ovirt 4.3 on 3 Centos 7 with Gluster 9. Another Centos 7 server is the Ovirt node, but only for management and file sharing.
Everything was fine until a power outage. Now node2 glusterfs will not spawn the listening port for the brick..
All nodes are connected, but just no brick port for the brick on this node due to glusterfsd not starting .
I pointed to the volume file: glusterfs --volfile=dds_cluster.kvm02.digitaldatatechs.com.gluster_bricks-kvm02_bricks-brick1-brick1.vol
and even the entire path:
glusterfs --volfile=/var/lib/glusterd/vols/dds_cluster/dds_cluster.kvm02.digitaldatatechs.com.gluster_bricks-kvm02_bricks-brick1-brick1.vol
I really need some help with this and it will be greatly appreciated.
Please direct replies to eevans6913(a)gmail.com.
My mail server is down.
3 years, 4 months
Re: [External] : Re: what difference between the Cloud-Init Network Protocol options ?
by Tommy Sway
Ok,thanks!
-----Original Message-----
From: Marcos Sungaila <marcos.sungaila(a)oracle.com>
Sent: Wednesday, August 25, 2021 1:39 AM
To: Tommy Sway <sz_cuitao(a)163.com>; 'Liran Rotenberg' <lrotenbe(a)redhat.com>
Cc: users(a)ovirt.org
Subject: RE: [ovirt-users] Re: [External] : Re: what difference between the Cloud-Init Network Protocol options ?
Once the KVM host is part of an oVirt cluster, many interactions come from the VDSM service.
It would help if you used a different KVM host for this kind of procedure.
Marcos
-----Original Message-----
From: Tommy Sway <sz_cuitao(a)163.com>
Sent: terça-feira, 24 de agosto de 2021 14:10
To: Marcos Sungaila <marcos.sungaila(a)oracle.com>; 'Liran Rotenberg' <lrotenbe(a)redhat.com>
Cc: users(a)ovirt.org
Subject: [ovirt-users] Re: [External] : Re: what difference between the Cloud-Init Network Protocol options ?
If so, can I still run it on KVM Server fn the oVirt platform?
It seems that a lot of oVirt's configuration information is not stored in QUEMU's configuration file like ordinary KVM SERVER, but in the database. Does this still work?
-----Original Message-----
From: Marcos Sungaila <marcos.sungaila(a)oracle.com>
Sent: Wednesday, August 25, 2021 12:55 AM
To: Liran Rotenberg <lrotenbe(a)redhat.com>; Tommy Sway <sz_cuitao(a)163.com>
Cc: users(a)ovirt.org
Subject: RE: [External] : [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
One important thing, you run the virt-sysprep command on the KVM host indicating the VM name to seal, you do not run it inside a VM.
It is not like the sysprep command on a Windows machine.
Marcos
-----Original Message-----
From: Liran Rotenberg <lrotenbe(a)redhat.com>
Sent: terça-feira, 24 de agosto de 2021 12:56
To: Tommy Sway <sz_cuitao(a)163.com>
Cc: users(a)oVirt.org
Subject: [External] : [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
On Tue, Aug 24, 2021 at 7:36 AM Tommy Sway <sz_cuitao(a)163.com> wrote:
>
> Thank you very much!
>
>
>
> However, if you use virt-Sysprep, you need to use this tool to complete template creation inside the VM to be created. Using oVirt's own template encapsulation option, however, does not require you to log in to the VM to run similar commands. It's just that using the Virt-Sysprep tool gives you more autonomy and options to choose from, whereas oVirt's own template encapsulation options are fixed and you can't personalize more options.
>
>
>
> Am I getting that right?
Yes, ovirt manages your environment and such does for you some of the operations to ease you from doing it manually.
When you create a template in ovirt you may or may not set the sealing option. In the bottom line it will run virt-sysprep with the parameters we thought are right.
Note the documentation in the thread, for windows OS you will need to do it manually.
>
>
>
>
>
>
>
> From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of
> Liran Rotenberg
> Sent: Monday, August 23, 2021 5:23 PM
> To: Tommy Sway <sz_cuitao(a)163.com>
> Cc: users(a)ovirt.org
> Subject: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
>
>
>
>
>
> On Sun, Aug 22, 2021 at 7:56 PM Tommy Sway <sz_cuitao(a)163.com> wrote:
> >
> > I have read the document you gave me, but can you list what specific information was deleted by the sealing action?
> Yes, it was more about how to do it.
>
> Here are some more detailed links:
> https://urldefense.com/v3/__https://www.ovirt.org/develop/release-mana
> gement/features/virt/virt-sysprep.html__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6i
> sDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdze6OUMY$
>
>
>
> Our linux sealing uses virt-sysprep:
>
> https://urldefense.com/v3/__https://libguestfs.org/virt-sysprep.1.html
> __;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walS
> mLU6F8JySXdosCfIz8$
>
>
>
> As for windows:
>
> https://urldefense.com/v3/__https://docs.microsoft.com/en-us/windows-h
> ardware/manufacture/desktop/sysprep--generalize--a-windows-installatio
> n__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-wal
> SmLU6F8JySXdXvrseps$
> >
> >
> >
> > Thanks!
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Liran Rotenberg <lrotenbe(a)redhat.com>
> > Sent: Sunday, August 22, 2021 11:33 PM
> > To: Tommy Sway <sz_cuitao(a)163.com>
> > Cc: Eitan Raviv <eraviv(a)redhat.com>; users(a)ovirt.org
> > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
> >
> >
> >
> >
> >
> > On Sun, Aug 22, 2021 at 5:54 PM Tommy Sway <sz_cuitao(a)163.com> wrote:
> > >
> > > I see. Can I just ask again, I've seen this option when you're referring to sealed Linux, but I don't understand what it means? What is a sealed Linux, and how is it different from a non-sealed Linux? Can you explain, thank you!
> > >
> > Usually you make a template sealed and create multiple VMs from it. The sealing is clearing system specific details.
> > You may find this link handy for sealing:
> > https://urldefense.com/v3/__https://access.redhat.com/documentation/
> > en-us/red_hat_virtualization/4.4/html/virtual_machine_management_gui
> > de/chap-templates__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLa
> > uWNhglwbS9fr0p-walSmLU6F8JySXdFW1of34$
> > >
> > >
> > > -----Original Message-----
> > > From: Liran Rotenberg <lrotenbe(a)redhat.com>
> > > Sent: Sunday, August 22, 2021 10:46 PM
> > > To: Tommy Sway <sz_cuitao(a)163.com>
> > > Cc: Eitan Raviv <eraviv(a)redhat.com>; users(a)ovirt.org
> > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
> > >
> > > On Sun, Aug 22, 2021 at 2:05 PM Tommy Sway <sz_cuitao(a)163.com> wrote:
> > > >
> > > > What I want to know is if I use openstack metadata, do I need to configure any additional information related to openstack? For example, do I need to set up an openstack node as an external provider to use cloud-init services based on it?
> > > >
> > > Not that I am aware of. It's just the protocol cloud-init will read the network information provided.
> > > You can set it via API/UI. Or, to set it within the custom script.
> > > Bottom line you need:
> > > A VM with cloud-init installed, service is running and enabled.
> > > Set the configuration you wish to set.
> > > If it's a first boot (usually a sealed VM) you can run the VM as you wish.
> > > If it's not the first boot, you will need to set the configuration within the Run-Once and run the VM as Run-Once.
> > >
> > > I hope it helps to your question,
> > > Liran
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Liran Rotenberg <lrotenbe(a)redhat.com>
> > > > Sent: Sunday, August 22, 2021 4:01 PM
> > > > To: Tommy Sway <sz_cuitao(a)163.com>; Eitan Raviv
> > > > <eraviv(a)redhat.com>
> > > > Cc: users(a)ovirt.org
> > > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
> > > >
> > > > On Sun, Aug 22, 2021 at 9:35 AM Tommy Sway <sz_cuitao(a)163.com> wrote:
> > > > >
> > > > > Any one can help me ?
> > > > >
> > > > Adding +Eitan Raviv
> > > > The general information I can give is that older versions of cloud-init support ENI protocol when network configuration provided while on newer versions (EL7+, Eitan please correct me if I'm wrong), support the openstack protocol.
> > > > The ENI option was added to support the back compatibility of older OSes and cloud-init versions.
> > > >
> > > > Regards,
> > > > Liran
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On
> > > > > Behalf Of Tommy Sway
> > > > > Sent: Saturday, August 14, 2021 6:18 PM
> > > > > To: users(a)ovirt.org
> > > > > Subject: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
> > > > >
> > > > >
> > > > >
> > > > > Any one can help to explain ?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On
> > > > > Behalf Of Tommy Sway
> > > > > Sent: Friday, August 13, 2021 12:55 PM
> > > > > To: users(a)ovirt.org
> > > > > Subject: [ovirt-users] what difference between the Cloud-Init Network Protocol options ?
> > > > >
> > > > >
> > > > >
> > > > > What is the difference between Openstack MateData and ENI in the cloud-init Network Protocol option? Or what kind of scenarios do they apply to?
> > > > >
> > > > > _______________________________________________
> > > > > Users mailing list -- users(a)ovirt.org To unsubscribe send an
> > > > > email to users-leave(a)ovirt.org Privacy
> > > > > Statement:
> > > > > https://urldefense.com/v3/__https://www.ovirt.org/privacy-poli
> > > > > cy.html__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNh
> > > > > glwbS9fr0p-walSmLU6F8JySXdU7c1QGc$
> > > > > oVirt Code of Conduct:
> > > > > https://urldefense.com/v3/__https://www.ovirt.org/community/ab
> > > > > out/community-guidelines/__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U
> > > > > _lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdVgkIxYc$
> > > > > List Archives:
> > > > > https://urldefense.com/v3/__https://lists.ovirt.org/archives/l
> > > > > ist/users(a)ovirt.org/message/F7HIV5__;!!ACWV5N9M2RV99hQ!ftpwz3R
> > > > > mG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdKPdbNk4$
> > > > > EI
> > > > > 4YCJ3XVIPMZCMPBTAPY5LLS6/
> > > >
> > > >
> > >
> > >
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!...
oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/communi...
List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@o...
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!...
oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/communi...
List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@o...
3 years, 4 months
ovirt-image-repository is unattached
by eevans＠digitaldatatechs.com
I had a gluster issue and got it resolved, but now the ovirt-image-repository is unattached in the storage domain section. I was able to import the images but want to make sure its something that just points to another problem I don't know about.
Any help is appreciated.
3 years, 4 months
Re: [External] : Re: what difference between the Cloud-Init Network Protocol options ?
by Tommy Sway
If so, can I still run it on KVM Server fn the oVirt platform?
It seems that a lot of oVirt's configuration information is not stored in QUEMU's configuration file like ordinary KVM SERVER, but in the database. Does this still work?
-----Original Message-----
From: Marcos Sungaila <marcos.sungaila(a)oracle.com>
Sent: Wednesday, August 25, 2021 12:55 AM
To: Liran Rotenberg <lrotenbe(a)redhat.com>; Tommy Sway <sz_cuitao(a)163.com>
Cc: users(a)ovirt.org
Subject: RE: [External] : [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
One important thing, you run the virt-sysprep command on the KVM host indicating the VM name to seal, you do not run it inside a VM.
It is not like the sysprep command on a Windows machine.
Marcos
-----Original Message-----
From: Liran Rotenberg <lrotenbe(a)redhat.com>
Sent: terça-feira, 24 de agosto de 2021 12:56
To: Tommy Sway <sz_cuitao(a)163.com>
Cc: users(a)oVirt.org
Subject: [External] : [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
On Tue, Aug 24, 2021 at 7:36 AM Tommy Sway <sz_cuitao(a)163.com> wrote:
>
> Thank you very much!
>
>
>
> However, if you use virt-Sysprep, you need to use this tool to complete template creation inside the VM to be created. Using oVirt's own template encapsulation option, however, does not require you to log in to the VM to run similar commands. It's just that using the Virt-Sysprep tool gives you more autonomy and options to choose from, whereas oVirt's own template encapsulation options are fixed and you can't personalize more options.
>
>
>
> Am I getting that right?
Yes, ovirt manages your environment and such does for you some of the operations to ease you from doing it manually.
When you create a template in ovirt you may or may not set the sealing option. In the bottom line it will run virt-sysprep with the parameters we thought are right.
Note the documentation in the thread, for windows OS you will need to do it manually.
>
>
>
>
>
>
>
> From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of
> Liran Rotenberg
> Sent: Monday, August 23, 2021 5:23 PM
> To: Tommy Sway <sz_cuitao(a)163.com>
> Cc: users(a)ovirt.org
> Subject: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
>
>
>
>
>
> On Sun, Aug 22, 2021 at 7:56 PM Tommy Sway <sz_cuitao(a)163.com> wrote:
> >
> > I have read the document you gave me, but can you list what specific information was deleted by the sealing action?
> Yes, it was more about how to do it.
>
> Here are some more detailed links:
> https://urldefense.com/v3/__https://www.ovirt.org/develop/release-mana
> gement/features/virt/virt-sysprep.html__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6i
> sDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdze6OUMY$
>
>
>
> Our linux sealing uses virt-sysprep:
>
> https://urldefense.com/v3/__https://libguestfs.org/virt-sysprep.1.html
> __;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walS
> mLU6F8JySXdosCfIz8$
>
>
>
> As for windows:
>
> https://urldefense.com/v3/__https://docs.microsoft.com/en-us/windows-h
> ardware/manufacture/desktop/sysprep--generalize--a-windows-installatio
> n__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-wal
> SmLU6F8JySXdXvrseps$
> >
> >
> >
> > Thanks!
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Liran Rotenberg <lrotenbe(a)redhat.com>
> > Sent: Sunday, August 22, 2021 11:33 PM
> > To: Tommy Sway <sz_cuitao(a)163.com>
> > Cc: Eitan Raviv <eraviv(a)redhat.com>; users(a)ovirt.org
> > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
> >
> >
> >
> >
> >
> > On Sun, Aug 22, 2021 at 5:54 PM Tommy Sway <sz_cuitao(a)163.com> wrote:
> > >
> > > I see. Can I just ask again, I've seen this option when you're referring to sealed Linux, but I don't understand what it means? What is a sealed Linux, and how is it different from a non-sealed Linux? Can you explain, thank you!
> > >
> > Usually you make a template sealed and create multiple VMs from it. The sealing is clearing system specific details.
> > You may find this link handy for sealing:
> > https://urldefense.com/v3/__https://access.redhat.com/documentation/
> > en-us/red_hat_virtualization/4.4/html/virtual_machine_management_gui
> > de/chap-templates__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLa
> > uWNhglwbS9fr0p-walSmLU6F8JySXdFW1of34$
> > >
> > >
> > > -----Original Message-----
> > > From: Liran Rotenberg <lrotenbe(a)redhat.com>
> > > Sent: Sunday, August 22, 2021 10:46 PM
> > > To: Tommy Sway <sz_cuitao(a)163.com>
> > > Cc: Eitan Raviv <eraviv(a)redhat.com>; users(a)ovirt.org
> > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
> > >
> > > On Sun, Aug 22, 2021 at 2:05 PM Tommy Sway <sz_cuitao(a)163.com> wrote:
> > > >
> > > > What I want to know is if I use openstack metadata, do I need to configure any additional information related to openstack? For example, do I need to set up an openstack node as an external provider to use cloud-init services based on it?
> > > >
> > > Not that I am aware of. It's just the protocol cloud-init will read the network information provided.
> > > You can set it via API/UI. Or, to set it within the custom script.
> > > Bottom line you need:
> > > A VM with cloud-init installed, service is running and enabled.
> > > Set the configuration you wish to set.
> > > If it's a first boot (usually a sealed VM) you can run the VM as you wish.
> > > If it's not the first boot, you will need to set the configuration within the Run-Once and run the VM as Run-Once.
> > >
> > > I hope it helps to your question,
> > > Liran
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Liran Rotenberg <lrotenbe(a)redhat.com>
> > > > Sent: Sunday, August 22, 2021 4:01 PM
> > > > To: Tommy Sway <sz_cuitao(a)163.com>; Eitan Raviv
> > > > <eraviv(a)redhat.com>
> > > > Cc: users(a)ovirt.org
> > > > Subject: Re: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
> > > >
> > > > On Sun, Aug 22, 2021 at 9:35 AM Tommy Sway <sz_cuitao(a)163.com> wrote:
> > > > >
> > > > > Any one can help me ?
> > > > >
> > > > Adding +Eitan Raviv
> > > > The general information I can give is that older versions of cloud-init support ENI protocol when network configuration provided while on newer versions (EL7+, Eitan please correct me if I'm wrong), support the openstack protocol.
> > > > The ENI option was added to support the back compatibility of older OSes and cloud-init versions.
> > > >
> > > > Regards,
> > > > Liran
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On
> > > > > Behalf Of Tommy Sway
> > > > > Sent: Saturday, August 14, 2021 6:18 PM
> > > > > To: users(a)ovirt.org
> > > > > Subject: [ovirt-users] Re: what difference between the Cloud-Init Network Protocol options ?
> > > > >
> > > > >
> > > > >
> > > > > Any one can help to explain ?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On
> > > > > Behalf Of Tommy Sway
> > > > > Sent: Friday, August 13, 2021 12:55 PM
> > > > > To: users(a)ovirt.org
> > > > > Subject: [ovirt-users] what difference between the Cloud-Init Network Protocol options ?
> > > > >
> > > > >
> > > > >
> > > > > What is the difference between Openstack MateData and ENI in the cloud-init Network Protocol option? Or what kind of scenarios do they apply to?
> > > > >
> > > > > _______________________________________________
> > > > > Users mailing list -- users(a)ovirt.org To unsubscribe send an
> > > > > email to users-leave(a)ovirt.org Privacy
> > > > > Statement:
> > > > > https://urldefense.com/v3/__https://www.ovirt.org/privacy-poli
> > > > > cy.html__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U_lLChsyamYgXLauWNh
> > > > > glwbS9fr0p-walSmLU6F8JySXdU7c1QGc$
> > > > > oVirt Code of Conduct:
> > > > > https://urldefense.com/v3/__https://www.ovirt.org/community/ab
> > > > > out/community-guidelines/__;!!ACWV5N9M2RV99hQ!ftpwz3RmG6isDe4U
> > > > > _lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdVgkIxYc$
> > > > > List Archives:
> > > > > https://urldefense.com/v3/__https://lists.ovirt.org/archives/l
> > > > > ist/users(a)ovirt.org/message/F7HIV5__;!!ACWV5N9M2RV99hQ!ftpwz3R
> > > > > mG6isDe4U_lLChsyamYgXLauWNhglwbS9fr0p-walSmLU6F8JySXdKPdbNk4$
> > > > > EI
> > > > > 4YCJ3XVIPMZCMPBTAPY5LLS6/
> > > >
> > > >
> > >
> > >
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!...
oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/communi...
List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@o...
3 years, 4 months
Re: [External] : about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name
by Tommy Sway
Thank you!
But where to set in on oVirt Platform when I create the VM ?
-----Original Message-----
From: Marcos Sungaila <marcos.sungaila(a)oracle.com>
Sent: Tuesday, August 24, 2021 9:10 PM
To: Tommy Sway <sz_cuitao(a)163.com>; users(a)ovirt.org
Subject: RE: [External] : [ovirt-users] about the network name rules on
CentOS/Redhat 8 and the cloud-init network interface name
The naming convention is called BiosDevName and was introduced in kernel
2.6.27. It is defined by the OS kernel you are using in the guest. It is not
related to oVirt itself or the KVM host.
In my case, I install my VMs passing "biosdevname=0 net.ifnames=0" during
the OS installation process, so all my VMs have ethX name style to make it
easier to use cloud-init and other scripts.
Marcos
From: Tommy Sway <sz_cuitao(a)163.com>
Sent: terça-feira, 24 de agosto de 2021 05:57
To: users(a)ovirt.org
Subject: [External] : [ovirt-users] about the network name rules on
CentOS/Redhat 8 and the cloud-init network interface name
Everybody is good!
As you all know, to use the client's network card name in cloud-init, you
must fill in the exact name of the network card interface.
This was easy in version 7 and before, which usually started with EN0.
After version 8, however, the naming conventions for network cards changed a
lot. In my own test environment, for example, I started with ENS3.
I'm not sure what naming convention it uses, which would make it impossible
to specify nic information using cloud-init.
Could you help me explain how to deal with this problem?
Thank you very much!
3 years, 4 months
Cannot delete pvc attached to pod using ovirt-csi in kubernetes
by ssarang520＠gmail.com
Hi all,
I deployed ovirt-csi in the k8s by applying yaml manually. I used the latest version of the container image.
(https://github.com/openshift/ovirt-csi-driver-operator/tree/master/assets)
After successfully creating pvc and pod, I tried to delete it.
And the pod is deleted, but the pvc is not deleted. This is because deleting a pod does not unmap /dev/rbd0 attached to the ovirt vm.
How can I delete the pvc successfully?
oVirt engine version is 4.4.7.6-1.el8.
Here is the engine log when deleting the pod:
2021-08-20 17:40:35,385+09 INFO [org.ovirt.engine.core.sso.service.AuthenticationService] (default task-149) [] User admin@internal-authz with profile [internal] successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access
2021-08-20 17:40:35,403+09 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-149) [68ee3182] Running command: CreateUserSessionCommand internal: false.
2021-08-20 17:40:35,517+09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-149) [68ee3182] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '192.168.7.169' using session 'XfDgNkmAGnPiZahK5itLhHQTCNHZ3JwXMMzOiZrYL3C32+1TTys3xcjrAmCIKPu02hgN1sdVpfZXWd0FznaPCQ==' logged in.
2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:35,663+09 INFO [org.ovirt.engine.core.bll.storage.disk.DetachDiskFromVmCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Running command: DetachDiskFromVmCommand internal: false. Entities affected : ID: 59a7461c-72fe-4e01-86a7-c70243f31596 Type: VMAction group CONFIGURE_VM_STORAGE with role type USER
2021-08-20 17:40:35,664+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] START, HotUnPlugDiskVDSCommand(HostName = host, HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094', vmId='59a7461c-72fe-4e01-86a7-c70243f31596', diskId='63a64445-1659-4d5f-8847-e7266e64b09e'}), log id: 506ff4a4
2021-08-20 17:40:35,678+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Disk hot-unplug: <?xml version="1.0" encoding="UTF-8"?><hotunplug>
<devices>
<disk>
<alias name="ua-63a64445-1659-4d5f-8847-e7266e64b09e"/>
</disk>
</devices>
</hotunplug>
2021-08-20 17:40:35,749+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] FINISH, HotUnPlugDiskVDSCommand, return: , log id: 506ff4a4
2021-08-20 17:40:35,842+09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] EVENT_ID: USER_DETACH_DISK_FROM_VM(2,018), Disk pvc-9845a0ff-e94c-497c-8c65-fc6a1e26db20 was successfully detached from VM centos by admin@internal-authz.
2021-08-20 17:40:35,916+09 ERROR [org.ovirt.engine.core.sso.service.SsoService] (default task-150) [] OAuthException invalid_grant: The provided authorization grant for the auth code has expired.
2021-08-20 17:40:35,917+09 ERROR [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-149) [] Cannot authenticate using authentication Headers: invalid_grant: The provided authorization grant for the auth code has expired.
2021-08-20 17:40:36,029+09 INFO [org.ovirt.engine.core.sso.service.AuthenticationService] (default task-149) [] User admin@internal-authz with profile [internal] successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access
2021-08-20 17:40:36,046+09 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-149) [4c4bf441] Running command: CreateUserSessionCommand internal: false.
2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null
2021-08-20 17:40:49,241+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-27) [] START, DumpXmlsVDSCommand(HostName = host, Params:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094', vmIds='[59a7461c-72fe-4e01-86a7-c70243f31596]'}), log id: 7eb54202
2021-08-20 17:40:49,244+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-27) [] FINISH, DumpXmlsVDSCommand, return: {59a7461c-72fe-4e01-86a7-c70243f31596=<domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
<name>centos</name>
<uuid>59a7461c-72fe-4e01-86a7-c70243f31596</uuid>
<metadata xmlns:ns1="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm="http://ovirt.org/vm/1.0">
<ns1:qos/>
<ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0">
<ovirt-vm:balloonTarget type="int">4194304</ovirt-vm:balloonTarget>
<ovirt-vm:ballooningEnabled>true</ovirt-vm:ballooningEnabled>
<ovirt-vm:clusterVersion>4.6</ovirt-vm:clusterVersion>
<ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot>
<ovirt-vm:launchPaused>false</ovirt-vm:launchPaused>
<ovirt-vm:memGuaranteedSize type="int">4096</ovirt-vm:memGuaranteedSize>
<ovirt-vm:minGuaranteedMemoryMb type="int">4096</ovirt-vm:minGuaranteedMemoryMb>
<ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior>
<ovirt-vm:startTime type="float">1628558564.8754532</ovirt-vm:startTime>
<ovirt-vm:device alias="ua-7c9f38e9-8889-46c8-83bb-92efb9272de9" mac_address="56:6f:16:a8:00:07">
<ovirt-vm:network>ovirtmgmt</ovirt-vm:network>
<ovirt-vm:custom>
<ovirt-vm:queues>2</ovirt-vm:queues>
</ovirt-vm:custom>
</ovirt-vm:device>
<ovirt-vm:device devtype="disk" name="sda">
<ovirt-vm:domainID>6ce3b498-532e-4dc0-9e22-15d0bb24166a</ovirt-vm:domainID>
<ovirt-vm:guestName>/dev/sda</ovirt-vm:guestName>
<ovirt-vm:imageID>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</ovirt-vm:imageID>
<ovirt-vm:managed type="bool">False</ovirt-vm:managed>
<ovirt-vm:poolID>4ca6e0e8-e3a4-11eb-8830-480fcf63834f</ovirt-vm:poolID>
<ovirt-vm:volumeID>a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4</ovirt-vm:volumeID>
<ovirt-vm:volumeChain>
<ovirt-vm:volumeChainNode>
<ovirt-vm:domainID>6ce3b498-532e-4dc0-9e22-15d0bb24166a</ovirt-vm:domainID>
<ovirt-vm:imageID>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</ovirt-vm:imageID>
<ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset>
<ovirt-vm:leasePath>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/4425404b-17f0-4519-812f-b09a952a9003.lease</ovirt-vm:leasePath>
<ovirt-vm:path>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/4425404b-17f0-4519-812f-b09a952a9003</ovirt-vm:path>
<ovirt-vm:volumeID>4425404b-17f0-4519-812f-b09a952a9003</ovirt-vm:volumeID>
</ovirt-vm:volumeChainNode>
<ovirt-vm:volumeChainNode>
<ovirt-vm:domainID>6ce3b498-532e-4dc0-9e22-15d0bb24166a</ovirt-vm:domainID>
<ovirt-vm:imageID>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</ovirt-vm:imageID>
<ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset>
<ovirt-vm:leasePath>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4.lease</ovirt-vm:leasePath>
<ovirt-vm:path>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4</ovirt-vm:path>
<ovirt-vm:volumeID>a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4</ovirt-vm:volumeID>
</ovirt-vm:volumeChainNode>
</ovirt-vm:volumeChain>
</ovirt-vm:device>
<ovirt-vm:device devtype="disk" name="sdc">
<ovirt-vm:managed type="bool">False</ovirt-vm:managed>
</ovirt-vm:device>
</ovirt-vm:vm>
</metadata>
<maxMemory slots='16' unit='KiB'>16777216</maxMemory>
<memory unit='KiB'>4194304</memory>
<currentMemory unit='KiB'>4194304</currentMemory>
<vcpu placement='static' current='2'>16</vcpu>
<resource>
<partition>/machine</partition>
</resource>
<sysinfo type='smbios'>
<system>
<entry name='manufacturer'>oVirt</entry>
<entry name='product'>RHEL</entry>
<entry name='version'>8.4-1.2105.el8</entry>
<entry name='serial'>83e66af8-0500-11e6-9c43-bc00007c0000</entry>
<entry name='uuid'>59a7461c-72fe-4e01-86a7-c70243f31596</entry>
<entry name='family'>oVirt</entry>
</system>
</sysinfo>
<os>
<type arch='x86_64' machine='pc-q35-rhel8.4.0'>hvm</type>
<boot dev='hd'/>
<smbios mode='sysinfo'/>
</os>
<features>
<acpi/>
</features>
<cpu mode='custom' match='exact' check='full'>
<model fallback='forbid'>Skylake-Client-noTSX-IBRS</model>
<topology sockets='16' dies='1' cores='1' threads='1'/>
<feature policy='require' name='ssbd'/>
<feature policy='require' name='md-clear'/>
<feature policy='disable' name='mpx'/>
<feature policy='require' name='hypervisor'/>
<numa>
<cell id='0' cpus='0-15' memory='4194304' unit='KiB'/>
</numa>
</cpu>
<clock offset='variable' adjustment='0' basis='utc'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<pm>
<suspend-to-mem enabled='no'/>
<suspend-to-disk enabled='no'/>
</pm>
<devices>
<emulator>/usr/libexec/qemu-kvm</emulator>
<disk type='file' device='cdrom'>
<driver name='qemu' error_policy='report'/>
<source startupPolicy='optional'/>
<target dev='sdc' bus='sata'/>
<readonly/>
<alias name='ua-df0ac774-3623-4868-8bd3-45c8f2aa3dc4'/>
<address type='drive' controller='0' bus='0' target='0' unit='2'/>
</disk>
<disk type='file' device='disk' snapshot='no'>
<driver name='qemu' type='qcow2' cache='none' error_policy='stop' io='threads'/>
<source file='/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4' index='8'>
<seclabel model='dac' relabel='no'/>
</source>
<backingStore type='file' index='1'>
<format type='qcow2'/>
<source file='/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/4425404b-17f0-4519-812f-b09a952a9003'>
<seclabel model='dac' relabel='no'/>
</source>
<backingStore/>
</backingStore>
<target dev='sda' bus='scsi'/>
<serial>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</serial>
<alias name='ua-bee44276-234f-4ed7-8a8a-d90a5e3cb5b3'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='pci' index='1' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='1' port='0x10'/>
<alias name='pci.1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
</controller>
<controller type='pci' index='2' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='2' port='0x11'/>
<alias name='pci.2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
</controller>
<controller type='pci' index='3' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='3' port='0x12'/>
<alias name='pci.3'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
</controller>
<controller type='pci' index='4' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='4' port='0x13'/>
<alias name='pci.4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
</controller>
<controller type='pci' index='5' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='5' port='0x14'/>
<alias name='pci.5'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
</controller>
<controller type='pci' index='6' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='6' port='0x15'/>
<alias name='pci.6'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/>
</controller>
<controller type='pci' index='7' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='7' port='0x16'/>
<alias name='pci.7'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/>
</controller>
<controller type='pci' index='8' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='8' port='0x17'/>
<alias name='pci.8'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/>
</controller>
<controller type='pci' index='9' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='9' port='0x18'/>
<alias name='pci.9'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/>
</controller>
<controller type='pci' index='10' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='10' port='0x19'/>
<alias name='pci.10'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/>
</controller>
<controller type='pci' index='11' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='11' port='0x1a'/>
<alias name='pci.11'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/>
</controller>
<controller type='pci' index='12' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='12' port='0x1b'/>
<alias name='pci.12'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/>
</controller>
<controller type='pci' index='13' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='13' port='0x1c'/>
<alias name='pci.13'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/>
</controller>
<controller type='pci' index='14' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='14' port='0x1d'/>
<alias name='pci.14'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/>
</controller>
<controller type='pci' index='15' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='15' port='0x1e'/>
<alias name='pci.15'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x6'/>
</controller>
<controller type='pci' index='16' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='16' port='0x1f'/>
<alias name='pci.16'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x7'/>
</controller>
<controller type='pci' index='0' model='pcie-root'>
<alias name='pcie.0'/>
</controller>
<controller type='sata' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
</controller>
<controller type='virtio-serial' index='0' ports='16'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</controller>
<controller type='scsi' index='0' model='virtio-scsi'>
<alias name='ua-82c49f93-c4e8-460b-bb7d-95db0e9d87a0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</controller>
<controller type='usb' index='0' model='qemu-xhci' ports='8'>
<alias name='ua-ad56daea-edb1-45c7-a1ab-2a7db3aaeee2'/>
<address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='56:6f:16:a8:00:07'/>
<source bridge='ovirtmgmt'/>
<target dev='vnet0'/>
<model type='virtio'/>
<driver name='vhost' queues='2'/>
<filterref filter='vdsm-no-mac-spoofing'/>
<link state='up'/>
<mtu size='1500'/>
<alias name='ua-7c9f38e9-8889-46c8-83bb-92efb9272de9'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</interface>
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channels/59a7461c-72fe-4e01-86a7-c70243f31596.ovirt-guest-agent.0'/>
<target type='virtio' name='ovirt-guest-agent.0' state='disconnected'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channels/59a7461c-72fe-4e01-86a7-c70243f31596.org.qemu.guest_agent.0'/>
<target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
<alias name='channel1'/>
<address type='virtio-serial' controller='0' bus='0' port='2'/>
</channel>
<channel type='spicevmc'>
<target type='virtio' name='com.redhat.spice.0' state='disconnected'/>
<alias name='channel2'/>
<address type='virtio-serial' controller='0' bus='0' port='3'/>
</channel>
<input type='tablet' bus='usb'>
<alias name='input0'/>
<address type='usb' bus='0' port='1'/>
</input>
<input type='mouse' bus='ps2'>
<alias name='input1'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input2'/>
</input>
<graphics type='vnc' port='5900' autoport='yes' listen='192.168.7.18' keymap='en-us' passwdValidTo='1970-01-01T00:00:01'>
<listen type='network' address='192.168.7.18' network='vdsm-ovirtmgmt'/>
</graphics>
<graphics type='spice' port='5901' tlsPort='5902' autoport='yes' listen='192.168.7.18' passwdValidTo='1970-01-01T00:00:01'>
<listen type='network' address='192.168.7.18' network='vdsm-ovirtmgmt'/>
<channel name='main' mode='secure'/>
<channel name='display' mode='secure'/>
<channel name='inputs' mode='secure'/>
<channel name='cursor' mode='secure'/>
<channel name='playback' mode='secure'/>
<channel name='record' mode='secure'/>
<channel name='smartcard' mode='secure'/>
<channel name='usbredir' mode='secure'/>
</graphics>
<video>
<model type='qxl' ram='65536' vram='8192' vgamem='16384' heads='1' primary='yes'/>
<alias name='ua-799f065a-b2b9-4e37-a502-f86c7cc8dc51'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
</video>
<memballoon model='virtio'>
<stats period='5'/>
<alias name='ua-c2bfe0b9-065a-46b7-9b0b-ef7e0f699611'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
</memballoon>
<rng model='virtio'>
<backend model='random'>/dev/urandom</backend>
<alias name='ua-fa110e6b-5eed-4b4b-93d8-0ac5de08aa2e'/>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
</rng>
</devices>
<seclabel type='dynamic' model='selinux' relabel='yes'>
<label>system_u:system_r:svirt_t:s0:c437,c650</label>
<imagelabel>system_u:object_r:svirt_image_t:s0:c437,c650</imagelabel>
</seclabel>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+107:+107</label>
<imagelabel>+107:+107</imagelabel>
</seclabel>
<qemu:capabilities>
<qemu:add capability='blockdev'/>
<qemu:add capability='incremental-backup'/>
</qemu:capabilities>
</domain>
}, log id: 7eb54202
Here is the engine log when deleting the pvc:
2021-08-20 17:43:12,964 - cinder.volume.driver - INFO - Driver hasn't implemented _init_vendor_properties()
2021-08-20 17:43:12,990 - cinderlib-client - INFO - Deleting volume '63a64445-1659-4d5f-8847-e7266e64b09e' [feefc62f-e7cb-435d-ae21-4b52b53fbdfa]
2021-08-20 17:43:28,856 - cinder.volume.drivers.rbd - WARNING - ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed.
2021-08-20 17:43:28,900 - cinderlib-client - ERROR - Failure occurred when trying to run command 'delete_volume': ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed. [feefc62f-e7cb-435d-ae21-4b52b53fbdfa]
2021-08-20 17:43:28,901 - cinder - CRITICAL - Unhandled error
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 1195, in delete_volume
_try_remove_volume(client, volume_name)
File "/usr/lib/python3.6/site-packages/cinder/utils.py", line 683, in _wrapper
return r.call(f, *args, **kwargs)
File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 409, in call
do = self.iter(retry_state=retry_state)
File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 368, in iter
raise retry_exc.reraise()
File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 186, in reraise
raise self.last_attempt.result()
File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 425, in result
return self.__get_result()
File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 384, in __get_result
raise self._exception
File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 412, in call
result = fn(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 1190, in _try_remove_volume
self.RBDProxy().remove(client.ioctx, volume_name)
File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 190, in doit
result = proxy_call(self._autowrap, f, *args, **kwargs)
File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 148, in proxy_call
rv = execute(f, *args, **kwargs)
File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 129, in execute
six.reraise(c, e, tb)
File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise
raise value
File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 83, in tworker
rv = meth(*args, **kwargs)
File "rbd.pyx", line 767, in rbd.RBD.remove
rbd.ImageBusy: [errno 16] RBD image is busy (error removing image)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./cinderlib-client.py", line 170, in main
args.command(args)
File "./cinderlib-client.py", line 218, in delete_volume
vol.delete()
File "/usr/local/lib/python3.6/site-packages/cinderlib/objects.py", line 494, in delete
self._raise_with_resource()
File "/usr/local/lib/python3.6/site-packages/cinderlib/objects.py", line 222, in _raise_with_resource
six.reraise(*exc_info)
File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise
raise value
File "/usr/local/lib/python3.6/site-packages/cinderlib/objects.py", line 487, in delete
self.backend.driver.delete_volume(self._ovo)
File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 1205, in delete_volume
raise exception.VolumeIsBusy(msg, volume_name=volume_name)
cinder.exception.VolumeIsBusy: ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./cinderlib-client.py", line 390, in <module>
sys.exit(main(sys.argv[1:]))
File "./cinderlib-client.py", line 176, in main
sys.stderr.write(traceback.format_exc(e))
File "/usr/lib64/python3.6/traceback.py", line 167, in format_exc
return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain))
File "/usr/lib64/python3.6/traceback.py", line 121, in format_exception
type(value), value, tb, limit=limit).format(chain=chain))
File "/usr/lib64/python3.6/traceback.py", line 498, in __init__
_seen=_seen)
File "/usr/lib64/python3.6/traceback.py", line 509, in __init__
capture_locals=capture_locals)
File "/usr/lib64/python3.6/traceback.py", line 338, in extract
if limit >= 0:
TypeError: '>=' not supported between instances of 'VolumeIsBusy' and 'int'
3 years, 4 months
