9:53 a.m.
On Tue, Nov 1, 2022 at 3:14 PM Michal Skrivanek <mskrivan(a)redhat.com> wrote:
> On 1. 11. 2022, at 11:46, Matthew J Black <matthew(a)peregrineit.net> wrote:
>
> Hi All,
>
> Long story short, I just tried to do a `hosted-engine --deploy` on a brand, new
"out-of-the-box box", following the oVirt doco *exactly*, and while I got past
my "Host is not up" issue, but almost exactly afterwards got this in my console
(I've included the couple of lines leading up to the "Host is no up" step):
>
> ~~~
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using
username/password credentials]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure]
> [ INFO ] skipping: [localhost]
Skipped, so this means that host_result_up_check (the check itself) didn't fail.
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set host_id]
> [ INFO ] ok: [localhost]
This means that we entered the block "Emit error messages about the
failure", which means all of the 3 "and-ed" conditions in its
"when:"
were true. Sadly, this (the block) isn't logged in itself - see [1]
(and [2], a simple attempt at a workaround that I eventually gave up
on). This means that we did get a host in the result, and that its
status is "non_operational".
[1] https://github.com/ansible/ansible/issues/33581
[2] https://gerrit.ovirt.org/c/ovirt-hosted-engine-setup/+/115775
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Collect error
events from the Engine]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Generate the error message from
the engine events]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify with error description]
> [ INFO ] ok: [localhost]
This means that the above tasks did manage to generate an
"error_description", but that for some reason it was not output to
your console. This is quite weird, I have no idea how this happened.
I am confident I tested it back then [3], and also can find examples
(very few) where it worked for others [4]. Incidentally, [4] does not
include the task name "Notify with error description", and neither
google finds it anywhere, but your output above does include it. [4]
does include the actual text, but your output does not. Perhaps this
is a change in ansible since then or something similar. Would you like
to create a github issue in [5] about it? Something like "HE
deployment gets stuck without details" or whatever, and add relevant
parts of the logs. Thanks.
[3] https://github.com/oVirt/ovirt-ansible-collection/pull/181
[4]
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/UZHD5KCPMKXO...
[5] https://github.com/oVirt/ovirt-ansible-collection
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify with
generic error]
> [ INFO ] skipping: [localhost]
(This is another indication that we did manage to generate an error message)
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Let the user
connect to the bootstrap engine to manually fix host configuration]
> [ INFO ] ok: [localhost]
Again - the actual text is missing.
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup :
include_tasks]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create temporary lock file]
> [ INFO ] changed: [localhost -> localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Pause execution until
/tmp/ansible.volt5pvv_he_setup_lock is removed, delete it once ready to proceed]
> ~~~
>
> I didn't ask for script to pause, so I need to ask: Is this normal?
No. I guess you did ask for that, maybe by mistake. The default is not to pause.
This isn't the case here - it paused due to a problem, but didn't emit details.
Can you please check the logs in /var/log/ovirt-hosted-engine-setup?
You most likely should be able to find the messages there, including
the URL to the web admin if needed.
can you get to webadmin now and confirm th host state?
and/or just remove that file and let it continue...
If you do that, it will shortly thereafter fail in the following task
"Check if the host is up".
Thanks,
michal
>
> I'm about to have a look at the logs, but its late here at the moment so I
wanted to get this up on the mailing lists so I don't loose too much time while
I'm asleep and everyone else is awake (& vice-versa).
Good luck, sorry for all the obstacles you bump into, and best regards,
--
Didi