16:00:59 #startmeeting OPNFV BGS Arno release readiness - daily checkin 16:00:59 Meeting started Thu May 14 16:00:59 2015 UTC. The chair is frankbrockners. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:59 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:59 The meeting name has been set to 'opnfv_bgs_arno_release_readiness___daily_checkin' 16:01:05 #info Frank Brockners 16:01:58 #info Fatih Degirmenci 16:02:08 #info Bryan Sullivan 16:02:12 #info Peter Bandzi 16:02:45 #info Morgan Richomme 16:02:48 hey folks, ... likely going to be a brief meeting today... most folks enjoy a public holiday 16:03:09 <[2]JonasB> #info Jonas Bjurel 16:03:14 nice to have them ;-) 16:03:50 #info Tim Rozet 16:04:50 ok - let's get started 16:05:11 #info daily updates on functest and automatic deploys on POD1 and POD2 16:05:26 Tim is pressed for time... - Tim could you go first? 16:05:49 #info have a puppet module that will configure the external network 16:06:02 #info need to do more testing on it to make sure its solid then will push a commit to gerrit 16:06:30 thats it from me 16:07:10 #info automatic deploy on POD2: Build #27 failed, #28 was successful. Any idea what was the issue? (log says some issues with vagrant) 16:07:42 #info #27 failed because the nodes did not pxe boot 16:08:01 #info I didnt have a chance to determine why 16:08:20 #info but if we see it again someone should go look at the remote console and see what happened 16:08:51 #info in the log you see "rebuilding node", and then you see it waiting to try to ssh back to the node 16:09:12 #info it will keep retrying to ssh to the node until linux is installed and the node comes up, if this does not happen within a timeout the deploy fails 16:10:02 so if we see it again we should look at that node and see why the pxe failed on the remote console 16:10:09 thats it from me, i got to run 16:10:20 thanks trozet - #29 is in progress - let's see what the result is going to be 16:10:38 anything else on automatic deploy? fdegir? 16:10:50 nope 16:10:54 cool 16:11:13 [2]JonasB: Quick update on POD1? 16:11:16 <[2]JonasB> #info No updates from my side 16:11:26 * frankbrockners seems that [1]JonasB got incremented... 16:11:42 thanks [2]JonasB 16:11:51 #info updates on functest 16:12:01 morgan_orange - any news? 16:12:23 #info POD 2 #29 shall perform the build/deploy/run 16:12:28 wait and see 16:12:35 including test? 16:12:36 #info Once the ongoing deployment #29 is successful, functest job will be triggered 16:12:43 cool! 16:12:59 last night it failed on deploy but it would not have work anyway, but it was a way to see how jobs are connected 16:13:10 #info change of job commited 16:13:27 #info (manual) functest on POD1 started 16:13:48 any early results? 16:13:59 #info functest/Pod1 vPing => TimeOut (bothe VM properly booted, network OK, but Ping not seen) 16:14:14 #info Tempest several tests run 16:14:29 #link https://wiki.opnfv.org/r1_tempest 16:14:47 #info first run showed 23 errors on 100 tests 16:15:06 # 4 root causes (3 common with Tests on POD2) 16:15:15 #info 4 root causes (3 common with Tests on POD2) 16:16:23 #info 3 common causes: Quota exceeded, Multiple possible networks found, need more than 1 value to unpack 16:16:46 #info first bench scenario in progress 16:17:09 for ODL I do not know if pbandzi had time to perform some test on POD 1 or 2 16:17:12 <[2]JonasB> How does this compare with the tempest runs on Ericsson Lab? 16:17:42 #info ODL no updates now 16:17:51 as far as I remember (need Jose for confirmation) there were 15 errors on E/// POD 16:18:00 but need to compare to see the difference 16:18:29 <[2]JonasB> Would be good to have a correlation to better understand wha could differ between the env. 16:18:37 and if OK we could also configure a nightly build/deploy/test on POD1 16:19:18 #info deployment #29 on POD2 failed 16:19:42 so no functest 16:19:59 :-( 16:20:09 I think we should disable automatic runs on pod2 somtrozet can take a look 16:20:34 fdegir: agreed 16:21:03 will send an email so trozet gets the info since he's left already 16:21:16 given the experience with POD2 autodeploy - should we try POD1 autodeploy the next night? Would at least give us some indication. 16:21:32 thanks fdegir 16:22:06 that is all for me 16:22:14 <[2]JonasB> frankbrockners: Depends on if Jose is planning to work on it tomorrow, which I think he did 16:22:48 yes 16:22:50 [2]JonasB: good point. morgan_orange: do you know? 16:23:08 no 16:23:36 so wait for his green light 16:23:46 ok - then let's keep with the original plan to switch POD1 to autodeploy on Monday... We can still redecide tomorrow. 16:23:48 for POD 1 16:24:18 ok... anything else to cover for today? Do we have anyone from docs? 16:24:47 ... if not, we can call it a day. 16:24:53 I'm still trying to get connected into the toolchain so I I can help. Minimal support so far. 16:24:55 <[2]JonasB> Thanks:-) 16:25:15 As soon as I can get the toolchain working I'll help move the docs forward. 16:25:16 <[2]JonasB> quit 16:25:20 as I can 16:25:27 bryan_att - could you check with Iben? 16:25:49 he might be around and he doesn't live in a holiday country... 16:26:09 He's on the list. I was told by Victor to check with the LF help desk. 16:26:29 yup - ping aricg 16:26:39 he's on IRC 16:26:49 I need to be able to commit without the overhead of gerrit reviews etc in order to test and improve the doc toolchain. 16:27:00 i'll ping aricg 16:27:11 well - you'll need to go through gerrit... 16:27:24 you can't push directly. 16:27:49 ok... looks like we're done with status updates. 16:27:50 if it's automatic then fine - but if I have to get votes from all committers for each change as I test/develop it wont happen 16:27:58 thanks everyone 16:28:03 #endmeeting