well, that's interesting... The deploy abortion did not destroy the local runing VM as usual. So i disabled CentOS-Stream-PowerTools.repo again (was re-enabled by deploy), and provided my modified oVirt repositories.
I ran engine-setup on the running local VM, setup checked for updates, nothing to be done, and then running fine through the complete setup. Now i have a local VM engine running fine, the hosts are recognized as "up" , VMs and storage domains are fine as well. Is there a way to make the deploy jump to that stage and resume? Or: can i do the engine-setup(with restore or without) myself after providing my modified repositories? If the deploy finds nothing to be updated, all should run afterwards? Since this is the test for upgrading the production i should not depend on "i hope the local VM is still running after deploy abort" All i could find in engine-setup log is, that the repository could not be reached. best regards _______________________________________________ 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/S25HQEQH3QQRGIPR5ECTTOP73IQFLFFT/
