mistral run-action nova.servers_get <input> -> succeeded
mistral run-action nova.servers_stop <input> -> succeeded
But if run action nova.servers_stop inside workflow, strange error occurs:
# mistral task-get 84e5860d-9522-4c0f-8d1a-a95da2c58fe6
+---------------+----------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+---------------+----------------------------------------------------------------------------------------------------------------------------+
| ID | 84e5860d-9522-4c0f-8d1a-a95da2c58fe6 |
| Name | task1 |
| Workflow name | test |
| Execution ID | 1e347de0-e19d-4d42-b213-83fd8250f4d6 |
| State | ERROR |
| State info | Failed to run action [action_ex_id=9d5825c4-f9ef-443f-8b04-f74f9e514c47, action_cls='<class |
| | 'mistral.actions.action_factory.NovaAction'>', attributes='{u'client_method_name': u'servers.stop'}', params='{u'server': |
| | u'98ce6169-1de9-487e-876b-04a09c70f056'}'] |
| | NovaAction.servers.stop failed: <class 'keystoneauth1.exceptions.discovery.DiscoveryFailure'>: Could not determine a |
| | suitable URL for the plugin |
+---------------+----------------------------------------------------------------------------------------------------------------------------+
Whereas nova.servers_get works well inside workflow.
Need to go deeper and inspect the problem.
P.S. This action inside workflow worked well on stable/mitaka.
Solved by adding
auth_version = v3
in [keystone_ authtoken] config section.
But it means that different mechanisms are used for separate actions and workflow actions. Need to standartize them.