Bug 1504743
Summary: | [UPDATES] Failed to run update: skipping: no hosts matched | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Yurii Prokulevych <yprokule> |
Component: | openstack-tripleo-validations | Assignee: | mathieu bultel <mbultel> |
Status: | CLOSED ERRATA | QA Contact: | Yurii Prokulevych <yprokule> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 12.0 (Pike) | CC: | jjoyce, jschluet, mbultel, rbrady, sathlang, slinaber, tvignaud |
Target Milestone: | ga | Keywords: | Triaged |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-validations-7.4.1-2 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-13 22:17:19 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: |
Description
Yurii Prokulevych
2017-10-20 14:08:12 UTC
According to my test on your env Yurii, its looks like the issue is due to ansible 2.4. The inventory file can't be read by the new release of ansible cli, all hosts are ignore When running the command on the undercloud manually with the value passed in mistral: ansible-playbook 2.4.0.0 PLAYBOOK: update_steps_playbook.yaml ********************************************************************************************************************************************************************************************************* 1 plays in /tmp/tripleo-ibN3FH-config/update_steps_playbook.yaml [WARNING]: Could not match supplied host pattern, ignoring: overcloud Running the same with the ansible 2.3 works Trying to figure out now what is wrong with the current inventory Verified with openstack-tripleo-validations-7.4.2-1.el7ost.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462 |