Description of problem: The tripleo.validations.v1.list action results in an empty list in a containerized undercloud, instead of producing the list of validations. The openstack-tripleo-validations package seems to be installed on the undercloud itself, but not in any of the mistral containers. When the action is called via openstack action execution create, log entries related to the call are created in the mistral containers. Version-Release number of selected component (if applicable): Rocky latest master How reproducible: 100% Steps to Reproduce: 1. Install upstream master 2. Call openstack action execution run tripleo.validations.v1.list 3. Actual results: {"result": []} Expected results: The result list should contain validations Additional info:
They are also missing from the UI.
To clarify: This BZ tracks both the broken listing of the validations as well as broken validation executions via mistral.
*** Bug 1636747 has been marked as a duplicate of this bug. ***
I ran "openstack action execution run tripleo.validations.v1.list" and got: Failed to find action [action_name=tripleo.validations.v1.list] Should the correct command be "openstack action execution run tripleo.validations.list_validations"? Is there a difference?
(In reply to Udi from comment #9) > I ran "openstack action execution run tripleo.validations.v1.list" and got: > Failed to find action [action_name=tripleo.validations.v1.list] > > Should the correct command be "openstack action execution run > tripleo.validations.list_validations"? Is there a difference? You can either use the workflow (and then poll the result) by using: openstack workflow execution create tripleo.validations.v1.list Or us the action using: openstack action execution run tripleo.validations.list_validations The latter one is a littler handier.
Verified: openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.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-2019:0045