18:00:25 #startmeeting Sahara 18:00:26 Meeting started Thu Jun 8 18:00:25 2017 UTC and is due to finish in 60 minutes. The chair is tenobreg. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:30 The meeting name has been set to 'sahara' 18:00:54 o/ 18:02:33 lets wait a couple more minutes to see if anyone else shows up, otherwise start just the three of us 18:03:16 tenobreg, three of us = me, you, __? 18:03:31 and vgridnev 18:03:39 right 18:04:25 should we ping our outreachy intern? 18:05:08 jeremyfreudberg, just did 18:05:15 yup 18:05:16 ok, lets start 18:05:24 #topic News/Updates 18:06:01 I'm still working on image creation and I have a question about that to ask vgridnev later. Also, I will cut Pike-2 today, since we got gate fixed 18:06:09 so I've been working to fix several jobs: spark dib, added new scenario job with py3 (experimental) , and grenade, but it will not pass because heat can't delete floating ip ... 18:06:27 vgridnev, where's the log for that? 18:06:40 https://review.openstack.org/#/c/471371/ 18:07:17 gate-grenade-dsvm-sahara-ubuntu-xenial-nv right? 18:07:31 yep 18:07:45 i'll take a look 18:07:48 I will take a look on the logs as well 18:08:12 http://logs.openstack.org/71/471371/2/check/gate-grenade-dsvm-sahara-ubuntu-xenial-nv/0587927/logs/new/screen-h-eng.txt.gz 18:09:05 thanks vgridnev 18:09:11 rebase the changes maybe, I'm seeing a nova floating ip association there 18:09:50 that is heat logs 18:10:30 2017-06-08 10:35:35.899 16016 INFO heat.engine.resource [req-d7f19a00-521b-4c83-a259-7e98efca16d2 - sahara_grenade - - -] DELETE: NovaFloatingIpAssociation "floating_ip_assoc" 18:10:47 jeremyfreudberg, these logs are from heat, not from sahara 18:10:59 looks to me like a client version problem, it tries to call self.client().floatingips but that doesn't exists anymore 18:11:03 vgridnev, i understand, that kind of heat resource is broken 18:11:52 vgridnev, i think a rebase would fix it, your parent commit is a month old 18:12:29 jeremyfreudberg, nope 18:13:07 does it make sense to be nova client version issue? 18:13:29 yes, tenobreg, heat had the same problem with the new novaclient is us 18:13:41 so they deprecated Nova floating IP associations in favor of Neutron ones 18:13:53 anyway, vgridnev has just rebased the patch so we will see 18:14:08 jeremyfreudberg, so you are saying that this might be old heat version we are using 18:14:58 ? 18:15:16 tenobreg, i'm not sure actually, because even though grenade failed with that error, our other jobs passed 18:15:34 I see 18:15:36 lets wait and see 18:16:34 #topic Pike-2 18:16:55 just want to make sure that we are ready to cut Pike-2 18:17:00 jeremyfreudberg, job use the following scenario : we are creating cluster using Sahara from ocata + Heat from ocata. After that we update Sahara and heat to master and then we delete cluster 18:17:16 tenobreg, ok 18:18:04 ah, vgridnev, I understand now... An Ocata cluster would create a Nova floating IP resource, but a master-branch Cluster can't delete it, since a master-branch Heat pulls down the newest novaclient 18:18:09 so the job will never pass 18:18:12 for ocata->pike 18:18:17 it will pass pike->queens 18:18:22 (when that happens) 18:18:34 Something like this, yep 18:18:35 jeremyfreudberg, makes perfect sense 18:18:39 do we have any thing else to do to cut Pike-2? From what I see we can cut it, gate is fixed and we have it stable with a reno about the breakage of the ironic 18:18:48 I think no 18:18:48 do we all agree? 18:19:08 Breakage of ironic? 18:19:10 What? 18:19:39 vgridnev, this is somewhat of a doubt we have... in order to fix gate jeremyfreudberg had to use pre created port on the Heat template 18:19:46 vgridnev, this is about using pre-created Neutron ports in our heat templates, we had to do that to get a stable gate 18:19:48 but that used to be an issue with ironic 18:19:55 https://bugs.launchpad.net/heat/+bug/1544195 18:19:56 Launchpad bug 1544195 in heat "User can not provision ironic node via nova when providing pre-created port" [Undecided,Confirmed] 18:20:19 Nova guys state that it might be fixed already 18:20:25 exactly, it "might" be 18:20:33 and we haven't tested it, so we are just putting a warning in release note 18:20:35 we are not sure that if it still the case 18:20:41 but hopefully it won't be 18:21:00 we set a release note stating that and we will make sure it works by P-3 18:21:18 tenobreg, you don't need such release note 18:21:39 Just fix it if it's broken 18:21:57 even if we are releasing a version with it broken? 18:22:02 and we don't have time to fix? 18:22:20 yes 18:22:24 P-2 deadline is today 18:22:30 vgridnev, i'm not sure, reno has a special section to mention these kinds of things, I think it's a nice thing to do 18:22:47 and we don't call it broken, we just warn that it is untested 18:22:48 Just file the bug 18:23:04 I agree with jeremyfreudberg, we may not need it, but it is good to have that written 18:23:57 jeremyfreudberg, can you file a bug? 18:25:12 so, we all agree we can cut Pike-2? 18:25:28 yes 18:25:30 yes, i think pike-2 is fine, unless you want to me to remove release note 18:25:40 jeremyfreudberg, lets leave it there 18:25:42 it won't hurt 18:25:49 once we fix it we can remove it 18:26:13 #topic Open Discussion 18:26:38 vgridnev, I have a question for you and maybe jeremyfreudberg as well... I'm working on image validation for the new image creation process 18:26:57 the validation process gets some scripts and runs on the instances 18:27:33 the problem I'm facing is the following: I export some variables distro and test_only(former reconcile0 18:28:21 but the variables aren't set during script execution 18:29:05 does paramiko has issues with export during its execution? is there a better way to do this? 18:29:52 I'm not an expert in the new mechanism of image generation, but it seems that there is some issue in our image generation code, doesn't it? 18:30:14 Variables on the node? 18:30:28 Node created with new image, I mean 18:30:46 what do you mean? The image creation is working properly 18:31:09 at least I tried with CDH here and the image created was working 18:31:36 So, I mean, your created the instance with new image. And then you test that instance with our scripts right? 18:31:38 the scripts generally work as far as i know, there's the experimental gate which seems to be doing something 18:32:14 the validation process uses the same scripts that we use for image creation 18:32:28 it just makes sure that everything that should be there is there already 18:32:48 no idea then 18:32:52 tenobreg, is this code that you have issues with somewhere 18:33:40 the problem here is basically with running a script remotely 18:34:25 tenobreg, nothing to do with this bug, right? https://review.openstack.org/#/c/446017/ 18:34:40 it sounds similar but i think yours is a different context 18:34:57 jeremyfreudberg, not really 18:35:42 it is similar, yes, we had the same issue during image creation because the "bash <<_SIV_" creates a new bash 18:35:43 Check which shell you script is using 18:36:10 It might just sh where you vars are not set 18:36:29 it uses /bin/bash 18:37:03 where are you "exporting" these variables from? 18:37:14 let me paste here 18:37:30 You also might be need to put these vars into some script in /etc/profile.d/ (how we do that with java) 18:37:46 https://github.com/openstack/sahara/blob/8b4af0daf3688dc79c8b15818dd817b01f5cc823/sahara/swift/swift_helper.py#L91 18:38:06 https://github.com/openstack/sahara/blob/master/sahara/plugins/images.py#L674-L681 18:38:56 vgridnev, I see, I will take a look and try to figure out why this is happening 18:39:04 ookay 18:39:50 so jeremyfreudberg, on that part of the code, we concatenate the script with the export of the variables 18:40:27 whole cmd is executed remotely 18:42:17 not sure really, it seems like it's fine 18:42:33 it does, but it is driving me crazy 18:42:34 lol 18:43:12 i assume you've thrown in some debug print statement already that prints script variable right before execution? 18:43:26 yes, as blank as it can be 18:44:08 So, I've got some sad news: next Tuesday is my last working day with Mirantis, btw I will try to stay around Sahara project, so you can always ping me by mail ( gridnevvvit at gmail ) 18:44:35 vgridnev :( 18:45:04 vgridnev, sad to see you go, hopefully we will not lose you completely 18:45:36 good luck on new endeavors 18:45:53 best of luck 18:45:54 But as I said, I will continue attending meetings sometimes if it would be possible. And will do code reviews! 18:46:03 tenobreg, jeremyfreudberg thanks! 18:46:06 vgridnev, we very much appreciate it 18:47:08 do we have any other topics to discuss today? 18:47:15 well, ptg 18:47:31 i assume we'll just have the one day (and not two or three) 18:47:34 if anything 18:48:03 true 18:48:21 We could get it all on one day for sure 18:48:29 i guess when enough people are back, we will find out if enough saharans will come 18:48:38 if it's just 2 people then not much point 18:50:12 sorry, internet went down 18:50:19 yeah, you've changed your name 18:50:32 jeremyfreudberg, I don't think skipping is the right thing to do 18:50:33 make sure the meeting ends properly, i've seen issue there before 18:51:10 I will clarify possibility of my attendance later. BTW, there are 3 open questions about that: I will need new visa, Travel support program, and new company - not sure they will allow me to attend. 18:51:45 vgridnev, completely understand, hopefully we will see you there 18:52:03 vgridnev, hope to see you there too. 18:52:17 hopefully we start having ptg in an "easier" country too 18:52:24 I think we should have, even if it is only two or three or four people, it is nice to get some face to face time and we could organize some coding, bug fix day, bug triage and so on 18:52:47 jeremyfreudberg, I think next year it will be in europe, lets see 18:53:05 changed to make sure I can end the meeting 18:53:32 jeremyfreudberg, how about we think on two days and organize some event for us, bug, documentation, or something like that 18:53:59 documentation seems like an interesting thing and easily fixable without lots of resources 18:54:17 i agree, docs would be good, and if we are at ptg we could talk to docs people 18:54:33 true 18:55:47 got to go 18:55:52 thanks guys 18:55:58 see you all next week 18:56:02 best of luck vgridnev 18:56:17 thanks 18:56:20 #endmeeting