Re: Hosts are non responsive Ovirt 3.6
by Strahil Nikolov
Have you tried to put a host into maintenance, remove and then readd it ?
You can access all Red Hat solutions with their free developer subscription.
Best Regards,
Strahil Nikolov
В сряда, 6 януари 2021 г., 13:17:42 Гринуич+2, Gary Lloyd <g.lloyd(a)keele.ac.uk> написа:
Hi please could someone point me in the right direction to renew ssl certificates for vdsm to communicate with ovirt 3.6 ?
I’m aware that this version hasn’t been supported for some time, this is a legacy environment which we are working towards decommissioning.
There seems to be a fix article for RHEV but we don’t have a subscription to view this information:
How to update expired RHEV certificates when all RHEV hosts got 'Non-responsive' - Red Hat Customer Portal
These are what the vdsm hosts are showing:
Reactor thread::ERROR::2021-01-06 11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read) Error during handshake: sslv3 alert certificate expired
I have rerun engine-setup but this only seems to have fixed one of the vdsm hosts and the others are non responsive.
The others are in different clusters and we have some important services still running on these.
Thanks
Gary Lloyd
IT Infrastructure Manager
Information and Digital Services
01782 733063
Innovation Centre 2 | Keele University | ST5 5NH
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/HT6Z3WHPFTB...
4 years, 3 months
Re: Ovirt and Vagrant
by Gervais de Montbrun
I saw that yesterday!
Thanks for the help guys. I'm not a Ruby programmer, so have been poking at this on and off for weeks. It looks like the two most recent PR's may have solved my two most apparent problems with the plugin.
I want to test more functionality with vagrant (like suspend, halt, resume, etc), but 🤞we are fully on track again.
Cheers,
Gervais
> On Jan 6, 2021, at 8:18 AM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
> Hello Gervais,
> update from our developers
>
> I've just checked the email chain, and it looks like it has since been fixed up stream (https://github.com/myoung34/vagrant-ovirt4/pull/121 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub....>) but perhaps not included in any gem release yet...
>
> Regards,
> Paul S.
> From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk <mailto:P.Staniforth@leedsbeckett.ac.uk>>
> Sent: 06 January 2021 10:59
> To: Gervais de Montbrun <gervais(a)demontbrun.com <mailto:gervais@demontbrun.com>>; users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org <mailto:users@ovirt.org>>
> Subject: Re: [ovirt-users] Ovirt and Vagrant
>
> Hello Gervais,
> I have asked our developers who use the plugin and here is the response.
> Regards,
>
> Paul S.
>
> Hi Paul,
>
> We have had to maintain our own changes to the oVirt Vagrant plugin. Probably we need to start committing to and publishing our own fork.
>
> Theres an obtuse and broken long one liner that get's the IP addresses, which has always been a bit problematic, and stopped working altogether with the newest release of oVirt we are using.
>
> Anyway, here are the changes we made to get the IP addresses working with the new versions of oVirt:
>
> line 58 wait_till_up.rb
> ip_addr = nil
> vm_nics_service = server.nics_service
> nics = vm_nics_service.list
> nics.each { |nic|
> puts "Waiting on #{nic.mac.address}"
> vm_nics_service.nic_service(nic.id <http://nic.id/>).reported_devices_service.list.each { |device|
> device.ips&.each {|ip|
> puts "ip: #{ip.to_s}"
> if ip && ip.version == 'v4' && ip.address
> ip_addr = ip.address
> break
> end
> }
> }
> }
>
> Also same in read_ssh.rb:
> ip_addr = nil
> vm_nics_service = server.nics_service
> nics = vm_nics_service.list
> nics.each { |nic|
> vm_nics_service.nic_service(nic.id <http://nic.id/>).reported_devices_service.list.each { |device|
> device.ips&.each {|ip|
> if ip && ip.version == 'v4' && ip.address
> ip_addr = ip.address
> break
> end
> }
> }
> }
> Sorry it's not the best way to share code, but feel free to pass this along.
>
> Cheers,
> Cliffe.
>
>
> .
>
> From: Gervais de Montbrun <gervais(a)demontbrun.com <mailto:gervais@demontbrun.com>>
> Sent: 04 January 2021 18:14
> To: users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org <mailto:users@ovirt.org>>
> Subject: [ovirt-users] Ovirt and Vagrant
>
> Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
> Anyone using vagrant with oVirt 4.4?
>
> I am trying to get the vagrant plugin working with oVirt, but I am experiencing issues. https://github.com/myoung34/vagrant-ovirt4/issues/120 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub....>
> I wonder what other folks are using or if someone has any suggestions to offer.
>
> We are trying to switch from vSphere to oVirt for internal, developer vm's at my office and we have a successful workflow using vagrant-vsphere plugin. Switching to oVirt should have been a simple step, but the issue I an having is a blocker.
>
> I built a single hyperconverged server to test with. Everything seems to work fine when I bring up vm's manually in my "cluster." Networking, console, etc all work fine. Ovirt-guest-additions work fine and display the vm's ip in the gui.
>
> When I try with the vagrant plugin, there seems to be a communication issue. Even though I can see the vm reporting its IP address fine in the ovirt web gui, it seems like the vagrant plugin is unable to do the same. The maintainer of the code says that he no longer runs oVirt which is why I am reaching out here to see if anyone has a suggestion or even an alternative to suggest.
>
> Cheers,
> Gervais
>
>
>
> To view the terms under which this email is distributed, please go to:-
> http://leedsbeckett.ac.uk/disclaimer/email/ <http://leedsbeckett.ac.uk/disclaimer/email/>_______________________________________________
> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OVFHZP4HSVG... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/OVFHZP4HSVG...>
4 years, 3 months
Re: Ovirt and Vagrant
by Staniforth, Paul
Hello Gervais,
update from our developers
I've just checked the email chain, and it looks like it has since been fixed up stream (https://github.com/myoung34/vagrant-ovirt4/pull/121<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub....>) but perhaps not included in any gem release yet...
Regards,
Paul S.
________________________________
From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
Sent: 06 January 2021 10:59
To: Gervais de Montbrun <gervais(a)demontbrun.com>; users(a)ovirt.org <users(a)ovirt.org>
Subject: Re: [ovirt-users] Ovirt and Vagrant
Hello Gervais,
I have asked our developers who use the plugin and here is the response.
Regards,
Paul S.
Hi Paul,
We have had to maintain our own changes to the oVirt Vagrant plugin. Probably we need to start committing to and publishing our own fork.
Theres an obtuse and broken long one liner that get's the IP addresses, which has always been a bit problematic, and stopped working altogether with the newest release of oVirt we are using.
Anyway, here are the changes we made to get the IP addresses working with the new versions of oVirt:
line 58 wait_till_up.rb
ip_addr = nil
vm_nics_service = server.nics_service
nics = vm_nics_service.list
nics.each { |nic|
puts "Waiting on #{nic.mac.address}"
vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { |device|
device.ips&.each {|ip|
puts "ip: #{ip.to_s}"
if ip && ip.version == 'v4' && ip.address
ip_addr = ip.address
break
end
}
}
}
Also same in read_ssh.rb:
ip_addr = nil
vm_nics_service = server.nics_service
nics = vm_nics_service.list
nics.each { |nic|
vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { |device|
device.ips&.each {|ip|
if ip && ip.version == 'v4' && ip.address
ip_addr = ip.address
break
end
}
}
}
Sorry it's not the best way to share code, but feel free to pass this along.
Cheers,
Cliffe.
.
________________________________
From: Gervais de Montbrun <gervais(a)demontbrun.com>
Sent: 04 January 2021 18:14
To: users(a)ovirt.org <users(a)ovirt.org>
Subject: [ovirt-users] Ovirt and Vagrant
Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
Anyone using vagrant with oVirt 4.4?
I am trying to get the vagrant plugin working with oVirt, but I am experiencing issues. https://github.com/myoung34/vagrant-ovirt4/issues/120<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub....>
I wonder what other folks are using or if someone has any suggestions to offer.
We are trying to switch from vSphere to oVirt for internal, developer vm's at my office and we have a successful workflow using vagrant-vsphere plugin. Switching to oVirt should have been a simple step, but the issue I an having is a blocker.
I built a single hyperconverged server to test with. Everything seems to work fine when I bring up vm's manually in my "cluster." Networking, console, etc all work fine. Ovirt-guest-additions work fine and display the vm's ip in the gui.
When I try with the vagrant plugin, there seems to be a communication issue. Even though I can see the vm reporting its IP address fine in the ovirt web gui, it seems like the vagrant plugin is unable to do the same. The maintainer of the code says that he no longer runs oVirt which is why I am reaching out here to see if anyone has a suggestion or even an alternative to suggest.
Cheers,
Gervais
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
4 years, 3 months
Re: Hosts are non responsive Ovirt 3.6
by Yedidyah Bar David
On Wed, Jan 6, 2021 at 1:17 PM Gary Lloyd <g.lloyd(a)keele.ac.uk> wrote:
> Hi please could someone point me in the right direction to renew ssl
> certificates for vdsm to communicate with ovirt 3.6 ?
>
> I’m aware that this version hasn’t been supported for some time, this is a
> legacy environment which we are working towards decommissioning.
>
>
>
> There seems to be a fix article for RHEV but we don’t have a subscription
> to view this information:
>
> How to update expired RHEV certificates when all RHEV hosts got
> 'Non-responsive' - Red Hat Customer Portal
> <https://access.redhat.com/solutions/3028811>
>
>
>
> These are what the vdsm hosts are showing:
>
> Reactor thread::ERROR::2021-01-06
> 11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
> Error during handshake: sslv3 alert certificate expired
>
>
>
> I have rerun engine-setup but this only seems to have fixed one of the
> vdsm hosts and the others are non responsive.
>
> The others are in different clusters and we have some important services
> still running on these.
>
The "canonical" way is to "Reinstall" or "Enroll Certificates".
I think this will require stopping all VMs on them.
Good luck and best regards,
--
Didi
4 years, 3 months
Hosts are non responsive Ovirt 3.6
by Gary Lloyd
Hi please could someone point me in the right direction to renew ssl certificates for vdsm to communicate with ovirt 3.6 ?
I'm aware that this version hasn't been supported for some time, this is a legacy environment which we are working towards decommissioning.
There seems to be a fix article for RHEV but we don't have a subscription to view this information:
How to update expired RHEV certificates when all RHEV hosts got 'Non-responsive' - Red Hat Customer Portal<https://access.redhat.com/solutions/3028811>
These are what the vdsm hosts are showing:
Reactor thread::ERROR::2021-01-06 11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read) Error during handshake: sslv3 alert certificate expired
I have rerun engine-setup but this only seems to have fixed one of the vdsm hosts and the others are non responsive.
The others are in different clusters and we have some important services still running on these.
Thanks
[https://lh5.googleusercontent.com/v29r0Xyldsxb-jrbIFBAQIhyVvznLy4FvU0sxq6...]
Gary Lloyd
IT Infrastructure Manager
Information and Digital Services
01782 733063
Innovation Centre 2 | Keele University | ST5 5NH
4 years, 3 months
Ovirt and Vagrant
by Gervais de Montbrun
Anyone using vagrant with oVirt 4.4?
I am trying to get the vagrant plugin working with oVirt, but I am experiencing issues. https://github.com/myoung34/vagrant-ovirt4/issues/120 <https://github.com/myoung34/vagrant-ovirt4/issues/120>
I wonder what other folks are using or if someone has any suggestions to offer.
We are trying to switch from vSphere to oVirt for internal, developer vm's at my office and we have a successful workflow using vagrant-vsphere plugin. Switching to oVirt should have been a simple step, but the issue I an having is a blocker.
I built a single hyperconverged server to test with. Everything seems to work fine when I bring up vm's manually in my "cluster." Networking, console, etc all work fine. Ovirt-guest-additions work fine and display the vm's ip in the gui.
When I try with the vagrant plugin, there seems to be a communication issue. Even though I can see the vm reporting its IP address fine in the ovirt web gui, it seems like the vagrant plugin is unable to do the same. The maintainer of the code says that he no longer runs oVirt which is why I am reaching out here to see if anyone has a suggestion or even an alternative to suggest.
Cheers,
Gervais
4 years, 3 months
Move HostedEngine to new data domain.
by Diggy Mc
Running oVirt 4.3.9 and would like to move the HostedEngine VM in its entirety (disks, templates, etc) from its current data domain to a new one. How can this be done?
Once the engine VM has been moved, I can simply detach the data domain with all existing VMs from my 4.3 environment and then attach it to my new 4.4 environment, correct?
4 years, 3 months
