Thursday, 2017-08-10

*** tzumainn has joined #openstack-mistral00:31
*** rbrady has joined #openstack-mistral00:34
*** rbrady has quit IRC00:34
*** rbrady has joined #openstack-mistral00:34
*** tzumainn has quit IRC00:47
*** bobh has joined #openstack-mistral01:02
*** jkilpatr has quit IRC01:04
*** bobh has quit IRC01:35
*** rbrady has quit IRC01:39
*** gongysh has joined #openstack-mistral01:46
*** zhurong has joined #openstack-mistral02:51
*** gkadam has joined #openstack-mistral03:41
*** gongysh has quit IRC04:30
*** gongysh has joined #openstack-mistral05:09
rakhmerovapetrich: the main point of Mistral cron is that it's distributed, no single point of failure (kind of)05:10
rakhmerovunlike regular cron05:10
apetrichrakhmerov, neat. I took a wee look at it yesterday afternoon to familiarize myself with it05:11
rakhmerovbobh: yes, you're right. It's a limitation. I'm actually looking forward to see our action subsystem refactored seriously and that work is going on but not as fast as we want05:12
rakhmerovthis obviously can be a good enhancement, I agree05:13
rakhmerovbobh: can you please file a BP (or bug) at launchpad?05:13
rakhmerovapetrich: ok :)05:13
*** shardy has joined #openstack-mistral07:09
d0ugalbtw, the issue yesterday, I was hitting was https://review.openstack.org/49204607:57
rakhmerovd0ugal: yeah, I thought it could be it07:59
d0ugalouch, the gate queue is huge08:33
*** jtomasek has joined #openstack-mistral08:35
*** jaosorior has quit IRC08:37
openstackgerritMerged openstack/python-mistralclient master: Task list now only queries the displayed fields.  https://review.openstack.org/49178008:38
*** nmakhotkin has joined #openstack-mistral08:38
nmakhotkinhi there!08:38
*** jtomasek has quit IRC08:39
*** jaosorior has joined #openstack-mistral08:41
*** jtomasek has joined #openstack-mistral08:47
rakhmerovnmakhotkin: welcome back to our IRC! :)08:48
rakhmerovd0ugal: the check queue is now pretty big08:49
rakhmerovgate seems to be fine now08:49
rakhmerovooh, no, I guess they both have problems..08:49
*** jaosorior has quit IRC08:54
*** gongysh has quit IRC09:19
nmakhotkingate queue is really big09:32
*** gongysh has joined #openstack-mistral09:37
*** jaosorior has joined #openstack-mistral09:54
*** shardy has quit IRC10:08
*** shardy has joined #openstack-mistral10:11
*** zhurong has quit IRC10:39
*** jkilpatr has joined #openstack-mistral10:59
*** gongysh has quit IRC11:01
*** rbrady has joined #openstack-mistral11:35
*** gkadam has quit IRC11:52
*** jtomasek has quit IRC12:05
*** katkapilatova has joined #openstack-mistral12:13
*** shardy has quit IRC12:23
*** shardy has joined #openstack-mistral12:25
*** rbrady has quit IRC12:29
katkapilatovahello everyone, I am trying to create a simple trigger - in this case, one that would print once per minute a list of nova flavors on the output.12:33
katkapilatovaBut what I found out was that both "*/1 * * * *" and "36 * * * *" (I wanted to check whether my syntax in "once per minute" isn't causing the issue) patterns, I encountered a strange behaviour. The trigger was created fine and I could get information about it.12:33
katkapilatovaBut once it got executed, the next estimated time started continually moving further to the past. For instance, in case of the "once per minute" trigger, the "next execution time" moved approximately 2 hours back into the past whenever I prompted for info about the trigger (say every second or two).12:33
katkapilatovaI used openstack client commands for it and my openstack-mistral version is 4.0.1 .12:33
katkapilatovaHowever, there's more. When I asked dmatthews about this, he found out that recent changes in mistral master don't enable him to create a trigger at all.12:33
d0ugaltoure|gone: ^ did you look at the cron triggers at all?12:34
d0ugalI think toure will be around soon.12:34
d0ugalrakhmerov: ^ this is the other cron problem I was trying to figure out.12:35
*** catintheroof has joined #openstack-mistral12:45
*** jrist has joined #openstack-mistral12:58
*** katkapilatova_ has joined #openstack-mistral13:15
*** katkapilatova has quit IRC13:16
*** katkapilatova_ is now known as katkapilatova13:16
*** katkapilatova1 has joined #openstack-mistral13:17
*** katkapilatova1 has quit IRC13:18
*** katkapilatova1 has joined #openstack-mistral13:20
*** toure|gone is now known as toure13:22
*** katkapilatova1 has quit IRC13:23
*** bobh has joined #openstack-mistral13:24
*** katkapilatova1 has joined #openstack-mistral13:29
toured0ugal still looking at it13:31
d0ugaltoure: k, thanks - let katkapilatova know if you have any ideas.13:59
*** katkapilatova1 has quit IRC14:00
*** katkapilatova has left #openstack-mistral14:00
*** katkapilatova has joined #openstack-mistral14:01
toured0ugal will do...I think I have a hint, just trying to prove it14:01
*** gongysh has joined #openstack-mistral14:02
*** gongysh has quit IRC14:03
d0ugalkatkapilatova: did you check for errors in the engine log?14:04
katkapilatova"Forbidden: You are not authorized to perform the requested action: Using trust-scoped token to create another token. Create a new trust-scoped token instead. (HTTP 403) (Request-ID: req-74c2c4e0-8ce9-4dcc-8c01-60f33e5182ff)"14:07
d0ugalhmm, interesting. That actually sounds similar to the error I was hitting.14:07
katkapilatovadOugal: last 50 lines from the log http://pastebin.test.redhat.com/50748114:08
katkapilatovait's interesting that you cannot even create the trigger while I can though14:09
d0ugalkatkapilatova: no, I can create the trigger - it just never executes14:09
katkapilatovaoh, then it might be the same...upon first execution, it does this to me14:09
d0ugalkatkapilatova: I have this in the api log. http://paste.openstack.org/show/618050/14:12
d0ugalI thought it would be fixed by this: https://review.openstack.org/#/c/492046/14:12
d0ugalbut I think I have that patch applied...14:12
katkapilatovaonce shadower is back, I can tell him to try it on his devbox14:15
d0ugalkatkapilatova: sounds good.14:15
d0ugalnmakhotkin: I just commented on https://review.openstack.org/#/c/492046/14:16
d0ugalnmakhotkin: I get a different error with cron triggers.14:16
d0ugalkatkapilatova: sorry about this, this bit should have been easy!14:16
katkapilatovaoh, ye that's different14:16
d0ugalbetween you, me and nmakhotkin we have three different errors, but they all seem to be related to authentication.14:18
katkapilatova:D14:19
toured0ugal so my cron-trigger is running correctly14:19
katkapilatovait's good that it seems to be connected to a specific area14:19
*** katkapilatova has left #openstack-mistral14:20
*** jkilpatr has quit IRC14:20
*** jkilpatr has joined #openstack-mistral14:20
toured0ugal did it take time to hit the error?14:21
d0ugaltoure: damn, lucky you!14:21
tourehahahaa14:21
d0ugaltoure: nah, it was very quick14:21
toureso I have a glance image list running every 2 mins14:21
toureso far it has been triggered correctly everytime14:22
nmakhotkind0ugal: yes, it seems like it depends on exact configuration14:22
nmakhotkinand your error means that you probably have more than needed in config14:23
d0ugaloh14:23
d0ugalI'll check...14:23
nmakhotkinbut I'm not so sure14:23
nmakhotkinkatkapilatova: Did you use trust-scoped token to create cron-trigger ?14:23
toured0ugal can I see the workflow you are running?14:23
toureI want to load it on my server and run it14:24
nmakhotkinI just tested cron-triggers with my patch, so usual(not trust-scoped) token should work fine14:24
d0ugaltoure: I just have a test workflow that does nothing. so that wont be very useful14:25
d0ugalnmakhotkin: k, thanks. I'll take a look at the config, I'm not sure what is in it :)14:25
toureack14:26
d0ugaltoure: it just has one action that is std.noop :)14:26
tourecool14:26
toured0ugal what I will do, is load another trigger and keep the current one running14:26
nmakhotkind0ugal: but again, this issue needs to be fixed too :)14:27
nmakhotkind0ugal: I'd like to fix this but next 3 weeks I'll be on the vacation14:27
d0ugalno problem :)14:28
d0ugalI'll see if I can figure it out14:28
nmakhotkinok :)14:28
*** katkapilatova has joined #openstack-mistral14:29
openstackgerritMerged openstack/python-mistralclient master: Use keystoneauth plugins and session instead of keystoneclient  https://review.openstack.org/45517414:59
*** nmakhotkin has quit IRC16:43
*** shardy has quit IRC17:38
*** apetrich has quit IRC18:10
*** apetrich has joined #openstack-mistral18:13
*** portdirect is now known as eteppete19:02
*** openstackgerrit has quit IRC19:03
*** eteppete is now known as portdirect19:03
*** portdirect has quit IRC19:17
*** portdirect has joined #openstack-mistral19:17
*** jrist has quit IRC19:48
*** brunograz has quit IRC19:50
*** brunograz1 has joined #openstack-mistral19:50
*** apetrich has quit IRC19:54
*** apetrich has joined #openstack-mistral19:55
*** brunograz1 has quit IRC20:07
*** brunograz has joined #openstack-mistral20:08
*** jkilpatr has quit IRC20:11
*** jkilpatr has joined #openstack-mistral21:00
*** openstackgerrit has joined #openstack-mistral21:05
openstackgerritMerged openstack/mistral master: [Triggers] Fix running openstack actions via triggers  https://review.openstack.org/49204621:05
openstackgerritMerged openstack/mistral master: Move dsl_v2 document to user guide  https://review.openstack.org/49083821:05
openstackgerritMerged openstack/mistral master: Add doc8 rule and check doc/source files  https://review.openstack.org/49204921:06
openstackgerritMerged openstack/mistral master: Fix the pep8 commands failed  https://review.openstack.org/48763721:06
*** rbrady has joined #openstack-mistral21:43
*** bobh has quit IRC21:47
*** bobh has joined #openstack-mistral21:48
*** bobh has quit IRC21:53
*** openstackgerrit has quit IRC22:18
*** catintheroof has quit IRC22:45
*** catintheroof has joined #openstack-mistral22:45
*** catintheroof has quit IRC22:49
kongrakhmerov: have we merged all patches we need for pike? If we release rc1 and create a stable branch based on that, only critical bugfix could be backported23:39
kongI can see there may be 2 candidates for pike, https://review.openstack.org/#/c/484986/ and https://review.openstack.org/#/c/490063/23:39
kongI can wait for the first one, but the latter one will need d0ugal to propose another patchset to fix the gate failure23:41
kongd0ugal: are you around?23:41
*** tung_doan has quit IRC23:52

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