16:00:02 #startmeeting OPNFV BGS daily Arno release readiness synch 16:00:02 Meeting started Fri May 22 16:00:02 2015 UTC. The chair is frankbrockners. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:02 The meeting name has been set to 'opnfv_bgs_daily_arno_release_readiness_synch' 16:00:12 #info Frank Brockners 16:01:03 #info Morgan Richomme 16:01:14 Hey Morgan 16:01:52 #info Tim Rozet 16:02:11 will probably be a quick meeting today - Jonas and Peter can't make it... 16:02:32 so we can get started - and record status for others. 16:02:44 I have a brief update from Jonas... will info this in 16:02:54 #info Updates on POD1 autodeploy 16:03:17 #info An non HA deployment is in place at LF POD1. 16:03:53 #info Jonas and team are finishing up some stuff for the ODL tests, hope to have it on Sunday. (per Jonas) 16:04:18 #info Jose Lausuch 16:04:20 that's it for Fuel - so POD1 is switched from pure O/S to O/S with ODL now 16:04:58 #info Updates on POD2 16:05:12 trozet - do you want to give a brief update? 16:05:36 #info I updated the quotas this morning, and tested it manually. Kicked off a new daily master so we should see the results with the quotas bumped 16:06:04 #info looking into functest failures with morgan_orange and jose_lausuch 16:06:18 thats it 16:06:30 did "network_external" help with any of the tests? 16:06:46 i.e. external network being available now? 16:06:57 frankbrockners: you have to tell tempest what the external network is 16:06:59 and tell it to use it 16:07:15 I'm trying to determine if rally does that automatically or if we need to update the tempest.conf file 16:07:17 ok... sounds like we should move to Morgan and Jose :-) 16:07:25 #info Updates on Functest 16:07:39 morgan_orange or jose_lausuch? 16:07:50 #info last night tests shared; results stable on POD1 (same errors reproducible) 16:07:52 the thing is that for fuel deployment, the external network is created and taken by rally to put it in the tempest.conf, at least this is what I can tell 16:08:17 #info more errors on POD2 but more tests attempted.. 16:08:28 #vPing failed on POD2 'Ping not seen) 16:08:37 #info vPing failed on POD2 'Ping not seen) 16:08:42 #info vPing OK on POD1 16:09:33 morgan_orange: was this done on the new O/S + ODL setup or the old O/S only setup (with native neutron networking) 16:09:34 #info ODL tests KO on POD1 (problem of rights on the file) 16:10:37 maybe we need to set the permissions from jenkins or something, strange error 16:11:05 it was on https://build.opnfv.org/ci/job/functest-opnfv-jump-1/16/console 16:11:10 #link https://build.opnfv.org/ci/job/functest-opnfv-jump-1/16/console 16:11:20 * fdegir jose_lausuch I'll look into those permission issues and come back to you 16:11:21 #info ODL test not executed on POD2 (vPing failure) 16:11:31 sure, thanks 16:11:34 I push a patch mentioned by Peter 16:11:43 ah 16:11:45 call bash start_tests.sh 16:11:54 but will that help? 16:11:56 to be merged on releng 16:12:30 will merge it whenever the patch comes in 16:13:13 from what I know Peter mentioned that manual ODL tests on POD2 ran ok 16:13:16 it has been done by aric 16:13:28 ok 16:13:41 yes ODL manual run on POD2 was OK 16:13:53 they have not been executed last night due to vPing Timeout 16:14:02 it seemsn that both VM properly started 16:14:20 but the no ping has been captured in the nova console 16:14:41 but I pushed a patch to timeout vping 16:14:45 did ntit work? 16:14:51 yes it worked well 16:14:56 ah ok 16:14:58 the test did not loop 16:15:04 great 16:15:04 it exited after time out 16:15:15 https://build.opnfv.org/ci/view/functest/job/functest-opnfv-jump-1/16/console 16:15:28 ah, ok, so then it does not continue with the next tests 16:15:52 what are the remaining tasks from a functest perspective? trozet changed the quotas - which hopefully fixes some issues. what is the plan to get rally recognize the external network on POD2 correctly (to drive the tempest.conf)? 16:16:22 but raceback (most recent call last): 16:16:22 File "/home/jenkins-ci/.functest/vPing/vPing.py", line 256, in 16:16:22 main() 16:16:22 File "/home/jenkins-ci/.functest/vPing/vPing.py", line 247, in main 16:16:22 if EXIT_CODE == 0: 16:16:22 UnboundLocalError: local variable 'EXIT_CODE' referenced before assignment 16:16:23 Build step 'Execute shell' marked build as failure 16:16:56 remaining tasks 16:17:23 - have a complete run (even with some errors) 16:17:35 - reduce the number of errors (quotas should fix some errors) 16:18:02 but last night we got new errors we never had Invalid credentials on tempest.api.identity.admin.v3 16:18:14 - document the errors 16:18:51 we still have lots of errors on nova/neutron bench but quota could be also one solution 16:19:25 we could contact Rally team next week because I think there are cleaining issues that could also be the cause of some errors 16:19:57 #link https://wiki.opnfv.org/r1_tempest?&#error_follow_up 16:19:57 identity stuff is set in tempest config 16:20:16 let's info some of this ... (doing this right now) 16:20:30 #info I think we need to save the tempest config file from runs. It is hard to debug these problems without it 16:20:51 yes but it is weird, if it would use identity creds from this config file everything shall fail..we source the o/S creds before launchin the installation 16:21:05 this error appear only on both POD yesterday night 16:21:18 #info FuncTest remaining tasks (a) achieve a complete test run (even with some errors), (b) reduce the number of errors (we still have lots of errors on nova/neutron bench but quota could be also one solution) (c) document the errors 16:21:55 the config file is not cleaned after test, it is always available on the Jumphost 16:22:04 back on the earlier question: is there a way to feed rally the info on the external network and other tempest config parameters? 16:22:53 frankbrockners: the suggestion is rally figures it out for you 16:22:56 my view was that tempest config was dynamically created based on a static default config and dynamic information retrieve through the different client 16:22:57 http://pastebin.com/VTw4xyG2 line 62 16:23:06 that is the tempest config for pod1 16:23:16 I need the tempest config for pod2 to help debug these issues 16:23:20 morgan_orange: but it should, if the test go well, at the end it will execute a clean, which will delete .rally/ 16:23:37 trozet: we will get it but I cleaned functest for the new run 16:23:51 morgan_orange: np we will see it I guess when functest runs on daily master 16:23:58 oups you are right, if the test go until the end we will clean it.. 16:25:44 so frankbrockners I think for the last 2 weeks we will need support on tempest/rally tuning... 16:26:15 quickly on tempest.conf: could you push it to some git - or log the tempest.config file to console? 16:26:37 that is actually a good idea 16:26:45 we could output it from the jenkins job 16:28:29 +1 16:28:31 morgan_orange: ack on the need to have support - though not sure how to get it. Should we ask opnfv-tech-discuss again for help? And all of us can dig for tempest/rally experts in our companies for help... 16:29:19 just copy it 16:29:24 as part of the jenkins bash script 16:29:49 copy it where? 16:30:59 in console 16:31:01 cat .rally/tempest/for-deployment-*/tempest.conf 16:31:10 or in final result dir? 16:31:15 jap 16:31:37 thats another option, or even both 16:31:55 yeah you can just cat it into the log file 16:32:06 or copy it into /tmp 16:32:07 or whatever 16:32:44 morgan_orange: on additional help: have you tried asking iben for help? 16:33:12 we could also add a rally show networks in the console (as we do for image , flavours and services) 16:33:27 frankbrockners: not doen nominatively 16:33:40 I will ask him 16:34:06 thanks - he might also know other test folks who could help 16:34:10 people from Mirantis on rally-chan were also responsive when I started discovering Rally 16:34:42 we will see on Tuesday.. 16:35:40 some admin-stuff: Monday is memorial day in the US and pentecoast in several countries 16:36:28 plan was to still do a synch on Monday (Peter Bandzi hosts it - I'm traveling) - we'll see who is going to make it (might be a very short meeting) 16:36:55 trozet: Is dradez covering for you next week? 16:37:13 dradez and dfarrell07 is also around to help 16:37:18 radez* 16:37:22 perfect - thanks 16:37:38 I'll still be checking email 16:38:46 ok - are we done for today? 16:39:28 looks like it.. 16:39:31 yep 16:39:43 Everyone have a nice loooong weekend 16:39:49 #endmeeting