Wednesday, 2018-06-06

*** weshay_ has joined #openstack-mistral00:28
*** weshay has quit IRC00:32
*** weshay has joined #openstack-mistral00:43
*** weshay_ has quit IRC00:44
*** harlowja has quit IRC01:10
*** threestrands_ has joined #openstack-mistral01:33
*** threestrands has quit IRC01:36
*** nguyenhai93 has quit IRC01:47
*** nguyenhai93 has joined #openstack-mistral01:48
openstackgerritBob Haddleton proposed openstack/mistral master: Update default Docker configuration and documentation  https://review.openstack.org/57266403:10
*** rbrady has quit IRC04:00
*** harlowja has joined #openstack-mistral04:17
*** hardikjasani has joined #openstack-mistral04:20
*** harlowja has quit IRC04:45
*** jaosorior has joined #openstack-mistral05:52
*** jaosorior has quit IRC06:47
*** gkadam has joined #openstack-mistral07:18
*** openstackgerrit has quit IRC07:19
*** jpich has joined #openstack-mistral07:55
*** threestrands_ has quit IRC08:03
*** shardy has joined #openstack-mistral08:05
*** lxkong has quit IRC08:29
*** gkadam has quit IRC09:25
*** openstackgerrit has joined #openstack-mistral09:40
openstackgerritchenge proposed openstack/mistral master: Amend the spelling error of a word  https://review.openstack.org/57271409:40
*** jaosorior has joined #openstack-mistral10:08
*** lxkong has joined #openstack-mistral10:45
*** thrash|g0ne is now known as thrash11:20
opetrenko_Well then, I want to crate workflow that can get alarm, reboot instance then check if instance finished rebooting and regarding if state is still EROR rebuild instance or not. Need some help to create that workflow. Little bit of idea there http://paste.openstack.org/show/722791/11:23
openstackgerritBrad P. Crochet proposed openstack/mistral master: Use trusts by default in OpenStack action calls  https://review.openstack.org/57244811:25
opetrenko_d0ugal: can you help with that?11:32
*** gkadam has joined #openstack-mistral11:49
d0ugalopetrenko_: Which bit do you need help with?12:19
d0ugalopetrenko_: In some of the TripleO workflows we wait for Heat stacks to reach a state12:20
d0ugalYou can probably use a similar approach to wait for the instance to come online12:20
d0ugalhttps://github.com/openstack/tripleo-common/blob/master/workbooks/stack.yaml#L69-L8012:20
d0ugalso you will want to wait for the instance state and then either finish or start the rebuild12:20
d0ugalDoes that make sense?12:21
opetrenko_I need a help with checking state of instance12:23
*** AlexeyAbashkin has joined #openstack-mistral12:29
*** shardy has quit IRC12:39
*** shardy has joined #openstack-mistral12:43
*** jaosorior has quit IRC13:20
*** hardikjasani has quit IRC13:20
d0ugalopetrenko_: right, I am not very familiar with the nova actions, but I guess you can use nova.server_get and then the response will have the status. You can then use on-complete to change the behaviour depending on the contents of the result13:41
d0ugalfor example...13:41
d0ugalhttps://github.com/openstack/tripleo-common/blob/master/workbooks/baremetal.yaml#L218-L22013:43
d0ugalThat is actually on-success, you probably want that rather than on-complete13:43
d0ugalbut that calls two different tasks based on YAQL expression. You can do something similar but with the result of the task13:44
d0ugalI would use "mistral run-action nova.servers_get '{...input...}' to see what the result looks like.13:44
d0ugalopetrenko_: ^13:44
d0ugalhope that helps!13:44
*** Alexey_Abashkin has joined #openstack-mistral13:51
*** AlexeyAbashkin has quit IRC13:53
*** Alexey_Abashkin is now known as AlexeyAbashkin13:53
opetrenko_Got a question14:04
opetrenko_how can I extract OS-EXT-STS:vm_state from result of nova.servers_get14:05
d0ugalopetrenko_: I don't know exactly what the result of nova.servers_get looks like, can you show me an example? but I suspect it will be something like  <% task().result.vm_state %>14:06
opetrenko_http://paste.openstack.org/show/722805/14:08
opetrenko_the problem is that OS:vm_state: value needed14:13
opetrenko_but there is 2 :14:13
openstackgerritBrad P. Crochet proposed openstack/mistral master: Register the collect_timing keystone_authtoken option  https://review.openstack.org/57278814:19
*** AlexeyAbashkin has quit IRC14:28
d0ugalopenstackgerrit: task().result.get("OS-EXT-STS:vm_state")14:29
d0ugaloops14:29
d0ugalopetrenko_: task().result.get("OS-EXT-STS:vm_state")14:29
opetrenko_oh, thx14:29
*** AlexeyAbashkin has joined #openstack-mistral14:36
therved0ugal: Hey have you seen http://paste.openstack.org/show/722743/ wrt the resolve_outputs stuff?14:46
*** shardy has quit IRC14:47
*** shardy has joined #openstack-mistral14:47
d0ugaltherve: I only spotted that apetrich tried it with no luck14:50
d0ugalbut I have not had a chance to try again today14:50
therveOk double checking would be cool14:51
therveAt least I don't have another idea for now :)14:51
d0ugalRight14:51
d0ugalI'll see what I can do14:51
therveAt it seems to make sense to me why that happens too14:51
therveThough, we probably need to work around it in tripleo-common14:51
therveWhich I can do if you want14:51
openstackgerritBrad P. Crochet proposed openstack/python-mistralclient master: Revert "Adding environment-get-definition for easy environment-update"  https://review.openstack.org/57211115:01
openstackgerritBrad P. Crochet proposed openstack/python-mistralclient master: Add --export option to environment-get  https://review.openstack.org/57279915:01
openstackgerritBrad P. Crochet proposed openstack/mistral master: Register the collect_timing keystone_authtoken option  https://review.openstack.org/57278815:08
*** lxkong has quit IRC15:12
*** AlexeyAbashkin has quit IRC15:14
*** AlexeyAbashkin has joined #openstack-mistral15:16
openstackgerritBrad P. Crochet proposed openstack/mistral master: Register the collect_timing keystone_authtoken option  https://review.openstack.org/57278815:16
d0ugaltherve: sure, if you have time that would be great. I am juggling a bunch of things this week.15:17
therveCool will do15:17
d0ugalapetrich: it is mistralclient tempest tests that are failing15:19
d0ugalapetrich: not mistral-tempest-plugin15:19
d0ugal... or I am going crazy15:20
d0ugalapetrich: http://logs.openstack.org/36/572136/1/check/python-mistralclient-devstack-dsvm/088fa08/job-output.txt.gz#_2018-06-04_16_18_35_64902115:20
d0ugalpgaxatte: Just trying to figure out how we fix your patch ^15:20
d0ugaloh and some of these failures are the collect_timing bug thrash is working on15:21
apetrichI was talking about this http://logs.openstack.org/36/572136/1/check/python-mistralclient-devstack-dsvm/088fa08/job-output.txt.gz#_2018-06-04_16_18_35_89096915:21
apetrichd0ugal, ^^15:21
pgaxatted0ugal: oh I did not see the error :)15:22
apetrichbut yeah they are mistralclient15:22
d0ugalapetrich: right, but that is still in mistralclient15:22
d0ugalapetrich: so we probably need a different fix15:22
apetrichthat's what I was thinking15:22
d0ugalpgaxatte: np15:22
pgaxatted0ugal, I don't get how this small patch can generate these strange errors15:24
d0ugalpgaxatte: yeah, it can be pretty confusing :)15:25
d0ugalapetrich: so I think we just need --force here? https://github.com/openstack/python-mistralclient/blob/master/mistralclient/tests/functional/cli/v2/base_v2.py#L155-L16015:25
d0ugalapetrich: but I don't understand how that passed previously...15:25
apetrichme neither15:26
apetricha try except there15:26
d0ugal:)15:27
d0ugaltry/except everywhere!15:27
d0ugalpgaxatte: Are you happy for me to update your patch?15:29
pgaxatted0ugal sure go ahead15:29
openstackgerritDougal Matthews proposed openstack/python-mistralclient master: Fix force parameter being always added to URL in execution delete  https://review.openstack.org/57213615:34
pgaxatted0ugal, sounds good to me. any idea why the test needs --force?15:36
openstackgerritAdriano Petrich proposed openstack/mistral master: Make cron-triggers not play catchup  https://review.openstack.org/57281315:37
apetrichpgaxatte, they just deleted any executions after the test no matter what. just cleaning15:38
apetrichpgaxatte, is not the tests but the clean up after a test that needs force now15:38
d0ugalpgaxatte: The tests user mistral master, mistral master requires that --force is used when deleting running executions (it is unsafe).15:38
d0ugalbut given that it is only testing code we don't mind that it is unsafe15:38
d0ugalbut yeah, as apetrich said it is just the cleanup code15:39
d0ugalI am not 100% this will fix it, we will see in the CI results in a bit.15:39
pgaxatteapetrich: ok but before the implementation of the --force, the running workflows were not cleaned?15:40
d0ugalpgaxatte: they were cleaned, but --force wasn't required.15:41
d0ugalSorry, it is a bit confusing :)15:41
pgaxatted0ugal I say this should do the trick since the force flag was always set :)15:41
d0ugalpgaxatte: hopefully15:42
apetrichdeleting running executions is unsafe. if you do you might see a storm of errors in the logs of objects being referenced that no longer exits15:42
d0ugalpgaxatte: just to clarify...15:42
apetrichthe --force was created to limit those errors to the times that you are ok with that15:42
d0ugalpgaxatte: mistral execution-delete UUID <- this command worked on any execution up until queens. However, it was unsafe to delete a running execution (you should stop it first). To stop users making that mistake we required they pass --force (a bit like git push --force is dangerous).15:43
apetrichwe don't care much what happens the env during tests after the test has run. so it was deleting all kinds of executions and that was fine15:43
pgaxatteok so if I understand correctly the old behavior was to not care whether or not the workflows you delete were still running or not?15:43
d0ugalpgaxatte: correct15:43
d0ugalpgaxatte: and now with rocky (git master) we care if the execution is still running15:43
d0ugaland the mistake we made was to release it in mistralclient so it works with master but not with queens15:44
pgaxatteok thanks for the explanations!15:44
*** jpich has quit IRC15:44
d0ugalnp15:45
pgaxattehopefully some people are stuck in ancient release, like me :D15:45
d0ugalhaha, I'm sure many people are15:45
d0ugalbut I guess they don't usually have an old API and the newest client :)15:45
d0ugalbut I am glad somebody is testing us!15:45
d0ugalI wonder if we could have a mistralclient CI job to test against the most recent stable Mistral15:46
d0ugalapetrich, thrash: ^ how hard would that be? :)15:46
pgaxatteI'm happy to report this15:46
pgaxattebtw I have a subject of discussion for you guys but it's gonna wait tomorrow because I gotta go home :)15:49
d0ugalPhew, my brain is fried.15:49
pgaxattebye!15:49
d0ugalcta15:49
d0ugaloops15:50
d0ugalcya15:50
d0ugalProof of a tired brain ^15:50
*** shardy has quit IRC16:03
*** shardy has joined #openstack-mistral16:04
*** gkadam has quit IRC16:15
*** apetrich has quit IRC16:34
*** apetrich has joined #openstack-mistral16:35
thrashd0ugal: probably not too difficult...16:47
*** AlexeyAbashkin has quit IRC16:57
*** shardy has quit IRC17:13
openstackgerritDoug Hellmann proposed openstack/mistral-lib master: fix tox python3 overrides  https://review.openstack.org/57290919:27
*** toure is now known as toure|gone21:56
*** lxkong has joined #openstack-mistral22:01
openstackgerritBrad P. Crochet proposed openstack/python-mistralclient master: Add --export to get commands and deprecate get-definition  https://review.openstack.org/57302022:05
*** threestrands has joined #openstack-mistral22:51

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