[ovirt-users] Re: Hosted-Engine Down VSDM Cert Expired

2023-01-21 Thread Strahil Nikolov via Users
I think that https://access.redhat.com/solutions/3532921 and the links 
mentioned in it will help you solve the problem. Just make a RH dev account and 
you will be able to access the links.
The certs generated in the manager are refreshed on each engine-setup (see 
https://access.redhat.com/solutions/6865861) and once done -> you can reenroll 
the hosts' certificate.
Best Regards,Strahil Nikolov 
 
 
  On Sun, Jan 22, 2023 at 9:36, jarr...@ecboces.org wrote: 
  Hey all,

I'm looking to get a bit of guidance here. As the subject suggests, we have a 
hosted-engine ovirt cluster. I ran into an issue trying to login to the web 
interface. I was seeing errors about certificate expiration, although I didn't 
know what cert it was referring to at the time. I ssh'd to the hosted-engine 
and restarted it. However, once it shutdown, it was unable to start again.

What I've discovered so far is that the hosted-engine is currently residing on 
node 33 (storage is on a gluster volume) and the vdsm certificate for that node 
has expired. There are three nodes in total, and two of them have expired 
certs. However, one of them has a valid cert still. I'm able to run vdsm-client 
commands on that node. Although I haven't done anything with that yet other 
than to verify that I'm able to do some of the Host get* commands successfully. 
I'm wondering if it is possible to "pull" the hosted-engine onto this host and 
fire it back up there.

Thanks in advance for your help!

I'm gathering log info etc as described and it will be available here: 
https://drive.google.com/drive/folders/1cBPrN8SuIR-dgnpRKe1eKXRZZTPPshyJ?usp=sharing

Version info:
Installed Packages
centos-release-gluster8.noarch                                                  
    1.0-1.el8                                                      @extras      
  
centos-release-storage-common.noarch                                            
    2-2.el8                                                        @extras      
  
glusterfs.x86_64                                                                
    8.6-2.el8                                                      
@centos-gluster8
ovirt-release44.noarch                                                          
    4.4.8.3-1.el8                                                  
@@commandline  
vdsm.x86_64                                                                     
   4.40.80.6-1.el8                                                @ovirt-4.4    
  
___
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/CIDB44H4L4NUBIUMF47PD62WJDP7C46I/
  
___
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/2JX3ANIKW6ZGDDVI7465Q244RPAUG5FN/


[ovirt-users] Hosted-Engine Down VSDM Cert Expired

2023-01-21 Thread jarredm
Hey all,

I'm looking to get a bit of guidance here. As the subject suggests, we have a 
hosted-engine ovirt cluster. I ran into an issue trying to login to the web 
interface. I was seeing errors about certificate expiration, although I didn't 
know what cert it was referring to at the time. I ssh'd to the hosted-engine 
and restarted it. However, once it shutdown, it was unable to start again.

What I've discovered so far is that the hosted-engine is currently residing on 
node 33 (storage is on a gluster volume) and the vdsm certificate for that node 
has expired. There are three nodes in total, and two of them have expired 
certs. However, one of them has a valid cert still. I'm able to run vdsm-client 
commands on that node. Although I haven't done anything with that yet other 
than to verify that I'm able to do some of the Host get* commands successfully. 
I'm wondering if it is possible to "pull" the hosted-engine onto this host and 
fire it back up there.

Thanks in advance for your help!

I'm gathering log info etc as described and it will be available here: 
https://drive.google.com/drive/folders/1cBPrN8SuIR-dgnpRKe1eKXRZZTPPshyJ?usp=sharing

Version info:
Installed Packages
centos-release-gluster8.noarch  
1.0-1.el8  @extras  
   
centos-release-storage-common.noarch
2-2.el8@extras  
   
glusterfs.x86_64
8.6-2.el8  
@centos-gluster8
ovirt-release44.noarch  
4.4.8.3-1.el8  
@@commandline   
vdsm.x86_64 
4.40.80.6-1.el8@ovirt-4.4   
   
___
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/CIDB44H4L4NUBIUMF47PD62WJDP7C46I/


[ovirt-users] Disaster recovery failed with direct lun 4.4.10

2023-01-21 Thread jaime luque
Good night

I am configuring the disaster recovery with the following environment

Ovirt 4.4.10

Site A

An external manager
A hypervisor server

Site B

An external manager
A hypervisor server

*Mons are being replicated from one storage to another with the conditions 
mentioned in the active passive guide.

In the File

disaster_recovery_vars.yml

 The mapping of the virtual machines is carried out, one of these has 
direct luns

When I execute the failover the virtual machines are not importing in the 
secondary site.

If I comment on the mapping of the direct luns, it is possible to import the 
virtual machines and they remain working correctly.

NOTE: The direct lun that the vm has is without format or partition, since I am 
in the testing phase.

Can you please give me ideas of what to check.
___
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/67ZTOKLJ54VAJU37BGYJBEE4QVTQXYJ2/


[ovirt-users] Re: Cannot prepare internal mirrorlist

2023-01-21 Thread ahmad.hidayat--- via Users
Good day Nathan!

Firstly, it's polite for me to thank the moderators for approving my post.. 

Thank you for guiding me on this. I have configured the /etc/environment and 
/etc/yum.conf with the proxy configurations then curl the mirrorlist site and 
it was successful.

Our KVM is behind a firewall, do we need to allow the traffic for a specific 
range of IP addresses for this?

Regards,
Hidayat
___
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/CC7WTIK5MBBJKLTYOC3RL6I25OYWOYSR/