Description of problem: openstack overcloud deploy fails due to incompatible mistral versions between the director and the tripleo container. Version-Release number of selected component (if applicable): RHOS 14 z2 stream. openstack-tripleo-common v9.5.0 How reproducible: Always Steps to Reproduce: 1. deploy overcloud from the z2 stream Actual results: ``` Removing the current plan files Uploading new plan files {u'result': u'Failed to run task [error=Invalid input [name=tripleo.parameters.update, class=tripleo_common.actions.parameters.UpdateParametersAction, unexpected=[u'validate']], wf=tripleo.swift_backup.v1.create_swift_backup_container_plan, task=set_put_tempurl]: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mistral/engine/task_handler.py", line 63, in run_task task.run() File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 159, in wrapper result = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/mistral/engine/tasks.py", line 431, in run self._run_new() File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 159, in wrapper result = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/mistral/engine/tasks.py", line 460, in _run_new self._schedule_actions() File "/usr/lib/python2.7/site-packages/mistral/engine/tasks.py", line 529, in _schedule_actions action.validate_input(input_dict) File "/usr/lib/python2.7/site-packages/mistral/engine/actions.py", line 336, in validate_input self.action_def.action_class File "/usr/lib/python2.7/site-packages/mistral/engine/utils.py", line 66, in validate_input raise exc.InputException(msg % tuple(msg_props)) InputException: Invalid input [name=tripleo.parameters.update, class=tripleo_common.actions.parameters.UpdateParametersAction, unexpected=[u'validate']] ``` Expected results: Overcloud deploys without errors. Additional info: The z1 stream is not impacted by this issue at the time of reporting. This issue seems to be fixed in a newer upstream release: https://bugs.launchpad.net/tripleo/+bug/1818926 Please let me know if I should provide further info, such as deployment parameters and templates.
It is unclear whether a backport of that change would help, or if Alex's comment[1] applies to this environment [1] https://bugs.launchpad.net/tripleo/+bug/1818926/comments/6
We need the rpm versions from the host and the rpm versions from the mistral containers. Please provide the output of "rpm -qa | grep tripleo" and a "docker exec -it mistral_engine rpm -qa | grep tripleo". Also can you provide the version information for the containers running on the undercloud?
$ rpm -qa | grep tripleo openstack-tripleo-image-elements-9.0.1-0.20181102144447.9f1c800.el7ost.noarch python-tripleoclient-10.6.1-0.20190117233304.e780899.el7ost.noarch openstack-tripleo-heat-templates-9.3.1-0.20190314162756.d0a6cb1.el7ost.noarch openstack-tripleo-puppet-elements-9.0.1-1.el7ost.noarch puppet-tripleo-9.4.0-0.20190307172344.b5220a7.el7ost.noarch openstack-tripleo-validations-9.3.1-0.20190119052820.f400181.el7ost.noarch python2-tripleo-common-9.5.0-1.el7ost.noarch ansible-tripleo-ipsec-9.1.0-1.el7ost.noarch ansible-role-tripleo-modify-image-1.0.1-0.20190226052419.9014df9.el7ost.noarch openstack-tripleo-common-containers-9.5.0-1.el7ost.noarch python-tripleoclient-heat-installer-10.6.1-0.20190117233304.e780899.el7ost.noarch openstack-tripleo-common-9.5.0-1.el7ost.noarch $ docker exec -it mistral_engine rpm -qa | grep tripleo ansible-role-tripleo-modify-image-1.0.1-0.20181011160036.48a56c1.el7ost.noarch ansible-tripleo-ipsec-9.0.1-0.20181012162415.8b37e93.el7ost.noarch openstack-tripleo-common-containers-9.4.1-0.20190119050432.261de49.el7ost.noarch openstack-tripleo-common-9.4.1-0.20190119050432.261de49.el7ost.noarch python2-tripleo-common-9.4.1-0.20190119050432.261de49.el7ost.noarch openstack-tripleo-common-container-base-9.4.1-0.20190119050432.261de49.el7ost.noarch puppet-tripleo-9.3.1-0.20190119004939.e8adf4b.el7ost.noarch Docker image versions (from registry.access.stage.redhat.com): Name Version Tag rhosp14/openstack-nova-compute-ironic 14.0-108 039578804f25 rhosp14/openstack-mistral-executor 14.0-110 233240ab8147 rhosp14/openstack-neutron-server 14.0-98 b8a6d5e76978 rhosp14/openstack-mistral-api 14.0-104 9ca6c52cf64b rhosp14/openstack-nova-api 14.0-107 4d7d86bd6604 rhosp14/openstack-neutron-l3-agent 14.0-98 d53aa96d81c5 rhosp14/openstack-nova-placement-api 14.0-104 e065a1e2d6d2 rhosp14/openstack-neutron-openvswitch-agent 14.0-100 725a5634d45f rhosp14/openstack-swift-object 14.0-104 a47cca77c502 rhosp14/openstack-ironic-conductor 14.0-102 2dba0d36d553 rhosp14/openstack-nova-scheduler 14.0-107 ccbb3a00f92a rhosp14/openstack-keystone 14.0-100 a9ae0a531c3a rhosp14/openstack-swift-proxy-server 14.0-105 22b09618bf72 rhosp14/openstack-neutron-dhcp-agent 14.0-98 21fbe16ebd81 rhosp14/openstack-glance-api 14.0-106 1877d5d754f1 rhosp14/openstack-mistral-engine 14.0-103 0ecc7a764d9c rhosp14/openstack-heat-engine 14.0-98 0e15fd4cbb56 rhosp14/openstack-swift-account 14.0-105 7fce67320677 rhosp14/openstack-ironic-pxe 14.0-100 f6c6ca4e8e4f rhosp14/openstack-swift-container 14.0-105 e03b979b7d53 rhosp14/openstack-heat-api 14.0-98 958f9f3be236 rhosp14/openstack-heat-api-cfn 14.0-97 7783468d16a2 rhosp14/openstack-ironic-api 14.0-99 e143f3ceffd3 rhosp14/openstack-ironic-neutron-agent 14.0-70 b74f32d00233 rhosp14/openstack-nova-conductor 14.0-107 90b77c851a99 rhosp14/openstack-mistral-event-engine 14.0-105 d8f5b09801bd rhosp14/openstack-ironic-inspector 14.0-105 f9aca4e81ec7 rhosp14/openstack-zaqar 14.0-109 91f380845ad7 rhosp14/openstack-tripleo-ui 14.0-84 9f974beb1330 rhosp14/openstack-tempest 14.0-110 e595af7c70b4 rhosp14/openstack-cron 14.0-137 a6f8d1d6f6fe rhosp14/openstack-iscsid 14.0-136 a3f376aa1ba1 rhosp14/openstack-rabbitmq 14.0-134 583640909c07 rhosp14/openstack-memcached 14.0-134 dfa9dcd6b7b7 rhosp14/openstack-mariadb 14.0-136 706788084842
So yea the issue is using pre-production rpms with released containers. You need to use the containers with the same versions.
*** Bug 1705694 has been marked as a duplicate of this bug. ***