08:00:01 #startmeeting mistral 08:00:02 Meeting started Fri Jun 8 08:00:01 2018 UTC and is due to finish in 60 minutes. The chair is d0ugal. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:06 The meeting name has been set to 'mistral' 08:00:16 Who is around for the Mistral office hour today? https://etherpad.openstack.org/p/mistral-office-hours 08:00:42 rakhmerov, apetrich, bobh, mcdoker181818 ^ 08:01:12 As usual, add your IRC nick to line 16 in the etherpad if you want a reminder ping in the future! 08:03:42 I am going to be proposing the Rocky Milestone 2 releases today. 08:10:19 and by today, I mean "now" :) 08:10:30 https://review.openstack.org/573610 08:27:26 d0ugal: Is it a good time to chat about https://review.openstack.org/572807 ? 08:27:44 therve: Sure 08:28:02 I'm just doing milestone 2 administrivia 08:28:17 d0ugal: https://review.openstack.org/573306 I think is the fix, hopefully that'll be confirmed 08:28:31 But it requires a heatclient release, so I was wondering if we can find a workaround 08:29:00 Right 08:29:06 Do we know where it is called from? 08:29:45 Yes, serialization code 08:30:21 That is what I suspected. Got a link to relevant line handy? 08:30:51 Hum I don't have the full traceback anymore 08:31:29 https://github.com/openstack/mistral/blob/master/mistral/serialization.py#L106 was the one in mistral I remember 08:31:34 Then it got in jsonutils 08:32:20 Right 08:32:35 therve: I guess a workaround would be for the mistral actions to set loaded=True? 08:33:23 d0ugal: Hum maybe. Just the get_stack one though 08:33:39 Right 08:33:51 It would be a fairly nasty hack, but I don't have any other immediate ideas 08:34:16 d0ugal: So there is no way in the workflow to operate on the result of the action before it's serialized? 08:34:59 therve: No, I don't think so 08:35:24 Right 08:35:38 In which case the client release is probably the best way then 08:36:40 Yeah 08:36:54 I guess my work around in the workflow would be good enough for now? 08:37:14 Until the release I mean 08:37:19 I guess 08:37:25 It doesn't prevent the double request 08:37:41 Well, it means we have one slow inefficient request :) 08:38:40 but it does mean we store that output in the action execution table in mistral. 08:47:46 Merged openstack/mistral-extra master: fix tox python3 overrides https://review.openstack.org/572969 08:52:37 Merged openstack/mistral-dashboard master: fix tox python3 overrides https://review.openstack.org/572968 09:01:10 #endmeeting