[ovirt-users] Re: Help installing oVirt on single machine, without cockpit
Strahil's suggestion is to use the backup and restore function of the ovirt engine by essentially putting host into maintenance i.e. shutting down all VMs and the hosted engine, upgrading the host using the repositories to the latest ovirt version and then deploying the new version hosted engine 'as new' but restoring from previous version backup. This may fall apart if there's a backup incompatibility between 2 versions but minor versions would be OK. -- Original Message -- From: "Cameron Showalter" To: users@ovirt.org Sent: 27/12/2021 5:38:17 PM Subject: [ovirt-users] Help installing oVirt on single machine, without cockpit The reply button is taking me to a "mailto" tab again, but hopefully making the subject the same, will put this under the right thread? If not, I'm not sure how to reply on the new system. The original thread is here: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/3L6EVRT4YBEJOIWLLXHF5QPVGJIXL7CR/, and it continues here for a bit: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/C4Z65RXLFPOCS6OD3FREAJLNFM2GD2KQ/. @Strahil Nikolov > Have you thought about deploying HostedEngine and when you need to update the engine -> put the host in maintenance -> backup & restore The way I understand the update process, you can't update with a hosted engine unless you have two hosts. One needs to run the engine VM, so the other can go into maintenance. Is this wrong? For my use case, I'm looking for something that'll work/update on a single host. I'm trying to get the engine running next to the hypervisor, so it can run when the VM's come down. I can get the engine running on a CentOS Stream install, but it says it has 0/0 hosts running, so I don't think it can deploy VM's. I can't find a way to install the node's hypervisor package-set either. Unless that package exists, the only other idea I have for this route is doing a "hosted engine" install, but destroy the engine VM and point it to the local engine. This seems extreme to me lol. I tried setting up the engine on a node itself, but the error I can't get past yet is in the second url, top of this message. It can't start the ovirt-imageio service, because of a missing file. Happy Holidays all! Cameron ___ 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/SZWVLPZDESDW24FHPDPOBXZR26RF3WAG/
[ovirt-users] what are the Gluster config files must be backed up for the restoration purpose
Hi Team As part of Hyperconverged setup, what are the Gluster config files must be backed up in daily basis to restore in case of disaster? ___ 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/7JP4IT7MYTAQTMY2KQ7GESEKF25GLSOM/
[ovirt-users] Re: Unable to start ovirt-ha-agent on all hosts
Hi Didi!
> On Sun, Dec 26, 2021 at 12:24 PM
> IIRC something similar was reported on the lists - that you can't
> (always? easily?) migrate VMs between CentOS Linux 8 (.3? .4? not
> sure) and current Stream. Is this mandatory for you? If not, you might
> test on a test env stopping/starting your VMs and decide this is good
> enough.
Of course I tried, instead of migrating the VMs, simply stopping them on the
Centos 8.5 hosts and starting them on the Centos Stream 8 host. It did not
work, the network was not reachable but there was no error thrown in the engine
appliance, no event, nothing.
> Perhaps provide more details, if you have them. Did you put host3 to
> maintenance? Remove it? etc.
With everything I performed host3 was put into maintenance first. It has not
been removed. I planned to remove it but then the error below (Unable to start
ovirt-ha-agent on all hosts) started appearing.
> Not sure where 'GATEWAY_IP' comes from, but it should be the actual IP
> address, e.g.:
I just replaced the actual gateway IP in the error message thrown with
'GATEWAY_IP', since the error message thrown does expose the gateway IP instead
of the respective host IP. This issue does confirm that finding:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DTEY6OTBIWNX2DKGA7M7ZGUZZNQJYZXW/
> MainThread::INFO::2021-12-20
> 07:51:05,151::brokerlink::82::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
> Starting monitor network, options {'addr': '192.168.201.1',
> 'network_test': 'dns', 'tcp_t_address': '',
> 'tcp_t_port': ''}
>
> Check (and perhaps fix manually, if you can't/do not want to first
> diagnose/fix your reinstallation) the line 'gateway=' in
> /etc/ovirt-hosted-engine/hosted-engine.conf . Perhaps compare this
> file to your other hosts - only the line 'host_id' should be different
> between them.
Everything in /etc/ovirt-hosted-engine/hosted-engine.conf is as you describe
it. Only the host_id is different. I haven't touched that file either.
Cheers, Martin
___
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/XMI45SIPO3SVH3PTCJIVG6YW3DZ6SWRC/
[ovirt-users] Re: Unable to start ovirt-ha-agent on all hosts
On Tue, Dec 28, 2021 at 7:39 AM wrote:
>
> Hi Didi!
>
> > On Sun, Dec 26, 2021 at 12:24 PM >
> > IIRC something similar was reported on the lists - that you can't
> > (always? easily?) migrate VMs between CentOS Linux 8 (.3? .4? not
> > sure) and current Stream. Is this mandatory for you? If not, you might
> > test on a test env stopping/starting your VMs and decide this is good
> > enough.
>
> Of course I tried, instead of migrating the VMs, simply stopping them on the
> Centos 8.5 hosts and starting them on the Centos Stream 8 host. It did not
> work, the network was not reachable but there was no error thrown in the
> engine appliance, no event, nothing.
>
> > Perhaps provide more details, if you have them. Did you put host3 to
> > maintenance? Remove it? etc.
>
> With everything I performed host3 was put into maintenance first. It has not
> been removed. I planned to remove it but then the error below (Unable to
> start ovirt-ha-agent on all hosts) started appearing.
>
> > Not sure where 'GATEWAY_IP' comes from, but it should be the actual IP
> > address, e.g.:
>
> I just replaced the actual gateway IP in the error message thrown with
> 'GATEWAY_IP', since the error message thrown does expose the gateway IP
> instead of the respective host IP. This issue does confirm that finding:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/DTEY6OTBIWNX2DKGA7M7ZGUZZNQJYZXW/
>
> > MainThread::INFO::2021-12-20
> > 07:51:05,151::brokerlink::82::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
> > Starting monitor network, options {'addr': '192.168.201.1',
> > 'network_test': 'dns', 'tcp_t_address': '',
> > 'tcp_t_port': ''}
> >
> > Check (and perhaps fix manually, if you can't/do not want to first
> > diagnose/fix your reinstallation) the line 'gateway=' in
> > /etc/ovirt-hosted-engine/hosted-engine.conf . Perhaps compare this
> > file to your other hosts - only the line 'host_id' should be different
> > between them.
>
> Everything in /etc/ovirt-hosted-engine/hosted-engine.conf is as you describe
> it. Only the host_id is different. I haven't touched that file either.
Can you please check/share also broker.log? Thanks.
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/EKSQJP4HM2DSKUDXBCODHFYWRK557SOP/
[ovirt-users] Re: Unable to start ovirt-ha-agent on all hosts
On Tue, Dec 28, 2021 at 9:06 AM Yedidyah Bar David wrote:
>
> On Tue, Dec 28, 2021 at 7:39 AM wrote:
> >
> > Hi Didi!
> >
> > > On Sun, Dec 26, 2021 at 12:24 PM > >
> > > IIRC something similar was reported on the lists - that you can't
> > > (always? easily?) migrate VMs between CentOS Linux 8 (.3? .4? not
> > > sure) and current Stream. Is this mandatory for you? If not, you might
> > > test on a test env stopping/starting your VMs and decide this is good
> > > enough.
> >
> > Of course I tried, instead of migrating the VMs, simply stopping them on
> > the Centos 8.5 hosts and starting them on the Centos Stream 8 host. It did
> > not work, the network was not reachable but there was no error thrown in
> > the engine appliance, no event, nothing.
> >
> > > Perhaps provide more details, if you have them. Did you put host3 to
> > > maintenance? Remove it? etc.
> >
> > With everything I performed host3 was put into maintenance first. It has
> > not been removed. I planned to remove it but then the error below (Unable
> > to start ovirt-ha-agent on all hosts) started appearing.
> >
> > > Not sure where 'GATEWAY_IP' comes from, but it should be the actual IP
> > > address, e.g.:
> >
> > I just replaced the actual gateway IP in the error message thrown with
> > 'GATEWAY_IP', since the error message thrown does expose the gateway IP
> > instead of the respective host IP. This issue does confirm that finding:
> > https://lists.ovirt.org/archives/list/users@ovirt.org/message/DTEY6OTBIWNX2DKGA7M7ZGUZZNQJYZXW/
> >
> > > MainThread::INFO::2021-12-20
> > > 07:51:05,151::brokerlink::82::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
> > > Starting monitor network, options {'addr': '192.168.201.1',
> > > 'network_test': 'dns', 'tcp_t_address': '',
> > > 'tcp_t_port': ''}
> > >
> > > Check (and perhaps fix manually, if you can't/do not want to first
> > > diagnose/fix your reinstallation) the line 'gateway=' in
> > > /etc/ovirt-hosted-engine/hosted-engine.conf . Perhaps compare this
> > > file to your other hosts - only the line 'host_id' should be different
> > > between them.
> >
> > Everything in /etc/ovirt-hosted-engine/hosted-engine.conf is as you
> > describe it. Only the host_id is different. I haven't touched that file
> > either.
>
> Can you please check/share also broker.log? Thanks.
Also, you can try enabling debug-level logging by editing
/etc/ovirt-hosted-engine-ha/*log.conf, setting 'level=DEBUG'
under '[logger_root]' and restarting the services.
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/YB5TPI72RS3HJHR53DNUN5G3TXCSDGLZ/
[ovirt-users] Re: Unable to start ovirt-ha-agent on all hosts
Hi Didi,
> Can you please check/share also broker.log? Thanks.
I did that. Turns out that ...
ovirt_hosted_engine_ha.lib.storage_backends.BackendFailureException: path to
storage domain e1f61a9f-0c93-4d01-8f6f-7f8a5470ee2f not found in
/rhev/data-center/mnt/glusterSD
... and I noticed that the glusterd service was not started on host3 (vendor
setting was set to disabled). After starting the glusterd service the
ovirt-ha-agent services recovered, the hosted-engine could be started and then
it blew my mind:
While I was switching host3 into maintenance, I did not notice that the
hosted-engine marked host1 "non-responsive" (although the host was fine) and
scheduled the migration of host1 VMs to host3. By setting host3 to maintenance
the migration of scheduled VMs was cancelled but two VMs were migrated, so they
were migrated (back) to host2.
Now this is the result:
VM xyz is down with error. Exit message: internal error: process exited while
connecting to monitor: 2021-12-28T06:33:19.011352Z qemu-kvm: -blockdev
{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}:
qcow2: Image is corrupt; cannot be opened read/write.
12/28/217:33:21 AM
Trying to repair the image with "qemu-img check -r all" failed.
What an experience. Maybe I'm too stupid 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/F6NTAZSLS4WSL2CNA3FARTKR5CMUSVP3/
