Monday, 2017-08-21

*** catintheroof has quit IRC00:33
openstackgerritMerged openstack/mistral master: Updated from global requirements  https://review.openstack.org/49482801:08
*** bobh has joined #openstack-mistral01:27
*** bobh has quit IRC01:32
*** zhurong has joined #openstack-mistral01:34
*** bobh has joined #openstack-mistral02:28
*** bobh has quit IRC02:32
*** zhurong has quit IRC02:34
kongd0ugal: i have approved that patch, feel free to backport to pike before end of this month, so I can propose a rc2 for mistral02:38
*** bobh has joined #openstack-mistral02:50
*** Dinesh_Bhor has joined #openstack-mistral03:45
*** bobh has quit IRC03:46
*** gkadam has joined #openstack-mistral03:51
*** bobh has joined #openstack-mistral03:54
*** bobh has quit IRC04:01
*** shardy has quit IRC04:06
openstackgerritMerged openstack/mistral master: Fix cron keystone calls when token is available  https://review.openstack.org/49355004:12
*** shardy has joined #openstack-mistral04:13
*** ying_zuo has joined #openstack-mistral05:04
*** jaosorior has joined #openstack-mistral06:16
*** jtomasek has joined #openstack-mistral06:20
*** sharatss has joined #openstack-mistral06:52
*** ddeja has joined #openstack-mistral07:12
*** jpich has joined #openstack-mistral07:32
*** shardy has quit IRC07:49
*** shardy has joined #openstack-mistral07:49
d0ugalkong: thanks!08:17
*** nkoffman has joined #openstack-mistral09:33
*** xavierhardy has joined #openstack-mistral10:04
*** Qiming has quit IRC10:04
*** Qiming has joined #openstack-mistral10:09
*** nkoffman has quit IRC10:36
*** nkoffman has joined #openstack-mistral10:39
*** jkilpatr has quit IRC10:41
*** shardy has quit IRC10:41
*** shardy has joined #openstack-mistral10:41
*** shardy has quit IRC10:50
*** shardy has joined #openstack-mistral10:51
*** jkilpatr has joined #openstack-mistral11:01
*** thrash|g0ne is now known as thrash11:15
*** openstackgerrit has quit IRC11:17
*** dprince has joined #openstack-mistral11:57
*** dprince has quit IRC12:00
*** dprince has joined #openstack-mistral12:00
*** jpich has quit IRC12:03
*** jpich has joined #openstack-mistral12:26
xavierhardyHi everyone12:29
xavierhardyI had a question about the code design of Mistral12:30
xavierhardyhere is the thing12:30
xavierhardyI would like to receive notifications from Mistral on workflow execution/action execution/task execution state update12:30
xavierhardyon an external API12:31
xavierhardyIs there any kind of listeners on the execution states ?12:31
xavierhardyrakhmerov, d0ugal?12:33
apetrichxavierhardy, I think you can half cook that with cron triggers and the ansible playbook12:34
xavierhardythe ansible playbook?12:34
apetrichnot an ideal situation12:34
xavierhardyIt's not notification if I have to actively contact the API for that.12:35
apetrichI mean workbook. you can call a ansible playbook that can do whatever12:35
apetrichI knwo12:35
apetrichknow12:35
apetrichnot ideal as I said12:35
xavierhardyThe 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
xavierhardyI 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
xavierhardyAnd 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 IRC12:41
*** dprince has quit IRC12:51
*** oidgar has joined #openstack-mistral12:54
oidgarhi, I'm having problems with mistral action "heat.stacks_get", I wonder if someone here can assist12:54
oidgarhttp://paste.openstack.org/show/618905/12:54
oidgarin tripleo we have a workflow which call in loop to this action in order to wait synchronously for a stack while running12:55
oidgarbut it seems that sometimes calling to heat.stacks_get get failed although the stack still running/exists12:56
*** sharatss has quit IRC13:24
*** bobh has joined #openstack-mistral13:28
*** dprince has joined #openstack-mistral13:32
*** nkoffman has quit IRC13:37
d0ugaloidgar: sure, I can help14:00
d0ugaloidgar: just going into a short meeting, so give me 10-1514:00
oidgarthanks :)14:32
d0ugaloidgar: looking at your paste now.14:35
d0ugaloidgar: Have you checked the Heat logs?14:36
d0ugaloidgar: or can you get the full traceback from the Mistral executor logs?14:38
d0ugaloidgar: 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
oidgard0ugal: how do I check the mistral executor logs?14:44
d0ugaloidgar: /var/log/mistral/executor.log14:44
oidgard0ugal: don't have much experience with mistral yet14:44
d0ugalnp14:44
oidgar:)14:44
oidgard0ugal: checking14:45
oidgard0ugal: I'm pasting the error messages regarding this action call. will send in a minute14:51
d0ugalcool14:51
d0ugalI am finding it very hard to parse the actual error message you are getting14:52
d0ugalERROR: Error in KeystoneBase output role_data: No function \"#operator_+\" matches supplied arguments"14:52
oidgarthat's the output I got by running the command. hope that the log messages will help more14:52
*** livelace has joined #openstack-mistral14:54
d0ugalYeah, they should have the full Python traceback14:55
oidgard0ugal: http://paste.openstack.org/show/618926/14:55
oidgard0ugal: hope you'll understand more from that output14:55
d0ugaloidgar: Line 2414:59
d0ugaloidgar: the error is coming from heatclient14:59
d0ugaloidgar: so to track this down, I think you'll need to look at the Heat logs14:59
d0ugal(and/or get some help from somebody more familiar with Heat)15:00
oidgarno problem... will check it15:00
oidgarhave to go to a meeting, I'll investigate after and will update... hope you'll be here :)15:00
*** oidgar has quit IRC15:01
d0ugalMistral meeting in #openstack-meeting-315:01
d0ugalthrash: ^15:02
d0ugalrbrady: ^15:02
livelaceHello everybody. Could anybody help with https://paste.fedoraproject.org/paste/KKvvejGLXrb3m30sn5Bucw ?15:09
*** openstackgerrit has joined #openstack-mistral15:11
openstackgerritMerged openstack/mistral-lib master: Updated from global requirements  https://review.openstack.org/49518715:11
rbradylivelace: what exactly would you like help with?15:13
openstackgerritMerged openstack/mistral-dashboard master: Updated from global requirements  https://review.openstack.org/49518615:16
livelacerbrady, I need to know, is it normal situation or not ?15:17
livelaceI have the failed "stop_all" task with an error: State info    | Failed by tasks: [u'task1', u'task2']15:17
d0ugalI don't really understand the example in the paste - it would be easier if there was a complete workflow we could try15:18
livelaceI read documentation and I expected that "stop_all" will be executed normally15:18
livelace"task1" and "task2" have parents, which were failed15:19
d0ugalWhat do you mean by parents?15:19
livelaceparents tasks15:19
livelacewhich execute task1 and task2 on-success15:20
livelace... task1 and task2 never will be started, but there is the task "stop_all" which waits task1/task2 completion15:21
thrashlivelace: can you show the parent task?15:21
livelacethrash, https://paste.fedoraproject.org/paste/LSDAA68e5Lp28rOmmYTCrQ15: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
livelaceIs 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 IRC15:43
*** oidgar_ has joined #openstack-mistral15:43
oidgar_d0ugal: still here?15:43
*** fultonj has joined #openstack-mistral15:44
*** fultonj has quit IRC15:45
thrashlivelace: 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
livelacethrash, I need to understand what I do and not trying check all variants15:56
oidgar_d0ugal: heat_api.log (relevant lines): https://paste.fedoraproject.org/paste/2SM0BG5Dd1gMANXO0AHApQ/15:57
thrashlivelace: let me see if I can reproduce this...15:57
livelaceI this case the question is simple - does "join" works for not started tasks15:57
thrashlivelace: well, no. If they aren't started, there is nothing to join.15:57
*** vishwanathj has joined #openstack-mistral15:58
oidgar_d0ugal: heat-engine.log (relevant lines): https://paste.fedoraproject.org/paste/WB5FDbNwFiIR2nXX0EgpTg/15:59
livelacethrash, 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
thrashlivelace: I don't understand that question tbh... I don't see where stop_all is in an on-error16:00
livelace<livelace> I have the failed "stop_all" task with an error: State info    | Failed by tasks: [u'task1', u'task2']16:02
livelaceIf "stop_all" starts its work with its action - it is Ok16:03
livelaceBut "stop_all" starts its work with just "on-error"16:03
livelacetask1/task2 failed -> stop_all/on-error16:04
thrashlivelace: 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
livelaceOk16:05
*** dprince has joined #openstack-mistral16:14
*** oidgar_ has quit IRC16:17
*** FL1SK has quit IRC16:20
*** ddeja has quit IRC16:20
*** ddeja has joined #openstack-mistral16:23
*** jpich has quit IRC16:48
*** livelace has quit IRC16:50
*** shardy has quit IRC17:07
*** livelace has joined #openstack-mistral17:28
*** harlowja has joined #openstack-mistral17:29
livelacetherve_, Take a look - https://paste.fedoraproject.org/paste/-YUE1iqyh8ypLarNs0BqVQ17:31
livelacetherve_, Sorry17:31
livelacethrash, Take a look https://paste.fedoraproject.org/paste/-YUE1iqyh8ypLarNs0BqVQ17:31
livelacethrash, And workflow itself - https://paste.fedoraproject.org/paste/H1FDGmfCGQwByrH-pmFB4A17:32
livelaceAll tasks were finished with success, but "join" just works with "on-error"17:33
thrashlivelace: ok... let me see what it does on my end.17:38
livelacethrash, If you remove "on-error" section from "task1" (which "fails") - all works as expected, but "task1" doesn't handle error situation17:58
thrashlivelace: ok... I will look at that17:59
*** livelace has quit IRC18:25
*** FL1SK has joined #openstack-mistral18:32
*** catintheroof has joined #openstack-mistral18:32
*** catintheroof has quit IRC19:17
*** jtomasek has quit IRC19:21
*** jtomasek has joined #openstack-mistral19:31
*** vishwanathj has quit IRC19:35
*** vishwanathj has joined #openstack-mistral19:39
*** zhenguo has quit IRC19:44
*** zhenguo has joined #openstack-mistral19:47
*** jtomasek has quit IRC19:58
*** thrash is now known as thrash|bbl20:17
*** jkilpatr has quit IRC20:35
*** dprince has quit IRC21:40
*** jkilpatr has joined #openstack-mistral21:53
*** thrash|bbl is now known as thrash22:04
*** bobh has quit IRC22:22
*** bobh has joined #openstack-mistral23:28
*** catintheroof has joined #openstack-mistral23:29
*** bobh has quit IRC23:56
*** bobh has joined #openstack-mistral23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!