Created attachment 1357058 [details] /var/log/mistral/mistral-db-manage.log Description of problem: I've a lot of error similar to this ones in my mistral log then I prepare the overcloud. 2017-11-20 17:54:34.933 25939 INFO mistral.actions.openstack.action_generator.base [-] Processing OpenStack action mapping from file: /usr/lib/python2.7/site-packages/mistral/actions/openstack/mapping.json 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base [-] Failed to create action: nova.floating_ips_list: AttributeError: 'Client' object has no attribute 'floating_ips' 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base Traceback (most recent call last): 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base File "/usr/lib/python2.7/site-packages/mistral/actions/openstack/action_generator/base.py", line 143, in create_actions 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base client_method = class_.get_fake_client_method() 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base File "/usr/lib/python2.7/site-packages/mistral/actions/openstack/base.py", line 75, in get_fake_client_method 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base return cls._get_client_method(cls._get_fake_client()) 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base File "/usr/lib/python2.7/site-packages/mistral/actions/openstack/base.py", line 59, in _get_client_method 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base attribute = getattr(attribute, attr) 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base AttributeError: 'Client' object has no attribute 'floating_ips' 2017-11-20 17:54:34.954 25939 ERROR mistral.actions.openstack.action_generator.base 2017-11-20 17:54:34.960 25939 ERROR mistral.actions.openstack.action_generator.base [-] Failed to create action: nova.security_groups_delete: AttributeError: 'Client' object has no attribute 'security_groups' 2017-11-20 17:54:34.960 25939 ERROR mistral.actions.openstack.action_generator.base Traceback (most recent call last): 2017-11-20 17:54:34.960 25939 ERROR mistral.actions.openstack.action_generator.base File "/usr/lib/python2.7/site-packages/mistral/actions/openstack/action_generator/base.py", line 143, in create_actions 2017-11-20 17:54:34.960 25939 ERROR mistral.actions.openstack.action_generator.base client_method = class_.get_fake_client_method() 2017-11-20 17:54:34.960 25939 ERROR mistral.actions.openstack.action_generator.base File "/usr/lib/python2.7/site-packages/mistral/actions/openstack/base.py", line 75, in get_fake_client_method 2017-11-20 17:54:34.960 25939 ERROR mistral.actions.openstack.action_generator.base return cls._get_client_method(cls._get_fake_client()) 2017-11-20 17:54:34.960 25939 ERROR mistral.actions.openstack.action_generator.base File "/usr/lib/python2.7/site-packages/mistral/actions/openstack/base.py", line 59, in _get_client_method 2017-11-20 17:54:34.960 25939 ERROR mistral.actions.openstack.action_generator.base attribute = getattr(attribute, attr) 2017-11-20 17:54:34.960 25939 ERROR mistral.actions.openstack.action_generator.base AttributeError: 'Client' object has no attribute 'security_groups' Version-Release number of selected component (if applicable): Puddle: 20171116.1
reproduced with puddle 2017-11-20.1.
The issue is still present with the last puddle. python-mistral-lib-0.3.1-1.el7ost.noarch python-mistral-lib-tests-0.3.1-1.el7ost.noarch puppet-mistral-11.3.0-2.el7ost.noarch openstack-mistral-engine-5.2.0-1.el7ost.noarch python-mistral-5.2.0-1.el7ost.noarch python-mistralclient-3.1.3-2.el7ost.noarch openstack-mistral-common-5.2.0-1.el7ost.noarch openstack-mistral-api-5.2.0-1.el7ost.noarch python-mistral-tests-5.2.0-1.el7ost.noarch openstack-mistral-executor-5.2.0-1.el7ost.noarch
these are still the latest packages, so moving back to assigned
This has not been backported to Pike. I will see if that is a possibility.
Hi Gonéri, at what stage exactly do these errors appear? Is it when you install the undercloud or when you do some other preparation? Please specify the exact sequence and commands used, thanks.
Udi, I don't have the exact command sequence but this would have been visible in the mistral-db-manage.log after the undercloud install has been completed.
Created attachment 1510814 [details] Mistral errors "Failed to create action" There is still an endless list of "failed to create action" mistral errors. See attached log file with the errors. openstack-mistral-common-5.2.3-1.el7ost.noarch puppet-mistral-11.4.0-2.el7ost.noarch python-mistralclient-3.1.4-1.el7ost.noarch openstack-mistral-engine-5.2.3-1.el7ost.noarch python-mistral-5.2.3-1.el7ost.noarch openstack-mistral-executor-5.2.3-1.el7ost.noarch openstack-mistral-api-5.2.3-1.el7ost.noarch python-mistral-lib-0.3.3-1.el7ost.noarch
Failed, see comment #18.
(In reply to Udi from comment #18) > Created attachment 1510814 [details] > Mistral errors "Failed to create action" > > There is still an endless list of "failed to create action" mistral errors. > See attached log file with the errors. Yes, this is expected and "by design", admittedly a bad design. For example, I see lots of muranoclient errors. This is just because we don't include Murano or Murano client. Essentially if there is a client that Mistral uses for actions but the client isn't present there will be errors creating actions with that client. This isn't something we should spend time on unless we want to support every client that Mistral supports. We could improve how Mistral outputs this information to make it clearer. That would be the most sensible fix.