Zaqar can't trigger Mistral workflow.

asked 2019-04-03 03:20:06 -0500

anonymous user

Anonymous

Good day, everyone!

I am new to OpenStack and I've had an issue for days now which is most likely related to Zaqar(maybe).
My setup is single-node which was installed using Packstack, Queens version.

I wanted to confirm auto-healing process using this template:
https://github.com/openstack/heat-templates/blob/master/hot/autohealing/autohealing_server.yaml (https://github.com/openstack/heat-tem...)

EXPECTED OUTPUT WHEN THE SERVER IS STOPPED
1. Stop event alarm is triggered.
2. The workflow resource is executed.
3. The stopped server is replaced with a working and active server.

ACTUAL OUTPUT
1. Stop event alarm is triggered.
2. The workflow resource was not executed.
3. The stopped server is still in SHUTOFF state and was not replaced.

Zaqar installation:
https://docs.openstack.org/zaqar/queens/install/install-rdo.html (https://docs.openstack.org/zaqar/quee...)
-- instead of using zaqar.uwsgi.service for the zaqar service, we used the zaqar-server command.

[root@localhost scaling(keystone_admin)]# lsof -i:8888
COMMAND   PID USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME
python  34685 root    7u  IPv4 97847527      0t0  TCP localhost:ddi-tcp-1 (LISTEN)
[root@localhost scaling(keystone_admin)]# openstack endpoint list | grep zaqar
WARNING: Failed to import plugin clustering.
| 31aeffd2897648fea515c5f17d4e6f49 | RegionOne | zaqar        | messaging         | True    | public    | http://192.168.6.4:8888                       |
| 54ce5b9c431e4366852c7452b945d6f9 | RegionOne | zaqar        | messaging         | True    | admin     | http://192.168.6.4:8888                       |
| 88830aef7b8642389628f50f18ff1008 | RegionOne | zaqar        | messaging         | True    | internal  | http://192.168.6.4:8888                       |
[root@localhost scaling(keystone_admin)]# ps aux | grep zaqar
root     34685  0.1  0.0 827892 69456 pts/6    Sl   Apr02   1:38 /usr/bin/python /usr/bin/zaqar-server --config-file /etc/zaqar/zaqar.conf --nodaemon --debug
root     57096  0.0  0.0 112712   976 pts/1    S+   14:13   0:00 grep --color=auto zaqar

Console logs:
http://s000.tinyupload.com/?file_id=47283324564197836687 (http://s000.tinyupload.com/?file_id=4...)

What's the reason why the MistralTrigger resource won't trigger the workflow even if a message was received in the queue? Could this be a config-related issue? I haven't seen any error in the log files (aodh, mistral, heat, zaqar) that indicates a failed process. I can provide OpenStack services' logs if needed.

edit retag flag offensive close merge delete

Comments

Looks like the issue is somewhere between the Zaqar queue and the Mistral workflow execution. It's not clear whether the Zaqar notification is failing to fire or if Mistral is failing to receive it, but those would be the places to start debugging.

zaneb gravatar imagezaneb ( 2019-04-09 15:33:10 -0500 )edit