*** catintheroof has quit IRC | 00:33 | |
openstackgerrit | Merged openstack/mistral master: Updated from global requirements https://review.openstack.org/494828 | 01:08 |
---|---|---|
*** bobh has joined #openstack-mistral | 01:27 | |
*** bobh has quit IRC | 01:32 | |
*** zhurong has joined #openstack-mistral | 01:34 | |
*** bobh has joined #openstack-mistral | 02:28 | |
*** bobh has quit IRC | 02:32 | |
*** zhurong has quit IRC | 02:34 | |
kong | d0ugal: i have approved that patch, feel free to backport to pike before end of this month, so I can propose a rc2 for mistral | 02:38 |
*** bobh has joined #openstack-mistral | 02:50 | |
*** Dinesh_Bhor has joined #openstack-mistral | 03:45 | |
*** bobh has quit IRC | 03:46 | |
*** gkadam has joined #openstack-mistral | 03:51 | |
*** bobh has joined #openstack-mistral | 03:54 | |
*** bobh has quit IRC | 04:01 | |
*** shardy has quit IRC | 04:06 | |
openstackgerrit | Merged openstack/mistral master: Fix cron keystone calls when token is available https://review.openstack.org/493550 | 04:12 |
*** shardy has joined #openstack-mistral | 04:13 | |
*** ying_zuo has joined #openstack-mistral | 05:04 | |
*** jaosorior has joined #openstack-mistral | 06:16 | |
*** jtomasek has joined #openstack-mistral | 06:20 | |
*** sharatss has joined #openstack-mistral | 06:52 | |
*** ddeja has joined #openstack-mistral | 07:12 | |
*** jpich has joined #openstack-mistral | 07:32 | |
*** shardy has quit IRC | 07:49 | |
*** shardy has joined #openstack-mistral | 07:49 | |
d0ugal | kong: thanks! | 08:17 |
*** nkoffman has joined #openstack-mistral | 09:33 | |
*** xavierhardy has joined #openstack-mistral | 10:04 | |
*** Qiming has quit IRC | 10:04 | |
*** Qiming has joined #openstack-mistral | 10:09 | |
*** nkoffman has quit IRC | 10:36 | |
*** nkoffman has joined #openstack-mistral | 10:39 | |
*** jkilpatr has quit IRC | 10:41 | |
*** shardy has quit IRC | 10:41 | |
*** shardy has joined #openstack-mistral | 10:41 | |
*** shardy has quit IRC | 10:50 | |
*** shardy has joined #openstack-mistral | 10:51 | |
*** jkilpatr has joined #openstack-mistral | 11:01 | |
*** thrash|g0ne is now known as thrash | 11:15 | |
*** openstackgerrit has quit IRC | 11:17 | |
*** dprince has joined #openstack-mistral | 11:57 | |
*** dprince has quit IRC | 12:00 | |
*** dprince has joined #openstack-mistral | 12:00 | |
*** jpich has quit IRC | 12:03 | |
*** jpich has joined #openstack-mistral | 12:26 | |
xavierhardy | Hi everyone | 12:29 |
xavierhardy | I had a question about the code design of Mistral | 12:30 |
xavierhardy | here is the thing | 12:30 |
xavierhardy | I would like to receive notifications from Mistral on workflow execution/action execution/task execution state update | 12:30 |
xavierhardy | on an external API | 12:31 |
xavierhardy | Is there any kind of listeners on the execution states ? | 12:31 |
xavierhardy | rakhmerov, d0ugal? | 12:33 |
apetrich | xavierhardy, I think you can half cook that with cron triggers and the ansible playbook | 12:34 |
xavierhardy | the ansible playbook? | 12:34 |
apetrich | not an ideal situation | 12:34 |
xavierhardy | It's not notification if I have to actively contact the API for that. | 12:35 |
apetrich | I mean workbook. you can call a ansible playbook that can do whatever | 12:35 |
apetrich | I knwo | 12:35 |
apetrich | know | 12:35 |
apetrich | not ideal as I said | 12:35 |
xavierhardy | The problem I see is that the notifications will not only come from the Mistral "server" instance since the other instances can update the DB as well. | 12:36 |
xavierhardy | I could add a SQLAlchemy hook (on update/insert) to do that, but it's better if it's already implemented in Mistral's core code. | 12:36 |
xavierhardy | And I would need to import the hook code at some point, I'm not sure how to do that without impacting Mistral's core code (which I don't want since I want to be able to upgrade easily) | 12:38 |
*** gkadam has quit IRC | 12:41 | |
*** dprince has quit IRC | 12:51 | |
*** oidgar has joined #openstack-mistral | 12:54 | |
oidgar | hi, I'm having problems with mistral action "heat.stacks_get", I wonder if someone here can assist | 12:54 |
oidgar | http://paste.openstack.org/show/618905/ | 12:54 |
oidgar | in tripleo we have a workflow which call in loop to this action in order to wait synchronously for a stack while running | 12:55 |
oidgar | but it seems that sometimes calling to heat.stacks_get get failed although the stack still running/exists | 12:56 |
*** sharatss has quit IRC | 13:24 | |
*** bobh has joined #openstack-mistral | 13:28 | |
*** dprince has joined #openstack-mistral | 13:32 | |
*** nkoffman has quit IRC | 13:37 | |
d0ugal | oidgar: sure, I can help | 14:00 |
d0ugal | oidgar: just going into a short meeting, so give me 10-15 | 14:00 |
oidgar | thanks :) | 14:32 |
d0ugal | oidgar: looking at your paste now. | 14:35 |
d0ugal | oidgar: Have you checked the Heat logs? | 14:36 |
d0ugal | oidgar: or can you get the full traceback from the Mistral executor logs? | 14:38 |
d0ugal | oidgar: I am trying to determine if the error is coming from Heat and being passed along or if the error is in Mistral. | 14:38 |
oidgar | d0ugal: how do I check the mistral executor logs? | 14:44 |
d0ugal | oidgar: /var/log/mistral/executor.log | 14:44 |
oidgar | d0ugal: don't have much experience with mistral yet | 14:44 |
d0ugal | np | 14:44 |
oidgar | :) | 14:44 |
oidgar | d0ugal: checking | 14:45 |
oidgar | d0ugal: I'm pasting the error messages regarding this action call. will send in a minute | 14:51 |
d0ugal | cool | 14:51 |
d0ugal | I am finding it very hard to parse the actual error message you are getting | 14:52 |
d0ugal | ERROR: Error in KeystoneBase output role_data: No function \"#operator_+\" matches supplied arguments" | 14:52 |
oidgar | that's the output I got by running the command. hope that the log messages will help more | 14:52 |
*** livelace has joined #openstack-mistral | 14:54 | |
d0ugal | Yeah, they should have the full Python traceback | 14:55 |
oidgar | d0ugal: http://paste.openstack.org/show/618926/ | 14:55 |
oidgar | d0ugal: hope you'll understand more from that output | 14:55 |
d0ugal | oidgar: Line 24 | 14:59 |
d0ugal | oidgar: the error is coming from heatclient | 14:59 |
d0ugal | oidgar: so to track this down, I think you'll need to look at the Heat logs | 14:59 |
d0ugal | (and/or get some help from somebody more familiar with Heat) | 15:00 |
oidgar | no problem... will check it | 15:00 |
oidgar | have to go to a meeting, I'll investigate after and will update... hope you'll be here :) | 15:00 |
*** oidgar has quit IRC | 15:01 | |
d0ugal | Mistral meeting in #openstack-meeting-3 | 15:01 |
d0ugal | thrash: ^ | 15:02 |
d0ugal | rbrady: ^ | 15:02 |
livelace | Hello everybody. Could anybody help with https://paste.fedoraproject.org/paste/KKvvejGLXrb3m30sn5Bucw ? | 15:09 |
*** openstackgerrit has joined #openstack-mistral | 15:11 | |
openstackgerrit | Merged openstack/mistral-lib master: Updated from global requirements https://review.openstack.org/495187 | 15:11 |
rbrady | livelace: what exactly would you like help with? | 15:13 |
openstackgerrit | Merged openstack/mistral-dashboard master: Updated from global requirements https://review.openstack.org/495186 | 15:16 |
livelace | rbrady, I need to know, is it normal situation or not ? | 15:17 |
livelace | I have the failed "stop_all" task with an error: State info | Failed by tasks: [u'task1', u'task2'] | 15:17 |
d0ugal | I don't really understand the example in the paste - it would be easier if there was a complete workflow we could try | 15:18 |
livelace | I read documentation and I expected that "stop_all" will be executed normally | 15:18 |
livelace | "task1" and "task2" have parents, which were failed | 15:19 |
d0ugal | What do you mean by parents? | 15:19 |
livelace | parents tasks | 15:19 |
livelace | which execute task1 and task2 on-success | 15:20 |
livelace | ... task1 and task2 never will be started, but there is the task "stop_all" which waits task1/task2 completion | 15:21 |
thrash | livelace: can you show the parent task? | 15:21 |
livelace | thrash, https://paste.fedoraproject.org/paste/LSDAA68e5Lp28rOmmYTCrQ | 15:28 |
livelace | "When a task has property “join” assigned with value “all” the task will run only if all upstream tasks (ones that lead to this task) are completed and corresponding conditions have triggered." | 15:31 |
livelace | Is it mean that "task1" and "task2" must be started and ended with any "success|error|complete" for "stop_all" start normally ? | 15:34 |
*** dprince has quit IRC | 15:43 | |
*** oidgar_ has joined #openstack-mistral | 15:43 | |
oidgar_ | d0ugal: still here? | 15:43 |
*** fultonj has joined #openstack-mistral | 15:44 | |
*** fultonj has quit IRC | 15:45 | |
thrash | livelace: have you tried using 'on-error' instead of on-complete in parent1? When parent1 and parent2 succeed, is the behavior what you expect? | 15:54 |
livelace | thrash, I need to understand what I do and not trying check all variants | 15:56 |
oidgar_ | d0ugal: heat_api.log (relevant lines): https://paste.fedoraproject.org/paste/2SM0BG5Dd1gMANXO0AHApQ/ | 15:57 |
thrash | livelace: let me see if I can reproduce this... | 15:57 |
livelace | I this case the question is simple - does "join" works for not started tasks | 15:57 |
thrash | livelace: well, no. If they aren't started, there is nothing to join. | 15:57 |
*** vishwanathj has joined #openstack-mistral | 15:58 | |
oidgar_ | d0ugal: heat-engine.log (relevant lines): https://paste.fedoraproject.org/paste/WB5FDbNwFiIR2nXX0EgpTg/ | 15:59 |
livelace | thrash, Ok, suppose it is, but why "stop_all" was started with "on-error" ? Ok, "join" is not working, why you start with "on-error" ? | 16:00 |
thrash | livelace: I don't understand that question tbh... I don't see where stop_all is in an on-error | 16:00 |
livelace | <livelace> I have the failed "stop_all" task with an error: State info | Failed by tasks: [u'task1', u'task2'] | 16:02 |
livelace | If "stop_all" starts its work with its action - it is Ok | 16:03 |
livelace | But "stop_all" starts its work with just "on-error" | 16:03 |
livelace | task1/task2 failed -> stop_all/on-error | 16:04 |
thrash | livelace: a full workflow that we can drop into an environment would go a long way in helping here. what you have pasted so far is not a usable workflow. | 16:04 |
livelace | Ok | 16:05 |
*** dprince has joined #openstack-mistral | 16:14 | |
*** oidgar_ has quit IRC | 16:17 | |
*** FL1SK has quit IRC | 16:20 | |
*** ddeja has quit IRC | 16:20 | |
*** ddeja has joined #openstack-mistral | 16:23 | |
*** jpich has quit IRC | 16:48 | |
*** livelace has quit IRC | 16:50 | |
*** shardy has quit IRC | 17:07 | |
*** livelace has joined #openstack-mistral | 17:28 | |
*** harlowja has joined #openstack-mistral | 17:29 | |
livelace | therve_, Take a look - https://paste.fedoraproject.org/paste/-YUE1iqyh8ypLarNs0BqVQ | 17:31 |
livelace | therve_, Sorry | 17:31 |
livelace | thrash, Take a look https://paste.fedoraproject.org/paste/-YUE1iqyh8ypLarNs0BqVQ | 17:31 |
livelace | thrash, And workflow itself - https://paste.fedoraproject.org/paste/H1FDGmfCGQwByrH-pmFB4A | 17:32 |
livelace | All tasks were finished with success, but "join" just works with "on-error" | 17:33 |
thrash | livelace: ok... let me see what it does on my end. | 17:38 |
livelace | thrash, If you remove "on-error" section from "task1" (which "fails") - all works as expected, but "task1" doesn't handle error situation | 17:58 |
thrash | livelace: ok... I will look at that | 17:59 |
*** livelace has quit IRC | 18:25 | |
*** FL1SK has joined #openstack-mistral | 18:32 | |
*** catintheroof has joined #openstack-mistral | 18:32 | |
*** catintheroof has quit IRC | 19:17 | |
*** jtomasek has quit IRC | 19:21 | |
*** jtomasek has joined #openstack-mistral | 19:31 | |
*** vishwanathj has quit IRC | 19:35 | |
*** vishwanathj has joined #openstack-mistral | 19:39 | |
*** zhenguo has quit IRC | 19:44 | |
*** zhenguo has joined #openstack-mistral | 19:47 | |
*** jtomasek has quit IRC | 19:58 | |
*** thrash is now known as thrash|bbl | 20:17 | |
*** jkilpatr has quit IRC | 20:35 | |
*** dprince has quit IRC | 21:40 | |
*** jkilpatr has joined #openstack-mistral | 21:53 | |
*** thrash|bbl is now known as thrash | 22:04 | |
*** bobh has quit IRC | 22:22 | |
*** bobh has joined #openstack-mistral | 23:28 | |
*** catintheroof has joined #openstack-mistral | 23:29 | |
*** bobh has quit IRC | 23:56 | |
*** bobh has joined #openstack-mistral | 23:59 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!