Thursday, 2019-11-21

openstackgerritVlad Gusev proposed openstack/mistral stable/stein: Fix error validate token when run cron trigger  https://review.opendev.org/69533201:06
openstackgerritVlad Gusev proposed openstack/mistral stable/stein: Add release note for fix error of cron trigger run  https://review.opendev.org/69533301:07
*** ricolin has joined #openstack-mistral01:55
*** apetrich has quit IRC03:08
rakhmerovd0ugal: hey06:25
rakhmerovjust noticed your ping06:25
openstackgerritMerged openstack/mistral stable/stein: Fix error validate token when run cron trigger  https://review.opendev.org/69533207:24
openstackgerritMerged openstack/mistral stable/stein: Add release note for fix error of cron trigger run  https://review.opendev.org/69533307:24
rakhmerovd0ugal: I approved everything I could submitted by yourself07:27
*** apetrich has joined #openstack-mistral07:34
*** pgaxatte has joined #openstack-mistral07:44
d0ugalrakhmerov: Great, thanks08:40
d0ugalrakhmerov: I was going to ask for help debbung the CI faiures. I really don't know where to start with it08:40
d0ugalbut maybe we just need to leave it non-voting? There isn't much happening in Rocky now.08:41
d0ugalrakhmerov: Did you see Jean's question on https://review.opendev.org/#/c/694781/ ?08:47
d0ugalI guess he didn't understand why the other patches were backported. Should it be a feature release?08:47
rakhmerovno, I didn't see that question08:56
rakhmerovwill have a look a bit later today..08:56
rakhmerovd0ugal: I replied to it09:00
rakhmerovyeah, it's kind of my fault but I didn't think it would be an issue09:01
d0ugalrakhmerov: no problem, I guess he was just curious09:04
openstackgerritMerged openstack/mistral stable/rocky: Make the mistral devstack jobs non-voting in Rocky  https://review.opendev.org/69524009:16
openstackgerritMerged openstack/mistral stable/rocky: Mask sensitive data when logging action results  https://review.opendev.org/69473309:16
*** ricolin has quit IRC09:22
openstackgerritDougal Matthews proposed openstack/mistral master: Remove the TripleO standalone job  https://review.opendev.org/69537809:29
rakhmerovd0ugal: I quickly glanced at those failures in Rocky, they actually look like some logical problems either with the tests or some relevant changes09:30
rakhmerovDetails: {'debuginfo': None, 'faultstring': "Invalid input [name=wf1, class=ReverseWorkflowSpec, missing=['farewell']]", 'faultcode': 'Client'}09:31
rakhmerova missing input parameter09:31
rakhmerovvery weird09:31
d0ugalrakhmerov: I tried to look and the code looks fine09:31
d0ugalThey also all passed at least once09:32
rakhmerovhm..09:32
rakhmerovwell, rocky is pretty old, I remember we had lots of issues with ordering etc. leading to race conditions09:32
d0ugalYeah, I remember that too. I forget how it was fixed :)09:33
rakhmerovbut I'm just surprised with a missing parameter, it doesn't look like falling into that category of issues09:33
d0ugalAgreed09:34
d0ugalMaybe the workflow name is reused and sometimes it has the parameter and sometimes it doesn't?09:35
rakhmerovyeah.. it is possible actually!09:36
rakhmerovyeah, maybe something is wrong with clean up09:37
rakhmerovd0ugal: I'm looking at https://review.opendev.org/#/c/695378/109:37
rakhmerovhow come that this job wasn't used? I'm not sure I understand your commit message09:37
rakhmerovthe "...standalone" job that we always see wasn't take from what you removed?09:38
d0ugalrakhmerov: there are two TripleO jobs, one of them doesn't use Mistral09:38
d0ugaloh wait09:38
d0ugalrakhmerov: it is the one I removed, look at the diff09:38
d0ugalit has "-standalone" at the end09:38
d0ugalSorry, I am used to TripleO devs just referring to it as "standalone"09:38
rakhmerovyes, I understand..09:38
rakhmerovso you're stating that it never used Mistral?09:39
d0ugalCorrect09:39
d0ugalthe other tripleo job does use Mistral09:39
rakhmerovoooh damn...09:39
rakhmerovreally? )09:39
d0ugalYeah, I don't know how I didn't notice this before09:39
rakhmerovwe've been running it for years )09:39
d0ugalI know :/09:39
rakhmerovok09:39
d0ugalMaybe it did a long time ago, but I forget09:39
rakhmerovit's good though that you finally noticed that )09:40
rakhmerovI'd never do09:40
d0ugalhaha true09:40
rakhmerovthanks anyway09:40
d0ugalIt does install Mistral, but doesn't use it. If you look at the link in the commit message you can see there are no action execution logs09:40
d0ugalwell, other than the startup and some debug logs09:40
rakhmerovyeah, ok09:40
d0ugalno executor logs I mean :)09:40
rakhmerovgot it09:40
rakhmerovone day I believe I need to learn how that all works, haha )09:41
d0ugalI hate to think how many hours of CI we have wasted there09:41
rakhmerovyeah09:41
d0ugalrakhmerov: well, we are removing Mistral from TripleO actually. So you might not want to bother learning...09:41
rakhmerovand how that increased the bills for electricity somewhere in a DC :)09:41
rakhmerovd0ugal: woow, really?09:42
rakhmerovcan you tell more?09:42
d0ugalrakhmerov: Sure, basically we are replacing it with Ansible09:42
d0ugalThere is a effort in tripleo to make things easier and simpler09:42
d0ugalThis is part of that09:42
rakhmerovAnsible Tower or just core Ansible?09:43
d0ugalJust core ansible, but it does mean that we can maybe use Tower/AWX in the future.09:43
rakhmerovaah, ok09:43
rakhmerovhopefully the TripleO members understand that these two things are not interchangeable09:44
d0ugalIndeed09:44
d0ugalbut we never really took advantage of all the features in Mistral.09:45
rakhmerovfor our use cases though it may be fine, I realised so far that you use Mistral in a pretty limited way09:45
rakhmerovyeah09:45
rakhmerovI actually expected that to happen pretty soon, so ok09:45
rakhmerovthanks for letting me know09:45
d0ugalno problem09:45
rakhmerovso when do you think we can remove the TripleO jobs then completely? :)09:46
d0ugalrakhmerov: I guess it will take some time, and we still have some people running Newton (!) so we will have some connection to Mistral for some time09:46
rakhmerovhow long may it last?09:46
rakhmerovthis transition09:46
rakhmerovok09:46
d0ugalrakhmerov: Good question. I don't know really, we have lots to do. Maybe by the end of V?09:46
d0ugalNewton was our first release that included Mistral btw09:47
rakhmerovyes :)09:48
rakhmerovok09:48
d0ugalI think our biggest problem was the development workflow with Mistral. Writing workflows and actions. Updating the workbooks, installing the actions, restarting mistral etc.09:49
d0ugalIt was very painful for everyone09:49
d0ugalLots of people know Ansible and it is generally easier to write09:49
d0ugalbut I do appreciate they are not the same thing :)09:50
rakhmerovd0ugal: I totally understand this concern. I keep raising it again and again so that we could get resources to make it all much easier10:11
rakhmerovand better documented etc.10:11
rakhmerovlots of people raise the same when they get to developing something relatively big10:11
d0ugalYeah10:12
d0ugalI feel like it is hard to do now unfortunately10:12
rakhmerovd0ugal: btw, that's why I really wanted to implement all those initiatives around actions, specifically10:12
rakhmerovd0ugal: it is, I know10:12
d0ugalrakhmerov: Can you look at https://review.opendev.org/#/c/695375/ and https://review.opendev.org/#/c/694786/10:13
rakhmerovok10:13
d0ugalrakhmerov: I made them feature releases because there were lots of unreleased changes in stable/rocky and stable/stein10:13
d0ugalthey didn't all feel like bug fixes to me10:13
rakhmerovok10:13
d0ugalstein changes: https://github.com/openstack/mistral/compare/8.0.0...stable/stein10:14
d0ugalrocky changes: https://github.com/openstack/mistral/compare/8.0.0...stable/stein10:14
d0ugalrakhmerov: ^ if you want a easy place to see them10:15
rakhmerovok10:15
d0ugaloops, the second link is bad10:15
d0ugalrocky changes: https://github.com/openstack/mistral/compare/7.0.4...stable/rocky10:15
rakhmerovd0ugal: is what you told me an official decision yet?10:18
d0ugalrakhmerov: yes, the work has already started10:18
rakhmerovok10:19
d0ugalrakhmerov: https://review.opendev.org/#/c/679272/10:19
d0ugalrakhmerov: the spec hasn't merged yet, but I guess it will soon (once I find time to update it!)10:19
rakhmerovit is disappointing, of course, but ok10:20
d0ugalrakhmerov: Indeed, I think it is a shame10:22
rakhmerovwell, another lesson..10:22
rakhmerovhopefully, we'll learn it10:22
rakhmerovit is especially sad to me because I've been trying to convince people in importance of improving all that stuff (extending, plugins, actions etc. etc.) for years10:23
rakhmerovbut we keep failing to address that10:24
d0ugalYup, growing a community around the project is probably one of the hardest but most important things :)10:24
rakhmerovd0ugal: approved your patches10:32
d0ugalrakhmerov: thanks!10:32
*** apetrich has quit IRC11:29
*** apetrich has joined #openstack-mistral11:59
*** ricolin has joined #openstack-mistral12:27
*** pgaxatte has quit IRC13:30
*** mmethot has quit IRC13:36
*** pgaxatte has joined #openstack-mistral13:47
*** jtomasek has quit IRC14:32
*** jtomasek has joined #openstack-mistral14:35
*** mmethot has joined #openstack-mistral14:43
*** pgaxatte has quit IRC15:25
*** jtomasek has quit IRC15:38
openstackgerritMerged openstack/mistral-dashboard master: [ussuri][goal] Drop python 2.7 support and testing  https://review.opendev.org/69456515:47
*** pgaxatte has joined #openstack-mistral15:57
openstackgerritMerged openstack/mistral-extra master: [ussuri][goal] Drop python 2.7 support and testing  https://review.opendev.org/69456416:11
*** ricolin has quit IRC16:39
*** pgaxatte has quit IRC17:14
*** openstack has joined #openstack-mistral21:15
*** ChanServ sets mode: +o openstack21:15

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