Thursday, 2017-07-27

*** esberglu has joined #openstack-powervm00:14
*** kylek3h has joined #openstack-powervm00:15
*** kylek3h has quit IRC00:16
*** kylek3h has joined #openstack-powervm00:52
*** kylek3h has quit IRC00:53
*** edmondsw has joined #openstack-powervm00:54
*** edmondsw has quit IRC00:58
*** kylek3h has joined #openstack-powervm01:29
*** kylek3h has quit IRC01:29
*** esberglu has quit IRC01:43
*** thorst has joined #openstack-powervm01:49
*** thorst has quit IRC01:49
*** kylek3h has joined #openstack-powervm02:23
*** kylek3h_ has joined #openstack-powervm02:30
*** kylek3h has quit IRC02:33
*** esberglu has joined #openstack-powervm02:38
*** esberglu has quit IRC02:42
*** edmondsw has joined #openstack-powervm02:42
*** kylek3h_ has quit IRC02:45
*** edmondsw has quit IRC02:46
*** thorst has joined #openstack-powervm03:22
*** thorst has quit IRC03:30
*** chhavi has joined #openstack-powervm04:31
*** k0da has joined #openstack-powervm04:57
*** thorst has joined #openstack-powervm05:26
*** thorst has quit IRC05:33
*** k0da has quit IRC05:51
*** k0da has joined #openstack-powervm05:58
*** thorst has joined #openstack-powervm06:01
*** thorst has quit IRC06:05
*** esberglu has joined #openstack-powervm06:16
*** edmondsw has joined #openstack-powervm06:18
*** esberglu has quit IRC06:21
*** edmondsw has quit IRC06:23
*** miltonm has quit IRC06:31
*** k0da has quit IRC06:50
*** thorst has joined #openstack-powervm08:02
*** esberglu has joined #openstack-powervm08:04
*** edmondsw has joined #openstack-powervm08:06
*** thorst has quit IRC08:06
*** esberglu has quit IRC08:08
*** edmondsw has quit IRC08:11
*** k0da has joined #openstack-powervm08:36
*** esberglu has joined #openstack-powervm09:52
*** edmondsw has joined #openstack-powervm09:54
*** esberglu has quit IRC09:57
*** edmondsw has quit IRC09:58
*** thorst has joined #openstack-powervm10:03
*** thorst has quit IRC10:07
*** thorst has joined #openstack-powervm10:24
*** thorst has quit IRC10:28
*** thorst has joined #openstack-powervm10:47
*** thorst has quit IRC10:51
*** smatzek has joined #openstack-powervm10:57
*** esberglu has joined #openstack-powervm11:40
*** kylek3h has joined #openstack-powervm11:42
*** kylek3h has quit IRC11:42
*** edmondsw has joined #openstack-powervm11:42
*** esberglu has quit IRC11:44
*** edmondsw has quit IRC11:47
*** thorst has joined #openstack-powervm11:54
*** kylek3h has joined #openstack-powervm12:02
*** kylek3h has quit IRC12:11
*** chhavi has quit IRC12:32
*** edmondsw has joined #openstack-powervm12:33
*** esberglu has joined #openstack-powervm13:23
*** esberglu has quit IRC13:24
*** esberglu has joined #openstack-powervm13:24
*** apearson has joined #openstack-powervm13:27
*** k0da has quit IRC13:27
*** efried_zzz is now known as efried13:40
*** miltonm has joined #openstack-powervm13:57
*** kjw3 has joined #openstack-powervm14:11
*** apearson has quit IRC15:13
*** tjakobs_ has joined #openstack-powervm15:17
*** apearson has joined #openstack-powervm15:20
*** apearson has quit IRC15:38
*** edmondsw has quit IRC15:42
*** apearson has joined #openstack-powervm15:42
*** edmondsw has joined #openstack-powervm15:50
esbergluedmondsw: Next time you try to get that system stacking make sure you run15:58
esberglusudo ppc64_cpu --smt=off15:58
esbergluBefore ./stack.sh15:58
edmondswesberglu yeah, I saw y'all talking about that yesterday15:58
edmondswt15:58
edmondswtx15:58
efriedshould add that to the top of the etherpad16:02
*** apearson has quit IRC16:26
*** apearson has joined #openstack-powervm16:27
*** apearson has quit IRC16:31
*** apearson has joined #openstack-powervm16:31
*** apearson has quit IRC16:32
*** apearson has joined #openstack-powervm17:25
*** apearson has quit IRC17:35
*** apearson has joined #openstack-powervm18:16
*** tjakobs_ has quit IRC19:42
*** tjakobs_ has joined #openstack-powervm19:42
*** smatzek has quit IRC20:15
thorstesberglu: see #openstack-nova20:51
thorstedmondsw efried: ^^20:51
thorstthey noted that https://review.openstack.org/#/c/487246/ broke the PowerVM CI20:51
thorstefried: some of those logs look like we're just having trouble connecting to novalink?20:53
efriedthorst That's pretty normal, I think, innit?20:56
edmondswnice that they noticed20:56
efriedIt looks to me like they're just killing the compute process too soon.20:56
thorstefried: why wouldn't we be able to connect...like instantly?20:56
efriedYeah, dunno, should be able to.20:57
efriedWhere's esberglu ?20:57
thorstI don't know how we do the pypowervm thing now, but I didn't think it would be connecting to localhost.20:58
thorstand that's probably why it's hitting this thing20:58
thorstnot sure where esberglu is atm20:58
thorstnet I think to nova is, we'll be investigating.20:58
esbergluCatching up20:58
thorstesberglu: the question I'd have is - are we setting this on the CI?21:02
thorsthttps://github.com/powervm/pypowervm/blob/master/pypowervm/adapter.py#L171-L17521:02
efriedIf we weren't, we never would have gotten started.  Which we kinda clearly didn't in this case.21:03
thorstyeah.  I haven't been paying super close attention to CI (obviously) but the statement that init_host takes ten minutes shocks me.21:04
thorstwe spent tons of effort getting the CI time down...21:04
thorstit almost sounded like we tried localhost for X minutes and then flipped over to this other config?21:04
esbergluthorst: So up until now we have been stacking, then changing the environment file setting for the relevant devstack services21:04
esbergluAnd then restarting those services21:05
esbergluat which point the load with 'PYPOWERVM_SESSION_CONFIG' set21:05
thorsto.21:05
thorstwell.21:05
thorstyikes?21:05
esbergluProblem is that the file we are modifying to do so is created during the stack21:05
esbergluSo we can't just update the env. file before stacking because it doesn't exist21:06
thorstright right.  Sec...21:06
esbergluWe might be able to create the env. file prior to stacking, but idk if stacking will overwrite that21:06
thorsthttps://github.com/openstack/nova-powervm/blob/master/nova_powervm/virt/powervm/driver.py#L16221:06
thorstseems to me that maybe we should make "conn_tries" a conf option21:06
thorstand you set that to like 2 or 3.21:07
thorstedmondsw efried: thoughts?21:07
esbergluI don't see how that helps with this21:07
efriedsowait, esberglu walk me through the timing again?21:08
efriedSo before, they weren't waiting for compute to come up, and they just went right by that part, and then after stack was done, we would swap out the adapter config to enable remote, and then we would start up compute again?21:09
efriedBut now they're waiting for compute to come up, which it never will while we're trying at localhost.21:09
edmondswI'm probably not much help at the moment... I have a splitting headache, can't think straight21:09
efriedAnd when they time out, they kill the compute service and fail the stack.21:10
edmondswI'm trying to keep up but I have to read everything 3 times to parse it21:10
efriededmondsw Go put a hot bag of rice over your eyes.  We've got it covered.21:10
edmondswtx21:11
thorstefried: I think it just died after it timed out21:12
thorstbut we restarted it or something21:12
thorstI guess I'm not sure why we can't put down the session conf file before stacking?21:12
thorstI'm sure I'm missing something obvious there.21:12
efried++21:12
esbergluefried: Here comes my blurb. But yeah that's pretty much it21:13
esbergluWe set PYPOWERVM_SESSION_CONFIG in /etc/environment which is needed for remote21:13
esbergluThen we stack. When stacking all of the devstack services get a service file (/etc/systemd/system/devstack@service.service)21:13
esbergluWe need to set the EnvironmentFile var in that service file to /etc/environment so that it knows what session config to load21:13
esbergluPreviously we were letting the stack finish, then updating the service file, then restarting the services at which point remote would work21:13
esbergluIf I understand everything correctly the problem is that we need remote working for the stack to complete.21:13
efriedYup.21:13
efriedI mean, they're reverting that change, but I imagine they're gonna try to bring it back in some form eventually.21:14
thorstesberglu: yeah, remote working pre-stack.  Which I think means we need to somehow set the os.environ attribute pre-stack21:14
esbergluSo we either need to have the service files in place before stacking (but they might get overwritten, haven't looked for this code yet)21:14
thorstefried: even if they revert, I'd imagine this would speed up our CI as is21:14
thorstmaybe not...if its non-blocking21:14
efriedthorst Well, I'm thinking we probably do the service file edit and restart n-cpu right after stack finishes, so it would be negligible.21:15
efriedCompute was sitting there failing to start while stack finished, but should start right up when we did that restart.21:15
esbergluefried: Yeah that's accurate21:15
efriedIt'll shave a hair off, but not significant.21:15
efriedBut regardless, we want to get remote set up so it takes effect during stack.21:16
efriedesberglu I think I would start by figuring out where those service files are generated in devstack, and see if we can hook in there.21:17
efriedWhat's the path to the compute service file?21:17
esberglu /etc/systemd/system/devstack@n-cpu.service21:17
efriedesberglu It looks like if you set up that file before stack, it won't get overwritten.21:19
efriedNeeds to be owned by root21:19
efriedI'm looking at devstack/functions-common:144321:20
efriedwrite_user_unit_file21:20
esbergluefried: Yep was just getting there. I'll test out a fix21:20
thorstfor reference - how is the CI holding up?21:21
thorstare we passing when we should be passing?21:21
efriedthorst It hasn't seemed very good to me.  I've got four, five rechecks in a row on a couple changes.21:21
thorstesberglu: are we identifying the root causes on those?  And importantly, pulling in the right people and forcing ownership to solve that  :-)21:22
esbergluefried: thorst: Yeah failure rates are higher than normal. There was a bunch failing due to discover_hosts timeouts and bad marker LUs that are now fixed21:22
esbergluTomorrow I was planning on diving into the timeouts that are hitting us21:22
thorstI need to head out, but if we need a renewed focus on CI...that's a tablestakes function.  New development basically goes on pause while we solve it.21:23
*** thorst has quit IRC21:25
*** thorst has joined #openstack-powervm21:26
*** thorst_ has joined #openstack-powervm21:27
*** thorst has quit IRC21:30
*** esberglu has quit IRC21:31
*** thorst_ has quit IRC21:32
*** apearson has quit IRC21:43
*** esberglu has joined #openstack-powervm21:45
*** thorst has joined #openstack-powervm21:45
*** esberglu has quit IRC21:49
*** thorst has quit IRC21:50
*** esberglu has joined #openstack-powervm21:51
*** edmondsw has quit IRC22:06
*** edmondsw has joined #openstack-powervm22:07
*** edmondsw has quit IRC22:12
*** thorst has joined #openstack-powervm22:13
*** thorst has quit IRC22:14
*** openstack has joined #openstack-powervm22:44
*** thorst has joined #openstack-powervm23:15
*** thorst has quit IRC23:21
*** edmondsw has joined #openstack-powervm23:37
*** edmondsw has quit IRC23:41
*** tjakobs_ has quit IRC23:44
*** thorst has joined #openstack-powervm23:46
*** thorst has quit IRC23:55
*** thorst has joined #openstack-powervm23:56

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