[ovirt-users] Re: Zanata user request

2022-03-23 Thread Sandro Bonazzola 
Il giorno mer 23 mar 2022 alle ore 10:54 Temuri Doghonadze <
temuri.doghona...@gmail.com> ha scritto:

> Hello again,
> Translation of 2 modules you gave access me to is completed.
> But I've noticed 2 additional modules I didn't have access to.
> Could you please tell me if they're not neccessary?
> Also, virt-manager translation is still unavailable.
>

For virt-manager I think you'll have to ask on Fedora developers mailing
list, we have no rights on that repository.



>
> On Tue, Mar 22, 2022 at 1:02 PM Temuri Doghonadze <
> temuri.doghona...@gmail.com> wrote:
>
>> Hello,
>> Got it, thank you.
>> All's ok, I'm in. Only thing I might also ask, is if you got any access
>> to person who is maintaining virt-manager, could you ask them to fix
>> translation? (at https://translate.fedoraproject.org/).
>>
>> Thanks for provided help, will try my best.
>> BR, Temuri
>>
>> On Tue, Mar 22, 2022 at 11:49 AM Sharon Gratch 
>> wrote:
>>
>>>
>>> Hi Temuri,
>>>
>>> I activated your account on Zanata (you already had one) and added you
>>> to the Georgian translation group.
>>> I'll send you the account details in a separate mail.
>>>
>>> Thanks for willing to help with translations!
>>> Sharon
>>>
>>> On Mon, Mar 21, 2022 at 3:32 PM Sandro Bonazzola 
>>> wrote:
>>>
 +Sharon Gratch  +Scott Dickerson
  +Michal Skrivanek  can you
 help here?

 Il giorno lun 21 mar 2022 alle ore 11:23 Temuri Doghonadze <
 temuri.doghona...@gmail.com> ha scritto:

> Hello,
> My name is Temuri and I'd like to ask for account for Zanata to help
> with translation of ovirt to Georgian.
>
> I've done translation of zoiper, FreeCAD, part of gitlab, protonmail,
> parts of gnome and KDE, etc etc etc.
> In case of questions feel free to ask.
> BR, Temuri
> ___
> 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/RYKJ2ZFIOYA66XY3PRPXHF5Y5ZDSTKVG/
>


 --

 Sandro Bonazzola

 MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

 Red Hat EMEA 

 sbona...@redhat.com
 

 *Red Hat respects your work life balance. Therefore there is no need to
 answer this email out of your office hours.*




-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/6PB5Z7LB3IIDLQLE76MMWHYRH5H3WKSN/

[ovirt-users] Re: Zanata user request

2022-03-23 Thread Sharon Gratch 
Hi,

On Wed, Mar 23, 2022 at 11:54 AM Temuri Doghonadze <
temuri.doghona...@gmail.com> wrote:

> Hello again,
> Translation of 2 modules you gave access me to is completed.
> But I've noticed 2 additional modules I didn't have access to.
> Could you please tell me if they're not neccessary?
>

Thanks for translating web-ui and ovirt-engine-ui-extensions projects.
Regarding the ovirt-engine project, please check now since for some reason
the Georgian language was disabled. I enabled it so it should be ok now.
The 4th project rhvm-branding is a downstream project so no need to
translate it.



> Also, virt-manager translation is still unavailable.
>
> On Tue, Mar 22, 2022 at 1:02 PM Temuri Doghonadze <
> temuri.doghona...@gmail.com> wrote:
>
>> Hello,
>> Got it, thank you.
>> All's ok, I'm in. Only thing I might also ask, is if you got any access
>> to person who is maintaining virt-manager, could you ask them to fix
>> translation? (at https://translate.fedoraproject.org/).
>>
>> Thanks for provided help, will try my best.
>> BR, Temuri
>>
>> On Tue, Mar 22, 2022 at 11:49 AM Sharon Gratch 
>> wrote:
>>
>>>
>>> Hi Temuri,
>>>
>>> I activated your account on Zanata (you already had one) and added you
>>> to the Georgian translation group.
>>> I'll send you the account details in a separate mail.
>>>
>>> Thanks for willing to help with translations!
>>> Sharon
>>>
>>> On Mon, Mar 21, 2022 at 3:32 PM Sandro Bonazzola 
>>> wrote:
>>>
 +Sharon Gratch  +Scott Dickerson
  +Michal Skrivanek  can you
 help here?

 Il giorno lun 21 mar 2022 alle ore 11:23 Temuri Doghonadze <
 temuri.doghona...@gmail.com> ha scritto:

> Hello,
> My name is Temuri and I'd like to ask for account for Zanata to help
> with translation of ovirt to Georgian.
>
> I've done translation of zoiper, FreeCAD, part of gitlab, protonmail,
> parts of gnome and KDE, etc etc etc.
> In case of questions feel free to ask.
> BR, Temuri
> ___
> 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/RYKJ2ZFIOYA66XY3PRPXHF5Y5ZDSTKVG/
>


 --

 Sandro Bonazzola

 MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

 Red Hat EMEA 

 sbona...@redhat.com
 

 *Red Hat respects your work life balance. Therefore there is no need to
 answer this email out of your office hours.*



___
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/ZNZ7AESRHIJKLYLCHCGFMYGX2SNINQ2N/

[ovirt-users] No bootable device

2022-03-23 Thread nicolas 

Hi,

We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit 
v.3, FWIW) using the GUI (Storage -> Disks -> Upload -> Start). The 
image is in qcow2 format. No options on the right side were checked. The 
upload went smoothly, so we now tried to attach the disk to a VM.


To do that, we opened the VM -> Disks -> Attach and selected the disk. 
As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so 
the "bootable" checkbox was selected.


The VM was later powered on, but when accessing the console the message 
"No bootable device." appears. We're pretty sure this is a bootable 
image, because it was tested on other virtualization infrastructure and 
it boots well. We also tried to upload the image in RAW format but the 
result is the same.


What are we missing here? Is anything else needed to do so the disk is 
bootable?


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/66MPXOVY62HCGBDOZGQKMNEE54FG6X6F/

[ovirt-users] No bootable device

2022-03-23 Thread Angus Clarke 
Hi Nicolas

In oVirt 4.3:

Compute -> Virtual Machines -> Select VM

On the VM screen:

Disks -> Highlight disk -> Edit

Check the bootable tick box

Hope that helps
Angus


From: nico...@devels.es 
Sent: 23 March 2022 14:00
To: users@ovirt.org 
Subject: [ovirt-users] No bootable device

Hi,

We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit
v.3, FWIW) using the GUI (Storage -> Disks -> Upload -> Start). The
image is in qcow2 format. No options on the right side were checked. The
upload went smoothly, so we now tried to attach the disk to a VM.

To do that, we opened the VM -> Disks -> Attach and selected the disk.
As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so
the "bootable" checkbox was selected.

The VM was later powered on, but when accessing the console the message
"No bootable device." appears. We're pretty sure this is a bootable
image, because it was tested on other virtualization infrastructure and
it boots well. We also tried to upload the image in RAW format but the
result is the same.

What are we missing here? Is anything else needed to do so the disk is
bootable?

Thanks.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.html&data=04%7C01%7C%7C21fb97dc59c24afe3c9908da0cce9079%7C84df9e7fe9f640afb435%7C1%7C0%7C637836378581024566%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2FRPdEWdd3CYyCPcn8khKsx%2BSUvPy%2BkbhoYvNTJUAhPQ%3D&reserved=0
oVirt Code of Conduct: 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2F&data=04%7C01%7C%7C21fb97dc59c24afe3c9908da0cce9079%7C84df9e7fe9f640afb435%7C1%7C0%7C637836378581024566%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Xu5G3BJFH8T0NMxR3jCfUKS0vNu81Ud3cLwIpNYYkR0%3D&reserved=0
List Archives: 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2F66MPXOVY62HCGBDOZGQKMNEE54FG6X6F%2F&data=04%7C01%7C%7C21fb97dc59c24afe3c9908da0cce9079%7C84df9e7fe9f640afb435%7C1%7C0%7C637836378581024566%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=hVp2qxt9fS2pA71HvQbZEqpRT26dSLgGk%2FoFLFbSG5I%3D&reserved=0
___
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/KGYZZVJFAGEBVGUW6XRJ2ZHIDYWC56FI/

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-23 Thread Abe E 
After running : yum reinstall ovirt-node-ng-image-update 
It re-installed the ovirt node and I was able to start VDSM again aswell as the 
ovirt-ha-broker an ovirt-ha-agent.

I was still unable to activate the 2nd Node in the engine so I tried to 
re-install with engine deploy and it was able to complete past the previous 
VDSM issue it had.

Thank You for your help in regards to the LVM issues I was having, noted for 
future reference!
___
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/KAGIM4OYGTVFBM42DHPLTEJZ7B2CL2T3/

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-23 Thread Nir Soffer 
On Wed, Mar 23, 2022 at 6:04 PM Abe E  wrote:

> After running : yum reinstall ovirt-node-ng-image-update
> It re-installed the ovirt node and I was able to start VDSM again aswell
> as the ovirt-ha-broker an ovirt-ha-agent.
>
> I was still unable to activate the 2nd Node in the engine so I tried to
> re-install with engine deploy and it was able to complete past the previous
> VDSM issue it had.
>
> Thank You for your help in regards to the LVM issues I was having, noted
> for future reference!
>

Great that you managed to recover, but if reinstalling fixed the issue, it
means that there is some issue with the node upgrade.

Sandro, do you think we need a bug for this?
___
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/UBZBQY5TYZPY55HZJ5ULX4RT4ZGBSSAX/

[ovirt-users] 4.4.9 -> 4.4.10 Cannot start or migrate any VM (hotpluggable cpus requested exceeds the maximum cpus supported by KVM)

2022-03-23 Thread Jillian Morgan 
After upgrading the engine from 4.4.9 to 4.4.10, and then upgrading one
host, any attempt to migrate a VM to that host or start a VM on that host
results in the following error:

Number of hotpluggable cpus requested (16) exceeds the maximum cpus
supported by KVM (8)

While the version of qemu is the same across hosts, (
qemu-kvm-6.0.0-33.el8s.x86_64), I traced the difference to the upgraded
kernel on the new host. I have always run elrepo's kernel-ml on these hosts
to support bcache which RHEL's kernel doesn't support. The working hosts
still run kernel-ml-5.15.12. The upgraded host ran kernel-ml-5.17.0.

In case anyone else runs kernel-ml, have you run into this issue?
Does anyone know why KVM's KVM_CAP_MAX_VCPUS value is lowered on the new
kernel?
Does anyone know how to query the KVM capabilities from userspace without
writing a program leveraging kvm_ioctl()'s?

Related to this, it seems that ovirt and/or libvirtd always runs qmu-kvm
with an -smp argument of "maxcpus=16". This causes qemu's built-in check to
fail on the new kernel which is supporting max_vpus of 8.

Why does ovirt always request maxcpus=16?

And yes, before you say it, I know you're going to say that running
kernel-ml isn't supported.

-- 
Jillian Morgan (she/her) 🏳️‍⚧️
Systems & Networking Specialist
Primordial Software Group & I.T. Consultancy
https://www.primordial.ca
___
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/YSOGCHERQIE53O2YRUTF4SUHKJ2WL7HN/

[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: dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.

2022-03-23 Thread Jillian Morgan 
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 '--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/
>>
>
> _

[ovirt-users] change mount point for hosted_storage

2022-03-23 Thread tpike 
Hello:
  I have an oVirt 4.4.10 cluster that is working fine. All storage is on NFS. I 
would like to change the mount point for the hosted_storage domain from 
localhost:/... to /... This will be the same physical volume, all I want to 
do is not run my NFS mounts through my local hosts but instead mount directly 
from the NFS server.

  I have used the "hosted-engine --set-shared-config storage" command to change 
the mount point for the storage. Looking at the hosted-engine.conf file 
confirms that the new path is set correctly. When I look at the storage inside 
the hosted-engine, however, it still shows the old value. How can I get the 
cluster to use the new path instead of the old path? I changed it both using 
he_local and he_shared keys. Thanks!

Tod Pike
___
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/BW5FHI6UAJ64BPG4INRLGEEZNGZOUJKL/

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

2022-03-23 Thread Sketch 
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 '--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-c

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

2022-03-23 Thread 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 '--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