1:03 p.m.
I am experiencing the error message in the
ovirt-hosted-engine-setup-ansible-create_target_vm log
{2020-05-06 14:15:30,024-0500 ERROR ansible failed {'status': 'FAILED',
'ansible_type': 'task', 'ansible_task': u"Fail if Engine IP
is different from engine's he_fqdn resolved IP", 'ansible_result':
u'type: <type \'dict\'>\nstr: {\'msg\': u"Engine VM IP
address is while the engine\'s he_fqdn ovirt1-engine.kelleykars.org resolves to
192.168.122.2. If you are using DHCP, check your DHCP reservation configuration",
\'changed\': False, \'_ansible_no_log\': False}',
'task_duration': 1, 'ansible_host': u'localhost',
'ansible_playbook':
u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'}}:Q!
The bug 1590266 says it should report the engine VM IP address xxx.xxx.xxx.xxx while the
Engines he_fqdn is xxxxxxxxx
I need to see what it thins is wrong as both dig fqdn engine name and dig -x ip return the
correct information.
Now this bug looks like it may play but I don't see the failed rediness check in the
this log https://access.redhat.com/solutions/4462431
or is it because the vm fails or dies or ???
12:37 a.m.
On Wed, May 6, 2020 at 11:06 PM kelley bryan <kelley.bryan10(a)gmail.com> wrote:
I am experiencing the error message in the
ovirt-hosted-engine-setup-ansible-create_target_vm log
{2020-05-06 14:15:30,024-0500 ERROR ansible failed {'status': 'FAILED',
'ansible_type': 'task', 'ansible_task': u"Fail if Engine IP
is different from engine's he_fqdn resolved IP", 'ansible_result':
u'type: <type \'dict\'>\nstr: {\'msg\': u"Engine VM IP
address is while the engine\'s he_fqdn ovirt1-engine.kelleykars.org resolves to
192.168.122.2. If you are using DHCP, check your DHCP reservation configuration",
\'changed\': False, \'_ansible_no_log\': False}',
'task_duration': 1, 'ansible_host': u'localhost',
'ansible_playbook':
u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'}}:Q!
The bug 1590266 says it should report the engine VM IP address xxx.xxx.xxx.xxx while the
Engines he_fqdn is xxxxxxxxx
I need to see what it thins is wrong as both dig fqdn engine name and dig -x ip return
the correct information.
Please check/share all relevant logs.
To answer the question in the subject, no, it did not reset. The code
was in ovirt-hosted-engine-setup when that bug was fixed, and the code
later moved to a different project, ovirt-ansible-hosted-engine-setup,
where you can find:
- name: Get target engine VM IP address
shell: getent {{ ip_key }} {{ he_fqdn }} | cut -d' ' -f1 | uniq
environment: "{{ he_cmd_lang }}"
register: engine_vm_ip
changed_when: true
- name: Get VDSM's target engine VM stats
command: vdsm-client VM getStats vmID={{ he_vm_details.vm.id }}
environment: "{{ he_cmd_lang }}"
register: engine_vdsm_stats
changed_when: true
- name: Convert stats to JSON format
set_fact: json_stats={{ engine_vdsm_stats.stdout|from_json }}
- name: Get target engine VM IP address from VDSM stats
set_fact: engine_vm_ip_vdsm={{ json_stats[0].guestIPs }}
- debug: var=engine_vm_ip_vdsm
- name: Fail if Engine IP is different from engine's he_fqdn resolved IP
fail:
msg: >-
Engine VM IP address is {{ engine_vm_ip_vdsm }} while the
engine's he_fqdn {{ he_fqdn }} resolves to
{{ engine_vm_ip.stdout_lines[0] }}. If you are using DHCP,
check your DHCP reservation configuration
when: engine_vm_ip_vdsm != engine_vm_ip.stdout_lines[0]
You should be able to find most of the relevant variable values used
above in your logs, and try to correlate them with reality, and find
out why deploy decided there is a problem and failed. If you think
there is a bug, please open one, and attach all relevant logs. Thanks!
Now this bug looks like it may play but I don't see the failed rediness check in the
this log https://access.redhat.com/solutions/4462431
This page is accessible only for Red Hat customers, so other people
can't access it. If you are a customer, please discuss its contents
with Red Hat's support, by opening a ticket. Thanks!
That said, there is nothing magical here. If your networking
configuration is 100% consistent, everything should work. This should
include name resolution (both DNS forward (A) and reverse (PTR), or
/etc/hosts), IP/MAC addresses matching, etc. If it's not, things would
eventually likely fail. The bug you mention, and the error in the log
snippet you provided, is simply meant to fail early, if deploy detects
some inconsistency, rather than continue blindly and fail much later.
or is it because the vm fails or dies or ???
Most likely this isn't the case, but you can simply check - do you see
a 'qemu' process running? Can you ssh to the VM? At this stage it
might still have the local, private IP address assigned by libvirt,
which you can find by searching the logs for 'local_vm_ip'.
Best regards,
--
Didi
8:08 a.m.
Hi Guys
I am facing same issue in my recent deployment. There is nothing in the log that points
towards the issue. I am deploying the VM on host with Centros Stream OS. Anybody recently
faced this issue? Please let me know if need any further information.
Many Thanks.
Regards
Sohail
10:49 p.m.
Hi Sohail,
On Thu, Jan 6, 2022 at 8:38 AM <sohail_akhter3(a)hotmail.com> wrote:
Hi Guys
I am facing same issue in my recent deployment.
Can you please clarify what issue you refer to? You replied to a
1.5-years-old thread without any context.
There is nothing in the log that points towards the issue. I am
deploying the VM on host with Centros Stream OS. Anybody recently faced this issue? Please
let me know if need any further information.
Please provide more details: What exact error message you get, at what
point, relevant logs. Thanks.
Best regards,
--
Didi
1:46 a.m.
Hi Didi,
Apologies as this is my first post. I am referring the issue that is mentioned in the Red
hat solution mentioned in this thread.
https://access.redhat.com/solutions/4462431
I am trying to deploy hosted engine VM. I tried via cockpit gui and through CLI. In both
cased deployment fails with error message
From the below error message I can see VM is in powering down state and health status is
bad
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check engine VM health]
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 180,
"changed": true, "cmd": ["hosted-engine",
"--vm-status", "--json"], "delta":
"0:00:00.162941", "end": "2022-01-06 00:43:07.060659",
"rc": 0, "start": "2022-01-06 00:43:06.897718",
"stderr": "", "stderr_lines": [], "stdout":
"{\"1\": {\"host-id\": 1, \"host-ts\": 117459,
\"score\": 3400, \"engine-status\": {\"vm\":
\"up\", \"health\": \"bad\", \"detail\":
\"Powering down\", \"reason\": \"failed liveliness check\"},
\"hostname\": \"seliics00123.ovirt4.fl.dselab.seli.gic.ericsson.se\",
\"maintenance\": false, \"stopped\": false, \"crc32\":
\"d889fd9b\", \"conf_on_shared_storage\": true,
\"local_conf_timestamp\": 117459, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=117459 (Thu Jan
6 00:43:02 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=117459 (Thu Jan 6
00:43:02
2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStop\\nstopped=False\\ntimeout=Fri
Jan 2 08:38:08 1970
\\n\", \"live-data\": true}, \"global_maintenance\":
false}", "stdout_lines": ["{\"1\": {\"host-id\":
1, \"host-ts\": 117459, \"score\": 3400, \"engine-status\":
{\"vm\": \"up\", \"health\": \"bad\",
\"detail\": \"Powering down\", \"reason\": \"failed
liveliness check\"}, \"hostname\":
\"seliics00123.ovirt4.fl.dselab.seli.gic.ericsson.se\",
\"maintenance\": false, \"stopped\": false, \"crc32\":
\"d889fd9b\", \"conf_on_shared_storage\": true,
\"local_conf_timestamp\": 117459, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=117459 (Thu Jan
6 00:43:02 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=117459 (Thu Jan 6
00:43:02
2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStop\\nstopped=False\\ntimeout=Fri
Jan 2 08:38:08 1970\\n\", \"live-data\": true},
\"global_maintenance\": false}"]}
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check VM status at virt level]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if engine VM is not running]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get target engine VM IP address]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get VDSM's target engine VM stats]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Convert stats to JSON format]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get target engine VM IP address from
VDSM stats]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if Engine IP is different from
engine's he_fqdn resolved IP]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg":
"Engine VM IP address is while the engine's he_fqdn
manager-ovirt4.fl.dselab.seli.gic.ericsson.se resolves to 10.228.170.36. If you are using
DHCP, check your DHCP reservation configuration"}
[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook
VM is running
[root@host]# virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf
list
Id Name State
------------------------------
37 HostedEngine running
Please let me know if you need any further output or log file.
Regards
Sohail
1:50 a.m.
On Thu, Jan 6, 2022 at 11:47 AM <sohail_akhter3(a)hotmail.com> wrote:
Hi Didi,
Apologies as this is my first post. I am referring the issue that is mentioned in the Red
hat solution mentioned in this thread.
https://access.redhat.com/solutions/4462431
I am trying to deploy hosted engine VM. I tried via cockpit gui and through CLI. In both
cased deployment fails with error message
From the below error message I can see VM is in powering down state and health status is
bad
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check engine VM health]
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 180,
"changed": true, "cmd": ["hosted-engine",
"--vm-status", "--json"], "delta":
"0:00:00.162941", "end": "2022-01-06 00:43:07.060659",
"rc": 0, "start": "2022-01-06 00:43:06.897718",
"stderr": "", "stderr_lines": [], "stdout":
"{\"1\": {\"host-id\": 1, \"host-ts\": 117459,
\"score\": 3400, \"engine-status\": {\"vm\":
\"up\", \"health\": \"bad\", \"detail\":
\"Powering down\", \"reason\": \"failed liveliness check\"},
\"hostname\": \"seliics00123.ovirt4.fl.dselab.seli.gic.ericsson.se\",
\"maintenance\": false, \"stopped\": false, \"crc32\":
\"d889fd9b\", \"conf_on_shared_storage\": true,
\"local_conf_timestamp\": 117459, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=117459 (Thu Jan
6 00:43:02 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=117459 (Thu Jan 6
00:43:02
2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStop\\nstopped=False\\ntimeout=Fri
Jan 2 08:38:08 1970
\\n\", \"live-data\": true}, \"global_maintenance\":
false}", "stdout_lines": ["{\"1\": {\"host-id\":
1, \"host-ts\": 117459, \"score\": 3400, \"engine-status\":
{\"vm\": \"up\", \"health\": \"bad\",
\"detail\": \"Powering down\", \"reason\": \"failed
liveliness check\"}, \"hostname\":
\"seliics00123.ovirt4.fl.dselab.seli.gic.ericsson.se\",
\"maintenance\": false, \"stopped\": false, \"crc32\":
\"d889fd9b\", \"conf_on_shared_storage\": true,
\"local_conf_timestamp\": 117459, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=117459 (Thu Jan
6 00:43:02 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=117459 (Thu Jan 6
00:43:02
2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStop\\nstopped=False\\ntimeout=Fri
Jan 2 08:38:08 1970\\n\", \"live-data\": true},
\"global_maintenance\": false}"]}
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check VM status at virt level]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if engine VM is not running]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get target engine VM IP address]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get VDSM's target engine VM stats]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Convert stats to JSON format]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get target engine VM IP address from
VDSM stats]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if Engine IP is different from
engine's he_fqdn resolved IP]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg":
"Engine VM IP address is while the engine's he_fqdn
manager-ovirt4.fl.dselab.seli.gic.ericsson.se resolves to 10.228.170.36. If you are using
DHCP, check your DHCP reservation configuration"}
[ ERROR ] Failed to execute stage 'Closing up': Failed executing
ansible-playbook
VM is running
[root@host]# virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf
list
Id Name State
------------------------------
37 HostedEngine running
Please let me know if you need any further output or log file.
Can you check qemu version, and try downgrading it to 6.0.0 if
applicable? Thanks.
Best regards,
--
Didi
3:08 p.m.
Hi Didi
downgrading qemu-kvm fixed the issue. What is the reason it is not working with version
6.1.0. Currently this is the version installed on my host
#yum info qemu-kvm
Last metadata expiration check: 2:03:58 ago on Thu 06 Jan 2022 03:18:40 PM UTC.
Installed Packages
Name : qemu-kvm
Epoch : 15
Version : 6.0.0
Release : 33.el8s
Architecture : x86_64
Size : 0.0
Source : qemu-kvm-6.0.0-33.el8s.src.rpm
Repository : @System
From repo : ovirt-4.4-centos-stream-advanced-virtualization
Summary : QEMU is a machine emulator and virtualizer
URL : http://www.qemu.org/
License : GPLv2 and GPLv2+ and CC-BY
Description : qemu-kvm is an open source virtualizer that provides hardware
: emulation for the KVM hypervisor. qemu-kvm acts as a virtual
: machine monitor together with the KVM kernel modules, and emulates the
: hardware for a full system such as a PC and its associated peripherals.
Available Packages
Name : qemu-kvm
Epoch : 15
Version : 6.1.0
Release : 5.module_el8.6.0+1040+0ae94936
Architecture : x86_64
Size : 156 k
Source : qemu-kvm-6.1.0-5.module_el8.6.0+1040+0ae94936.src.rpm
Repository : appstream
Summary : QEMU is a machine emulator and virtualizer
URL : http://www.qemu.org/
License : GPLv2 and GPLv2+ and CC-BY
Description : qemu-kvm is an open source virtualizer that provides hardware
: emulation for the KVM hypervisor. qemu-kvm acts as a virtual
: machine monitor together with the KVM kernel modules, and emulates the
: hardware for a full system such as a PC and its associated peripherals.
Many thanks for your help
Regards
Sohail
12:04 a.m.
On Fri, Jan 7, 2022 at 1:09 AM <sohail_akhter3(a)hotmail.com> wrote:
Hi Didi
downgrading qemu-kvm fixed the issue.
Thanks for the update!
What is the reason it is not working with version 6.1.0.
https://bugzilla.redhat.com/show_bug.cgi?id=2024605
Currently this is the version installed on my host
#yum info qemu-kvm
Last metadata expiration check: 2:03:58 ago on Thu 06 Jan 2022 03:18:40 PM UTC.
Installed Packages
Name : qemu-kvm
Epoch : 15
Version : 6.0.0
Release : 33.el8s
Architecture : x86_64
Size : 0.0
Source : qemu-kvm-6.0.0-33.el8s.src.rpm
Repository : @System
From repo : ovirt-4.4-centos-stream-advanced-virtualization
Summary : QEMU is a machine emulator and virtualizer
URL : http://www.qemu.org/
License : GPLv2 and GPLv2+ and CC-BY
Description : qemu-kvm is an open source virtualizer that provides hardware
: emulation for the KVM hypervisor. qemu-kvm acts as a virtual
: machine monitor together with the KVM kernel modules, and emulates the
: hardware for a full system such as a PC and its associated peripherals.
Available Packages
Name : qemu-kvm
Epoch : 15
Version : 6.1.0
Release : 5.module_el8.6.0+1040+0ae94936
Architecture : x86_64
Size : 156 k
Source : qemu-kvm-6.1.0-5.module_el8.6.0+1040+0ae94936.src.rpm
Repository : appstream
Summary : QEMU is a machine emulator and virtualizer
URL : http://www.qemu.org/
License : GPLv2 and GPLv2+ and CC-BY
Description : qemu-kvm is an open source virtualizer that provides hardware
: emulation for the KVM hypervisor. qemu-kvm acts as a virtual
: machine monitor together with the KVM kernel modules, and emulates the
: hardware for a full system such as a PC and its associated peripherals.
Many thanks for your help
Regards
Sohail
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/P6S4CYOYQLD...
--
Didi
837
days inactive
1451
days old
7 comments
3 participants
participants (3)
-
kelley bryan -
sohail_akhter3＠hotmail.com -
Yedidyah Bar David