[ovirt-users] Re: Fibre Channel storage issue
On Thu, Feb 10, 2022 at 1:10 AM Timothy J. Wielgos via Users
wrote:
>
> Thanks everyone for helping me through the last issue I had. Once I changed
> bonding mode to 2, everything worked.
>
> However, now I have another issue.
>
> I'm trying to install this using fibre channel storage. I set up a new lun
> from my storage array, assigned it to my host, and configured multipathing.
> All looks good. Then, when I ran the install script, I got the following
> error:
>
> [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail
> is "[Physical device initialization failed. Please check that the device is
> empty and accessible by the host.]". HTTP response code is 400.
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault
> reason is \"Operation Failed\". Fault detail is \"[Physical device
> initialization failed. Please check that the device is empty and accessible
> by the host.]\". HTTP response code is 400."}
>
>
>
> Google says that's because the lun is dirty - maybe reused. I tried doing
> the suggested - I used dd to write all zeroes to the lun. I used wipefs on
> the lun. I deleted the lun from the array and created a new one. No matter
> what I did with that lun, it's still showing up with this error.
>
> I then created a second LUN. I mapped it to the host, and attempted to use
> that lun for storage - and it worked!
>
> There must be a dirty config somewhere on this thing that I need to clean up
> from that first lun.
>
> Anybody know what I might have to clean up on this host to clear out that old
> config?
dd zeros should have been enough, for the storage.
To clean the host, you can try ovirt-hosted-engine-cleanup before
retrying, but this script is not perfect - if in doubt, better
reinstall the OS.
Can you please check/share relevant logs from /var/log on the host -
vdsm/*, ovirt-hosted-engine-*/*?
Best regards,
--
Didi
___
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/B4S6VGC32HKBWACDYTUTN26CCOF4ULLF/
[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED
On Wed, Feb 9, 2022, 21:33 Nir Soffer wrote: > On Wed, Feb 9, 2022 at 5:06 PM Gilboa Davara wrote: > > > > > > On Wed, Feb 9, 2022 at 3:35 PM Nir Soffer wrote: > >> > >> On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara > wrote: > >> > > >> > On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov > wrote: > >> >> > >> >> Or just add an exclude in /etc/dnf/dnf.conf > >> > > >> > > >> > I personally added and exclusion to > /etc/yum.repos.d/CentOS-Stream-AppStream.repo > >> > exclude=qemu* > >> > It allows ovirt-4.4* repos to push a new qemu release, without > letting CentOS stream break things... > >> > >> But new libvirt versions may require a newer qemu version, and oVirt > itself > >> may require a new libvirt version. > >> > >> These kind of excludes are fragile and need constant maintenance. > >> > >> Nir > > > > > > The previous poster proposed a global qemu exclusion. > > I propose a partial qemu exclusion (on centos-streams only), with the > assumption that ovirt-required qemu will be pushed directly via the ovirt > repo. > > In both cases, this is a temporary measure needed to avoid using the > broken qemu pushed by streams. > > In both cases libvirt update from appstreams will get blocked - assuming > it requires the broken qemu release. > > > > Do you advise we simply --exclude=qemu* everything we run dnf? I would > imagine it's far more dangerous and will block libvirt update just as well. > > I don't have a better solution, I just wanted to warn about these excludes. > > Nir > Ok, understood, thanks. Gilboa > ___ 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/WYUFB55GKFXI7UDTHZLEZNFYVDVQEEDW/
[ovirt-users] Fibre Channel storage issue
Thanks everyone for helping me through the last issue I had. Once I changed
bonding mode to 2, everything worked.
However, now I have another issue.
I'm trying to install this using fibre channel storage. I set up a new lun
from my storage array, assigned it to my host, and configured multipathing.
All looks good. Then, when I ran the install script, I got the following error:
[ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is
"[Physical device initialization failed. Please check that the device is empty
and accessible by the host.]". HTTP response code is 400.[ ERROR ] fatal:
[localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation
Failed\". Fault detail is \"[Physical device initialization failed. Please
check that the device is empty and accessible by the host.]\". HTTP response
code is 400."}
Google says that's because the lun is dirty - maybe reused. I tried doing the
suggested - I used dd to write all zeroes to the lun. I used wipefs on the
lun. I deleted the lun from the array and created a new one. No matter what I
did with that lun, it's still showing up with this error.
I then created a second LUN. I mapped it to the host, and attempted to use
that lun for storage - and it worked!
There must be a dirty config somewhere on this thing that I need to clean up
from that first lun.
Anybody know what I might have to clean up on this host to clear out that old
config?___
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/CTFW546WOEVCDZ4C7EZMDLROQ7IKUOU6/
[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED
On Wed, Feb 9, 2022 at 5:06 PM Gilboa Davara wrote: > > > On Wed, Feb 9, 2022 at 3:35 PM Nir Soffer wrote: >> >> On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara wrote: >> > >> > On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov >> > wrote: >> >> >> >> Or just add an exclude in /etc/dnf/dnf.conf >> > >> > >> > I personally added and exclusion to >> > /etc/yum.repos.d/CentOS-Stream-AppStream.repo >> > exclude=qemu* >> > It allows ovirt-4.4* repos to push a new qemu release, without letting >> > CentOS stream break things... >> >> But new libvirt versions may require a newer qemu version, and oVirt itself >> may require a new libvirt version. >> >> These kind of excludes are fragile and need constant maintenance. >> >> Nir > > > The previous poster proposed a global qemu exclusion. > I propose a partial qemu exclusion (on centos-streams only), with the > assumption that ovirt-required qemu will be pushed directly via the ovirt > repo. > In both cases, this is a temporary measure needed to avoid using the broken > qemu pushed by streams. > In both cases libvirt update from appstreams will get blocked - assuming it > requires the broken qemu release. > > Do you advise we simply --exclude=qemu* everything we run dnf? I would > imagine it's far more dangerous and will block libvirt update just as well. I don't have a better solution, I just wanted to warn about these excludes. Nir ___ 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/A46XCFC7PYWPAF7EDS2LU4SDYP34J3XW/
[ovirt-users] Re: Unable to install on a bonded NIC
An alternative, you install it without bonding, you install the manager on
eth0, you install the HE and you add the host and there you create the
bonding and the corresponding vlans of each host
El mié., 9 de febrero de 2022 12:40 p. m., Timothy J. Wielgos via Users <
users@ovirt.org> escribió:
> That did it!
>
> I changed bonding mode from 0 to 2 (XOR) and it installs!
>
> I think that error message needs to be a bit more descriptive, and
> documentation should be updated to reflect that bonding mode 0 is not
> supported.
>
> Thanks all for your help!
>
> On Tuesday, February 8, 2022, 05:19:58 PM CST, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>
> On Tue, Feb 8, 2022 at 10:41 PM Tim W. via Users wrote:
>
> I think I found the problem. The regex in
> 001_validate_network_interfaces.yml really wants there to be a number after
> the 'bond' identifier, i.e. bond0. However, the regex is as follows:
>
> bond_valid_name="{{ iface_item | regex_search('(^bond[0-9]+)') }}"
>
> which will not return a good value if just 'bond' is passed to it (the
> output of nmcli -g GENERAL.TYPE device show).
>
> However, I am not an ansible expert, nor am I an expert on how these
> scripts are called. I humbly request someone else's expert opinion on this.
>
> Thanks again.
>
>
>
> I think the main failure reason is about the current bonding mode:
> balance-rr that is not supported:
>
>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/sect-network_bonding#Bonding_Modes
>
> Actually here below in hosted engine installation guide:
>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_command_line/installing_hosts_for_rhv_she_cli_deploy#Recommended_practices_for_configuring_host_networks_SHE_cli_deploy
>
> is stated:
> "
> If the ovirtmgmt network is not used by virtual machines, the network may
> use any supported bonding mode.
> "
>
> But in 001_validate_network_interfaces.yml there is:
>
> - name: Set variable for supported bond modes
> set_fact:
> acceptable_bond_modes: ['active-backup', 'balance-xor', 'broadcast',
> '802.3ad']
>
> and then a when condition with
>
> hostvars[inventory_hostname]['ansible_' + iface_item]['mode'] in
> acceptable_bond_modes
>
> so that the balance-rr interface is filtered out.
> Not digged about the "false" positive regarding messages about only team
> devices detected...
>
> HIH,
> Gianluca
>
>
> ___
> 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/M5URESC32W4MQ2HVB2HMSXAKCSCQTKFX/
>
___
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/PFDZYHKKNOAFD7WLLIOFD4D5TYBE2O3C/
[ovirt-users] Re: Unable to install on a bonded NIC
That did it!
I changed bonding mode from 0 to 2 (XOR) and it installs!
I think that error message needs to be a bit more descriptive, and
documentation should be updated to reflect that bonding mode 0 is not supported.
Thanks all for your help!
On Tuesday, February 8, 2022, 05:19:58 PM CST, Gianluca Cecchi
wrote:
On Tue, Feb 8, 2022 at 10:41 PM Tim W. via Users wrote:
I think I found the problem. The regex in 001_validate_network_interfaces.yml
really wants there to be a number after the 'bond' identifier, i.e. bond0.
However, the regex is as follows:
bond_valid_name="{{ iface_item | regex_search('(^bond[0-9]+)') }}"
which will not return a good value if just 'bond' is passed to it (the output
of nmcli -g GENERAL.TYPE device show).
However, I am not an ansible expert, nor am I an expert on how these scripts
are called. I humbly request someone else's expert opinion on this.
Thanks again.
I think the main failure reason is about the current bonding mode: balance-rr
that is not supported:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/sect-network_bonding#Bonding_Modes
Actually here below in hosted engine installation guide:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_command_line/installing_hosts_for_rhv_she_cli_deploy#Recommended_practices_for_configuring_host_networks_SHE_cli_deploy
is stated:
"If the ovirtmgmt network is not used by virtual machines, the network may use
any supported bonding mode."
But in 001_validate_network_interfaces.yml there is:
- name: Set variable for supported bond modes
set_fact:
acceptable_bond_modes: ['active-backup', 'balance-xor', 'broadcast',
'802.3ad']
and then a when condition with
hostvars[inventory_hostname]['ansible_' + iface_item]['mode'] in
acceptable_bond_modes
so that the balance-rr interface is filtered out.Not digged about the "false"
positive regarding messages about only team devices detected...
HIH,
Gianluca
___
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/M5URESC32W4MQ2HVB2HMSXAKCSCQTKFX/
[ovirt-users] Re: RHGS and RHV closing down: could you please put that on the home page?
Il giorno mer 9 feb 2022 alle ore 16:39 赵井达 ha scritto: > Hi, I am the head of the oVirt China User Community, which is founded and > maintained by a non-profit organization. Our site: www.cnovirt.com. > Hi, a huge welcome to the user mailing list! > First of all, thanks to the oVirt community for providing such an > excellent open source project. We hope this project can continue > forever.Our community currently has 1000+ registered users and an online > communication group of 500+ enthusiasts. > > The work we have done so far: > 1. Share the oVirt tutorial in Chinese. > 2. Answer the questions in the use of oVirt. (Due to language problems, > these users cannot directly participate in the maillist) > 3. The oVirt mirror site has been established: > http://mirror.massclouds.com/ovirt/, which is convenient for users in > China to obtain and update software packages. > 4. Publish and maintain oVirt desktop client software opencc, > https://github.com/cnovirt/opencc-ovirt-pro, > https://gitee.com/cnovirt/opencc-ovirt-pro. > 5. Publish and maintain the offline version, merge the engine rpm into the > node and remove the dependency on the external network during deployment. > An iso image of the engine is made to facilitate independent deployment. > > We plan to contribute to the community in the following ways: > 1. Collect user questions and feedback bugs to the community. > 2. Try to participate in bug fixes. > 3. Submit some code, such as oVirt's support for arm architecture and > loongarch. > 4. Participate in the preparation of Chinese version documents. > Looking forward to collaborating with the Chinese community! +Avital Pinnick a heads up we need to organize the docs to be able to accept contributions in different languages if not already able to accept contributions in that direction. > > > > -- > Jingda Zhao > > 发件人："Sandro Bonazzola" > 发送日期：2022-02-07 15:54:30 > 收件人："Nathanaël Blanchet" ,"Sanja Bonic" < > sbo...@redhat.com> > 抄送人："Thomas Hoberg" ,"oVirt Users" > 主题：[ovirt-users] Re: RHGS and RHV closing down: could you please put that > on the home page? > > > > Il giorno sab 5 feb 2022 alle ore 13:30 Nathanaël Blanchet < > blanc...@abes.fr> ha scritto: > >> Can anybody from redhat confirm what is supposed here, all my staff >> depends on the future of ovirt. How can we help to maintain this project >> alive if redhat dev are not implicated anymore? I may donate some hardware >> or is it unuseful? >> > > Looks like this is being asked on several channels so I guess I'll end up > writing a blog post or add some statement on the oVirt home page. > Anyway, let me reiterate the message: > > This has been discussed publicly ( > https://lists.ovirt.org/archives/list/users@ovirt.org/message/VIYHOW3WDR6N4APWIXQQONVHNXT3LK5L/ > ) > As a product, Redhat Virtualization has a different lifecycle than > oVirt which is a community project. > What will be the future of oVirt project depends on how the community will > be shaping it. > As members of the Red Hat team working on the oVirt project we are > actively doing whatever we can to ensure that the project will survive > after we'll stop working on it in the future. > - We are moving the development to public platform (GitHub) > - We are changing our release process to ship oVirt builds via widely > supported community systems like Fedora COPR and CentOS CBS. > - We started a peering program helping whoever would like to start having > an active role in oVirt community trying to make the onboarding as easy as > possible ( > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QQVZHTFBF7NVI67PYW2EY2HV5FSIBVF3/ > ) > - We actively reached out to Rocky Linux, Alma Linux and Oracle, trying > to engage them (CentOS is already engaged providing Community Build System > for Virtualization SIG). > So, what will be the future of the oVirt project depends on how the > community will be shaping it. You're welcome to contribute to shaping this > future! https://ovirt.org/develop/ > > Up to now: > - We have one person who reached out being interested to the peering > program, Maithreyi Gopal ( > https://lists.ovirt.org/archives/list/de...@ovirt.org/message/TSSE7U36UQTEGEBPWLUAETCGV4XOYLOL/ > ) and she's been peered with @Sanja Bonic . > - Rocky Linux replied they were discussing within the Foundation meeting > about oVirt but I didn't got the result of the discussion yet. > - Oracle replied they are looking to get a list of OLVM developers that > can join the peering program in October 2021 but nobody reached out so far. > - I don't remember I have seen any reply from Alma so far. > - Tried to reach out to oVirt China http://www.cnovirt.com/ as they seems > to ship a rebuild of oVirt targeting Chinese speaking users without any > success > > That said, no : oVirt is not dead. oVirt 4.5 is being developed actively > and it has 566 bugzilla tickets targeting it: > https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt-4.5.0%
[ovirt-users] Re: RHGS and RHV closing down: could you please put that on the home page?
Hi, I am the head of the oVirt China User Community, which is founded and maintained by a non-profit organization. Our site: www.cnovirt.com. First of all, thanks to the oVirt community for providing such an excellent open source project. We hope this project can continue forever.Our community currently has 1000+ registered users and an online communication group of 500+ enthusiasts. The work we have done so far: 1. Share the oVirt tutorial in Chinese. 2. Answer the questions in the use of oVirt. (Due to language problems, these users cannot directly participate in the maillist) 3. The oVirt mirror site has been established: http://mirror.massclouds.com/ovirt/, which is convenient for users in China to obtain and update software packages. 4. Publish and maintain oVirt desktop client software opencc, https://github.com/cnovirt/opencc-ovirt-pro, https://gitee.com/cnovirt/opencc-ovirt-pro. 5. Publish and maintain the offline version, merge the engine rpm into the node and remove the dependency on the external network during deployment. An iso image of the engine is made to facilitate independent deployment. We plan to contribute to the community in the following ways: 1. Collect user questions and feedback bugs to the community. 2. Try to participate in bug fixes. 3. Submit some code, such as oVirt's support for arm architecture and loongarch. 4. Participate in the preparation of Chinese version documents. -- Jingda Zhao 发件人："Sandro Bonazzola" 发送日期：2022-02-07 15:54:30 收件人："Nathanaël Blanchet" ,"Sanja Bonic" 抄送人："Thomas Hoberg" ,"oVirt Users" 主题：[ovirt-users] Re: RHGS and RHV closing down: could you please put that on the home page? Il giorno sab 5 feb 2022 alle ore 13:30 Nathanaël Blanchet ha scritto: Can anybody from redhat confirm what is supposed here, all my staff depends on the future of ovirt. How can we help to maintain this project alive if redhat dev are not implicated anymore? I may donate some hardware or is it unuseful? Looks like this is being asked on several channels so I guess I'll end up writing a blog post or add some statement on the oVirt home page. Anyway, let me reiterate the message: This has been discussed publicly (https://lists.ovirt.org/archives/list/users@ovirt.org/message/VIYHOW3WDR6N4APWIXQQONVHNXT3LK5L/ ) As a product, Redhat Virtualization has a different lifecycle than oVirt which is a community project. What will be the future of oVirt project depends on how the community will be shaping it. As members of the Red Hat team working on the oVirt project we are actively doing whatever we can to ensure that the project will survive after we'll stop working on it in the future. - We are moving the development to public platform (GitHub) - We are changing our release process to ship oVirt builds via widely supported community systems like Fedora COPR and CentOS CBS. - We started a peering program helping whoever would like to start having an active role in oVirt community trying to make the onboarding as easy as possible (https://lists.ovirt.org/archives/list/users@ovirt.org/message/QQVZHTFBF7NVI67PYW2EY2HV5FSIBVF3/ ) - We actively reached out to Rocky Linux, Alma Linux and Oracle, trying to engage them (CentOS is already engaged providing Community Build System for Virtualization SIG). So, what will be the future of the oVirt project depends on how the community will be shaping it. You're welcome to contribute to shaping this future! https://ovirt.org/develop/ Up to now: - We have one person who reached out being interested to the peering program, Maithreyi Gopal (https://lists.ovirt.org/archives/list/de...@ovirt.org/message/TSSE7U36UQTEGEBPWLUAETCGV4XOYLOL/ ) and she's been peered with @Sanja Bonic . - Rocky Linux replied they were discussing within the Foundation meeting about oVirt but I didn't got the result of the discussion yet. - Oracle replied they are looking to get a list of OLVM developers that can join the peering program in October 2021 but nobody reached out so far. - I don't remember I have seen any reply from Alma so far. - Tried to reach out to oVirt China http://www.cnovirt.com/ as they seems to ship a rebuild of oVirt targeting Chinese speaking users without any success That said, no : oVirt is not dead. oVirt 4.5 is being developed actively and it has 566 bugzilla tickets targeting it: https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt-4.5.0%20 and 242 of them have been already handled. Le 5 févr. 2022 11:31, Thomas Hoberg a écrit : Please have a look here: https://access.redhat.com/support/policy/updates/rhev/ Without a commercial product to pay the vast majority of the developers, there is just no chance oVirt can survive (unless you're ready to take over). RHV 4.4 full support ends this August and that very likely means that oVirt won't receive updates past July (judging by how things happened with 4.3). And those will be CI tested against
[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED
On Wed, Feb 9, 2022 at 3:35 PM Nir Soffer wrote: > On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara wrote: > > > > On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov > wrote: > >> > >> Or just add an exclude in /etc/dnf/dnf.conf > > > > > > I personally added and exclusion to > /etc/yum.repos.d/CentOS-Stream-AppStream.repo > > exclude=qemu* > > It allows ovirt-4.4* repos to push a new qemu release, without letting > CentOS stream break things... > > But new libvirt versions may require a newer qemu version, and oVirt itself > may require a new libvirt version. > > These kind of excludes are fragile and need constant maintenance. > > Nir > The previous poster proposed a global qemu exclusion. I propose a partial qemu exclusion (on centos-streams only), with the assumption that ovirt-required qemu will be pushed directly via the ovirt repo. In both cases, this is a temporary measure needed to avoid using the broken qemu pushed by streams. In both cases libvirt update from appstreams will get blocked - assuming it requires the broken qemu release. Do you advise we simply --exclude=qemu* everything we run dnf? I would imagine it's far more dangerous and will block libvirt update just as well. ... Unless I'm missing something? - Gilboa ___ 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/F7XJJERVVZY2NC5BR7Y46KJUQFHANWRB/
[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED
On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara wrote: > > On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov wrote: >> >> Or just add an exclude in /etc/dnf/dnf.conf > > > I personally added and exclusion to > /etc/yum.repos.d/CentOS-Stream-AppStream.repo > exclude=qemu* > It allows ovirt-4.4* repos to push a new qemu release, without letting CentOS > stream break things... But new libvirt versions may require a newer qemu version, and oVirt itself may require a new libvirt version. These kind of excludes are fragile and need constant maintenance. Nir ___ 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/GUCYLOMBEETBHGP7GPPEAWYSYSRSP2LC/
[ovirt-users] Re: what are the steps to swap/upgrade/reboot my main storage domain with minimum downtime
Depends what you mean by "sync" and "swap". If you can keep the same NFS endpoint, but swap-in your upgraded storage under the hood then I think you can do as you propose. Stop all VMs, put the storage domain in maintenance, make you changes and bring the domain out of maintenance. However, if you're moving to a different NFS server, or even different path on the same server then I think the answer is no. In this scenario you'd need to create a new domain and move each vdisk across. On Wed, 09 Feb 2022 06:07:44 + Pascal D wrote I need to upgrade my main domain storage (NFS) which hosts 100s of VMs and templates including the hosted engine. Can I put the data center in global maintenance, do a quick sync and swap of the domain storage and bring it back up without missing a beat? ___ Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email to mailto: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/LM4CUDWXJKR2RH5ITCAQG4O56J3YXA2N/___ 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/72E3A4J4DK6AOI5GQT6BS6V53V4EPNO5/
[ovirt-users] Re: what are the steps to swap/upgrade/reboot my main storage domain with minimum downtime
Sorry, I missed the fact that you also have HE in the same domain. I think the previous statement still stands. But you'd be advised to stop the ovirt-ha-agent and ovirt-ha-broker on all hosts as well. On Wed, 09 Feb 2022 06:07:44 + Pascal D wrote I need to upgrade my main domain storage (NFS) which hosts 100s of VMs and templates including the hosted engine. Can I put the data center in global maintenance, do a quick sync and swap of the domain storage and bring it back up without missing a beat? ___ Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email to mailto: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/LM4CUDWXJKR2RH5ITCAQG4O56J3YXA2N/___ 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/CMDO4MHVIIJQXYVLFVLOWGTBR4KNDWHX/
[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED
On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov wrote: > Or just add an exclude in /etc/dnf/dnf.conf I personally added and exclusion to /etc/yum.repos.d/CentOS-Stream-AppStream.repo exclude=qemu* It allows ovirt-4.4* repos to push a new qemu release, without letting CentOS stream break things... - Gilboa > > On Tue, Feb 8, 2022 at 18:32, Gilboa Davara > wrote: > ___ > 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/AMWN33K6BELU6VXBGVMTUEDHR2YKTIC5/ > > ___ 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/J4IMOXBMP3NFOK6FLV3OISA76TEUA5DG/
[ovirt-users] Post SSL certificate expiration recovery, openvswitch certificates are still expired. Bug?
Hello all, Seems the engine-setup fails to update the openvswitch certificate on the HE itself. $ openssl x509 -in /etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer -noout -dates notBefore=Dec 26 16:25:04 2020 GMT notAfter=Jan 29 16:25:04 2022 GMT $ engine-setup [ INFO ] Stage: Termination [ INFO ] Execution of setup completed successfully $ openssl x509 -in /etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer -noout -dates notBefore=Dec 26 16:25:04 2020 GMT notAfter=Jan 29 16:25:04 2022 GMT $ cat /var/log/messages | grep ovsdb-server ... Feb 9 09:56:32 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22660|jsonrpc|WARN|ssl:[:::192.168.2.22]:57924: receive err or: Protocol error Feb 9 09:56:32 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22661|reconnect|WARN|ssl:[:::192.168.2.22]:57924: connectio n dropped (Protocol error) Feb 9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22662|stream_ssl|WARN|SSL_accept: error:14094415:SSL routines:s sl3_read_bytes:sslv3 alert certificate expired Feb 9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22663|jsonrpc|WARN|ssl:[:::192.168.2.22]:57928: receive err or: Protocol error Feb 9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22664|reconnect|WARN|ssl:[:::192.168.2.22]:57928: connection dropped (Protocol error) @RH people. Is it a bug? - Gilboa ___ 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/4WAWTWLTTQYTOQPNL4CQKZJGZY3T7KQH/
[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue
On Wed, Feb 9, 2022 at 9:20 AM Gilboa Davara wrote: > > > On Wed, Feb 9, 2022 at 7:52 AM Patrick Hibbs > wrote: > >> The certificates used in SPICE connections are stored on the VM hosts. By >> default they are at /etc/pki/vdsm/libvirt-spice, and configured by VDSM in >> /etc/libvirt/qemu.conf. Their default names are ca-cert.pem, >> server-cert.pem, and server-key.pem. Using openssl x509 -noout -text -in >> should show you the certificate's expiration info. >> >> Note: Don't try to change anything, it will be overwritten by VDSM on the >> next host update / reinstall. >> >> As for remote-viewer, if you run it manually from the console with >> "remote-viewer --debug " or "remote-viewer --verbose >> " it will print log information about the connection >> it's trying to establish. >> >> -Patrick Hibbs >> >> > Hello, > > You must have missed my answer above. (Understandable, given the length of > this thread...) > I replaced and verified /etc/pki/vdsm/libvirt-spice/server-cert.pem > Restarted all the services on the host. > > $ openssl x509 -in /etc/pki/vdsm/libvirt-spice/server-cert.pem -noout > -dates > notBefore=Feb 7 13:59:14 2022 GMT > notAfter=Feb 7 13:59:14 2027 GMT > $ openssl x509 -in /etc/pki/vdsm/libvirt-spice/ca-cert.pem -noout -dates > notBefore=Dec 26 16:25:01 2020 GMT > notAfter=Dec 25 16:25:01 2030 GMT > > However, remote-viewer still fails: > $ remote-viewer --debug console.vv > ... > (remote-viewer:14874): Spice-WARNING **: 18:14:33.500: > ../subprojects/spice-common/common/ssl_verify.c:506:openssl > _verify: ssl: subject 'O=localdomain,CN=gilboa-wx-srv.localdomain' > verification failed > > The main problem here is that while we assume the problem is expired > certificates, it can be something else (Subject, CN, etc). > The error is not informative.. > > - Gilboa. > > > Seems that openvswitch is also using the old certificates. Feb 9 09:56:32 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22660|jsonrpc|WARN|ssl:[:::192.168.2.22]:57924: receive err or: Protocol error Feb 9 09:56:32 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22661|reconnect|WARN|ssl:[:::192.168.2.22]:57924: connectio n dropped (Protocol error) Feb 9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22662|stream_ssl|WARN|SSL_accept: error:14094415:SSL routines:s sl3_read_bytes:sslv3 alert certificate expired Feb 9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22663|jsonrpc|WARN|ssl:[:::192.168.2.22]:57928: receive err or: Protocol error Feb 9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]: ovs|22664|reconnect|WARN|ssl:[:::192.168.2.22]:57928: connection dropped (Protocol error) Seems that https://access.redhat.com/solutions/3532921 is missing a couple of certificates.. (I don't even see it in https://www.ovirt.org/develop/release-management/features/infra/pki.html). - Gilboa > > >> On Wed, 2022-02-09 at 06:58 +0200, Gilboa Davara wrote: >> >> >> >> On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov >> wrote: >> >> I have no clue , but I would give vdsm.service a restart. >> >> >> Thanks again for the prompt response. >> Tried that, restarted all services and the all the VMS, didn't work. >> >> Any idea how I can verify the certificate information actually being used >> by qemu for the spice console? >> remote-viewer just fails, without giving any meaningful error message. >> >> - Gilboa >> >> >> >> Best Regards, >> Strahil Nikolov >> >> On Tue, Feb 8, 2022 at 18:19, Gilboa Davara >> wrote: >> ___ >> 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/2GAQH44QD6KTS4RHXQBDWL6PNI6OKCS3/ >> >> ___ >> 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/OG57VT2XGDTY2MFOJFFUCZAMXS22W4OG/ >> >> >> ___ >> 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/AKQVBARD4EWIS3PCQYLX7AH575XRDYAD/ >> > ___ 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-g
