Bug 2044034 - Failed to deploy HE due to deprecations in ansible.
Summary: Failed to deploy HE due to deprecations in ansible.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: 2.6.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.5.0
: 2.6.1
Assignee: Asaf Rachmani
QA Contact: Nikolai Sednev
URL:
Whiteboard:
Depends On:
Blocks: 2050512
TreeView+ depends on / blocked
 
Reported: 2022-01-23 09:21 UTC by Nikolai Sednev
Modified: 2022-04-20 06:33 UTC (History)
3 users (show)

Fixed In Version: ovirt-hosted-engine-setup-2.6.1
Clone Of:
Environment:
Last Closed: 2022-04-20 06:33:59 UTC
oVirt Team: Integration
Embargoed:
sbonazzo: ovirt-4.5+
sbonazzo: planning_ack?
sbonazzo: devel_ack+
sbonazzo: testing_ack?


Attachments (Terms of Use)
sosreport-serval14 (15.15 MB, application/x-xz)
2022-01-23 09:21 UTC, Nikolai Sednev
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-hosted-engine-setup pull 18 0 None Merged spec: Add conflict with ansible-core 2022-01-24 08:15:13 UTC
Red Hat Issue Tracker RHV-44526 0 None None None 2022-01-23 09:23:17 UTC

Description Nikolai Sednev 2022-01-23 09:21:49 UTC
Created attachment 1852828 [details]
sosreport-serval14

Description of problem:
serval14 ~]# hosted-engine --deploy
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
          During customization use CTRL-D to abort.
          Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine.
          The locally running engine will be used to configure a new storage domain and create a VM there.
          At the end the disk of the local VM will be moved to the shared storage.
          Are you sure you want to continue? (Yes, No)[Yes]: 
          It has been detected that this program is executed through an SSH connection without using tmux.
          Continuing with the installation may lead to broken installation if the network connection fails.
          It is highly recommended to abort the installation and run it inside a tmux session using command "tmux".
          Do you want to continue anyway? (Yes, No)[No]: yes
          Configuration files: 
          Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20220123100630-s87ai6.log
          Version: otopi-1.9.6 (otopi-1.9.6-2.el8ev)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup (late)
[ INFO  ] Stage: Environment customization
         
          --== STORAGE CONFIGURATION ==--
         
         
          --== HOST NETWORK CONFIGURATION ==--
         
          Please indicate the gateway IP address [10.35.235.254]: 
[ INFO  ] Checking available network interfaces:
[ ERROR ] b'[DEPRECATION WARNING]: ANSIBLE_CALLBACK_WHITELIST option, normalizing names to \n'
[ ERROR ] b'new standard, use ANSIBLE_CALLBACKS_ENABLED instead. This feature will be \n'
[ ERROR ] b'removed from ansible-core in version 2.15. Deprecation warnings can be disabled\n'
[ ERROR ] b' by setting deprecation_warnings=False in ansible.cfg.\n'
[ ERROR ] b"ERROR! couldn't resolve module/action 'virt_net'. This often indicates a misspelling, missing collection, or incorrect module path.\n"
[ ERROR ] b'\n'
[ ERROR ] b"The error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml': line 21, column 5, but may\n"
[ ERROR ] b'be elsewhere in the file depending on the exact syntax problem.\n'
[ ERROR ] b'\n'
[ ERROR ] b'The offending line appears to be:\n'
[ ERROR ] b'\n'
[ ERROR ] b'      enabled: true\n'
[ ERROR ] b'  - name: Activate default libvirt network\n'
[ ERROR ] b'    ^ here\n'
[ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook
[ INFO  ] Stage: Clean up
[ INFO  ] Cleaning temporary resources
[ ERROR ] b'[DEPRECATION WARNING]: ANSIBLE_CALLBACK_WHITELIST option, normalizing names to \n'
[ ERROR ] b'new standard, use ANSIBLE_CALLBACKS_ENABLED instead. This feature will be \n'
[ ERROR ] b'removed from ansible-core in version 2.15. Deprecation warnings can be disabled\n'
[ ERROR ] b' by setting deprecation_warnings=False in ansible.cfg.\n'
[ ERROR ] b"ERROR! couldn't resolve module/action 'virt_net'. This often indicates a misspelling, missing collection, or incorrect module path.\n"
[ ERROR ] b'\n'
[ ERROR ] b"The error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml': line 21, column 5, but may\n"
[ ERROR ] b'be elsewhere in the file depending on the exact syntax problem.\n'
[ ERROR ] b'\n'
[ ERROR ] b'The offending line appears to be:\n'
[ ERROR ] b'\n'
[ ERROR ] b'      enabled: true\n'
[ ERROR ] b'  - name: Activate default libvirt network\n'
[ ERROR ] b'    ^ here\n'
[ ERROR ] Failed to execute stage 'Clean up': Failed executing ansible-playbook
[ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20220123100641.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Hosted Engine deployment failed
          Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20220123100630-s87ai6.log


Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-2.6.0-1.el8.noarch
ovirt-hosted-engine-ha-2.4.9-1.el8ev.noarch
ansible-core-2.12.1-1.el8.x86_64
ovirt-ansible-collection-1.6.5-1.el8ev.noarch
Linux 4.18.0-359.el8.x86_64 #1 SMP Mon Jan 10 15:32:06 EST 2022 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.6 Beta (Ootpa)



How reproducible:
100%

Steps to Reproduce:
1.Deploy HE.

Actual results:
Deployment fails.

Expected results:
Should be successful.

Additional info:
Logs attached.

Comment 1 Asaf Rachmani 2022-01-23 09:57:00 UTC
The issue is that ansible-core-2.12 is installed and it provides an ansible version RHV currently doesn't support (ovirt-engine and ovirt-hosted-engine-setup require ansible-2.9).
This should fix that - https://github.com/oVirt/ovirt-hosted-engine-setup/pull/18

Comment 5 Nikolai Sednev 2022-01-24 15:01:04 UTC
This bug was found, while trying to deploy on RHEL6.
Linux serval14.lab.eng.tlv2.redhat.com 4.18.0-359.el8.x86_64 #1 SMP Mon Jan 10 15:32:06 EST 2022 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.6 Beta (Ootpa)

When I retested on 
Red Hat Enterprise Linux release 8.5 (Ootpa)
Linux 4.18.0-348.el8.x86_64 #1 SMP Mon Oct 4 12:17:22 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
# yum list | grep ovirt-hosted-engine-setup ovirt-hosted-engine-setup.noarch 2.6.0-1.el8 rhv-4.5.0-1 
ovirt-hosted-engine-setup-2.6.0-1.el8.noarch
ovirt-hosted-engine-ha-2.4.9-1.el8ev.noarch

Then the deployment has failed just like it did over RHEL8.6:

~]# hosted-engine --deploy
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
          During customization use CTRL-D to abort.
          Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine.
          The locally running engine will be used to configure a new storage domain and create a VM there.
          At the end the disk of the local VM will be moved to the shared storage.
          Are you sure you want to continue? (Yes, No)[Yes]: 
          It has been detected that this program is executed through an SSH connection without using tmux.
          Continuing with the installation may lead to broken installation if the network connection fails.
          It is highly recommended to abort the installation and run it inside a tmux session using command "tmux".
          Do you want to continue anyway? (Yes, No)[No]: yes
          Configuration files: 
          Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20220124165838-dpel0c.log
          Version: otopi-1.9.6 (otopi-1.9.6-2.el8ev)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup (late)
[ INFO  ] Stage: Environment customization
         
          --== STORAGE CONFIGURATION ==--
         
         
          --== HOST NETWORK CONFIGURATION ==--
         
          Please indicate the gateway IP address [10.35.235.254]: 
[ INFO  ] Checking available network interfaces:
[ ERROR ] b'[DEPRECATION WARNING]: ANSIBLE_CALLBACK_WHITELIST option, normalizing names to \n'
[ ERROR ] b'new standard, use ANSIBLE_CALLBACKS_ENABLED instead. This feature will be \n'
[ ERROR ] b'removed from ansible-core in version 2.15. Deprecation warnings can be disabled\n'
[ ERROR ] b' by setting deprecation_warnings=False in ansible.cfg.\n'
[ ERROR ] b"ERROR! couldn't resolve module/action 'virt_net'. This often indicates a misspelling, missing collection, or incorrect module path.\n"
[ ERROR ] b'\n'
[ ERROR ] b"The error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml': line 21, column 5, but may\n"
[ ERROR ] b'be elsewhere in the file depending on the exact syntax problem.\n'
[ ERROR ] b'\n'
[ ERROR ] b'The offending line appears to be:\n'
[ ERROR ] b'\n'
[ ERROR ] b'      enabled: true\n'
[ ERROR ] b'  - name: Activate default libvirt network\n'
[ ERROR ] b'    ^ here\n'
[ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook
[ INFO  ] Stage: Clean up
[ INFO  ] Cleaning temporary resources
[ ERROR ] b'[DEPRECATION WARNING]: ANSIBLE_CALLBACK_WHITELIST option, normalizing names to \n'
[ ERROR ] b'new standard, use ANSIBLE_CALLBACKS_ENABLED instead. This feature will be \n'
[ ERROR ] b'removed from ansible-core in version 2.15. Deprecation warnings can be disabled\n'
[ ERROR ] b' by setting deprecation_warnings=False in ansible.cfg.\n'
[ ERROR ] b"ERROR! couldn't resolve module/action 'virt_net'. This often indicates a misspelling, missing collection, or incorrect module path.\n"
[ ERROR ] b'\n'
[ ERROR ] b"The error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml': line 21, column 5, but may\n"
[ ERROR ] b'be elsewhere in the file depending on the exact syntax problem.\n'
[ ERROR ] b'\n'
[ ERROR ] b'The offending line appears to be:\n'
[ ERROR ] b'\n'
[ ERROR ] b'      enabled: true\n'
[ ERROR ] b'  - name: Activate default libvirt network\n'
[ ERROR ] b'    ^ here\n'
[ ERROR ] Failed to execute stage 'Clean up': Failed executing ansible-playbook
[ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20220124165931.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Hosted Engine deployment failed
          Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20220124165838-dpel0c.log
]#

Comment 9 Nikolai Sednev 2022-02-21 10:26:58 UTC
ovirt-hosted-engine-setup-2.6.1-1.el8ev.noarch
ovirt-hosted-engine-ha-2.4.10-1.el8ev.noarch
ansible-2.9.27-1.el8ae.noarch
ovirt-ansible-collection-2.0.0-0.4.BETA.el8ev.noarch
python3-ovirt-setup-lib-1.3.3-1.el8ev.noarch
Red Hat Enterprise Linux release 8.6 Beta (Ootpa)
Linux 4.18.0-367.el8.x86_64 #1 SMP Thu Feb 10 14:56:38 EST 2022 x86_64 x86_64 x86_64 GNU/Linux

Comment 10 Sandro Bonazzola 2022-04-20 06:33:59 UTC
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.