[ovirt-users] Re: Hosted-engine restore failing
Same problem... Tried CentOS 8 Host and CentOS 9 host. ___ 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/TRT7GXNYBEH6KNKLMGGQTIH6QIZKXLDZ/
[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain
This saga is finally over, at least for now. I never succeeded in restoring our hosted engine to a new iSCSI storage domain. For one reason or another, however, I was able to restore it to a new NFS storage domain. Any advice on the benefits or downsides of using an NFS storage domain versus iSCSI for the self hosted engine would be greatly appreciated. At least for now, however, things seem to be stable. Just incase helps anyone else, here's a rough outline of the procedure I finally used. - set the cluster into global maintenance mode - backup the engine using "engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log" - shutdown the engine - restore the engine using "hosted-engine --deploy --4 --restore-from-file=backup.bck" - when the restore pauses waiting for the lock file to be removed, scp backup.bck to the new engine VM. - ssh into the new VM, and restore the DBs using: - engine-backup --mode=restore --file=backup.bck --provision-all-databases --scope=db - engine-backup --mode=restore --file=backup.bck --provision-all-databases --scope=dwhdb - engine-backup --mode=restore --file=backup.bck --provision-all-databases --scope=grafanadb - delete the lock file, and proceed as usual Without manual intervention, the Postgres db on the new engine VM was never initialized or setup. Thanks again for everyones attention and advice. Sincerely, Devin > On Nov 6, 2023, at 12:00 PM, Devin A. Bougie wrote: > > Does anyone know how to regenerate > /etc/ovirt-hosted-engine/hosted-engine.conf? Or where exactly I find each > field to create the file manually? > > After trying to switch from an iscsi storage domain to NFS for the new hosted > engine, I finally have the engine back up and running. However, when trying > to reinstall a host to move it to the new hosted engine domain, I get "Failed > to fetch hosted engine configuration file." > > /etc/ovirt-hosted-engine/hosted-engine.conf doesn't exist on the host I ran > "hosted-engine --deploy" on. And on all other hosts, it still references the > old hosted engine VM and storage domain. > > Thanks, > Devin > >> On Oct 25, 2023, at 3:55 PM, Devin A. Bougie >> wrote: >> >> Thanks again, Gianluca. >> >> I'm currently ssh'd into the new local engine VM, and Postgres is running. >> However, an engine DB doesn't exist? Should it at this point, and do you >> have any other suggestions of where I should look? >> >> Devin >> >> -- >> [root@lnxvirt-engine ~]# su - postgres >> Last login: Wed Oct 25 15:47:18 EDT 2023 on pts/0 >> [postgres@lnxvirt-engine ~]$ psql >> psql (12.12) >> Type "help" for help. >> >> postgres=# \l >> List of databases >> Name| Owner | Encoding | Collate |Ctype| Access >> privileges >> ---+--+--+-+-+--- >> postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | >> postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + >> | | | | | >> postgres=CTc/postgres >> template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres >> + >> | | | | | >> postgres=CTc/postgres >> (3 rows) >> >> postgres=# >> -- >> >> >>> On Oct 25, 2023, at 12:40 PM, Gianluca Cecchi >>> wrote: >>> >>> >>> On Wed, Oct 25, 2023 at 5:50 PM Devin A. Bougie >>> wrote: >>> I've had a chance to try this restore again, and this time login to the >>> local (new) hosted-engine VM to verify that >>> /root/DisableFenceAtStartupInSec.txt just contains: >>> to >>> >>> And if I try the "engine-config -g DisableFenceAtStartupInSec" from the new >>> hosted-engine VM, my connection closes. >>> [root@lnxvirt-engine ~]# cat /root/DisableFenceAtStartupInSec.txt >>> to >>> [root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g >>> DisableFenceAtStartupInSec >>> Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false >>> Connection to the Database failed. Please check that the hostname and port >>> number are correct and that the Database service is up and running. >>> Connection to 192.168.222.25 closed. >>> >>> Any new suggestions or more tests I can run would be greatly appreciated. >>> >>> Thanks, >>> Devin >>> >>> >>> The key thing here is that for some reason it seems it is not able to >>> connect to the database and so when "engine-config" command tries to get >>> the second field of the output (the " | cut -d' ' -f2" part) it gets the >>> "to" string here: >>> >>> Connection to the Database failed >>> and anyway it returns error with failure of the overall playbook >>> It should be investigated if there is a problem with the database itself on >>> the new engine or if for some reason the "engine-config" command is not >>> able to implicitly connect to the database >>> >> >>
[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain
Does anyone know how to regenerate /etc/ovirt-hosted-engine/hosted-engine.conf? Or where exactly I find each field to create the file manually? After trying to switch from an iscsi storage domain to NFS for the new hosted engine, I finally have the engine back up and running. However, when trying to reinstall a host to move it to the new hosted engine domain, I get "Failed to fetch hosted engine configuration file." /etc/ovirt-hosted-engine/hosted-engine.conf doesn't exist on the host I ran "hosted-engine --deploy" on. And on all other hosts, it still references the old hosted engine VM and storage domain. Thanks, Devin > On Oct 25, 2023, at 3:55 PM, Devin A. Bougie wrote: > > Thanks again, Gianluca. > > I'm currently ssh'd into the new local engine VM, and Postgres is running. > However, an engine DB doesn't exist? Should it at this point, and do you > have any other suggestions of where I should look? > > Devin > > -- > [root@lnxvirt-engine ~]# su - postgres > Last login: Wed Oct 25 15:47:18 EDT 2023 on pts/0 > [postgres@lnxvirt-engine ~]$ psql > psql (12.12) > Type "help" for help. > > postgres=# \l > List of databases > Name| Owner | Encoding | Collate |Ctype| Access > privileges > ---+--+--+-+-+--- > postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | > postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + > | | | | | > postgres=CTc/postgres > template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres > + > | | | | | > postgres=CTc/postgres > (3 rows) > > postgres=# > -- > > >> On Oct 25, 2023, at 12:40 PM, Gianluca Cecchi >> wrote: >> >> >> On Wed, Oct 25, 2023 at 5:50 PM Devin A. Bougie >> wrote: >> I've had a chance to try this restore again, and this time login to the >> local (new) hosted-engine VM to verify that >> /root/DisableFenceAtStartupInSec.txt just contains: >> to >> >> And if I try the "engine-config -g DisableFenceAtStartupInSec" from the new >> hosted-engine VM, my connection closes. >> [root@lnxvirt-engine ~]# cat /root/DisableFenceAtStartupInSec.txt >> to >> [root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g >> DisableFenceAtStartupInSec >> Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false >> Connection to the Database failed. Please check that the hostname and port >> number are correct and that the Database service is up and running. >> Connection to 192.168.222.25 closed. >> >> Any new suggestions or more tests I can run would be greatly appreciated. >> >> Thanks, >> Devin >> >> >> The key thing here is that for some reason it seems it is not able to >> connect to the database and so when "engine-config" command tries to get the >> second field of the output (the " | cut -d' ' -f2" part) it gets the "to" >> string here: >> >> Connection to the Database failed >> and anyway it returns error with failure of the overall playbook >> It should be investigated if there is a problem with the database itself on >> the new engine or if for some reason the "engine-config" command is not able >> to implicitly connect to the database >> > > ___ > 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/XJ6PEGB2LUCIOXJ5RKA35IUMIGR6LPIF/ ___ 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/472WX3JWJNGD4NKTF4IOUTKXOTQTHORE/
[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain
Thanks again, Gianluca. I'm currently ssh'd into the new local engine VM, and Postgres is running. However, an engine DB doesn't exist? Should it at this point, and do you have any other suggestions of where I should look? Devin -- [root@lnxvirt-engine ~]# su - postgres Last login: Wed Oct 25 15:47:18 EDT 2023 on pts/0 [postgres@lnxvirt-engine ~]$ psql psql (12.12) Type "help" for help. postgres=# \l List of databases Name| Owner | Encoding | Collate |Ctype| Access privileges ---+--+--+-+-+--- postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres (3 rows) postgres=# -- > On Oct 25, 2023, at 12:40 PM, Gianluca Cecchi > wrote: > > > On Wed, Oct 25, 2023 at 5:50 PM Devin A. Bougie > wrote: > I've had a chance to try this restore again, and this time login to the local > (new) hosted-engine VM to verify that /root/DisableFenceAtStartupInSec.txt > just contains: > to > > And if I try the "engine-config -g DisableFenceAtStartupInSec" from the new > hosted-engine VM, my connection closes. > [root@lnxvirt-engine ~]# cat /root/DisableFenceAtStartupInSec.txt > to > [root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g > DisableFenceAtStartupInSec > Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false > Connection to the Database failed. Please check that the hostname and port > number are correct and that the Database service is up and running. > Connection to 192.168.222.25 closed. > > Any new suggestions or more tests I can run would be greatly appreciated. > > Thanks, > Devin > > > The key thing here is that for some reason it seems it is not able to connect > to the database and so when "engine-config" command tries to get the second > field of the output (the " | cut -d' ' -f2" part) it gets the "to" string > here: > > Connection to the Database failed > and anyway it returns error with failure of the overall playbook > It should be investigated if there is a problem with the database itself on > the new engine or if for some reason the "engine-config" command is not able > to implicitly connect to the database > ___ 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/XJ6PEGB2LUCIOXJ5RKA35IUMIGR6LPIF/
[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain
On Wed, Oct 25, 2023 at 5:50 PM Devin A. Bougie wrote: > I've had a chance to try this restore again, and this time login to the > local (new) hosted-engine VM to verify that > /root/DisableFenceAtStartupInSec.txt just contains: > to > > And if I try the "engine-config -g DisableFenceAtStartupInSec" from the > new hosted-engine VM, my connection closes. > [root@lnxvirt-engine ~]# cat /root/DisableFenceAtStartupInSec.txt > to > [root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g > DisableFenceAtStartupInSec > Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false > Connection to the Database failed. Please check that the hostname and port > number are correct and that the Database service is up and running. > Connection to 192.168.222.25 closed. > > Any new suggestions or more tests I can run would be greatly appreciated. > > Thanks, > Devin > > The key thing here is that for some reason it seems it is not able to connect to the database and so when "engine-config" command tries to get the second field of the output (the " | cut -d' ' -f2" part) it gets the "to" string here: Connection to the Database failed and anyway it returns error with failure of the overall playbook It should be investigated if there is a problem with the database itself on the new engine or if for some reason the "engine-config" command is not able to implicitly connect to the database ___ 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/FR7KU3LAMEDTAZYBWJM4JO22M3FUVO65/
[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain
I've had a chance to try this restore again, and this time login to the local (new) hosted-engine VM to verify that /root/DisableFenceAtStartupInSec.txt just contains: to And if I try the "engine-config -g DisableFenceAtStartupInSec" from the new hosted-engine VM, my connection closes. [root@lnxvirt-engine ~]# cat /root/DisableFenceAtStartupInSec.txt to [root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g DisableFenceAtStartupInSec Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false Connection to the Database failed. Please check that the hostname and port number are correct and that the Database service is up and running. Connection to 192.168.222.25 closed. Any new suggestions or more tests I can run would be greatly appreciated. Thanks, Devin > On Oct 15, 2023, at 9:10 AM, Devin A. Bougie wrote: > > Hi Gianluca, > > Thanks for taking another look. I'm not sure what to make of > /var/log/ovirt-hosted-engine-setup/engine-logs-2023-10-14T14:30:39Z/log/ovirt-engine/setup/restore-backup-20231014150412.log, > but here it is. Does that explain anything to you, or give an idea of where > to look next? > > Thanks again! > Devin > > -- > 2023-10-14 11:04:12 7680: Start of engine-backup mode restore scope all file > /root/engine_backup > 2023-10-14 11:04:12 7680: OUTPUT: Start of engine-backup with mode 'restore' > 2023-10-14 11:04:12 7680: OUTPUT: scope: all > 2023-10-14 11:04:12 7680: OUTPUT: archive file: /root/engine_backup > 2023-10-14 11:04:12 7680: OUTPUT: log file: > /var/log/ovirt-engine/setup/restore-backup-20231014150412.log > 2023-10-14 11:04:12 7680: OUTPUT: Preparing to restore: > 2023-10-14 11:04:12 7680: OUTPUT: - Unpacking file '/root/engine_backup' > 2023-10-14 11:04:12 7680: Opening tarball /root/engine_backup to > /tmp/engine-backup.Onm6LsDR0g > 2023-10-14 11:04:13 7680: Verifying hash > 2023-10-14 11:04:13 7680: Verifying version > 2023-10-14 11:04:13 7680: Reading config > 2023-10-14 11:04:13 7680: Scope after checking backup content: > 2023-10-14 11:04:13 7680: SCOPE_FILES:1 > 2023-10-14 11:04:13 7680: SCOPE_ENGINE_DB:1 > 2023-10-14 11:04:13 7680: SCOPE_DWH_DB:1 > 2023-10-14 11:04:13 7680: SCOPE_CINDERLIB_DB: > 2023-10-14 11:04:13 7680: SCOPE_KEYCLOAK_DB: > 2023-10-14 11:04:13 7680: SCOPE_GRAFANA_DB:1 > 2023-10-14 11:04:13 7680: OUTPUT: Restoring: > 2023-10-14 11:04:13 7680: OUTPUT: - Files > 2023-10-14 11:04:13 7680: Restoring files > tar: var/lib/grafana/plugins/performancecopilot-pcp-app: Cannot open: File > exists > tar: Exiting with failure status due to previous errors > 2023-10-14 11:04:13 7680: FATAL: Failed restoring /etc/ovirt-engine > /etc/ovirt-engine-dwh > /etc/ovirt-provider-ovn/conf.d > /etc/ovirt-provider-ovn/logger.conf > /etc/ovirt-vmconsole > /etc/pki/ovirt-engine > /etc/pki/ovirt-vmconsole > /etc/ovirt-engine-setup.conf.d > /etc/httpd/conf.d/internalsso-openidc.conf > /etc/httpd/conf.d/ovirt-engine-grafana-proxy.conf > /etc/httpd/conf.d/ovirt-engine-root-redirect.conf > /etc/httpd/conf.d/ssl.conf > /etc/httpd/conf.d/z-ovirt-engine-proxy.conf > /etc/httpd/conf.d/z-ovirt-engine-keycloak-proxy.conf > /etc/httpd/http.keytab > /etc/httpd/conf.d/ovirt-sso.conf > /etc/yum/pluginconf.d/versionlock.list > /etc/dnf/plugins/versionlock.list > /etc/firewalld/services/ovirt-https.xml > /etc/firewalld/services/ovirt-http.xml > /etc/firewalld/services/ovirt-postgres.xml > /etc/firewalld/services/ovirt-provider-ovn.xml > /etc/firewalld/services/ovn-central-firewall-service.xml > /var/lib/openvswitch > /etc/grafana > /var/lib/ovirt-engine/content > /var/lib/ovirt-engine/setup > /var/lib/grafana/plugins > -- > >> On Oct 15, 2023, at 5:59 AM, Gianluca Cecchi >> wrote: >> >> On Sat, Oct 14, 2023 at 7:05 PM Devin A. Bougie >> wrote: >> [snip] >> Any additional questions or suggestions would be greatly appreciated. >> >> Thanks again, >> Devin >> >> >> There is another FATAL line regarding restore itself, before the message I >> pointed out in my previous message. >> Can you analyze and/or share the contents of >> /var/log/ovirt-engine/setup/restore-backup-20231014150412.log? >> >> 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/D7LPPXNHQV3YCVSA7CSJHRXYU3T2FWQF/
[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain
Hi Gianluca, Thanks for taking another look. I'm not sure what to make of /var/log/ovirt-hosted-engine-setup/engine-logs-2023-10-14T14:30:39Z/log/ovirt-engine/setup/restore-backup-20231014150412.log, but here it is. Does that explain anything to you, or give an idea of where to look next? Thanks again! Devin -- 2023-10-14 11:04:12 7680: Start of engine-backup mode restore scope all file /root/engine_backup 2023-10-14 11:04:12 7680: OUTPUT: Start of engine-backup with mode 'restore' 2023-10-14 11:04:12 7680: OUTPUT: scope: all 2023-10-14 11:04:12 7680: OUTPUT: archive file: /root/engine_backup 2023-10-14 11:04:12 7680: OUTPUT: log file: /var/log/ovirt-engine/setup/restore-backup-20231014150412.log 2023-10-14 11:04:12 7680: OUTPUT: Preparing to restore: 2023-10-14 11:04:12 7680: OUTPUT: - Unpacking file '/root/engine_backup' 2023-10-14 11:04:12 7680: Opening tarball /root/engine_backup to /tmp/engine-backup.Onm6LsDR0g 2023-10-14 11:04:13 7680: Verifying hash 2023-10-14 11:04:13 7680: Verifying version 2023-10-14 11:04:13 7680: Reading config 2023-10-14 11:04:13 7680: Scope after checking backup content: 2023-10-14 11:04:13 7680: SCOPE_FILES:1 2023-10-14 11:04:13 7680: SCOPE_ENGINE_DB:1 2023-10-14 11:04:13 7680: SCOPE_DWH_DB:1 2023-10-14 11:04:13 7680: SCOPE_CINDERLIB_DB: 2023-10-14 11:04:13 7680: SCOPE_KEYCLOAK_DB: 2023-10-14 11:04:13 7680: SCOPE_GRAFANA_DB:1 2023-10-14 11:04:13 7680: OUTPUT: Restoring: 2023-10-14 11:04:13 7680: OUTPUT: - Files 2023-10-14 11:04:13 7680: Restoring files tar: var/lib/grafana/plugins/performancecopilot-pcp-app: Cannot open: File exists tar: Exiting with failure status due to previous errors 2023-10-14 11:04:13 7680: FATAL: Failed restoring /etc/ovirt-engine /etc/ovirt-engine-dwh /etc/ovirt-provider-ovn/conf.d /etc/ovirt-provider-ovn/logger.conf /etc/ovirt-vmconsole /etc/pki/ovirt-engine /etc/pki/ovirt-vmconsole /etc/ovirt-engine-setup.conf.d /etc/httpd/conf.d/internalsso-openidc.conf /etc/httpd/conf.d/ovirt-engine-grafana-proxy.conf /etc/httpd/conf.d/ovirt-engine-root-redirect.conf /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/z-ovirt-engine-proxy.conf /etc/httpd/conf.d/z-ovirt-engine-keycloak-proxy.conf /etc/httpd/http.keytab /etc/httpd/conf.d/ovirt-sso.conf /etc/yum/pluginconf.d/versionlock.list /etc/dnf/plugins/versionlock.list /etc/firewalld/services/ovirt-https.xml /etc/firewalld/services/ovirt-http.xml /etc/firewalld/services/ovirt-postgres.xml /etc/firewalld/services/ovirt-provider-ovn.xml /etc/firewalld/services/ovn-central-firewall-service.xml /var/lib/openvswitch /etc/grafana /var/lib/ovirt-engine/content /var/lib/ovirt-engine/setup /var/lib/grafana/plugins -- > On Oct 15, 2023, at 5:59 AM, Gianluca Cecchi > wrote: > > On Sat, Oct 14, 2023 at 7:05 PM Devin A. Bougie > wrote: > [snip] > Any additional questions or suggestions would be greatly appreciated. > > Thanks again, > Devin > > > There is another FATAL line regarding restore itself, before the message I > pointed out in my previous message. > Can you analyze and/or share the contents of > /var/log/ovirt-engine/setup/restore-backup-20231014150412.log? > > 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/UVWBRJNQ3HVKVXQ7T56ERN4MVT5BSSG5/
[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain
On Sat, Oct 14, 2023 at 7:05 PM Devin A. Bougie wrote: [snip] > Any additional questions or suggestions would be greatly appreciated. > > Thanks again, > Devin > > There is another FATAL line regarding restore itself, before the message I pointed out in my previous message. Can you analyze and/or share the contents of /var/log/ovirt-engine/setup/restore-backup-20231014150412.log? 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/4AWQKUBFC2V5CKHYSQ3VWAU2LFROT7ZF/
[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain
Thank you so much, Gianluca! Yes, the source and target environments are the
same version.
I'm not able to find /root/DisableFenceAtStartupInSec.txt anywhere, but maybe
that's because at this point I've reverted to the original hosted_engine?
Here is the output of the commands you sent:
--
[root@lnxvirt-engine ~]# engine-config -g DisableFenceAtStartupInSec
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
DisableFenceAtStartupInSec: 300 version: general
[root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g
DisableFenceAtStartupInSec | cut -d' ' -f 2
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
300
engine=# select * from vdc_options where
option_name='DisableFenceAtStartupInSec';
option_id |option_name | option_value | version | default_value
---++--+-+---
45 | DisableFenceAtStartupInSec | 300 | general | 300
(1 row)
--
I also tried the following from the host I tried running the restore on.
--
[root@lnxvirt07 ~]# set -euo pipefail && echo "Picked up JAVA_TOOL_OPTIONS:
-Dcom.redhat.fips=false
DisableFenceAtStartupInSec: 300 version: general" | cut -d' ' -f 2
up
300
--
Any additional questions or suggestions would be greatly appreciated.
Thanks again,
Devin
On Oct 14, 2023, at 12:30 PM, Gianluca Cecchi wrote:
On Sat, Oct 14, 2023 at 5:53 PM Devin A. Bougie
mailto:devin.bou...@cornell.edu>> wrote:
Hello,
We have a functioning oVirt 4.5.4 cluster running on fully-updated EL9.2 hosts.
We are trying to migrate the self-hosted engine to a new iSCSI storage domain
using the existing hosts, following the documented procedure:
- set the cluster into global maintenance mode
- backup the engine using "engine-backup --scope=all --mode=backup
--file=backup.bck --log=backuplog.log"
- shutdown the engine
- restore the engine using "hosted-engine --deploy --4
--restore-from-file=backup.bck"
This almost works, but fails with the attached log file. Any help or
suggestions would be greatly appreciated, including alternate procedures for
migrating a self-hosted engine from one domain to another.
Many thanks,
Devin
If I'm right, the starting error seems to be this one:
2023-10-14 11:06:16,529-0400 ERROR
otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113
fatal: [local
host -> 192.168.1.25]: FAILED! => {"changed": true, "cmd": "set -euo pipefail
&& engine-config -g DisableFenceAtStartupInSec | c
ut -d' ' -f2 > /root/DisableFenceAtStartupInSec.txt", "delta":
"0:00:01.495195", "end": "2023-10-14 11:06:16.184479", "msg": "no
n-zero return code", "rc": 1, "start": "2023-10-14 11:06:14.689284", "stderr":
"Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=f
alse", "stderr_lines": ["Picked up JAVA_TOOL_OPTIONS:
-Dcom.redhat.fips=false"], "stdout": "", "stdout_lines": []}
As the return code is 1 ("rc": 1,) and determines the failure of the playbook,
possibly the old environment doesn't have DisableFenceAtStartupInSec engine
config property correctly set and/or the "cut" command fails... Or some other
problem with that config parameter. Can you verify what it put into
/root/DisableFenceAtStartupInSec.txt?
I have only a 4.4.10 env at hand and on it:
[root@ovengine01 ~]# engine-config -g DisableFenceAtStartupInSec
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
DisableFenceAtStartupInSec: 300 version: general
[root@ovengine01 ~]#
[root@ovengine01 ~]# set -euo pipefail && engine-config -g
DisableFenceAtStartupInSec | cut -d' ' -f 2
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
300
[root@ovengine01 ~]#
what is the output of this command on your old env:
engine-config -g DisableFenceAtStartupInSec
?
Are the source and target environments the same version?
If you have access to your old env could you also run this query on engine
database:
select * from vdc_options where option_name='DisableFenceAtStartupInSec';
eg this way
[root@ovengine01 ~]# su - postgres
[postgres@ovengine01 ~]$ psql engine
psql (12.9)
Type "help" for help.
engine=# select * from vdc_options where
option_name='DisableFenceAtStartupInSec';
option_id |option_name | option_value | version | default_value
---++--+-+---
40 | DisableFenceAtStartupInSec | 300 | general | 300
(1 row)
engine=#
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/7FPSGAMPCTNYWQIA3MWFJM5QOBYM3VSC/
[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain
On Sat, Oct 14, 2023 at 5:53 PM Devin A. Bougie
wrote:
> Hello,
>
> We have a functioning oVirt 4.5.4 cluster running on fully-updated EL9.2
> hosts. We are trying to migrate the self-hosted engine to a new iSCSI
> storage domain using the existing hosts, following the documented procedure:
> - set the cluster into global maintenance mode
> - backup the engine using "engine-backup --scope=all --mode=backup
> --file=backup.bck --log=backuplog.log"
> - shutdown the engine
> - restore the engine using "hosted-engine --deploy --4
> --restore-from-file=backup.bck"
>
> This almost works, but fails with the attached log file. Any help or
> suggestions would be greatly appreciated, including alternate procedures
> for migrating a self-hosted engine from one domain to another.
>
> Many thanks,
> Devin
If I'm right, the starting error seems to be this one:
2023-10-14 11:06:16,529-0400 ERROR
otopi.ovirt_hosted_engine_setup.ansible_utils
ansible_utils._process_output:113 fatal: [local
host -> 192.168.1.25]: FAILED! => {"changed": true, "cmd": "set -euo
pipefail && engine-config -g DisableFenceAtStartupInSec | c
ut -d' ' -f2 > /root/DisableFenceAtStartupInSec.txt", "delta":
"0:00:01.495195", "end": "2023-10-14 11:06:16.184479", "msg": "no
n-zero return code", "rc": 1, "start": "2023-10-14 11:06:14.689284",
"stderr": "Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=f
alse", "stderr_lines": ["Picked up JAVA_TOOL_OPTIONS:
-Dcom.redhat.fips=false"], "stdout": "", "stdout_lines": []}
As the return code is 1 ("rc": 1,) and determines the failure of the
playbook, possibly the old environment doesn't have
DisableFenceAtStartupInSec engine config property correctly set and/or the
"cut" command fails... Or some other problem with that config parameter.
Can you verify what it put into /root/DisableFenceAtStartupInSec.txt?
I have only a 4.4.10 env at hand and on it:
[root@ovengine01 ~]# engine-config -g DisableFenceAtStartupInSec
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
DisableFenceAtStartupInSec: 300 version: general
[root@ovengine01 ~]#
[root@ovengine01 ~]# set -euo pipefail && engine-config -g
DisableFenceAtStartupInSec | cut -d' ' -f 2
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
300
[root@ovengine01 ~]#
what is the output of this command on your old env:
engine-config -g DisableFenceAtStartupInSec
?
Are the source and target environments the same version?
If you have access to your old env could you also run this query on engine
database:
select * from vdc_options where option_name='DisableFenceAtStartupInSec';
eg this way
[root@ovengine01 ~]# su - postgres
[postgres@ovengine01 ~]$ psql engine
psql (12.9)
Type "help" for help.
engine=# select * from vdc_options where
option_name='DisableFenceAtStartupInSec';
option_id |option_name | option_value | version |
default_value
---++--+-+---
40 | DisableFenceAtStartupInSec | 300 | general | 300
(1 row)
engine=#
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/PC3HGYPF2J3FPSF4CAZQCQ6PHESL64N7/
[ovirt-users] Re: Hosted-engine restore failing
I was able to work around this by editing /usr/share/ovirt-hosted-engine-setup/he_ansible/callback_plugins/2_ovirt_logger.py and changing: from collections import Callable to: from collections.abc import Callable Thanks again for taking a look, Devin > On Oct 11, 2023, at 12:17 PM, Devin A. Bougie > wrote: > > Hi Jorge, > > Please see below for a full package listing. We are running on fully updated > RHEL9.2 hosts, and are simply trying to migrate to a new hosted engine > storage domain (not trying to replace or upgrade any of the underlying hosts). > > If there's a way to accomplish this without the full "engine-backup" from the > hosted engine followed by "hosted-engine --deploy --restore..." from a host, > that would work too. > > Many thanks for taking a look, > Devin > > -- > [root@lnxvirt01 ~]# rpm -qa | grep -e python -e ovirt > python3-pip-wheel-21.2.3-6.el9.noarch > python3-dbus-1.2.18-2.el9.x86_64 > python3-six-1.15.0-9.el9.noarch > python3-dasbus-1.4-5.el9.noarch > python3-idna-2.10-7.el9.noarch > python3-argcomplete-1.12.0-5.el9.noarch > libpeas-loader-python3-1.30.0-4.el9.x86_64 > python3-distro-1.5.0-7.el9.noarch > python3-dateutil-2.8.1-6.el9.noarch > python3-libcomps-0.1.18-1.el9.x86_64 > python3-chardet-4.0.0-5.el9.noarch > python3-ptyprocess-0.6.0-12.el9.noarch > python3-pexpect-4.8.0-7.el9.noarch > python3-pysocks-1.7.1-12.el9.noarch > python3-urllib3-1.26.5-3.el9.noarch > python3-pyyaml-5.4.1-6.el9.x86_64 > python3-systemd-234-18.el9.x86_64 > libcap-ng-python3-0.8.2-7.el9.x86_64 > python3-cups-2.0.1-10.el9.x86_64 > python3-enchant-3.2.0-5.el9.noarch > python3-louis-3.16.1-4.el9.noarch > python3-ply-3.11-14.el9.noarch > python3-pycparser-2.20-6.el9.noarch > python3-cffi-1.14.5-5.el9.x86_64 > python3-pyxdg-0.27-3.el9.noarch > python3-pyatspi-2.38.1-3.el9.noarch > python3-gpg-1.15.1-6.el9.x86_64 > python3-libreport-2.15.2-6.el9.alma.x86_64 > python-srpm-macros-3.9-52.el9.noarch > python3-speechd-0.10.2-4.el9.x86_64 > python3-brlapi-0.8.2-4.el9.x86_64 > ibus-anthy-python-1.5.13-1.el9.noarch > python3-audit-3.0.7-103.el9.x86_64 > python-rpm-macros-3.9-52.el9.noarch > python3-rpm-macros-3.9-52.el9.noarch > python3-pip-21.2.3-6.el9.noarch > python3-pyparsing-2.4.7-9.el9.noarch > python3-packaging-20.9-5.el9.noarch > python3-rpm-generators-12-8.el9.noarch > python3-lxml-4.6.5-3.el9.x86_64 > python3-gobject-base-3.40.1-6.el9.x86_64 > python3-gobject-base-noarch-3.40.1-6.el9.noarch > python3-cairo-1.20.1-1.el9.x86_64 > python3-gobject-3.40.1-6.el9.x86_64 > python3-pyudev-0.22.0-6.el9.noarch > python3-cryptography-36.0.1-2.el9.x86_64 > python3-sanlock-3.8.4-4.el9.x86_64 > python3-docutils-0.16-6.el9.noarch > python3-decorator-4.4.2-6.el9.noarch > python3-pyasn1-0.4.8-6.el9.noarch > python3-pwquality-1.4.4-8.el9.x86_64 > python3-ovirt-setup-lib-1.3.3-1.el9.noarch > python3-augeas-0.5.0-25.el9.noarch > ovirt-vmconsole-1.0.9-1.el9.noarch > python3-otopi-1.10.3-1.el9.noarch > python3-ioprocess-1.4.2-1.202111071752.git53786ff.el9.x86_64 > python3-lockfile-0.12.2-2.el9s.noarch > python3-daemon-2.3.0-1.el9s.noarch > python3-ovirt-engine-lib-4.5.4-1.el9.noarch > python3-pynacl-1.4.0-2.el9s.x86_64 > python3-sortedcontainers-2.3.0-2.el9s.noarch > vdsm-python-4.50.3.4-1.el9.noarch > python3-bcrypt-3.1.7-7.el9s.x86_64 > python3-paramiko-2.7.2-4.el9s.noarch > ovirt-engine-setup-base-4.5.4-1.el9.noarch > python3-pbr-5.6.0-1.el9s.noarch > python3-pytz-2021.1-4.el9.noarch > python3-greenlet-1.1.2-3.el9.x86_64 > python3-qrcode-core-6.1-12.el9.noarch > python3-pyusb-1.0.2-13.el9.noarch > python3-pyasn1-modules-0.4.8-6.el9.noarch > python3-netifaces-0.10.6-15.el9.x86_64 > python3-gssapi-1.6.9-5.el9.x86_64 > python3-msgpack-1.0.3-2.el9s.x86_64 > python3-extras-1.0.0-15.el9s.noarch > python3-fixtures-3.0.0-27.el9s.noarch > python3-testtools-2.5.0-2.el9s.noarch > ovirt-hosted-engine-ha-2.5.0-1.el9.noarch > python3-yubico-1.3.3-7.el9.noarch > python3-babel-2.9.1-2.el9.noarch > python3-inotify-0.9.6-25.el9.noarch > python3-ethtool-0.15-2.el9.x86_64 > python3-resolvelib-0.5.4-5.el9.noarch > python3-prettytable-0.7.2-27.el9.noarch > python3-jwcrypto-0.8-4.el9.noarch > ovirt-vmconsole-host-1.0.9-1.el9.noarch > python3-yappi-1.3.1-2.el9s.x86_64 > python3-wrapt-1.13.3-2.el9s.x86_64 > python3-debtcollector-2.5.0-1.el9s.noarch > python3-oslo-context-4.1.0-1.el9s.noarch > python3-tenacity-6.3.1-1.el9s.noarch > python3-tempita-0.5.2-2.el9s.noarch > python3-stevedore-3.5.2-1.el9s.noarch > python3-rfc3986-1.5.0-1.el9s.noarch > python3-repoze-lru-0.7-10.el9s.noarch > python3-routes-2.5.1-1.el9s.noarch > python3-jmespath-0.10.0-1.el9s.noarch > python3-iso8601-0.1.13-4.el9s.noarch > python-oslo-utils-lang-4.12.3-1.el9s.noarch > python-oslo-privsep-lang-2.7.0-1.el9s.noarch > python-oslo-log-lang-4.7.0-1.el9s.noarch > python-oslo-i18n-lang-5.1.0-1.el9s.noarch > python3-oslo-i18n-5.1.0-1.el9s.noarch > python3-oslo-utils-4.12.3-1.el9s.noarch > python3-oslo-config-8.8.0-1.el9s.noarch >
[ovirt-users] Re: Hosted-engine restore failing
Hi Jorge, Please see below for a full package listing. We are running on fully updated RHEL9.2 hosts, and are simply trying to migrate to a new hosted engine storage domain (not trying to replace or upgrade any of the underlying hosts). If there's a way to accomplish this without the full "engine-backup" from the hosted engine followed by "hosted-engine --deploy --restore..." from a host, that would work too. Many thanks for taking a look, Devin -- [root@lnxvirt01 ~]# rpm -qa | grep -e python -e ovirt python3-pip-wheel-21.2.3-6.el9.noarch python3-dbus-1.2.18-2.el9.x86_64 python3-six-1.15.0-9.el9.noarch python3-dasbus-1.4-5.el9.noarch python3-idna-2.10-7.el9.noarch python3-argcomplete-1.12.0-5.el9.noarch libpeas-loader-python3-1.30.0-4.el9.x86_64 python3-distro-1.5.0-7.el9.noarch python3-dateutil-2.8.1-6.el9.noarch python3-libcomps-0.1.18-1.el9.x86_64 python3-chardet-4.0.0-5.el9.noarch python3-ptyprocess-0.6.0-12.el9.noarch python3-pexpect-4.8.0-7.el9.noarch python3-pysocks-1.7.1-12.el9.noarch python3-urllib3-1.26.5-3.el9.noarch python3-pyyaml-5.4.1-6.el9.x86_64 python3-systemd-234-18.el9.x86_64 libcap-ng-python3-0.8.2-7.el9.x86_64 python3-cups-2.0.1-10.el9.x86_64 python3-enchant-3.2.0-5.el9.noarch python3-louis-3.16.1-4.el9.noarch python3-ply-3.11-14.el9.noarch python3-pycparser-2.20-6.el9.noarch python3-cffi-1.14.5-5.el9.x86_64 python3-pyxdg-0.27-3.el9.noarch python3-pyatspi-2.38.1-3.el9.noarch python3-gpg-1.15.1-6.el9.x86_64 python3-libreport-2.15.2-6.el9.alma.x86_64 python-srpm-macros-3.9-52.el9.noarch python3-speechd-0.10.2-4.el9.x86_64 python3-brlapi-0.8.2-4.el9.x86_64 ibus-anthy-python-1.5.13-1.el9.noarch python3-audit-3.0.7-103.el9.x86_64 python-rpm-macros-3.9-52.el9.noarch python3-rpm-macros-3.9-52.el9.noarch python3-pip-21.2.3-6.el9.noarch python3-pyparsing-2.4.7-9.el9.noarch python3-packaging-20.9-5.el9.noarch python3-rpm-generators-12-8.el9.noarch python3-lxml-4.6.5-3.el9.x86_64 python3-gobject-base-3.40.1-6.el9.x86_64 python3-gobject-base-noarch-3.40.1-6.el9.noarch python3-cairo-1.20.1-1.el9.x86_64 python3-gobject-3.40.1-6.el9.x86_64 python3-pyudev-0.22.0-6.el9.noarch python3-cryptography-36.0.1-2.el9.x86_64 python3-sanlock-3.8.4-4.el9.x86_64 python3-docutils-0.16-6.el9.noarch python3-decorator-4.4.2-6.el9.noarch python3-pyasn1-0.4.8-6.el9.noarch python3-pwquality-1.4.4-8.el9.x86_64 python3-ovirt-setup-lib-1.3.3-1.el9.noarch python3-augeas-0.5.0-25.el9.noarch ovirt-vmconsole-1.0.9-1.el9.noarch python3-otopi-1.10.3-1.el9.noarch python3-ioprocess-1.4.2-1.202111071752.git53786ff.el9.x86_64 python3-lockfile-0.12.2-2.el9s.noarch python3-daemon-2.3.0-1.el9s.noarch python3-ovirt-engine-lib-4.5.4-1.el9.noarch python3-pynacl-1.4.0-2.el9s.x86_64 python3-sortedcontainers-2.3.0-2.el9s.noarch vdsm-python-4.50.3.4-1.el9.noarch python3-bcrypt-3.1.7-7.el9s.x86_64 python3-paramiko-2.7.2-4.el9s.noarch ovirt-engine-setup-base-4.5.4-1.el9.noarch python3-pbr-5.6.0-1.el9s.noarch python3-pytz-2021.1-4.el9.noarch python3-greenlet-1.1.2-3.el9.x86_64 python3-qrcode-core-6.1-12.el9.noarch python3-pyusb-1.0.2-13.el9.noarch python3-pyasn1-modules-0.4.8-6.el9.noarch python3-netifaces-0.10.6-15.el9.x86_64 python3-gssapi-1.6.9-5.el9.x86_64 python3-msgpack-1.0.3-2.el9s.x86_64 python3-extras-1.0.0-15.el9s.noarch python3-fixtures-3.0.0-27.el9s.noarch python3-testtools-2.5.0-2.el9s.noarch ovirt-hosted-engine-ha-2.5.0-1.el9.noarch python3-yubico-1.3.3-7.el9.noarch python3-babel-2.9.1-2.el9.noarch python3-inotify-0.9.6-25.el9.noarch python3-ethtool-0.15-2.el9.x86_64 python3-resolvelib-0.5.4-5.el9.noarch python3-prettytable-0.7.2-27.el9.noarch python3-jwcrypto-0.8-4.el9.noarch ovirt-vmconsole-host-1.0.9-1.el9.noarch python3-yappi-1.3.1-2.el9s.x86_64 python3-wrapt-1.13.3-2.el9s.x86_64 python3-debtcollector-2.5.0-1.el9s.noarch python3-oslo-context-4.1.0-1.el9s.noarch python3-tenacity-6.3.1-1.el9s.noarch python3-tempita-0.5.2-2.el9s.noarch python3-stevedore-3.5.2-1.el9s.noarch python3-rfc3986-1.5.0-1.el9s.noarch python3-repoze-lru-0.7-10.el9s.noarch python3-routes-2.5.1-1.el9s.noarch python3-jmespath-0.10.0-1.el9s.noarch python3-iso8601-0.1.13-4.el9s.noarch python-oslo-utils-lang-4.12.3-1.el9s.noarch python-oslo-privsep-lang-2.7.0-1.el9s.noarch python-oslo-log-lang-4.7.0-1.el9s.noarch python-oslo-i18n-lang-5.1.0-1.el9s.noarch python3-oslo-i18n-5.1.0-1.el9s.noarch python3-oslo-utils-4.12.3-1.el9s.noarch python3-oslo-config-8.8.0-1.el9s.noarch python3-oslo-serialization-4.3.0-1.el9s.noarch python3-oslo-log-4.7.0-1.el9s.noarch python3-oslo-privsep-2.7.0-1.el9s.noarch python-oslo-concurrency-lang-4.5.0-1.el9s.noarch ovirt-provider-ovn-driver-1.2.36-1.el9.noarch python3-webob-1.8.7-1.el9s.noarch python3-paste-3.5.0-3.el9s.noarch python3-paste-deploy-2.1.1-2.el9s.noarch python3-markupsafe-2.0.0-2.el9s.x86_64 python3-jinja2-3.0.1-2.el9s.noarch python3-fasteners-0.14.1-24.el9s.noarch python3-oslo-concurrency-4.5.0-1.el9s.noarch python3-os-win-5.6.0-1.el9s.noarch python3-oslo-service-2.8.0-1.el9s.noarch
[ovirt-users] Re: Hosted-engine restore failing
Hi. It looks like you have different versions of Python or another package. *rpm -qa | grep python* *rpm -qa | grep ovirt* On both hosts (old and new) Em qua., 11 de out. de 2023 às 12:08, Devin A. Bougie < devin.bou...@cornell.edu> escreveu: > Hi, All. We are attempting to migrate to a new storage domain for our > oVirt 4.5.4 self-hosted engine setup, and are failing with "cannot import > name 'Callable' from 'collections'" > > Please see below for the errors on the console. > > Many thanks, > Devin > > -- > hosted-engine --deploy --restore-from-file=backup.bck --4 > ... > [ INFO ] Checking available network interfaces: > [ ERROR ] b'[WARNING]: Skipping plugin (/usr/share/ovirt-hosted-engine-\n' > [ ERROR ] b'setup/he_ansible/callback_plugins/2_ovirt_logger.py), cannot > load: cannot\n' > [ ERROR ] b"import name 'Callable' from 'collections'\n" > [ ERROR ] b'(/usr/lib64/python3.11/collections/__init__.py)\n' > [ ERROR ] b"ERROR! Unexpected Exception, this is probably a bug: cannot > import name 'Callable' from 'collections' > (/usr/lib64/python3.11/collections/__init__.py)\n" > [ ERROR ] Failed to execute stage 'Environment customization': Failed > executing ansible-playbook > [ INFO ] Stage: Clean up > [ INFO ] Cleaning temporary resources > [ ERROR ] b'[WARNING]: Skipping plugin (/usr/share/ovirt-hosted-engine-\n' > [ ERROR ] b'setup/he_ansible/callback_plugins/2_ovirt_logger.py), cannot > load: cannot\n' > [ ERROR ] b"import name 'Callable' from 'collections'\n" > [ ERROR ] b'(/usr/lib64/python3.11/collections/__init__.py)\n' > [ ERROR ] b"ERROR! Unexpected Exception, this is probably a bug: cannot > import name 'Callable' from 'collections' > (/usr/lib64/python3.11/collections/__init__.py)\n" > [ ERROR ] Failed to execute stage 'Clean up': Failed executing > ansible-playbook > [ INFO ] Generating answer file > '/var/lib/ovirt-hosted-engine-setup/answers/answers-2023100358.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > [ ERROR ] Hosted Engine deployment failed > Log file is located at > > /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-2023100352-raupj9.log > ___ > 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/A7DPYZ4DG5EXB2YTYDERHVN5A2ZVKUPR/ > -- Att, Jorge Visentini +55 55 98432-9868 ___ 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/XFIQXYQEVIKX2BN5DYZKL5JNOZSH2VQZ/
