On Wed, May 27, 2020 at 12:37 PM Oliver Leinfelder
<oliver.leinfel...@gmail.com> wrote:
>
> Hi there,
>
> > You should also see one or more ERROR messages, can you check/post them?
>
> There is one error message that immediately follows, if that helps:
>
> 2020-05-27 00:17:12,397+0200 ERROR otopi.context
> context._executeMethod:154 Failed to execute stage 'Closing up': Failed
> executing ansible-playbook
> 2020-05-27 00:17:12,397+0200 DEBUG otopi.context
> context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN
> 2020-05-27 00:17:12,398+0200 DEBUG otopi.context
> context.dumpEnvironment:775 ENV BASE/error=bool:'True'
> 2020-05-27 00:17:12,398+0200 DEBUG otopi.context
> context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class
> 'RuntimeError'>, RuntimeError('Failed executing ansible-playbook',),
> <traceback object at 0x7f9bbdea5cc8>)]'
> 2020-05-27 00:17:12,398+0200 DEBUG otopi.context
> context.dumpEnvironment:779 ENVIRONMENT DUMP - END
> 2020-05-27 00:17:12,398+0200 INFO otopi.context context.runSequence:616
> Stage: Clean up
> 2020-05-27 00:17:12,399+0200 DEBUG otopi.context context.runSequence:620
> STAGE cleanup
>
> Other than that, there is nothing that looks like an error (or contains
> the word "error").Perhaps it's not engine-setup that failed, but something later on in ansible code. Can you check/share the full ansible logs? Search also for 'failed', or 'fatal'. > > > Also, if possible, please try to check/share the engine-setup log. If > > you can access the engine VM, it's there, in: > > > > /var/log/ovirt-engine/setup > > The engine is not running after that, "hosted-engine --vm-status" gives > me the following error: > > It seems like a previous attempt to deploy hosted-engine failed or it's > still in progress. Please clean it up before trying again > > Otherwise, you might find it in the host doing the deployment, in: > > > > /var/log/ovirt-hosted-engine-setup/engine-logs* > I have 4 directories like this (from my failed deployment attempts ;-)), > but all of them are empty. I happened to see that myself, but still not sure why it happens. Perhaps open a bug to track this? In any case (perhaps not relevant to you right now, if indeed engine-setup succeeded), usually the engine vm is left running at the end of a failed deploy. If it's still the local vm, you can find its IP address by searching the ansible logs for local_vm_ip, then you can ssh to it from the host. For fixing the "empty engine-logs dirs", now pushed this: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/pull/325 Didn't test yet, it's just a guess. > > The last attempt was with a new backup, just in case. > > The production oVirt is 4.3.9, the host I'm installing from is a clean > install from the ovirt node 4.4.0 release ISO with the last available > package upgrades. Sounds ok to me. 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/UURQ3HHQSON4UPMFPKDCDMP6G6GJCR25/
