-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
self-hosted engine deployment failed because "'elasticsearch_host' is undefined" #708
Comments
I have the same problem on Rocky 8.8 node
Engine OS:
|
I was able to bypass the error like this: When deploying the hosted-engine use the he_pause_host: When the deployment stopped then login the HostedEngineLocal using root via ssh or virsh console
Deploy host from the ovirt ui console |
Currently, the only working solution is to have both the hosts and the hosted-engine version 4.4.10, and then update the hosted-engine to 4.5.4 first, and then the hosts. It is important that you cannot add a 4.4.10 host to the 4.5.4 hosted-engine, everything must be started from 4.4.10. |
this was fixed by oVirt/ovirt-engine-metrics#35 |
i was able to get past this error by set a versionlock for the preinstalled ansible-core version e.g.: this does also prevent #695 so that workaround does not need to be applied. but good to know that nightly has that already fixed. feel free to close this issue - or let it open for others. :) |
Try this and finally works !! Thanks |
Downgrading to ansible 2.14 also works |
Also note, dnf versionlock ansible-core-0:2.13.5-1.el8.* needs to be run on the ovirt engine VM, not the host. |
Why is this not released ? |
SUMMARY
Hello,
I am currently facing some challenges with my oVirt deployment and would appreciate your assistance.
Last week, on Thursday, I successfully deployed oVirt 4.5.4 using the self-hosted engine deployment, based on the latest oVirt Node NG 4.5.4 image.
During the deployment process, I encountered and addressed issue #695 by applying the suggested workaround, which resolved the problem.
However, upon attempting to redeploy oVirt on the same hardware using a fresh Node NG installation today, I encountered a new issue...
COMPONENT NAME
STEPS TO REPRODUCE
Nothing special:
Answer / input values as necessary. (when possible default)
EXPECTED RESULTS
Successful deployment of self-hosted engine.
ACTUAL RESULTS
Upon reviewing the logs, I came across the following error message:
and in the ovirt-host-deploy-ansible log i see this:
maybe related packages after
[ INFO ] TASK [ovirt.ovirt.engine_setup : Update all packages]
The text was updated successfully, but these errors were encountered: