Hide Forgot
Description of problem: ----------------------- Attempt to run minor update fails. openstack overcloud update stack 2>&1 Waiting for messages on queue 'c4880dcf-96a9-4fb4-b41b-fb6b615d9063' with no timeout. Started Mistral Workflow tripleo.package_update.v1.update_nodes. Execution ID: b8ac5f1b-26ce-445d-ba69-597bbb0b356a None In /var/log/mistral/executor.log we can see: -------------------------------------------- ... 2017-10-20 09:21:30.449 15158 INFO mistral.actions.std_actions [req-b07e855d-bfd6-4f56-8086-f74aabddea8a fa8565196ca24c5d93b8bdbab7d046b5 0e181e596fae4866926197e50f751e0b - default default] Running no-op action 2017-10-20 09:21:30.627 15158 INFO mistral.executors.executor_server [req-2a429919-b123-4781-922f-ef643f1953c8 fa8565196ca24c5d93b8bdbab7d046b5 0e181e596fae4866926197e50f751e0b - default default] Received RPC re quest 'run_action'[action_ex_id=4b91e6d7-cb02-49f3-97ff-ef15fdd2308c, action_cls_str=mistral.actions.openstack.actions.ZaqarAction, action_cls_attrs={u'client_method_name': u'queue_post'}, params={queue_name: eb d73dd0-24f8-4e9c-a9d1-4c2a56e1201d, messages: {u'body': {u'type': u'tripleo.package_update.v1.update_nodes', u'payload': {u'status': u'SUCCESS', u'message': {u'stderr': u'\nPLAY [overcloud] ********************* ******************************************\nskipping: no hosts matched\n\nPLAY RECAP *********************************************************************\n\n', u'stdout': u"[DEPRECATION WARNING]: The use of 'in clude' for tasks has been deprecated. Use \n'import_tasks' for static inclusions or 'include_tasks' for dynamic inclusions.\n This feature will be removed in a future release. Deprecation warnings can be \ndisab led by setting deprecation_warnings=False in ansible.cfg.\n Version-Release number of selected component (if applicable): -------------------------------------------------------------- openstack-mistral-api-5.1.1-0.20171013201429.f9129b7.el7ost.noarch python-mistral-lib-0.3.0-0.20171011162405.9c2d6d9.el7ost.noarch python-mistralclient-3.1.3-0.20170915002443.c33d39c.el7ost.noarch python-mistral-5.1.1-0.20171013201429.f9129b7.el7ost.noarch openstack-mistral-engine-5.1.1-0.20171013201429.f9129b7.el7ost.noarch openstack-mistral-executor-5.1.1-0.20171013201429.f9129b7.el7ost.noarch puppet-mistral-11.3.1-0.20170825184651.cf2e493.el7ost.noarch openstack-mistral-common-5.1.1-0.20171013201429.f9129b7.el7ost.noarch Steps to Reproduce: ------------------- 1. Update uc to build 2017-10-16.2 2. Apply patches: https://review.openstack.org/#/c/487488 https://review.openstack.org/#/c/513701 https://review.openstack.org/#/c/509718 https://review.openstack.org/#/c/510970 3. Update workbooks mistral workbook-update /usr/share/tripleo-common/workbooks/access.yaml mistral workbook-update /usr/share/tripleo-common/workbooks/ceph-ansible.yaml mistral workbook-update /usr/share/tripleo-common/workbooks/fernet-key-rotate.yaml mistral workbook-update /usr/share/tripleo-common/workbooks/package_update.yaml 4. Update heat outputs openstack overcloud update stack --init-minor-update --container-registry-file docker-images.yaml 5. Try to perform minor update openstack overcloud update stack Additional info: ---------------- Virtual env: 3controllers + 2computes + 3ceph
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