On Tue, Mar 29, 2022 at 12:21 PM Vladimir Belov <jvlad...@gmail.com> wrote:
>
>
> I'm trying to deploy oVirt from a self-hosted engine, but at the last step I
> get an engine startup error.
>
> [ INFO ] TASK [Wait for the engine to come up on the target VM]
> [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true,
> "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": "0:00:00.181846",
> "end": "2022-03-28 15:41:28.853150", "rc": 0, "start": "2022-03-28
> 15:41:28.671304", "stderr": "", "stderr_lines": [], "stdout": "{\"1\":
> {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon
> Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537
> (Mon Mar 28 15:41:20
> 2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
> \"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\":
> {\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\":
> \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false,
> \"maintenance\": false, \"crc32\": \"4d2eeaea\", \"local_conf_timestamp\":
> 5537, \"host-ts\": 5537}, \"global_maintenance\": false}", "stdout_lines":
> ["{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon
> Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537
> (Mon Mar 28 15:41:20
> 2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
> \"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\":
> {\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\":
> \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false,
> \"maintenance\": false, \"crc32\": \"4d2eeaea\", \"local_conf_timestamp\":
> 5537, \"host-ts\": 5537}, \"global_maintenance\": false}"]}
>
> Аfter the installation is completed, the condition of the engine is as
> follows:
> Engine status: {"reason": "failed liveliness check", "health": "bad", "vm":
> "up", "detail": "Up"}
>
> After reading the vdsm.logs, I found that qemu-guest-agent failed to connect
> to the engine for some reason.
>
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5400, in
> qemuGuestAgentShutdown
> self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT)
> File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 98, in
> f
> ret = attr(*args, **kwargs)
> File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py",
> line 130, in wrapper
> ret = f(*args, **kwargs)
> File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92,
> in wrapper
> return func(inst, *args, **kwargs)
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2517, in
> shutdownFlags
> if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed',
> dom=self)
> libvirtError: Guest agent is not responding: QEMU guest agent is not connected
IIRC this shouldn't fail anything, other than functionality that
relies on the agent (which should be non-critical).
>
> During the installation phase, qemu-guest-agent on the guest VM is running.
>
> Setting a temporary password (hosted-engine --add-console-password
> --password) and connecting via VNC also failed.
>
> Using "hosted-engine --console" also failed to connect
>
> The engine VM is running on this host
> Connected to HostedEngine domain
> Escaping character: ^]
> error: internal error: character device <null> not found
>
> The network settings are configured using static addressing, without DHCP.
> It seems to me that this is due to the fact that the engine receives an IP
> address that does not match the entry in /etc/hosts, but I do not know how to
> fix it.
"Receives"? Where from? If you choose static, all should be configured
using the values you provided.
Anyway, this should not prevent logging in using the console.
> Any help is welcome, I will provide the necessary logs. Thanks
Do you use qemu-kvm 6.1? If so, please try 6.0 or 6.2. Otherwise,
please check more logs on the host, including:
/var/log/ovirt-hosted-engine*/*
/var/log/libvirt
/var/log/messages
Good luck and 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/YUIYKXVYXNL6NVF2KHAW3UIRTKXQ6OAX/
