Hi List, I see the same issue on my CentOS Stream 8 hosts and engine. I'm running 4.4.10. My systems are all migrated from CentOS 8 to CentOS Stream 8. Might this be caused by that? Best regards Christoph Am 20.02.22 um 19:58 schrieb Gilboa Davara:

I managed to upgrade a couple of 8-streams based clusters w/ --nobest, and thus far, I've yet to experience any issues (knocks wood feaviously).

- Gilboa

On Sat, Feb 19, 2022 at 3:21 PM Daniel McCoshen <upstagecoronet@gmail.com> wrote:

Hey all, I'm running ovirt 4.4 in production (4.4.5-11-1.el8), and I'm attempting to update the OS on my hosts. The hosts are all centos 8 stream, and dnf update is failing on all of them with the following output:

[root@ovirthost ~]# dnf update Last metadata expiration check: 1:36:32 ago on Thu 17 Feb 2022 12:01:25 PM CST. Error:  Problem: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires ansible, but none of the providers can be installed   - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-1.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.17-1.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.18-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.20-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.21-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.23-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.24-2.el8.noarch   - cannot install the best update candidate for package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch   - cannot install the best update candidate for package ansible-2.9.27-2.el8.noarch   - package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering   - package ansible-2.9.16-1.el8.noarch is filtered out by exclude filtering   - package ansible-2.9.19-1.el8.noarch is filtered out by exclude filtering   - package ansible-2.9.23-1.el8.noarch is filtered out by exclude filtering (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

cockpit-ovirt-dashboard.noarch is at 0.15.1-1.el8, and it looks like that conflicting ansible-core package was added to the 8-stream repo two days ago. That's when I first noticed the issue, but I it might be older. When the eariler issues with the centos 8 deprecation happened, I had swapped out the repos on some of these hosts for the new ones, and have since added new hosts as well, using the updated repos. Both hosts that had been moved from the old repos, and ones created with the new repos are experienceing this issue.

ansible-core is being pulled from the centos 8 stream AppStream repo, and the ansible package that cockpit-ovirt-dashboard.noarch is trying to use as a dependency is comming from ovirt-4.4-centos-ovirt44

I'm tempted to blacklist ansible-core in my dnf conf, but that seems like a hacky work-around and not the actual fix here. Thanks, Dan _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/3N4ZO6LXNOQNQU...

_______________________________________________ Users mailing list --users@ovirt.org To unsubscribe send an email tousers-leave@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/YJ336275NTG4M4...

Just a warning, adding --allowerasing on my engine causes ovirt-engine and a bunch of other ovirt-* packages to be removed. So make sure you check the yum output carefully before running the command. On Wed, 23 Mar 2022, Jillian Morgan wrote:

I had to add --allowerasing to my dnf update command to get it to go through (which it did, cleanly removing the old ansible package and replacing it with ansible-core). I suspect that the new ansible-core package doesn't properly obsolete the older ansible package. Trying to Upgrade hosts from the Admin portal would fail because of this requirement.

As a side note, my systems hadn't been updated since before the mirrors for Centos 8 packages went away, so all updates failed due to failure downloading mirrorlists. I had to do this first, to get the updated repo files pointing to Centos 8 Stream packages:

dnf update --disablerepo ovirt-4.4-* ovirt-realease44

-- Jillian Morgan (she/her) 🏳️‍⚧️ Systems & Networking Specialist Primordial Software Group & I.T. Consultancy https://www.primordial.ca

On Wed, Mar 23, 2022 at 3:53 PM Christoph Timm <ovirt@timmi.org> wrote: Hi List,

I see the same issue on my CentOS Stream 8 hosts and engine. I'm running 4.4.10. My systems are all migrated from CentOS 8 to CentOS Stream 8. Might this be caused by that?

Best regards Christoph

Am 20.02.22 um 19:58 schrieb Gilboa Davara: I managed to upgrade a couple of 8-streams based clusters w/ --nobest, and thus far, I've yet to experience any issues (knocks wood feaviously).

- Gilboa

On Sat, Feb 19, 2022 at 3:21 PM Daniel McCoshen <upstagecoronet@gmail.com> wrote: Hey all, I'm running ovirt 4.4 in production (4.4.5-11-1.el8), and I'm attempting to update the OS on my hosts. The hosts are all centos 8 stream, and dnf update is failing on all of them with the following output:

[root@ovirthost ~]# dnf update Last metadata expiration check: 1:36:32 ago on Thu 17 Feb 2022 12:01:25 PM CST. Error:  Problem: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires ansible, but none of the providers can be installed   - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-1.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.17-1.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.18-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.20-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.21-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.23-2.el8.noarch   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.24-2.el8.noarch   - cannot install the best update candidate for package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch   - cannot install the best update candidate for package ansible-2.9.27-2.el8.noarch   - package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering   - package ansible-2.9.16-1.el8.noarch is filtered out by exclude filtering   - package ansible-2.9.19-1.el8.noarch is filtered out by exclude filtering   - package ansible-2.9.23-1.el8.noarch is filtered out by exclude filtering (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

cockpit-ovirt-dashboard.noarch is at 0.15.1-1.el8, and it looks like that conflicting ansible-core package was added to the 8-stream repo two days ago. That's when I first noticed the issue, but I it might be older. When the eariler issues with the centos 8 deprecation happened, I had swapped out the repos on some of these hosts for the new ones, and have since added new hosts as well, using the updated repos. Both hosts that had been moved from the old repos, and ones created with the new repos are experienceing this issue.

ansible-core is being pulled from the centos 8 stream AppStream repo, and the ansible package that cockpit-ovirt-dashboard.noarch is trying to use as a dependency is comming from ovirt-4.4-centos-ovirt44

I'm tempted to blacklist ansible-core in my dnf conf, but that seems like a hacky work-around and not the actual fix here. Thanks, Dan _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/3N4ZO6LXNOQNQ U5HHDGNOZHDSO4IBGFF/

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guide lines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message /YJ336275NTG4M4AUOBTJNBZ3RD2L6HXA/

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/YZSDKGFDHRXVY 2S2WKW4XFQOAGUZ4HLQ/

Good morning, please note that I have performed some tests and I'm quite sure that oVirt is not compatible with ansible-core-2.12. I run into issues with hosts installation and the check for updates results into a Null pointer exception. So I have reverted back to ansible-2.9 which is also provided from the oVirt repositories. Guess the OS (CentOS Stream 8) is providing already a newer version which is not working for oVirt. Best regards Christoph Am 24.03.22 um 03:43 schrieb Sketch:

Just for the record, I fixed this with:

# rpm -e ansible --nodeps # dnf install ansible

Now dnf update works as expected without errors or removing any packages.

I haven't encounted this issue on my hosts because they are running Rocky, not Stream.

On Thu, 24 Mar 2022, Sketch wrote:

...

Just a warning, adding --allowerasing on my engine causes ovirt-engine and a bunch of other ovirt-* packages to be removed.  So make sure you check the yum output carefully before running the command.

On Wed, 23 Mar 2022, Jillian Morgan wrote:

...

 I had to add --allowerasing to my dnf update command to get it to go  through  (which it did, cleanly removing the old ansible package and replacing it  with ansible-core). I suspect that the new ansible-core package doesn't  properly obsolete the older ansible package. Trying to Upgrade hosts from  the Admin portal would fail because of this requirement.

 As a side note, my systems hadn't been updated since before the mirrors  for  Centos 8 packages went away, so all updates failed due to failure  downloading mirrorlists. I had to do this first, to get the updated repo  files pointing to Centos 8 Stream packages:

 dnf update --disablerepo ovirt-4.4-* ovirt-realease44

 --  Jillian Morgan (she/her) 🏳️‍⚧️  Systems & Networking Specialist  Primordial Software Group & I.T. Consultancy  https://www.primordial.ca

 On Wed, Mar 23, 2022 at 3:53 PM Christoph Timm <ovirt@timmi.org> wrote:        Hi List,

       I see the same issue on my CentOS Stream 8 hosts and engine.        I'm running 4.4.10.        My systems are all migrated from CentOS 8 to CentOS Stream 8.        Might this be caused by that?

       Best regards        Christoph

       Am 20.02.22 um 19:58 schrieb Gilboa Davara:        I managed to upgrade a couple of 8-streams based clusters        w/ --nobest, and thus far, I've yet to experience any        issues (knocks wood feaviously).

 - Gilboa

 On Sat, Feb 19, 2022 at 3:21 PM Daniel McCoshen  <upstagecoronet@gmail.com> wrote:        Hey all,        I'm running ovirt 4.4 in production        (4.4.5-11-1.el8), and I'm attempting to update the        OS on my hosts. The hosts are all centos 8 stream,        and dnf update is failing on all of them with the        following output:

       [root@ovirthost ~]# dnf update        Last metadata expiration check: 1:36:32 ago on Thu        17 Feb 2022 12:01:25 PM CST.        Error:         Problem: package        cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires        ansible, but none of the providers can be installed          - package ansible-2.9.27-2.el8.noarch conflicts        with ansible-core > 2.11.0 provided by        ansible-core-2.12.2-2.el8.x86_64          - package ansible-core-2.12.2-2.el8.x86_64        obsoletes ansible < 2.10.0 provided by        ansible-2.9.27-2.el8.noarch          - package ansible-core-2.12.2-2.el8.x86_64        obsoletes ansible < 2.10.0 provided by        ansible-2.9.27-1.el8.noarch          - package ansible-core-2.12.2-2.el8.x86_64        obsoletes ansible < 2.10.0 provided by        ansible-2.9.17-1.el8.noarch          - package ansible-core-2.12.2-2.el8.x86_64        obsoletes ansible < 2.10.0 provided by        ansible-2.9.18-2.el8.noarch          - package ansible-core-2.12.2-2.el8.x86_64        obsoletes ansible < 2.10.0 provided by        ansible-2.9.20-2.el8.noarch          - package ansible-core-2.12.2-2.el8.x86_64        obsoletes ansible < 2.10.0 provided by        ansible-2.9.21-2.el8.noarch          - package ansible-core-2.12.2-2.el8.x86_64        obsoletes ansible < 2.10.0 provided by        ansible-2.9.23-2.el8.noarch          - package ansible-core-2.12.2-2.el8.x86_64        obsoletes ansible < 2.10.0 provided by        ansible-2.9.24-2.el8.noarch          - cannot install the best update candidate for        package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch          - cannot install the best update candidate for        package ansible-2.9.27-2.el8.noarch          - package ansible-2.9.20-1.el8.noarch is filtered        out by exclude filtering          - package ansible-2.9.16-1.el8.noarch is filtered        out by exclude filtering          - package ansible-2.9.19-1.el8.noarch is filtered        out by exclude filtering          - package ansible-2.9.23-1.el8.noarch is filtered        out by exclude filtering        (try to add '--allowerasing' to command line to        replace conflicting packages or '--skip-broken' to        skip uninstallable packages or '--nobest' to use not        only best candidate packages)

       cockpit-ovirt-dashboard.noarch is at 0.15.1-1.el8,        and it looks like that conflicting ansible-core        package was added to the 8-stream repo two days ago.        That's when I first noticed the issue, but I it        might be older. When the eariler issues with the        centos 8 deprecation happened, I had swapped out the        repos on some of these hosts for the new ones, and        have since added new hosts as well, using the        updated repos. Both hosts that had been moved from        the old repos, and ones created with the new repos        are experienceing this issue.

       ansible-core is being pulled from the centos 8        stream AppStream repo, and the ansible package that        cockpit-ovirt-dashboard.noarch is trying to use as a        dependency is comming from ovirt-4.4-centos-ovirt44

       I'm tempted to blacklist ansible-core in my dnf        conf, but that seems like a hacky work-around and        not the actual fix here.        Thanks,        Dan        _______________________________________________        Users mailing list -- users@ovirt.org        To unsubscribe send an email to        users-leave@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/3N4ZO6LXNOQNQ        U5HHDGNOZHDSO4IBGFF/

 _______________________________________________  Users mailing list -- users@ovirt.org  To unsubscribe send an email to users-leave@ovirt.org  Privacy Statement: https://www.ovirt.org/privacy-policy.html  oVirt Code of Conduct:  https://www.ovirt.org/community/about/community-guide  lines/  List Archives:  https://lists.ovirt.org/archives/list/users@ovirt.org/message  /YJ336275NTG4M4AUOBTJNBZ3RD2L6HXA/

 _______________________________________________  Users mailing list -- users@ovirt.org  To unsubscribe send an email to users-leave@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/YZSDKGFDHRXVY

 2S2WKW4XFQOAGUZ4HLQ/

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/TGWZDDZECQMN7A...

Hi, oVirt 4.4 requires ansible 2.9, it cannot work with any newer version of ansible because of deep changes in ansible between ansible 2.9 and 2.10. We are preparing upgrade to ansible-core-2.12 in oVirt 4.5, the process is tracked by https://bugzilla.redhat.com/show_bug.cgi?id=2065052 So if you need to perform package updates manually before oVirt 4.5 is released, then please use: dnf update -x ansible -x ansible-core Regards, Martin On Fri, Mar 25, 2022 at 7:47 AM Christoph Timm <ovirt@timmi.org> wrote:

Good morning,

please note that I have performed some tests and I'm quite sure that oVirt is not compatible with ansible-core-2.12. I run into issues with hosts installation and the check for updates results into a Null pointer exception.

So I have reverted back to ansible-2.9 which is also provided from the oVirt repositories. Guess the OS (CentOS Stream 8) is providing already a newer version which is not working for oVirt.

Best regards Christoph

Am 24.03.22 um 03:43 schrieb Sketch:

...

Just for the record, I fixed this with:

# rpm -e ansible --nodeps # dnf install ansible

Now dnf update works as expected without errors or removing any packages.

I haven't encounted this issue on my hosts because they are running Rocky, not Stream.

On Thu, 24 Mar 2022, Sketch wrote:

...

Just a warning, adding --allowerasing on my engine causes ovirt-engine and a bunch of other ovirt-* packages to be removed. So make sure you check the yum output carefully before running the command.

On Wed, 23 Mar 2022, Jillian Morgan wrote:

...

I had to add --allowerasing to my dnf update command to get it to go through (which it did, cleanly removing the old ansible package and replacing it with ansible-core). I suspect that the new ansible-core package doesn't properly obsolete the older ansible package. Trying to Upgrade hosts from the Admin portal would fail because of this requirement.

As a side note, my systems hadn't been updated since before the mirrors for Centos 8 packages went away, so all updates failed due to failure downloading mirrorlists. I had to do this first, to get the updated repo files pointing to Centos 8 Stream packages:

dnf update --disablerepo ovirt-4.4-* ovirt-realease44

-- Jillian Morgan (she/her) 🏳️‍⚧️ Systems & Networking Specialist Primordial Software Group & I.T. Consultancy https://www.primordial.ca

On Wed, Mar 23, 2022 at 3:53 PM Christoph Timm <ovirt@timmi.org> wrote: Hi List,

I see the same issue on my CentOS Stream 8 hosts and engine. I'm running 4.4.10. My systems are all migrated from CentOS 8 to CentOS Stream 8. Might this be caused by that?

Best regards Christoph

Am 20.02.22 um 19:58 schrieb Gilboa Davara: I managed to upgrade a couple of 8-streams based clusters w/ --nobest, and thus far, I've yet to experience any issues (knocks wood feaviously).

- Gilboa

On Sat, Feb 19, 2022 at 3:21 PM Daniel McCoshen <upstagecoronet@gmail.com> wrote: Hey all, I'm running ovirt 4.4 in production (4.4.5-11-1.el8), and I'm attempting to update the OS on my hosts. The hosts are all centos 8 stream, and dnf update is failing on all of them with the following output:

[root@ovirthost ~]# dnf update Last metadata expiration check: 1:36:32 ago on Thu 17 Feb 2022 12:01:25 PM CST. Error: Problem: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires ansible, but none of the providers can be installed - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64 - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.17-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.18-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.20-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.21-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.23-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.24-2.el8.noarch - cannot install the best update candidate for package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch - cannot install the best update candidate for package ansible-2.9.27-2.el8.noarch - package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.16-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.19-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.23-1.el8.noarch is filtered out by exclude filtering (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

cockpit-ovirt-dashboard.noarch is at 0.15.1-1.el8, and it looks like that conflicting ansible-core package was added to the 8-stream repo two days ago. That's when I first noticed the issue, but I it might be older. When the eariler issues with the centos 8 deprecation happened, I had swapped out the repos on some of these hosts for the new ones, and have since added new hosts as well, using the updated repos. Both hosts that had been moved from the old repos, and ones created with the new repos are experienceing this issue.

ansible-core is being pulled from the centos 8 stream AppStream repo, and the ansible package that cockpit-ovirt-dashboard.noarch is trying to use as a dependency is comming from ovirt-4.4-centos-ovirt44

I'm tempted to blacklist ansible-core in my dnf conf, but that seems like a hacky work-around and not the actual fix here. Thanks, Dan _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/3N4ZO6LXNOQNQ U5HHDGNOZHDSO4IBGFF/

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guide lines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message /YJ336275NTG4M4AUOBTJNBZ3RD2L6HXA/

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/YZSDKGFDHRXVY

2S2WKW4XFQOAGUZ4HLQ/

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/TGWZDDZECQMN7A...

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/KLZ3IXJS6YDFGY...

-- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.