from:"Christoph Timm"

[ovirt-users] Re: Ovirt-node don't communicate with qemu-agent

2022-12-27 Thread Christoph Timm


Hi Arik,

I have checked the installed version of VDSM:
vdsm.x86_64 4.50.3.4-1.el8 @centos-ovirt45

I also refreshed the repos and don't see any update for the VDSM. Looks 
like that this version have not been released yet.


Best regards
Christoph

Am 27.12.22 um 12:25 schrieb Christoph Timm:

No this is on none of my 6 hosts.

/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py

    def _qga_call_get_vcpus(self, vm):
    try:
    self.log.debug('Requesting guest CPU info for vm=%s', vm.id)
    with vm.qga_context(_COMMAND_TIMEOUT):
    vcpus = QemuGuestAgentDomain(vm).guestVcpus()
    except (exception.NonResponsiveGuestAgent, 
libvirt.libvirtError) as e:
    self.log.info('Failed to get guest CPU info for vm=%s, 
error: %s',

  vm.id, e)
    self.set_failure(vm.id)
    return {}
    except virdomain.NotConnectedError:
    self.log.debug(
    'Not querying QEMU-GA for guest CPU info because domain'
    'is not running for vm-id=%s', vm.id)
    return {}
    if 'online' in vcpus:
    count = len(taskset.cpulist_parse(vcpus['online']))
    else:
    count = -1
    return {'guestCPUCount': count}


Am 27.12.22 um 12:17 schrieb Arik Hadas:



On Tue, Dec 27, 2022 at 12:52 PM Christoph Timm  wrote:

No for me with 4.5.4-1.el8


Do you see the same error in the vdsm log?
The stacktrace below suggests that the fix is not included there, see:
https://github.com/oVirt/vdsm/blob/v4.50.4.1/lib/vdsm/virt/qemuguestagent.py#L797 




Am 27.12.22 um 11:22 schrieb Arik Hadas:



On Tue, Dec 27, 2022 at 11:50 AM Christoph Timm
 wrote:

Hi Fernando,

I have also from time to time this issue.

I can see the following in the vdsm.log if the issue occurs:

2022-12-27 10:38:22,473+0100 ERROR (qgapoller/3)
[virt.periodic.Operation] > operation failed (periodic:187)
Traceback (most recent call last):
  File
"/usr/lib/python3.6/site-packages/vdsm/virt/periodic.py",
line 185, in __call__
    self._func()
  File
"/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py",
line 476, in _poller
    vm_id, self._qga_call_get_vcpus(vm_obj))
  File
"/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py",
line 797, in _qga_call_get_vcpus
    if 'online' in vcpus:
TypeError: argument of type 'NoneType' is not iterable


This should have been resolved by
https://github.com/oVirt/vdsm/pull/350



I had this also in older versions so this is nothing new for me.
Sometimes I can solve it with putting the host in
maintenance. But it is coming back after a while.


Best regards
Christoph

Am 19.12.22 um 19:22 schrieb Fernando Hallberg:

Hi all,

I reinstalled one of the ovirt-nodes, with ovirt-4.5.4, and
after the reinstallation the agents of the vms connected to
this node cannot communicate with the ovirt-engine.

ovirt-engine 4.5.4

any idea?

VMs work perfectly, but the agent doesn't communicate.

Best regards,

Fernando Hallberg



___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/KCCPQWTYU4D2EZFNRO77FNAKVFKWKFDA/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/LHQSH7AIOPVGG5IDANH4LBQALJRPW7KR/






___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/QHR2YGNY4HNZU227ID2CKRF5ZUXLLJB5/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/arch

[ovirt-users] Re: Ovirt-node don't communicate with qemu-agent

2022-12-27 Thread Christoph Timm


No this is on none of my 6 hosts.

/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py

    def _qga_call_get_vcpus(self, vm):
    try:
    self.log.debug('Requesting guest CPU info for vm=%s', vm.id)
    with vm.qga_context(_COMMAND_TIMEOUT):
    vcpus = QemuGuestAgentDomain(vm).guestVcpus()
    except (exception.NonResponsiveGuestAgent, 
libvirt.libvirtError) as e:
    self.log.info('Failed to get guest CPU info for vm=%s, 
error: %s',

  vm.id, e)
    self.set_failure(vm.id)
    return {}
    except virdomain.NotConnectedError:
    self.log.debug(
    'Not querying QEMU-GA for guest CPU info because domain'
    'is not running for vm-id=%s', vm.id)
    return {}
    if 'online' in vcpus:
    count = len(taskset.cpulist_parse(vcpus['online']))
    else:
    count = -1
    return {'guestCPUCount': count}


Am 27.12.22 um 12:17 schrieb Arik Hadas:



On Tue, Dec 27, 2022 at 12:52 PM Christoph Timm  wrote:

No for me with 4.5.4-1.el8


Do you see the same error in the vdsm log?
The stacktrace below suggests that the fix is not included there, see:
https://github.com/oVirt/vdsm/blob/v4.50.4.1/lib/vdsm/virt/qemuguestagent.py#L797 




Am 27.12.22 um 11:22 schrieb Arik Hadas:



On Tue, Dec 27, 2022 at 11:50 AM Christoph Timm 
wrote:

Hi Fernando,

I have also from time to time this issue.

I can see the following in the vdsm.log if the issue occurs:

2022-12-27 10:38:22,473+0100 ERROR (qgapoller/3)
[virt.periodic.Operation] > operation failed (periodic:187)
Traceback (most recent call last):
  File
"/usr/lib/python3.6/site-packages/vdsm/virt/periodic.py",
line 185, in __call__
    self._func()
  File
"/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py",
line 476, in _poller
    vm_id, self._qga_call_get_vcpus(vm_obj))
  File
"/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py",
line 797, in _qga_call_get_vcpus
    if 'online' in vcpus:
TypeError: argument of type 'NoneType' is not iterable


This should have been resolved by
https://github.com/oVirt/vdsm/pull/350



I had this also in older versions so this is nothing new for me.
Sometimes I can solve it with putting the host in
maintenance. But it is coming back after a while.


Best regards
Christoph

Am 19.12.22 um 19:22 schrieb Fernando Hallberg:

Hi all,

I reinstalled one of the ovirt-nodes, with ovirt-4.5.4, and
after the reinstallation the agents of the vms connected to
this node cannot communicate with the ovirt-engine.

ovirt-engine 4.5.4

any idea?

VMs work perfectly, but the agent doesn't communicate.

Best regards,

Fernando Hallberg



___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/KCCPQWTYU4D2EZFNRO77FNAKVFKWKFDA/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/LHQSH7AIOPVGG5IDANH4LBQALJRPW7KR/



___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QHR2YGNY4HNZU227ID2CKRF5ZUXLLJB5/

[ovirt-users] Re: Ovirt-node don't communicate with qemu-agent

2022-12-27 Thread Christoph Timm


No for me with 4.5.4-1.el8

Am 27.12.22 um 11:22 schrieb Arik Hadas:



On Tue, Dec 27, 2022 at 11:50 AM Christoph Timm  wrote:

Hi Fernando,

I have also from time to time this issue.

I can see the following in the vdsm.log if the issue occurs:

2022-12-27 10:38:22,473+0100 ERROR (qgapoller/3)
[virt.periodic.Operation] > operation failed (periodic:187)
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/virt/periodic.py",
line 185, in __call__
    self._func()
  File
"/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py",
line 476, in _poller
    vm_id, self._qga_call_get_vcpus(vm_obj))
  File
"/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py",
line 797, in _qga_call_get_vcpus
    if 'online' in vcpus:
TypeError: argument of type 'NoneType' is not iterable


This should have been resolved by https://github.com/oVirt/vdsm/pull/350



I had this also in older versions so this is nothing new for me.
Sometimes I can solve it with putting the host in maintenance. But
it is coming back after a while.


Best regards
Christoph

Am 19.12.22 um 19:22 schrieb Fernando Hallberg:

Hi all,

I reinstalled one of the ovirt-nodes, with ovirt-4.5.4, and after
the reinstallation the agents of the vms connected to this node
cannot communicate with the ovirt-engine.

ovirt-engine 4.5.4

any idea?

VMs work perfectly, but the agent doesn't communicate.

Best regards,

Fernando Hallberg



___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/KCCPQWTYU4D2EZFNRO77FNAKVFKWKFDA/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/LHQSH7AIOPVGG5IDANH4LBQALJRPW7KR/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/CJB5PKYSNFWKG47P4GKHYPJVM5DVP37I/

[ovirt-users] Re: Ovirt-node don't communicate with qemu-agent

2022-12-27 Thread Christoph Timm


Hi Fernando,

I have also from time to time this issue.

I can see the following in the vdsm.log if the issue occurs:

2022-12-27 10:38:22,473+0100 ERROR (qgapoller/3) 
[virt.periodic.Operation] 0x7fbdf00ced68>> operation failed (periodic:187)

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/virt/periodic.py", line 
185, in __call__

    self._func()
  File "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py", 
line 476, in _poller

    vm_id, self._qga_call_get_vcpus(vm_obj))
  File "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py", 
line 797, in _qga_call_get_vcpus

    if 'online' in vcpus:
TypeError: argument of type 'NoneType' is not iterable

I had this also in older versions so this is nothing new for me.
Sometimes I can solve it with putting the host in maintenance. But it is 
coming back after a while.


Best regards
Christoph

Am 19.12.22 um 19:22 schrieb Fernando Hallberg:

Hi all,

I reinstalled one of the ovirt-nodes, with ovirt-4.5.4, and after the 
reinstallation the agents of the vms connected to this node cannot 
communicate with the ovirt-engine.


ovirt-engine 4.5.4

any idea?

VMs work perfectly, but the agent doesn't communicate.

Best regards,

Fernando Hallberg



___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/KCCPQWTYU4D2EZFNRO77FNAKVFKWKFDA/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/LHQSH7AIOPVGG5IDANH4LBQALJRPW7KR/

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-22 Thread Christoph Timm


Hi all,

also the update of a CentOS Stream 8 host is not working.
Also here I have updated the centos-release-ovirt45 (8.7-3) package before.

Error:
 Problem: package rdo-openvswitch-1:2.15-2.el8.noarch requires 
network-scripts-openvswitch = 1:2.15, but none of the providers can be 
installed
  - cannot install both 
rdo-network-scripts-openvswitch-2:2.17-3.el8.noarch and 
rdo-network-scripts-openvswitch-1:2.15-2.el8.noarch
  - cannot install the best update candidate for package 
network-scripts-openvswitch2.15-2.15.0-115.el8s.x86_64

  - problem with installed package rdo-openvswitch-1:2.15-2.el8.noarch
(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)


The rdo-openvswitch is getting excluded with the new repo files. I guess 
also rdo-network-scripts-openvswitch needs to be excluded from that 
ovirt-45-centos-stream-openstack-yoga repo in case the version 2.15 
should be used.


dnf list | grep rdo-openvswitch
rdo-openvswitch.noarch 1:2.15-2.el8 @ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-devel.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-test.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga


The command "dnf update --refresh 
--exclude=rdo-network-scripts-openvswitch" would work on the host.


Best regards
Christoph

Am 21.10.22 um 10:55 schrieb Christoph Timm:

Hi all,

I updated my engine to 4.5.3.1 without any issues and want to update 
the self hosted engine (CentOS Stream 8).
There I run into the reported issues which I fix with the update of 
the please centos-release-ovirt45 package (8.7-3).
But still I have the issue with the ansible-core.2-13 which is not 
supported by the engine. Means dnf update is still failing.


Error:
 Problem: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with 
ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-engine-4.5.3.1-1.el8.noarch
  - cannot install the best update candidate for package 
ansible-core-2.12.7-1.el8.x86_64
(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)


As you can see the correct version is installed but appstream is 
already providing a newer version which needs to be excluded (I guess).

dnf list | grep ansible-core
ansible-core.x86_64 2.12.7-1.el8 @appstream
ansible-core.x86_64 2.13.3-1.el8 appstream

DNF looks happy if I run: dnf update --refresh --exclude=ansible-core

I guess it should be fine to run it like this?

Best regards
Christoph

Am 21.10.22 um 09:59 schrieb Martin Perina:

Hi Latchezar,

so there seems to be several issues according the error you have 
posted below:


1. ovirt-engine is not compatible with ansible-core-2.13 on EL8, so 
if this package is already installed on your machine, you need to 
downgrade it to ansible-core-2.12 before continuing with engine 
installation
2. If any of those rdo* packages are already installed on your 
machine, you need remote them manually before proceeding with engine 
installation
3. Please check that you really have installed only required 
repositories on your machine as mentioned in Installation guide:

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
4. Please make sure that you have installed the latest version of 
ovirt-release45, which is 4.5.3.1. This is the version which blocks 
RDO packages to interfere with oVirt


Regards,
Martin



On Fri, Oct 21, 2022 at 9:51 AM Latchezar Filtchev  
wrote:


Dear Martin,

Not getting e-mails from ovirt list is my local issue. I will
deal with this.

Async upgrade is OK. The update of Standalone engine/CentOS
Stream release 8 shows - Version 4.5.3.1-1.el8

When executing ‘dnf update’ on standalone engine – update fails -
the result is below. Do you thing manual elimination of
rdo-related will solve it?

Thank you!

Best,

Latcho

Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022
06:47:31 AM EEST.

Error:

 Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts
with ansible-core >= 2.13.0 provided by
ansible-core-2.13.3-1.el8.x86_64

- cannot install the best update candidate for package
ovirt-engine-4.5.3.1-1.el8.noarch

- cannot install the best update candidate for package
ansible-core-2.12.7-1.el8.x86_64

Problem 2: package ovirt-openvswitch-2.15-4.el8.noarch requires
openvswitch2.15, but none of the providers can be installed

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-119.el8s.x86_64

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Christoph Timm

OK after reading the message from Martin again I understood that the rdo 
packages should not be installed. By chance I picked one host with such 
packages installed.

I have removed them and update was successful.

So looks like the engine and the ansible-core looks like still a bit 
strange but I have excluded it manually for now on the engine.


Best regards
Christoph

Am 21.10.22 um 11:35 schrieb Christoph Timm:

Hi all,

also the update of a CentOS Stream 8 host is not working.
Also here I have updated the centos-release-ovirt45 (8.7-3) package 
before.


Error:
 Problem: package rdo-openvswitch-1:2.15-2.el8.noarch requires 
network-scripts-openvswitch = 1:2.15, but none of the providers can be 
installed
  - cannot install both 
rdo-network-scripts-openvswitch-2:2.17-3.el8.noarch and 
rdo-network-scripts-openvswitch-1:2.15-2.el8.noarch
  - cannot install the best update candidate for package 
network-scripts-openvswitch2.15-2.15.0-115.el8s.x86_64

  - problem with installed package rdo-openvswitch-1:2.15-2.el8.noarch
(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)


The rdo-openvswitch is getting excluded with the new repo files. I 
guess also rdo-network-scripts-openvswitch needs to be excluded from 
that ovirt-45-centos-stream-openstack-yoga repo in case the version 
2.15 should be used.


dnf list | grep rdo-openvswitch
rdo-openvswitch.noarch 1:2.15-2.el8 @ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-devel.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-test.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga


The command "dnf update --refresh 
--exclude=rdo-network-scripts-openvswitch" would work on the host.


Best regards
Christoph


Am 21.10.22 um 10:55 schrieb Christoph Timm:

Hi all,

I updated my engine to 4.5.3.1 without any issues and want to update 
the self hosted engine (CentOS Stream 8).
There I run into the reported issues which I fix with the update of 
the please centos-release-ovirt45 package (8.7-3).
But still I have the issue with the ansible-core.2-13 which is not 
supported by the engine. Means dnf update is still failing.


Error:
 Problem: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with 
ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-engine-4.5.3.1-1.el8.noarch
  - cannot install the best update candidate for package 
ansible-core-2.12.7-1.el8.x86_64
(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)


As you can see the correct version is installed but appstream is 
already providing a newer version which needs to be excluded (I guess).

dnf list | grep ansible-core
ansible-core.x86_64 2.12.7-1.el8 @appstream
ansible-core.x86_64 2.13.3-1.el8 appstream

DNF looks happy if I run: dnf update --refresh --exclude=ansible-core

I guess it should be fine to run it like this?

Best regards
Christoph

Am 21.10.22 um 09:59 schrieb Martin Perina:

Hi Latchezar,

so there seems to be several issues according the error you have 
posted below:


1. ovirt-engine is not compatible with ansible-core-2.13 on EL8, so 
if this package is already installed on your machine, you need to 
downgrade it to ansible-core-2.12 before continuing with engine 
installation
2. If any of those rdo* packages are already installed on your 
machine, you need remote them manually before proceeding with engine 
installation
3. Please check that you really have installed only required 
repositories on your machine as mentioned in Installation guide:

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
4. Please make sure that you have installed the latest version of 
ovirt-release45, which is 4.5.3.1. This is the version which blocks 
RDO packages to interfere with oVirt


Regards,
Martin



On Fri, Oct 21, 2022 at 9:51 AM Latchezar Filtchev  
wrote:


Dear Martin,

Not getting e-mails from ovirt list is my local issue. I will
deal with this.

Async upgrade is OK. The update of Standalone engine/CentOS
Stream release 8 shows - Version 4.5.3.1-1.el8

When executing ‘dnf update’ on standalone engine – update fails
- the result is below. Do you thing manual elimination of
rdo-related will solve it?

Thank you!

Best,

Latcho

Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022
06:47:31 AM EEST.

Error:

 Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts
with ansible-core >= 2.13.0 provided by
ansible-core-2.13.3-1.el8.x86_64

- cannot install the best update candidate for package

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Christoph Timm


Hi all,

also the update of a CentOS Stream 8 host is not working.
Also here I have updated the centos-release-ovirt45 (8.7-3) package before.

Error:
 Problem: package rdo-openvswitch-1:2.15-2.el8.noarch requires 
network-scripts-openvswitch = 1:2.15, but none of the providers can be 
installed
  - cannot install both 
rdo-network-scripts-openvswitch-2:2.17-3.el8.noarch and 
rdo-network-scripts-openvswitch-1:2.15-2.el8.noarch
  - cannot install the best update candidate for package 
network-scripts-openvswitch2.15-2.15.0-115.el8s.x86_64

  - problem with installed package rdo-openvswitch-1:2.15-2.el8.noarch
(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)


The rdo-openvswitch is getting excluded with the new repo files. I guess 
also rdo-network-scripts-openvswitch needs to be excluded from that 
ovirt-45-centos-stream-openstack-yoga repo in case the version 2.15 
should be used.


dnf list | grep rdo-openvswitch
rdo-openvswitch.noarch 1:2.15-2.el8 @ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-devel.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-test.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga


The command "dnf update --refresh 
--exclude=rdo-network-scripts-openvswitch" would work on the host.


Best regards
Christoph


Am 21.10.22 um 10:55 schrieb Christoph Timm:

Hi all,

I updated my engine to 4.5.3.1 without any issues and want to update 
the self hosted engine (CentOS Stream 8).
There I run into the reported issues which I fix with the update of 
the please centos-release-ovirt45 package (8.7-3).
But still I have the issue with the ansible-core.2-13 which is not 
supported by the engine. Means dnf update is still failing.


Error:
 Problem: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with 
ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-engine-4.5.3.1-1.el8.noarch
  - cannot install the best update candidate for package 
ansible-core-2.12.7-1.el8.x86_64
(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)


As you can see the correct version is installed but appstream is 
already providing a newer version which needs to be excluded (I guess).

dnf list | grep ansible-core
ansible-core.x86_64 2.12.7-1.el8 @appstream
ansible-core.x86_64 2.13.3-1.el8 appstream

DNF looks happy if I run: dnf update --refresh --exclude=ansible-core

I guess it should be fine to run it like this?

Best regards
Christoph

Am 21.10.22 um 09:59 schrieb Martin Perina:

Hi Latchezar,

so there seems to be several issues according the error you have 
posted below:


1. ovirt-engine is not compatible with ansible-core-2.13 on EL8, so 
if this package is already installed on your machine, you need to 
downgrade it to ansible-core-2.12 before continuing with engine 
installation
2. If any of those rdo* packages are already installed on your 
machine, you need remote them manually before proceeding with engine 
installation
3. Please check that you really have installed only required 
repositories on your machine as mentioned in Installation guide:

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
4. Please make sure that you have installed the latest version of 
ovirt-release45, which is 4.5.3.1. This is the version which blocks 
RDO packages to interfere with oVirt


Regards,
Martin



On Fri, Oct 21, 2022 at 9:51 AM Latchezar Filtchev  
wrote:


Dear Martin,

Not getting e-mails from ovirt list is my local issue. I will
deal with this.

Async upgrade is OK. The update of Standalone engine/CentOS
Stream release 8 shows - Version 4.5.3.1-1.el8

When executing ‘dnf update’ on standalone engine – update fails -
the result is below. Do you thing manual elimination of
rdo-related will solve it?

Thank you!

Best,

Latcho

Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022
06:47:31 AM EEST.

Error:

 Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts
with ansible-core >= 2.13.0 provided by
ansible-core-2.13.3-1.el8.x86_64

- cannot install the best update candidate for package
ovirt-engine-4.5.3.1-1.el8.noarch

- cannot install the best update candidate for package
ansible-core-2.12.7-1.el8.x86_64

Problem 2: package ovirt-openvswitch-2.15-4.el8.noarch requires
openvswitch2.15, but none of the providers can be installed

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-119.el8s.x86_64

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Christoph Timm


Hi all,

I updated my engine to 4.5.3.1 without any issues and want to update the 
self hosted engine (CentOS Stream 8).
There I run into the reported issues which I fix with the update of the 
please centos-release-ovirt45 package (8.7-3).
But still I have the issue with the ansible-core.2-13 which is not 
supported by the engine. Means dnf update is still failing.


Error:
 Problem: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with 
ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-engine-4.5.3.1-1.el8.noarch
  - cannot install the best update candidate for package 
ansible-core-2.12.7-1.el8.x86_64
(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)


As you can see the correct version is installed but appstream is already 
providing a newer version which needs to be excluded (I guess).

dnf list | grep ansible-core
ansible-core.x86_64 2.12.7-1.el8 @appstream
ansible-core.x86_64 
2.13.3-1.el8   appstream


DNF looks happy if I run: dnf update --refresh --exclude=ansible-core

I guess it should be fine to run it like this?

Best regards
Christoph

Am 21.10.22 um 09:59 schrieb Martin Perina:

Hi Latchezar,

so there seems to be several issues according the error you have 
posted below:


1. ovirt-engine is not compatible with ansible-core-2.13 on EL8, so if 
this package is already installed on your machine, you need to 
downgrade it to ansible-core-2.12 before continuing with engine 
installation
2. If any of those rdo* packages are already installed on your 
machine, you need remote them manually before proceeding with engine 
installation
3. Please check that you really have installed only required 
repositories on your machine as mentioned in Installation guide:

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
4. Please make sure that you have installed the latest version of 
ovirt-release45, which is 4.5.3.1. This is the version which blocks 
RDO packages to interfere with oVirt


Regards,
Martin



On Fri, Oct 21, 2022 at 9:51 AM Latchezar Filtchev  wrote:

Dear Martin,

Not getting e-mails from ovirt list is my local issue. I will deal
with this.

Async upgrade is OK. The update of Standalone engine/CentOS Stream
release 8 shows - Version 4.5.3.1-1.el8

When executing ‘dnf update’ on standalone engine – update fails -
the result is below. Do you thing manual elimination of
rdo-related will solve it?

Thank you!

Best,

Latcho

Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022
06:47:31 AM EEST.

Error:

 Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts
with ansible-core >= 2.13.0 provided by
ansible-core-2.13.3-1.el8.x86_64

- cannot install the best update candidate for package
ovirt-engine-4.5.3.1-1.el8.noarch

- cannot install the best update candidate for package
ansible-core-2.12.7-1.el8.x86_64

Problem 2: package ovirt-openvswitch-2.15-4.el8.noarch requires
openvswitch2.15, but none of the providers can be installed

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-119.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-106.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-110.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-115.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-117.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-22.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-23.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-24.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-27.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-30.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-32.el8s.x86_64

- package

[ovirt-users] Re: Ovirt 4.5.2 problem with change CD during VM installation

2022-08-24 Thread Christoph Timm


Good morning,

there is a bug in 4.5.2 with the ISO upload. So if you uploaded the ISO 
after 4.5.2 installation you need to use the workaround.


Your find the workaround here:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AQ4ASWHSMVYJ2AUAJ377CJTMLVURHCPJ/

Best regards
Christoph

Am 25.08.22 um 00:59 schrieb Facundo Badaracco:

HI everyone

i have a GlusterGS replica 3 node. All is working fine. Except when i 
want to install a win10 x64 test VM. The windows ISO loads fine, when 
it comes the time to put de virio win so the VM recongnizes the disk, 
the change CD feature doesnt change anything. I have tried with 
several ISOs, but in the windows installer it never changes the CD, 
always seems empty.


Any ideas?

thx in advance.

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VZSB2Q7ABCMDM4VGASZEUYCPJ4HETCQ4/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/XALM25IJC7R4XSXK7D7FRYUO5OZTWHS7/

[ovirt-users] Re: oVirt 4.5.2 new ISO uploads are not usable

2022-08-24 Thread Christoph Timm

Am 24.08.22 um 06:49 schrieb Arik Hadas:

On Tue, Aug 23, 2022, 18:58 Michal Skrivanek wrote:

On 23. 8. 2022, at 17:42, Christoph Timm wrote:

Hi Michal,

yes this is the issue I'm facing.
Do you require any information from my setup for the ticket?

no, I think it's clear, just needs to be fixed:)

The download is also behaving differently between old and newly
uploaded ISOs on the data domain.

old: filename.iso.raw
new: filename.iso.qcow2

That's also a result of enabling incremental backup by default now,
which is incorrect for ISOs. Deselecting the "Enable incremental
backup" option in the upload-image dialog should do the trick

Thank you for the hint!! Yes this is does the trick. ;)

Best regards
Christoph

Am 23.08.22 um 17:34 schrieb Michal Skrivanek:

On 23. 8. 2022, at 15:38, Christoph Timm wrote:

Hi list,

we have uploaded new ISO files to our data domain which we are
using for ISO images and found out that we cannot boot from
these ISO.
Older ISOs are still working but no new one.

I have not really any idea what to check and where to look so
any kind of help would be really appreciated.

Sounds like https://bugzilla.redhat.com/show_bug.cgi?id=2120228

i don't know if there's any easy workaround. What I ended up
doing was create ISO domain instead and place the files into the
NFS directory manually

Thanks,
michal

Best regards
Christoph
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/5MPQNCFRW3PFPNB252DP5M34XRSLG2A2/

[ovirt-users] Re: oVirt 4.5.2 new ISO uploads are not usable

2022-08-23 Thread Christoph Timm


Hi Michal,

yes this is the issue I'm facing.
Do you require any information from my setup for the ticket?

The download is also behaving differently between old and newly uploaded 
ISOs on the data domain.


old: filename.iso.raw
new: filename.iso.qcow2

Best regards
Christoph

Am 23.08.22 um 17:34 schrieb Michal Skrivanek:




On 23. 8. 2022, at 15:38, Christoph Timm  wrote:

Hi list,

we have uploaded new ISO files to our data domain which we are using 
for ISO images and found out that we cannot boot from these ISO.

Older ISOs are still working but no new one.

I have not really any idea what to check and where to look so any 
kind of help would be really appreciated.


Sounds like https://bugzilla.redhat.com/show_bug.cgi?id=2120228

i don't know if there's any easy workaround. What I ended up doing was 
create ISO domain instead and place the files into the NFS directory 
manually


Thanks,
michal



Best regards
Christoph
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/5MPQNCFRW3PFPNB252DP5M34XRSLG2A2/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/PQXB5EYYFIGG6FRVGYPNEKWPBSOTE5FQ/

[ovirt-users] oVirt 4.5.2 new ISO uploads are not usable

2022-08-23 Thread Christoph Timm


Hi list,

we have uploaded new ISO files to our data domain which we are using for 
ISO images and found out that we cannot boot from these ISO.

Older ISOs are still working but no new one.

I have not really any idea what to check and where to look so any kind 
of help would be really appreciated.


Best regards
Christoph
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/5MPQNCFRW3PFPNB252DP5M34XRSLG2A2/

[ovirt-users] Re: Unable to start VMs after upgrade from 4.4.9 to 4.4.10

2022-03-27 Thread Christoph Timm


Hi Ales,

thank you so much for the feedback and for the possible workaround.
For the moment I have tweaked the bridge to perform the port mirror.

Best regards
Christoph


Am 28.03.22 um 07:08 schrieb Ales Musil:

Hi,

this is already fixed in oVirt 4.5 [0]. Possible workaround might be 
to downgrade the iproute-tc package below version 5.15.0-3.


Regards,
Ales

[0] 
https://github.com/oVirt/vdsm/commit/503a98139d65daed856d97a8c6d7f875bcbe42df


On Fri, Mar 25, 2022 at 1:15 PM Christoph Timm  wrote:

Hello again,

I'm quite sure that this is a bug

Using up to date CentOS Stream 8 with vdsm-4.40.100.2-1.el8 and
oVirt 4.4.10.
The VM is getting into unresponsive state during the power down if
port mirror is activated in the vNIC profile of the VM.
The supervdsm.log on the host is showing the following error
during power off.

This was working in < 4.4.10. So I would say that this is a bug.
Where should I report this?

MainProcess|libvirt/events::DEBUG::2022-03-25
08:44:39,670::supervdsm_server::95::SuperVdsm.ServerCallback::(wrapper)
call unsetPortMirroring with ('probe_traffic', 'vnet2') {}
MainProcess|libvirt/events::DEBUG::2022-03-25
08:44:39,670::cmdutils::130::root::(exec_cmd) /sbin/tc filter show
dev probe_traffic parent : (cwd None)
MainProcess|libvirt/events::DEBUG::2022-03-25
08:44:39,678::cmdutils::138::root::(exec_cmd) SUCCESS:  =
b'';  = 0
MainProcess|libvirt/events::ERROR::2022-03-25
08:44:39,678::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper)
Error in unsetPortMirroring
Traceback (most recent call last):
  File
"/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", line
97, in wrapper
    res = func(*args, **kwargs)
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py",
line 104, in unsetPortMirroring
    acts = _delTarget(network, QDISC_INGRESS, target)
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py",
line 50, in _delTarget
    fs = list(filters(network, parent))
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py",
line 174, in filters
    for filt in _filters(dev, parent=parent, out=out):
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py",
line 199, in _iterate
    yield module.parse(tokens)
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", line
99, in parse
    data[data['kind']] = _filter_cls_parser(tokens)
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", line
119, in _parse_u32
    _parser.consume(tokens, '???')
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/_parser.py",
line 36, in consume
    raise TCParseError('Found %s, expected %s' % (found, expected))
vdsm.network.tc._parser.TCParseError: Found not_in_hw, expected
('???',)


Best regards
Christoph


Am 25.03.22 um 07:42 schrieb Christoph Timm:

Good morning,

please note that I got a bit further with my investigation.

It might be a bug in the VDSM as I see the following while
powering down the problematic VM:

MainProcess|libvirt/events::ERROR::2022-03-24
20:43:48,740::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper)
Error in unsetPortMirroring
Traceback (most recent call last):
  File
"/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", line
97, in wrapper
    res = func(*args, **kwargs)
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py",
line 104, in unsetPortMirroring
    acts = _delTarget(network, QDISC_INGRESS, target)
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py",
line 50, in _delTarget
    fs = list(filters(network, parent))
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py",
line 174, in filters
    for filt in _filters(dev, parent=parent, out=out):
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py",
line 199, in _iterate
    yield module.parse(tokens)
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py",
line 99, in parse
    data[data['kind']] = _filter_cls_parser(tokens)
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py",
line 119, in _parse_u32
    _parser.consume(tokens, '???')
  File
"/usr/lib/python3.6/site-packages/vdsm/network/tc/_parser.py",
line 36, in consume
    raise TCParseError('Found %s, expected %s' % (found, expected))
vdsm.network.tc._parser.TCParseError: Found not_in_hw, expected
('???',)

I already manage to find out that this is related to the specific
vNI

[ovirt-users] Re: Unable to start VMs after upgrade from 4.4.9 to 4.4.10

2022-03-25 Thread Christoph Timm


Hello again,

I'm quite sure that this is a bug

Using up to date CentOS Stream 8 with vdsm-4.40.100.2-1.el8 and oVirt 
4.4.10.
The VM is getting into unresponsive state during the power down if port 
mirror is activated in the vNIC profile of the VM.
The supervdsm.log on the host is showing the following error during 
power off.


This was working in < 4.4.10. So I would say that this is a bug. Where 
should I report this?


MainProcess|libvirt/events::DEBUG::2022-03-25 
08:44:39,670::supervdsm_server::95::SuperVdsm.ServerCallback::(wrapper) 
call unsetPortMirroring with ('probe_traffic', 'vnet2') {}
MainProcess|libvirt/events::DEBUG::2022-03-25 
08:44:39,670::cmdutils::130::root::(exec_cmd) /sbin/tc filter show dev 
probe_traffic parent : (cwd None)
MainProcess|libvirt/events::DEBUG::2022-03-25 
08:44:39,678::cmdutils::138::root::(exec_cmd) SUCCESS:  = b'';  = 0
MainProcess|libvirt/events::ERROR::2022-03-25 
08:44:39,678::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper) 
Error in unsetPortMirroring

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", 
line 97, in wrapper

    res = func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 104, in unsetPortMirroring

    acts = _delTarget(network, QDISC_INGRESS, target)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 50, in _delTarget

    fs = list(filters(network, parent))
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 174, in filters

    for filt in _filters(dev, parent=parent, out=out):
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 199, in _iterate

    yield module.parse(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 99, in parse

    data[data['kind']] = _filter_cls_parser(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 119, in _parse_u32

    _parser.consume(tokens, '???')
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/_parser.py", 
line 36, in consume

    raise TCParseError('Found %s, expected %s' % (found, expected))
vdsm.network.tc._parser.TCParseError: Found not_in_hw, expected ('???',)


Best regards
Christoph


Am 25.03.22 um 07:42 schrieb Christoph Timm:

Good morning,

please note that I got a bit further with my investigation.

It might be a bug in the VDSM as I see the following while powering 
down the problematic VM:


MainProcess|libvirt/events::ERROR::2022-03-24 
20:43:48,740::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper) 
Error in unsetPortMirroring

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", 
line 97, in wrapper

    res = func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 104, in unsetPortMirroring

    acts = _delTarget(network, QDISC_INGRESS, target)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 50, in _delTarget

    fs = list(filters(network, parent))
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 174, in filters

    for filt in _filters(dev, parent=parent, out=out):
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 199, in _iterate

    yield module.parse(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 99, in parse

    data[data['kind']] = _filter_cls_parser(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 119, in _parse_u32

    _parser.consume(tokens, '???')
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/_parser.py", 
line 36, in consume

    raise TCParseError('Found %s, expected %s' % (found, expected))
vdsm.network.tc._parser.TCParseError: Found not_in_hw, expected ('???',)

I already manage to find out that this is related to the specific vNIC 
configuration which is using the port mirror flag.


My plan is remove and add the port mirror from the vNIC as the first 
step. After that I will recreate the vNIC.


Any recommendations?

Best regards
Christoph

Am 24.03.22 um 12:31 schrieb Christoph Timm:

Hi List,

I receive the following error while starting some of our VMs after 
the upgrade to 4.4.10.


VM v4-probe is down with error. Exit message: internal error: process 
exited while connecting to monitor: 2022-03-24T11:27:23.098838Z 
qemu-kvm: -blockdev 
{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":"libvirt-3-format"}: 
Failed to get "write" lock
Is another process using t

[ovirt-users] Re: dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.

2022-03-25 Thread Christoph Timm


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  
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
  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 o

[ovirt-users] Re: dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.

2022-03-25 Thread Christoph Timm


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  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
  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 '--

[ovirt-users] Re: Unable to start VMs after upgrade from 4.4.9 to 4.4.10

2022-03-25 Thread Christoph Timm


Good morning,

please note that I got a bit further with my investigation.

It might be a bug in the VDSM as I see the following while powering down 
the problematic VM:


MainProcess|libvirt/events::ERROR::2022-03-24 
20:43:48,740::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper) 
Error in unsetPortMirroring

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", 
line 97, in wrapper

    res = func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 104, in unsetPortMirroring

    acts = _delTarget(network, QDISC_INGRESS, target)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 50, in _delTarget

    fs = list(filters(network, parent))
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 174, in filters

    for filt in _filters(dev, parent=parent, out=out):
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/__init__.py", 
line 199, in _iterate

    yield module.parse(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 99, in parse

    data[data['kind']] = _filter_cls_parser(tokens)
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/filter.py", 
line 119, in _parse_u32

    _parser.consume(tokens, '???')
  File "/usr/lib/python3.6/site-packages/vdsm/network/tc/_parser.py", 
line 36, in consume

    raise TCParseError('Found %s, expected %s' % (found, expected))
vdsm.network.tc._parser.TCParseError: Found not_in_hw, expected ('???',)

I already manage to find out that this is related to the specific vNIC 
configuration which is using the port mirror flag.


My plan is remove and add the port mirror from the vNIC as the first 
step. After that I will recreate the vNIC.


Any recommendations?

Best regards
Christoph

Am 24.03.22 um 12:31 schrieb Christoph Timm:

Hi List,

I receive the following error while starting some of our VMs after the 
upgrade to 4.4.10.


VM v4-probe is down with error. Exit message: internal error: process 
exited while connecting to monitor: 2022-03-24T11:27:23.098838Z 
qemu-kvm: -blockdev 
{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":"libvirt-3-format"}: 
Failed to get "write" lock
Is another process using the image 
[/rhev/data-center/mnt/lxskinner:_exports_skinner__2tb__1/28da0c79-b6f1-4740-bd24-e7bafcb62c75/images/90b28e7e-98a3-4f80-a136-c5a52c4a3e05/c1450651-b1e5-47fd-906b-8ebd62ace8a4]?.


The example disk is located on a NFS share.

Any idea how to tell oVirt that there is no other process using this 
disk?


Best regards and thx
Christoph
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SIDIS42UA5DUTS3GF5W7XBQFCNVMN3YG/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3DD4UJSQXJENYYYP762Q5Z3TTHE7GKBH/

[ovirt-users] Unable to start VMs after upgrade from 4.4.9 to 4.4.10

2022-03-24 Thread Christoph Timm


Hi List,

I receive the following error while starting some of our VMs after the 
upgrade to 4.4.10.


VM v4-probe is down with error. Exit message: internal error: process 
exited while connecting to monitor: 2022-03-24T11:27:23.098838Z 
qemu-kvm: -blockdev 
{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":"libvirt-3-format"}: 
Failed to get "write" lock
Is another process using the image 
[/rhev/data-center/mnt/lxskinner:_exports_skinner__2tb__1/28da0c79-b6f1-4740-bd24-e7bafcb62c75/images/90b28e7e-98a3-4f80-a136-c5a52c4a3e05/c1450651-b1e5-47fd-906b-8ebd62ace8a4]?.


The example disk is located on a NFS share.

Any idea how to tell oVirt that there is no other process using this disk?

Best regards and thx
Christoph
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SIDIS42UA5DUTS3GF5W7XBQFCNVMN3YG/

[ovirt-users] Re: dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.

2022-03-23 Thread Christoph Timm


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 
 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-le...@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/3N4ZO6LXNOQNQU5HHDGNOZHDSO4IBGFF/


___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/YJ336275NTG4M4AUOBTJNBZ3RD2L6HXA/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/YZSDKGFDHRXVY2S2WKW4XFQOAGUZ4HLQ/

[ovirt-users] Re: Update Issue

2021-11-18 Thread Christoph Timm


looks like they are already aware of it:
https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/BDYP62MAJL2QVQZ7RHM2USZD4HXBGUA6/


Am 18.11.21 um 11:10 schrieb Yoann Laissus:

It's also working with 6.0.0. So the problem definitely appears on 6.1.0.
The latest build https://cbs.centos.org/koji/taskinfo?taskID=2604860 is also 
impacted.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/4IZZTSG6Y3TBVUPG7O2L6JWH4Z4CRRRQ/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BRMRQS2D33ZSY5M2ELUMGPVZ77Q2OPVD/

[ovirt-users] Re: upgrade dependency issues

2021-11-15 Thread Christoph Timm


Hi Andi,

I guess you are trying to update to oVirt 4.4.9 on CentOS 8.4. This is 
not supported any more on the host.

See host section: https://www.ovirt.org/download/

So you would need to migrate to CentOS Stream 8 for example.
For example like this:
1. dnf swap centos-linux-repos centos-stream-repos
2. dnf update ovirt-release44
3. dnf distro-sync
4. reboot

Best regards
Christoph

Am 15.11.21 um 12:38 schrieb a...@b4restore.com:

Hi,

We are also seeing this issue or something close to it:

Error:
  Problem 1: cannot install the best update candidate for package 
vdsm-4.40.80.6-1.el8.x86_64
   - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by 
vdsm-4.40.90.4-1.el8.x86_64
  Problem 2: package ovirt-host-dependencies-4.4.9-2.el8.x86_64 requires vdsm 
>= 4.40.90, but none of the providers can be installed
   - cannot install the best update candidate for package 
ovirt-host-dependencies-4.4.8-1.el8.x86_64
   - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by 
vdsm-4.40.90.3-1.el8.x86_64
   - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by 
vdsm-4.40.90.4-1.el8.x86_64
  Problem 3: package ovirt-host-4.4.9-2.el8.x86_64 requires 
ovirt-host-dependencies = 4.4.9-2.el8, but none of the providers can be 
installed
   - package ovirt-host-dependencies-4.4.9-2.el8.x86_64 requires vdsm >= 
4.40.90, but none of the providers can be installed
   - cannot install the best update candidate for package 
ovirt-host-4.4.8-1.el8.x86_64
   - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by 
vdsm-4.40.90.3-1.el8.x86_64
   - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by 
vdsm-4.40.90.4-1.el8.x86_64
  Problem 4: package ovirt-provider-ovn-driver-1.2.34-1.el8.noarch requires 
vdsm, but none of the providers can be installed
   - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-http = 4.40.80.6-1.el8, 
but none of the providers can be installed
   - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-http = 4.40.17-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-http = 4.40.18-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-http = 4.40.19-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-http = 4.40.20-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-http = 4.40.21-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-http = 4.40.22-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-http = 4.40.26.3-1.el8, 
but none of the providers can be installed
   - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-http = 4.40.30-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-http = 4.40.31-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-http = 4.40.32-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-http = 4.40.33-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-http = 4.40.34-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-http = 4.40.35-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-http = 4.40.35.1-1.el8, 
but none of the providers can be installed
   - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-http = 4.40.36-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-http = 4.40.37-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-http = 4.40.38-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-http = 4.40.39-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-http = 4.40.40-1.el8, but 
none of the providers can be installed
   - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-http = 4.40.50.8-1.el8, 
but none of the providers can be installed
   - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-http = 4.40.50.9-1.el8, 
but none of the providers can be installed
   - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-http = 4.40.60.6-1.el8, 
but none of the providers can be installed
   - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-http = 4.40.60.7-1.el8, 
but none of the providers can be installed
   - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-http = 4.40.70.6-1.el8, 
but none of the providers can be installed
   - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-http = 4.40.80.5-1.el8, 
but none of the providers can be installed
   - package vdsm-4.40.16-1.el8.x86_64 requires ovirt-imageio-common = 2.0.6, 
but none

[ovirt-users] Re: Suggested upgrading path from CentOS based 4.4.8 to 4.4.9

2021-11-08 Thread Christoph Timm

Hi Gianluca,

I have a self hosted platform with plain CentOS 8.4 host. Also my engine
is currently running CentOS 8.4.

I updated my whole system from 4.4.7 to 4.4.9.

As 4.4.9 does not support CentOS hosts I had to migrate them to CentOS
Stream 8 as well.
Due to dependency issues I have put the host into maintenance mode and
did the rest through CLI.

# dnf swap centos-linux-repos centos-stream-repos
# dnf update ovirt-release44
# dnf distro-sync
# reboot
Done

I did not change the engine OS aa CentOS 8.4 is still supported here.

Also I did the update in multiple steps over a couple of days which did
not cause any issue on my side.

Hope this helps.

Best regards
Christoph

Am 08.11.21 um 13:41 schrieb Gianluca Cecchi:
I have a lab with an environment based on 4.4.8.6-1, with 3 CentOS
Linux 8.4 hosts and a CentOS 8.4 external engine system (that is a VM
on vSphere, so that I can leverage a snapshot methodology for the
process...).
I would like to pass to 4.4.9 and retain a full plain OS on hosts for
the moment, without going through oVirt nodes, but standing the repo
problems and CentOS 8.x going through EOL this is what I'm planning to do:

1. stop engine service on engine system

2. convert engine to CentOS Stream
This step needs some confirmation.
Could you provide an official link about the process?
I'm not able to find it again. Is it a problem of mine or all (CentOS
website, RHEL website) seem to point only to conversion from CentOS
Linux to RHEL??
Apart external websites provided workflows, I was only able to find a
mid January youtube video, when CentOS was based on 8.3, with these steps:

yum install centos-release-stream
yum swap centos-{linux,stream}-repos
yum repolist
yum distro-sync
reboot
The video link is here:
https://www.youtube.com/watch?v=Ba2ytp_8x7s

No mention at
https://www.redhat.com/en/blog/faq-centos-stream-updates

And on CentOS page I only found this:
https://centos.org/distro-faq/
with Q7 containing only the two instructions:
dnf swap centos-linux-repos centos-stream-repos
dnf distro-sync

What to use safely?
Is it possible to include some sort of documentation or links on oVirt
page, to migrate from CentOS Linux to CentOS Stream for oVirt upgrade
purposes?

3. After reboot implied, I think, in step 2., use the usual steps to
update engine to 4.4.9

4. update the first out of three hosts from CentOS Linux to CentOS
Stream and to 4.4.9.

4.a follow the same approach of engine (when defined) and pass it to
Stream retaining the 4.4.8.

4.b upgrade from the web admin gui to 4.4.9

5. Do the same for second host and third hosts

Any hints, comments, limitations in having mixed 4.4.8 and 4.4.9 hosts
for a while and such?

Thanks,
Gianluca

___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/L3CRTNR2IUGNRZNVQMROQABHHBKMEYPP/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/RGF6HG7LSJOYTV3AVYK4VP7HPQ4UAK2A/

[ovirt-users] Re: Cannot to update hosts, nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.4-1.el8.x86_64

2021-11-04 Thread Christoph Timm


Correct, the host of oVirt 4.4.9 does not support CentOS 8.4 anymore.
If you are running CentOS 8.4 just to the following:

# dnf swap centos-linux-repos centos-stream-repos
# dnf update ovirt-release44
# dnf distro-sync

In case you are running Stream already just run to get the update working.
# dnf update ovirt-release44


Am 04.11.21 um 05:56 schrieb Alex McWhirter:

On 2021-11-03 16:52, Patrick Lomakin wrote:

I think it's a bug. I couldn't find any rpm "libvirt-daemon-kvm"
package in CentOS or Ovirt repo.(only libvirt-daemon-kvm 7.0.0). Try
to use --nobest flag to install updates.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/JR4SOVSBBMM4TIJIQXV6JMXZNAXR3QXB/ 



7.6.0-4 is currently what is available on stream. I believe 8.4 is no 
longer supported as a host OS (CentOS or RHEL) as they list CentOS 
Stream, Node, and RHEL 8.5 Beta as supported OS's for host.

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SP6ENO2V3HMPQ54KTTHHRKFQQ5ZVAJMV/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/5SUPKGRXCJMCQDUJY3OHML3JCYUVT4A7/

[ovirt-users] Re: CentOS 8 Stream: hosted-engine deploy with CPU type is not supported

2021-10-25 Thread Christoph Timm


Hi,

I think the edk2-ovmf is still not working in CentOS 8 Stream.
Try to downgrade.

dnf downgrade edk2-ovmf-20200602gitca407c7246bf-4.el8

This solved the problem on my oVirt hosts.

Best regards
Christoph

Am 25.10.21 um 11:59 schrieb matyi.szabo...@internetx.com:

Hi all,

On CentOS 8 Stream I get the following error during "hosted-engine --deploy":

[ INFO ] The host has been set in non_operational status, deployment errors: 
code 156: Host HOST moved to Non-Operational state as host CPU type is not 
supported in this cluster compatibility version or is not supported at all, 
code 519



CPU:

[root@ovirt-test ~]# lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
CPU(s):  24
On-line CPU(s) list: 0-23
Thread(s) per core:  2
Core(s) per socket:  6
Socket(s):   2
NUMA node(s):2
Vendor ID:   GenuineIntel
BIOS Vendor ID:  Intel
CPU family:  6
Model:   63
Model name:  Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz


I set up cluster compatibility but it did not solve the problem.
On a normal CentOS 8.4 system, the error is not present.

Does anyone have an idea?
Or have older drivers been removed from the Streram version?

Thanks
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/TT3MNE4VJS2ZMGL5WFQ7UVFSMEMNB22W/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2E24TT42BRXYTSYQLSYDS6QSF7N2JB66/

[ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host

2021-07-28 Thread Christoph Timm


Hi Lucia, Hi Michal,

thank you so much for getting back to me.
I have downgraded the edk2-ovmf package two times to 
20200602gitca407c7246bf-4.el8.


This have solve the issue for me. Means I'm able to activate the host on 
CentOS Stream 8 again.


Does this mean that this will be fixed in future versions?

Best regards
Christoph


Am 28.07.21 um 09:58 schrieb Lucia Jelinkova:

Hi Christoph,

The 20200602gitca407c7246bf-5.el8 is the "broken" one [1], try 
downgrading to the older version (I have 
20200602gitca407c7246bf-4.el8_4.1).


1: https://bugzilla.redhat.com/show_bug.cgi?id=1961558#c6 
<https://bugzilla.redhat.com/show_bug.cgi?id=1961558#c6>


Regards,

Lucia

On Wed, Jul 28, 2021 at 9:40 AM Michal Skrivanek 
mailto:michal.skriva...@redhat.com>> wrote:





On 26. 7. 2021, at 15:06, Christoph Timm mailto:ov...@timmi.org>> wrote:

Hi all,

please note that I also tried to migrate one of my hosts from
CentOS 8 to CentOS Stream 8.
After the reboot I received the following message:
The host CPU does not match the Cluster CPU Type and is running
in a degraded mode. It is missing the following CPU flags:
model_IvyBridge, spec_ctrl. Please update the host CPU microcode
or change the Cluster CPU Type.

I downgraded the edk2-ovmf package to the following version:
20200602gitca407c7246bf-5.el8


upgraded. that’s a newer version than the one below


The following version was installed before:
20210527gite1999b264f1f-1.el8

But still the issue is present for me.


I’m not aware of any issue with the virt stack packages in Stream,
that edk2-ovmf issue has been fixed few weeks back, the new
version is the right one, but maybe you have other outdated packages?
Also please refresh host capabilities after each such package change.

There also could be a microcode change for IvyBridge that you’ve
missed (or intel didn’t fix for your particular cpu)…perhaps it’s
good enough to just change the Cluster CPU to SandyBridge instead.



I'm running latest 4.4.7 and my cluster version is 4.6.

Best regards
Christoph


Am 27.05.21 um 16:26 schrieb Gunasekhar Kothapalli via Users:

The issue was with edk2-ovmf package update, rolling that
package back and it started recognizing the CPU and host coming
up... tested on one host and worked fine.
Thanks & Regards,
*Gunasekhar Kothapalli*

*From:*Nur Imam Febrianto
<mailto:nur_i...@outlook.com>
*Sent:*Wednesday, May 26, 2021 9:54 PM
*To:*k.gunasek...@non.keysight.com
<mailto:k.gunasek...@non.keysight.com>;users@ovirt.org
<mailto:users@ovirt.org>
*Subject:*RE: [ovirt-users] Re: CPU Compatibility Problem after
Upgrading Centos 8 Stream Host

*CAUTION:*This message originates from an external sender.

Already trying several things, seem kernel update doesn’t make
this problem happen. Already tried to yum update exclude kernel,
the issue still happened.
Thanks.
Regards,
Nur Imam Febrianto
*From:*k.gunasekhar--- via Users <mailto:users@ovirt.org>
*Sent:*26 May 2021 12:27
*To:*users@ovirt.org <mailto:users@ovirt.org>
*Subject:*[ovirt-users] Re: CPU Compatibility Problem after
Upgrading Centos 8 Stream Host
I also end up with the same problem today. How did rollback yum
i see many yum updates in the yum history.

Here is what the error says.

The host CPU does not match the Cluster CPU Type and is running
in a degraded mode. It is missing the following CPU flags:
model_IvyBridge, spec_ctrl. Please update the host CPU microcode
or change the Cluster CPU Type.
___
Users mailing list --users@ovirt.org <mailto:users@ovirt.org>
To unsubscribe send an email tousers-le...@ovirt.org
<mailto:users-le...@ovirt.org>
Privacy

Statement:https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.htmldata=04%7C01%7C%7Ccdfdf3baa30a417b631a08d92006eeac%7C84df9e7fe9f640afb435%7C1%7C0%7C637576036430558160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=ioM1ZSkM2q7CNvInAJQdg0n%2BZdUNSMG%2BpmapvHi%2FFKo%3Dreserved=0

<https://urldefense.com/v3/__https:/apac01.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.ovirt.org*2Fprivacy-policy.htmldata=04*7C01*7C*7Ccdfdf3baa30a417b631a08d92006eeac*7C84df9e7fe9f640afb435*7C1*7C0*7C637576036430558160*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000sdata=ioM1ZSkM2q7CNvInAJQdg0n*2BZdUNSMG*2BpmapvHi*2FFKo*3Dreserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJQ!!I5pVk4LIGAfnvw!z2C_Ouh0Q3nYWfWKibSBaaaBHwgak7FV-Ok_FYbnb0eps3P5m70NpEFQ6QPlpXoozSEpgJU$>
oVirt Code of

Conduct:https://apac01.safelinks.protection.outlook.com/?url=https

[ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host

2021-07-26 Thread Christoph Timm


Hi all,

please note that I also tried to migrate one of my hosts from CentOS 8 
to CentOS Stream 8.

After the reboot I received the following message:
The host CPU does not match the Cluster CPU Type and is running in a 
degraded mode. It is missing the following CPU flags: model_IvyBridge, 
spec_ctrl. Please update the host CPU microcode or change the Cluster 
CPU Type.


I downgraded the edk2-ovmf package to the following version: 
20200602gitca407c7246bf-5.el8

The following version was installed before: 20210527gite1999b264f1f-1.el8

But still the issue is present for me.

I'm running latest 4.4.7 and my cluster version is 4.6.

Best regards
Christoph


Am 27.05.21 um 16:26 schrieb Gunasekhar Kothapalli via Users:


The issue was with edk2-ovmf package update, rolling that package back 
and it started recognizing the CPU and host coming up... tested on one 
host and worked fine.


Thanks & Regards,
*Gunasekhar Kothapalli*

*From:* Nur Imam Febrianto 
*Sent:* Wednesday, May 26, 2021 9:54 PM
*To:* k.gunasek...@non.keysight.com; users@ovirt.org
*Subject:* RE: [ovirt-users] Re: CPU Compatibility Problem after 
Upgrading Centos 8 Stream Host


*CAUTION:*This message originates from an external sender.

Already trying several things, seem kernel update doesn’t make this 
problem happen. Already tried to yum update exclude kernel, the issue 
still happened.


Thanks.

Regards,

Nur Imam Febrianto

*From: *k.gunasekhar--- via Users 
*Sent: *26 May 2021 12:27
*To: *users@ovirt.org 
*Subject: *[ovirt-users] Re: CPU Compatibility Problem after Upgrading 
Centos 8 Stream Host


I also end up with the same problem today. How did rollback yum i see 
many yum updates in the yum history.


Here is what the error says.

The host CPU does not match the Cluster CPU Type and is running in a 
degraded mode. It is missing the following CPU flags: model_IvyBridge, 
spec_ctrl. Please update the host CPU microcode or change the Cluster 
CPU Type.

___
Users mailing list -- users@ovirt.org 
To unsubscribe send an email to users-le...@ovirt.org 

Privacy Statement: 
https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.htmldata=04%7C01%7C%7Ccdfdf3baa30a417b631a08d92006eeac%7C84df9e7fe9f640afb435%7C1%7C0%7C637576036430558160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=ioM1ZSkM2q7CNvInAJQdg0n%2BZdUNSMG%2BpmapvHi%2FFKo%3Dreserved=0 

oVirt Code of Conduct: 
https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2Fdata=04%7C01%7C%7Ccdfdf3baa30a417b631a08d92006eeac%7C84df9e7fe9f640afb435%7C1%7C0%7C637576036430558160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=6pxtmPuppncwbn6Q3sRxYq%2BdpbK68bZ1HV28qnxAf0w%3Dreserved=0 

List Archives: 
https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2F7VQ7CABK4FIP4SLPNNPEVZSCM6DTIUAD%2Fdata=04%7C01%7C%7Ccdfdf3baa30a417b631a08d92006eeac%7C84df9e7fe9f640afb435%7C1%7C0%7C637576036430558160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=UxZ3oeiPqYUo1N6dvIAyUmlTPWv%2FG1FM0AMmF%2FLHmno%3Dreserved=0

[ovirt-users] Re: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Penalizing score by 1600 due to network status

2021-07-23 Thread Christoph Timm

Am 21.07.21 um 12:33 schrieb Christoph Timm:

Am 21.07.21 um 12:17 schrieb Yedidyah Bar David:
On Mon, Jul 19, 2021 at 2:20 PM Yedidyah Bar David
wrote:

On Mon, Jul 19, 2021 at 1:54 PM Christoph Timm wrote:

Am 19.07.21 um 10:52 schrieb Yedidyah Bar David:
On Mon, Jul 19, 2021 at 11:39 AM Christoph Timm
wrote:

Am 19.07.21 um 10:25 schrieb Yedidyah Bar David:
On Mon, Jul 19, 2021 at 11:02 AM Christoph Timm
wrote:

Am 19.07.21 um 09:27 schrieb Yedidyah Bar David:
On Mon, Jul 19, 2021 at 10:04 AM Christoph Timm
wrote:

Hi Didi,

thank you for the quick response.

Am 19.07.21 um 07:59 schrieb Yedidyah Bar David:
On Mon, Jul 19, 2021 at 8:39 AM Christoph Timm
wrote:

Hi List,

I'm trying to understand why my hosted engine is moved from
one node to

another from time to time.
It is happening sometime multiple times a day. But there
are also days

without it.

I can see the following in the
ovirt-hosted-engine-ha/agent.log:
ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score)

Penalizing score by 1600 due to network status

After that the engine will be shutdown and started on
another host.
The oVirt Admin portal is showing the following around the
same time:
Invalid status on Data Center Default. Setting status to
Non Responsive.

But the whole cluster is working normally during that time.

I believe that I have somehow a network issue on my side
but I have no
clue what kind of check is causing the network status to
penalized.

Does anyone have an idea how to investigate this further?

Please check also broker.log. Do you see 'dig' failures?

Yes I found them as well.

Thread-1::WARNING::2021-07-19
08:02:00,032::network::120::network.Network::(_dns) DNS query
failed:

; <<>> DiG 9.11.26-RedHat-9.11.26-4.el8_4 <<>> +tries=1 +time=5
;; global options: +cmd
;; connection timed out; no servers could be reached

This happened several times already on our CI
infrastructure, but yours is

the first report from an actual real user. See also:

https://lists.ovirt.org/archives/list/in...@ovirt.org/thread/LIGS5WXGEKWACY5GCK7Z6Q2JYVWJ6JBF/

So I understand that the following command is triggered to
test the

network: "dig +tries=1 +time=5"

Indeed.

I didn't open a bug for this (yet?), also because I never
reproduced on my
own machines and am not sure about the exact failing flow.
If this is

reproducible
reliably for you, you might want to test the patch I pushed:

https://gerrit.ovirt.org/c/ovirt-hosted-engine-ha/+/115596
Now filed this bug and linked to it in the above patch. Thanks for
your report!

https://bugzilla.redhat.com/show_bug.cgi?id=1984356

Perfect I added me cc as well.

I have implemented the change on one of my nodes, restarted the
ovirt-ha-broker and moved the engine to that node.
Since than the issue did not occur. I guess I will leave it running
until end of the week and will move the engine back to a none changed
node to see that the issue is back again.
So I had no issue with the changed host until now. So I moved the engine
to different host in the morning and now I received the issue. So I will
implement the fix on all my hosts now.

So hope this fix will be permanently included in the next release.

Best regards,

I'm happy to give it a try.
Please confirm that I need to replace this file (network.py)
on all my

nodes (CentOS 8.4 based) which can host my engine.
It definitely makes sense to do so, but in principle there is
no problem
with applying it only on some of them. That's especially
useful if you try
this first on a test env and try to enforce a reproduction
somehow (overload

the network, disconnect stuff, etc.).

OK will give it a try and report back.

Thanks and good luck.

Do I need to restart anything after that change?
Yes, the broker. This might restart some other services there, so
best put the

host to maintenance during this.

Also please confirm that the comma after TCP is correct as there
wasn't

one before after the timeout in row 110.

It is correct, but not mandatory. We (my team, at least) often add it
in such cases
to make a theoretical future patch that adds another parameter not
require adding
it again (thus making the patch smaller and hopefully cleaner).

Other ideas/opinions about how to enhance this part of the
monitoring

are most welcome.

If this phenomenon is new for you, and you can reliably say
it's not due to
a recent "natural" higher network load, I wonder if it's due
to some weird

bug/change somewhere.

I'm quite sure that I see this since we moved to 4.4.(4).
Just for house keeping I'm running 4.4.7 now.
We use 'dig' as the network monitor since 4.3.5, around one
year before 4.4

was released: https://bugzilla.redhat.com/1659052

Which version did you use before 4.4?
The last 4.3 versions have been 4.3.7, 4.3.9 and 4.3.10 before
migrating

to 4.4.4.
I now realize that in above-linked bug we only changed the
default, for new
setups. So if you de

[ovirt-users] Re: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Penalizing score by 1600 due to network status

2021-07-21 Thread Christoph Timm

Am 21.07.21 um 12:17 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 2:20 PM Yedidyah Bar David wrote:

On Mon, Jul 19, 2021 at 1:54 PM Christoph Timm wrote:

Am 19.07.21 um 10:52 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 11:39 AM Christoph Timm wrote:

Am 19.07.21 um 10:25 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 11:02 AM Christoph Timm wrote:

Am 19.07.21 um 09:27 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 10:04 AM Christoph Timm wrote:

Hi Didi,

thank you for the quick response.

Am 19.07.21 um 07:59 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 8:39 AM Christoph Timm wrote:

Hi List,

I'm trying to understand why my hosted engine is moved from one node to
another from time to time.
It is happening sometime multiple times a day. But there are also days
without it.

I can see the following in the ovirt-hosted-engine-ha/agent.log:
ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score)
Penalizing score by 1600 due to network status

After that the engine will be shutdown and started on another host.
The oVirt Admin portal is showing the following around the same time:
Invalid status on Data Center Default. Setting status to Non Responsive.

But the whole cluster is working normally during that time.

I believe that I have somehow a network issue on my side but I have no
clue what kind of check is causing the network status to penalized.

Does anyone have an idea how to investigate this further?

Please check also broker.log. Do you see 'dig' failures?

Yes I found them as well.

Thread-1::WARNING::2021-07-19
08:02:00,032::network::120::network.Network::(_dns) DNS query failed:
; <<>> DiG 9.11.26-RedHat-9.11.26-4.el8_4 <<>> +tries=1 +time=5
;; global options: +cmd
;; connection timed out; no servers could be reached

This happened several times already on our CI infrastructure, but yours is
the first report from an actual real user. See also:

https://lists.ovirt.org/archives/list/in...@ovirt.org/thread/LIGS5WXGEKWACY5GCK7Z6Q2JYVWJ6JBF/

So I understand that the following command is triggered to test the
network: "dig +tries=1 +time=5"

Indeed.

I didn't open a bug for this (yet?), also because I never reproduced on my
own machines and am not sure about the exact failing flow. If this is
reproducible
reliably for you, you might want to test the patch I pushed:

https://gerrit.ovirt.org/c/ovirt-hosted-engine-ha/+/115596

Now filed this bug and linked to it in the above patch. Thanks for your report!

https://bugzilla.redhat.com/show_bug.cgi?id=1984356

Perfect I added me cc as well.

Best regards,

I'm happy to give it a try.
Please confirm that I need to replace this file (network.py) on all my
nodes (CentOS 8.4 based) which can host my engine.

It definitely makes sense to do so, but in principle there is no problem
with applying it only on some of them. That's especially useful if you try
this first on a test env and try to enforce a reproduction somehow (overload
the network, disconnect stuff, etc.).

OK will give it a try and report back.

Thanks and good luck.

Do I need to restart anything after that change?

Yes, the broker. This might restart some other services there, so best put the
host to maintenance during this.

Also please confirm that the comma after TCP is correct as there wasn't
one before after the timeout in row 110.

Other ideas/opinions about how to enhance this part of the monitoring
are most welcome.

If this phenomenon is new for you, and you can reliably say it's not due to
a recent "natural" higher network load, I wonder if it's due to some weird
bug/change somewhere.

I'm quite sure that I see this since we moved to 4.4.(4).
Just for house keeping I'm running 4.4.7 now.

We use 'dig' as the network monitor since 4.3.5, around one year before 4.4
was released: https://bugzilla.redhat.com/1659052

Which version did you use before 4.4?

The last 4.3 versions have been 4.3.7, 4.3.9 and 4.3.10 before migrating
to 4.4.4.

Hm, I'm sorry but I don't recall this. I'm quite sure that we started

OK, thanks for trying.

[ovirt-users] Re: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Penalizing score by 1600 due to network status

2021-07-19 Thread Christoph Timm

Am 19.07.21 um 10:52 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 11:39 AM Christoph Timm wrote:

Am 19.07.21 um 10:25 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 11:02 AM Christoph Timm wrote:

Am 19.07.21 um 09:27 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 10:04 AM Christoph Timm wrote:

Hi Didi,

thank you for the quick response.

Am 19.07.21 um 07:59 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 8:39 AM Christoph Timm wrote:

Hi List,

I'm trying to understand why my hosted engine is moved from one node to
another from time to time.
It is happening sometime multiple times a day. But there are also days
without it.

I can see the following in the ovirt-hosted-engine-ha/agent.log:
ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score)
Penalizing score by 1600 due to network status

After that the engine will be shutdown and started on another host.
The oVirt Admin portal is showing the following around the same time:
Invalid status on Data Center Default. Setting status to Non Responsive.

But the whole cluster is working normally during that time.

I believe that I have somehow a network issue on my side but I have no
clue what kind of check is causing the network status to penalized.

Does anyone have an idea how to investigate this further?

Please check also broker.log. Do you see 'dig' failures?

Yes I found them as well.

This happened several times already on our CI infrastructure, but yours is
the first report from an actual real user. See also:

https://lists.ovirt.org/archives/list/in...@ovirt.org/thread/LIGS5WXGEKWACY5GCK7Z6Q2JYVWJ6JBF/

So I understand that the following command is triggered to test the
network: "dig +tries=1 +time=5"

Indeed.

https://gerrit.ovirt.org/c/ovirt-hosted-engine-ha/+/115596

I'm happy to give it a try.
Please confirm that I need to replace this file (network.py) on all my
nodes (CentOS 8.4 based) which can host my engine.

OK will give it a try and report back.

Thanks and good luck.

Do I need to restart anything after that change?
Also please confirm that the comma after TCP is correct as there wasn't
one before after the timeout in row 110.

Other ideas/opinions about how to enhance this part of the monitoring
are most welcome.

If this phenomenon is new for you, and you can reliably say it's not due to
a recent "natural" higher network load, I wonder if it's due to some weird
bug/change somewhere.

I'm quite sure that I see this since we moved to 4.4.(4).
Just for house keeping I'm running 4.4.7 now.

We use 'dig' as the network monitor since 4.3.5, around one year before 4.4
was released: https://bugzilla.redhat.com/1659052

Which version did you use before 4.4?

The last 4.3 versions have been 4.3.7, 4.3.9 and 4.3.10 before migrating
to 4.4.4.

Hm, I'm sorry but I don't recall this. I'm quite sure that we started

OK, thanks for trying.

with 4.0 something. But we moved to a HE setup around September 2019.
But I don't recall the version. But we installed also the backup from
the old installation into the HE environment if I'm not wrong.

If indeed this change was the trigger for you, you can rather easily try to
change this to 'ping' and see if this helps - I think it's enough to change
'network_test' to 'ping' in /etc/ovirt-hosted-engine/hosted-engine.conf
and restart the broker - didn't try, though. But generally speaking, I do not
think we want to change the default back to 'ping', but rather make 'dns'
work better/well. We had valid reasons to move away from ping...

OK I will try this if the tcp change does not help me.

Best regards,

[ovirt-users] Re: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Penalizing score by 1600 due to network status

2021-07-19 Thread Christoph Timm

Am 19.07.21 um 10:25 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 11:02 AM Christoph Timm wrote:

Am 19.07.21 um 09:27 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 10:04 AM Christoph Timm wrote:

Hi Didi,

thank you for the quick response.

Am 19.07.21 um 07:59 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 8:39 AM Christoph Timm wrote:

Hi List,

I'm trying to understand why my hosted engine is moved from one node to
another from time to time.
It is happening sometime multiple times a day. But there are also days
without it.

I can see the following in the ovirt-hosted-engine-ha/agent.log:
ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score)
Penalizing score by 1600 due to network status

After that the engine will be shutdown and started on another host.
The oVirt Admin portal is showing the following around the same time:
Invalid status on Data Center Default. Setting status to Non Responsive.

But the whole cluster is working normally during that time.

I believe that I have somehow a network issue on my side but I have no
clue what kind of check is causing the network status to penalized.

Does anyone have an idea how to investigate this further?

Please check also broker.log. Do you see 'dig' failures?

Yes I found them as well.

This happened several times already on our CI infrastructure, but yours is
the first report from an actual real user. See also:

https://lists.ovirt.org/archives/list/in...@ovirt.org/thread/LIGS5WXGEKWACY5GCK7Z6Q2JYVWJ6JBF/

So I understand that the following command is triggered to test the
network: "dig +tries=1 +time=5"

Indeed.

https://gerrit.ovirt.org/c/ovirt-hosted-engine-ha/+/115596

I'm happy to give it a try.
Please confirm that I need to replace this file (network.py) on all my
nodes (CentOS 8.4 based) which can host my engine.

OK will give it a try and report back.

Thanks and good luck.

Other ideas/opinions about how to enhance this part of the monitoring
are most welcome.

If this phenomenon is new for you, and you can reliably say it's not due to
a recent "natural" higher network load, I wonder if it's due to some weird
bug/change somewhere.

I'm quite sure that I see this since we moved to 4.4.(4).
Just for house keeping I'm running 4.4.7 now.

We use 'dig' as the network monitor since 4.3.5, around one year before 4.4
was released: https://bugzilla.redhat.com/1659052

Which version did you use before 4.4?

The last 4.3 versions have been 4.3.7, 4.3.9 and 4.3.10 before migrating
to 4.4.4.

I now realize that in above-linked bug we only changed the default, for new
setups. So if you deployed He before 4.3.5, upgrade to later 4.3 would not
change the default (as opposed to upgrade to 4.4, which was actually a
new deployment with engine backup/restore). Do you know which version
your cluster was originally deployed with?
Hm, I'm sorry but I don't recall this. I'm quite sure that we started
with 4.0 something. But we moved to a HE setup around September 2019.
But I don't recall the version. But we installed also the backup from
the old installation into the HE environment if I'm not wrong.

Best regards,

[ovirt-users] Re: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Penalizing score by 1600 due to network status

2021-07-19 Thread Christoph Timm

Am 19.07.21 um 09:27 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 10:04 AM Christoph Timm wrote:

Hi Didi,

thank you for the quick response.

Am 19.07.21 um 07:59 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 8:39 AM Christoph Timm wrote:

Hi List,

I'm trying to understand why my hosted engine is moved from one node to
another from time to time.
It is happening sometime multiple times a day. But there are also days
without it.

I can see the following in the ovirt-hosted-engine-ha/agent.log:
ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score)
Penalizing score by 1600 due to network status

After that the engine will be shutdown and started on another host.
The oVirt Admin portal is showing the following around the same time:
Invalid status on Data Center Default. Setting status to Non Responsive.

But the whole cluster is working normally during that time.

I believe that I have somehow a network issue on my side but I have no
clue what kind of check is causing the network status to penalized.

Does anyone have an idea how to investigate this further?

Please check also broker.log. Do you see 'dig' failures?

Yes I found them as well.

This happened several times already on our CI infrastructure, but yours is
the first report from an actual real user. See also:

https://lists.ovirt.org/archives/list/in...@ovirt.org/thread/LIGS5WXGEKWACY5GCK7Z6Q2JYVWJ6JBF/

So I understand that the following command is triggered to test the
network: "dig +tries=1 +time=5"

Indeed.

https://gerrit.ovirt.org/c/ovirt-hosted-engine-ha/+/115596

I'm happy to give it a try.
Please confirm that I need to replace this file (network.py) on all my
nodes (CentOS 8.4 based) which can host my engine.

OK will give it a try and report back.

Other ideas/opinions about how to enhance this part of the monitoring
are most welcome.

If this phenomenon is new for you, and you can reliably say it's not due to
a recent "natural" higher network load, I wonder if it's due to some weird
bug/change somewhere.

I'm quite sure that I see this since we moved to 4.4.(4).
Just for house keeping I'm running 4.4.7 now.

We use 'dig' as the network monitor since 4.3.5, around one year before 4.4
was released: https://bugzilla.redhat.com/1659052

Which version did you use before 4.4?
The last 4.3 versions have been 4.3.7, 4.3.9 and 4.3.10 before migrating
to 4.4.4.

Best regards,

[ovirt-users] Re: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Penalizing score by 1600 due to network status

2021-07-19 Thread Christoph Timm

Hi Didi,

thank you for the quick response.

Am 19.07.21 um 07:59 schrieb Yedidyah Bar David:

On Mon, Jul 19, 2021 at 8:39 AM Christoph Timm wrote:

Hi List,

I'm trying to understand why my hosted engine is moved from one node to
another from time to time.
It is happening sometime multiple times a day. But there are also days
without it.

I can see the following in the ovirt-hosted-engine-ha/agent.log:
ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score)
Penalizing score by 1600 due to network status

After that the engine will be shutdown and started on another host.
The oVirt Admin portal is showing the following around the same time:
Invalid status on Data Center Default. Setting status to Non Responsive.

But the whole cluster is working normally during that time.

I believe that I have somehow a network issue on my side but I have no
clue what kind of check is causing the network status to penalized.

Does anyone have an idea how to investigate this further?

Please check also broker.log. Do you see 'dig' failures?

Yes I found them as well.

Thread-1::WARNING::2021-07-19
08:02:00,032::network::120::network.Network::(_dns) DNS query failed:

; <<>> DiG 9.11.26-RedHat-9.11.26-4.el8_4 <<>> +tries=1 +time=5
;; global options: +cmd
;; connection timed out; no servers could be reached

This happened several times already on our CI infrastructure, but yours is
the first report from an actual real user. See also:

https://lists.ovirt.org/archives/list/in...@ovirt.org/thread/LIGS5WXGEKWACY5GCK7Z6Q2JYVWJ6JBF/
So I understand that the following command is triggered to test the
network: "dig +tries=1 +time=5"

https://gerrit.ovirt.org/c/ovirt-hosted-engine-ha/+/115596

I'm happy to give it a try.
Please confirm that I need to replace this file (network.py) on all my
nodes (CentOS 8.4 based) which can host my engine.

Other ideas/opinions about how to enhance this part of the monitoring
are most welcome.

If this phenomenon is new for you, and you can reliably say it's not due to
a recent "natural" higher network load, I wonder if it's due to some weird
bug/change somewhere.

I'm quite sure that I see this since we moved to 4.4.(4).
Just for house keeping I'm running 4.4.7 now.

Thanks and best regards,

[ovirt-users] ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Penalizing score by 1600 due to network status

2021-07-18 Thread Christoph Timm


Hi List,

I'm trying to understand why my hosted engine is moved from one node to 
another from time to time.
It is happening sometime multiple times a day. But there are also days 
without it.


I can see the following in the ovirt-hosted-engine-ha/agent.log:
ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) 
Penalizing score by 1600 due to network status


After that the engine will be shutdown and started on another host.
The oVirt Admin portal is showing the following around the same time:
Invalid status on Data Center Default. Setting status to Non Responsive.

But the whole cluster is working normally during that time.

I believe that I have somehow a network issue on my side but I have no 
clue what kind of check is causing the network status to penalized.


Does anyone have an idea how to investigate this further?

Best regards
Christoph
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2HTD5WR43M5MUTEDMM4HRFBADIXEQNB4/

[ovirt-users] Re: [4.4.7] The latest guest agent needs to be installed and running on the guest

2021-07-09 Thread Christoph Timm

Hi Tomáš,

I put the host in maintenance today and give it another reboot.
After that the information are available for the VMs running on that host.
Also the exclamation mark is gone.

So I guess something did not come up correctly during the restart of the
host.

Best regards
Christoph

Am 08.07.21 um 20:36 schrieb Christoph Timm:

Hi Tomáš,

sorry for the late reply and for my the missing information.

Am 08.07.21 um 16:50 schrieb Tomáš Golembiovský:

On Thu, Jul 08, 2021 at 02:02:14PM +0200, Christoph Timm wrote:

Hi list,

I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs have
issues to report the performance information via the guest agent.

The performance info is provided by libvirt and not by guest agent.
Could you be more specific about which information is missing?
Sorry I did not mean the performance information like Memory, CPU and
Network. These are available. The missing information are IP Addresses
and FQDN.

What is the version of vdsm and libvirt on the host?

All hosts are running:libvirt-7.0.0-14.1.el8

I see the following message on the VMs: The latest guest agent needs to be
installed and running on the guest

This is probably unrelated to the above. But still, what is the exact
version of the guest agent?

I have tried already different versions.
For example:
qemu-guest-agent.x86_64 15:4.2.0-48.module_el8.4.0+783+f8734d30
@@commandline
qemu-guest-agent.x86_64 15:2.12.0-88.module_el8.1.0+248+298dec18
@AppStream

The qemu-guest agent is installed on VMs (the VM OS is CentOS 8).

Any advice how to troubleshoot this?

I can see the stats will be presented in the GUI, if I migrate the VM to a
different host.

Same here, could you provide version of vdsm and libvirt on the host
where your VM is working fine?

KVM Version: 5.2.0 - 16.el8
LIBVIRT Version: libvirt-7.0.0-14.1.el8
VDSM Version: vdsm-4.40.70.6-1.el8

My 4 hosts are running the same versions on CentOS 8.
As I said I can migrate the VM to another host and the exclamation
mark is gone and the information IPs and FQDNs are displayed.

Tomas

Best regards
Christoph

[ovirt-users] Re: [4.4.7] The latest guest agent needs to be installed and running on the guest

2021-07-08 Thread Christoph Timm


Hi Tomáš,

sorry for the late reply and for my the missing information.

Am 08.07.21 um 16:50 schrieb Tomáš Golembiovský:

On Thu, Jul 08, 2021 at 02:02:14PM +0200, Christoph Timm wrote:

Hi list,

I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs have
issues to report the performance information via the guest agent.

The performance info is provided by libvirt and not by guest agent.
Could you be more specific about which information is missing?
Sorry I did not mean the performance information like Memory, CPU and 
Network. These are available. The missing information are IP Addresses 
and FQDN.


What is the version of vdsm and libvirt on the host?

All hosts are running:libvirt-7.0.0-14.1.el8



I see the following message on the VMs: The latest guest agent needs to be
installed and running on the guest


This is probably unrelated to the above. But still, what is the exact
version of the guest agent?

I have tried already different versions.
For example:
qemu-guest-agent.x86_64 15:4.2.0-48.module_el8.4.0+783+f8734d30 
@@commandline

qemu-guest-agent.x86_64 15:2.12.0-88.module_el8.1.0+248+298dec18 @AppStream




The qemu-guest agent is installed on VMs (the VM OS is CentOS 8).

Any advice how to troubleshoot this?

I can see the stats will be presented in the GUI, if I migrate the VM to a
different host.

Same here, could you provide version of vdsm and libvirt on the host
where your VM is working fine?

KVM Version: 5.2.0 - 16.el8
LIBVIRT Version: libvirt-7.0.0-14.1.el8
VDSM Version: vdsm-4.40.70.6-1.el8

My 4 hosts are running the same versions on CentOS 8.
As I said I can migrate the VM to another host and the exclamation mark 
is gone and the information IPs and FQDNs are displayed.


 Tomas


Best regards
Christoph

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/4F5X6BK5OYACFSPSLIHWYE2NXQROS5R3/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/KT6FNKUQXQ5HGELZRZNGZX57MHOH4SFV/

[ovirt-users] [4.4.7] The latest guest agent needs to be installed and running on the guest

2021-07-08 Thread Christoph Timm


Hi list,

I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs 
have issues to report the performance information via the guest agent.


I see the following message on the VMs: The latest guest agent needs to 
be installed and running on the guest


The qemu-guest agent is installed on VMs (the VM OS is CentOS 8).

Any advice how to troubleshoot this?

I can see the stats will be presented in the GUI, if I migrate the VM to 
a different host.


Best regards
Christoph

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/4F5X6BK5OYACFSPSLIHWYE2NXQROS5R3/

[ovirt-users] Re: oVirt Engine LDAP aaa - rfc2307bis issues

2020-11-23 Thread Christoph Timm


Hi Jake,

I'm also using the RFC2307bis schema in my LDAP server.

We are still running 4.3.10 not sure if this will be different in 4.4.
I have changed my aaa properties file to use my own LDAP config file.
Which looks like this:
|include = 
|

The file need to be located here: 
/usr/share/ovirt-engine-extension-aaa-ldap/profiles/rfc2307-special.properties

Content will be like this:
include = 
search.rfc2307-resolve-groups-memberUid.search-request.filter = 
&(objectClass=posixGroup)(member=${seq:_rfc2307_dn})


That enabled group support for me.

Maybe it helps you as well.

Best regards
Christoph


Am 23.11.20 um 11:50 schrieb Jake R:

Hi,

I have LDAP with rfc2307bis schema - I have posixGroup, with members 
defined as FDNs under the member attribute.


Currently, if I login to oVirt via the AAA extension. then my groups 
are not enumerated. The LDAP searches (recorded on the LDAP server)  are:


 slapd[1503]: conn=7876 op=2 SRCH base="dc=example,dc=com" scope=2 
deref=0 filter="(&(objectClass=posixGroup)(memberUid=jreynolds))"

 slapd[1503]: conn=7876 op=2 SRCH attr=entryUUID cn description
 slapd[1503]: conn=7871 op=2 SRCH base="dc=example,dc=com" scope=2 
deref=0 
filter="(&(|(objectClass=groupOfUniqueNames)(objectClass=posixGroup))(uniqueMember:uniqueMemberMatch:=cn=jreynolds,ou=users,dc=example,dc=com))"

 slapd[1503]: conn=7871 op=2 SRCH attr=entryUUID cn description

This returns no results, as the search needs to search for 'member' 
attribute, with an FDN. The issue looks to be inherited from the 
simple.properties file (regardless of if I use rfc2307, 
rfc2307-openldap profile), with the line:


search.simple-resolve-groups-member.search-request.filter = 
&${seq:simple_filterGroupObject}(${seq:simple_attrGroupMemberDN}=${seq:_simple_dn_encoded})


I can fix the issue by replacing "${seq:simple_attrGroupMemberDN}=" 
with "member=", but this feels pretty hacky. I cannot find where this 
variable is defined, nor how to change it. Is the correct way to do 
this to create a new profile that overwrites the filter value? Or am I 
doing something wrong? I don't think my LDAP schema is particularly 
unusual, as far as I'm aware it complies with rfc2307bis spec.


Thanks,
Jake

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3XOIVHSOLQ2VWVKGB6T4V5Z6GIDATR76/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/FBDEC2IIFGGIGCDFKGNODJZZRCR5LIOX/

[ovirt-users] oVrit 4.3.10 on CentOS 7.9

2020-11-12 Thread Christoph Timm


Hi list,

I want to update my oVirt installation to 4.3.10 on the weekend to get 
ready to move to 4.4 by end of December.


Would it be OK to update to oVirt 4.3.10 on CentOS 7.9 which was release 
today?


Best regards
Christoph
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IZTVRWU42EUMSPJLTCMB2OZPVQWGZWB7/

38 matches

Mail list logo