"Register mistral actions" fails on `staging-unstable`. about ansible-st2

[dzimine]

Took a closer look:

1. this seems wrong as it marks the file regardless of exit code /success/failure of the mistral script https://github.com/StackStorm/ansible-st2/blame/master/roles/st2mistral/tasks/main.yml#L77

2. The mistral script that registers the action and the three types of actions are bundled together: mistral standard actions (we need them), stevedore plugins (our st2mistral action is the one, so we need it) and openstack actions (we don't need it). It is the openstack actions that we don't need, and any bug with them and their dependent libraries puts us at risk.

If this place where openstack actions are loaded is made optional via arguments?

[dzimine]

Works fine with st2_pkg_repo: stable. Makes me say "we must CI unstable".

[arm4b]

@dzimine This is fresh st2mistral bug which as I understand appeared after synchronizing https://github.com/StackStorm/mistral with recent upstream mistral.

@m4dcoder knows the details, there is a hack as temporary workaround: StackStorm/st2-packages#411

[arm4b]

After it happens, re-running the playbook skips the Register mistral actions step.

And yes, this is wrong behavior. Re-running playbook should try to register mistral actions again if they failed before. Will fix it.

---

Talking about upstream mistral bug, I'll wait for a while and if there won't be any better solution instead of StackStorm/st2-packages#411, - I'll include same changes @m4dcoder applied for st2-packages curl|bash install script.

[arm4b]

Ansible re-run behavior is fixed #105.

Re-opening to keep this issue with upstream mistral bug and StackStorm/st2-packages#411 in mind (decide: wait for upstream changes or use that hotfix).

[arm4b]

Fixed by #109

Proposal to include unstable repo in the build matrix is implemented in #110