08:00:23 <morgan_orange> #startmeeting Functest weekly meeting August 23rd
08:00:23 <collabot> Meeting started Tue Aug 23 08:00:23 2016 UTC.  The chair is morgan_orange. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:23 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:00:23 <collabot> The meeting name has been set to 'functest_weekly_meeting_august_23rd'
08:00:29 <morgan_orange> #topic call role
08:00:38 <morgan_orange> #info Morgan Richomme
08:00:40 <viktor_t> #info Viktor Tikkanen
08:00:42 <juhak> #info Juha Kosonen
08:00:59 <morgan_orange> #info agenda for today: https://wiki.opnfv.org/display/functest/Functest+Meeting
08:01:00 <SerenaFeng> #info SerenaFeng
08:01:13 <JuhaHaapa> #info Juha Haapavirta
08:01:26 <boucherv_orange> #info Valentin Boucher
08:01:50 <morgan_orange> #topic action points follow up
08:01:58 <CG_Nokia> #info CG_Nokia (Colum Gaynor)
08:01:58 <lhinds> #info Luke Hinds
08:02:02 <morgan_orange> #info AP1: morgan_orange viktor_t create a wiki page to explain how to justify case exclusion for Tempest => done https://wiki.opnfv.org/pages/viewpage.action?pageId=6828523
08:02:15 <morgan_orange> #info AP2: morgan_orange merge userguide patch + call feature proejct to complete user guide with their own reference => done
08:02:27 <morgan_orange> #info AP3: all review config guide => done even a new review will be necessary before final release
08:02:42 <morgan_orange> #info AP4: morgan_orange see why json rally result files are not pushed anymore to artifact => they are pushed...in DB as rally-details, push in artifact if the complete run is OK (blue ball)
08:03:01 <morgan_orange> #info AP5: juhak see json locally on lf-pod1 to troubleshoot rally issue with apex scenario
08:03:13 <juhak> #info apex guys corrected heat issue last Fri, https://gerrit.opnfv.org/gerrit/#/c/18951/
08:03:22 <juhak> #info rally sanity success rate 100% in apex starting from that https://build.opnfv.org/ci/view/functest/job/functest-apex-apex-daily-master-daily-master/274/
08:03:57 <morgan_orange> good news, we will discuss apex scenarios in next topics
08:04:01 <morgan_orange> #info AP6: morgan_orange SerenaFeng sync with Juraj and peopel dealing with ElasticSearch licence => mail sent, no feedback, dashboard activity to be planned when Colorado stabilized
08:04:11 <morgan_orange> #action morgan_orange SerenaFeng sync with Juraj for dashboard activity
08:04:20 <morgan_orange> #info AP7: SerenaFeng morgan_orange add report flag to avoid meaningless results or 500 because source is not referenced => done
08:04:34 <morgan_orange> #info AP8: create rules for D release to decide to which category a case belong to => Jira created https://jira.opnfv.org/browse/FUNCTEST-430
08:04:44 <morgan_orange> #info AP9: lhinds modify exec_test to point to security repo => done
08:04:55 <morgan_orange> #info AP10: morgan_orange re-enable security_scan when ready => closed no recent run seen in CI but enabled in testcases.yaml (not in automatic reporting because no aggregated results pushed to DB)
08:05:00 <lhinds> morgan_orange: is security scans active again?
08:05:14 <lhinds> I can never find it in the jenkins build runs
08:05:35 <lhinds> sorry you beat me too it ;)
08:06:17 <raghu_> #info raghavendrachari
08:06:19 <morgan_orange> lhinds: hmm why secruity scan is not triggered on apex scenario...
08:06:44 <morgan_orange> seems ok in exec_test.sh and tetcases.yaml
08:06:59 <ollivier> #info ollivier
08:07:53 <lhinds> would it be worth us moving up closer to the top of the run, now that a timeout clause in is there for broken connections?
08:08:29 <morgan_orange> lhinds: the run is relatively short
08:08:30 <lhinds> we could prio the list to have TC's that commonly fail, lower down the list?
08:09:13 <morgan_orange> that is already a little bit the case, copper or bgpvpn that fails are triggered at the end but it is very short
08:09:24 <morgan_orange> we will dedicate a section to apex scenatio in next topic
08:09:38 <morgan_orange> my concern is why security_scan has not been triggered
08:09:54 <lhinds> sure, we could trigger from Apex, but still push results to functest
08:10:20 <lhinds> or trigger indepently might be a better way to word it.
08:10:32 <morgan_orange> #action morgan_orange lhinds see why security_scan is no more triggered on apex scenario
08:10:42 <viktor_t> what is "scenario: 'disable'" ?
08:10:55 <viktor_t> I mean for security scan
08:11:24 <lhinds> no idea viktor_t - that's not from my code
08:11:44 <viktor_t> it is in functest/tree/ci/testcases.yaml
08:12:56 <viktor_t> should it be scenario: ' ' ?
08:13:00 <morgan_orange> viktor_t: OK that is what I was looking for
08:13:05 <morgan_orange> yes
08:13:39 <viktor_t> I can make a patch
08:13:47 <morgan_orange> so that is all for action points, we already a little but anticipate on scenarios
08:13:53 <morgan_orange> #topic Colorado
08:14:07 <SerenaFeng> should it be scenario: 'apex' not ' '
08:14:13 <morgan_orange> #info we branched yesterday and have now a nice Colorado branch
08:14:17 <SerenaFeng> for now, only apex is supported, I think
08:14:33 <morgan_orange> #info reminder patch on master => merge => cherry pick to colorado => merge
08:14:41 <morgan_orange> SerenaFeng: yes you are right
08:15:07 <viktor_t> SerenaFeng: do you mean: installer: 'apex'
08:15:10 <morgan_orange> #info branching will have consequences on CI (soon...) with master and colorado jobs in ..
08:15:21 <morgan_orange> installer:'apex', scenario:''
08:15:45 <morgan_orange> we will have also to modify the docker to fix all the version of the feature project in the colorado docker
08:16:03 <morgan_orange> I assume all the projects have branched now (deadline was yesterday)
08:17:07 <SerenaFeng> morgan_orange: I am not very sure whether docker in fuel is okey on yesterday's branch or not,
08:17:08 <morgan_orange> #info considering master ~ colorado scenarios, we got first green scenarios
08:17:32 <SerenaFeng> I saw you merged to it, I will ask docker people to make sure of it
08:18:27 <morgan_orange> let's review the scenarios per installer
08:18:40 <SerenaFeng> docker -> doctor
08:18:47 <morgan_orange> ah ok
08:19:09 <morgan_orange> doctor was successul on apex, I merged the patch to run it on fuel this morning
08:19:25 <morgan_orange> #info compass scenarios:  http://testresults.opnfv.org/reporting/functest/release/master/index-status-compass.html
08:21:27 <morgan_orange> #info still open question on odl management (ports): errors on moon scenario, not on th odl scenario (it should be FAIL as well)
08:21:53 <morgan_orange> May-meimei: could you ask how ports are managed in compass/odl scenarios?
08:22:26 <morgan_orange> #info still issues with moon scenario (authentication errors when running specific moon tests)
08:22:44 <morgan_orange> May-meimei: any update on the rollback to liberty for ocl scenarios?
08:22:48 <May-meimei> morgan_orange: sorry, wait a moment
08:23:19 <May-meimei> odl restapi-port use 8181
08:25:05 <May-meimei> but heruan said the issue is cause by the password
08:26:06 <May-meimei> we have issues on ocl , because default sec-group
08:26:16 <morgan_orange> for moon it is a password issue, but for ODL it is a port conflict between AS-SAL and MD-SAL
08:26:32 <May-meimei> juniper will update the pkg
08:26:49 <morgan_orange> it is surprising that this issue affects only odl_l2-moon, we would expect the same behavior with the other odl_scenario
08:27:10 <morgan_orange> #info compass/ocl juniper will release new pkg to fix sec-group issues
08:27:22 <May-meimei> odl-moon deployed on xenial
08:27:53 <May-meimei> and other odl scenario deployed on liberty
08:29:03 <morgan_orange> odl-moon is in mitaka/xenial, other odl_scenarios in liberty/trusty?
08:29:23 <May-meimei> sorry
08:29:44 <May-meimei> odl-moon is in mitaka/xenial, other odl_scenarios in mitaka/trusty?
08:29:52 <May-meimei> confused
08:30:34 <morgan_orange> no sure to see why ODL config could be impacted by the OS/Ubuntu version but OK interesting to see that moon has a different config
08:30:46 <morgan_orange> #action ollivier May-meimei clarify port management on ODL
08:31:05 <morgan_orange> #info issues with onos-sfc tests
08:31:38 <morgan_orange> #info fuel scenarios: http://testresults.opnfv.org/reporting/functest/release/master/index-status-fuel.html
08:32:35 <morgan_orange> #info still some Tempest issues in some scenarios but globally looks fine. Parser tests OK now
08:32:38 <ollivier> morgan_orange: ok. 8181 is used for both ports for this installer which is the default for MD-SAL (tested by basic suite)
08:33:42 <morgan_orange> #info joid scenarios: http://testresults.opnfv.org/reporting/functest/release/master/index-status-joid.html
08:34:10 <morgan_orange> #info issues reported by Narinder due to some regression on our sides (patches merged)
08:34:34 <morgan_orange> #info lxd scenario run but still not appear here because healthcheck is FAIL
08:35:08 <morgan_orange> #info issue in lxd is due to teh fact that DHCP check is based on a trace seen in the nova log, traces is ok in cirrios/VM but not with the lxd image
08:35:31 <morgan_orange> #info discussion in progress to see how to deal with that (with minimum impact)
08:35:54 <morgan_orange> #info apex scenarios: http://testresults.opnfv.org/reporting/functest/release/master/index-status-apex.html
08:36:01 <morgan_orange> #info doctor tests now OK
08:36:14 <morgan_orange> #info but still unstable env
08:36:58 <morgan_orange> #info functest with scenarios onos, onos-sfc, odl_l2-fdio, nosdn-fdio, nosdn-ovs FAIL due to authentication issues (/home/stack/overcloudrc not found)
08:37:00 <viktor_t> some discussion in https://jira.opnfv.org/browse/APEX-236
08:37:59 <morgan_orange> in this case, we even do not start a single test because we are not able to source the creds
08:38:13 <morgan_orange> which scenarios did you test on apex/nokia?
08:38:42 <viktor_t> odl-l2-nofeature
08:39:05 <morgan_orange> ok this one is also working fine (last run issue due to vPing regression but should be ok now)
08:39:31 <morgan_orange> #action morgan_orange contact Apex to see why 50% of the scenarios are FAIl due to creds
08:40:11 <morgan_orange> #info copper systematically FAIL in apex (ok with joid) => shall we remove apex in copper dependency? question raised to Bryan on the JIRA
08:40:25 <morgan_orange> #info some odl issues (on delecte)
08:40:52 <morgan_orange> #undo
08:40:52 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2e77410>
08:41:04 <morgan_orange> #info some odl issues (on delete) in bgpvpn scenarios
08:41:07 <morgan_orange> #action ollivier look at https://build.opnfv.org/ci/view/functest/job/functest-apex-apex-daily-master-daily-master/296/console
08:41:33 <morgan_orange> #info bgpvpn issues on apex (ok on fuel)
08:41:52 <morgan_orange> #info Tempest => discussion between apex and viktor_t https://jira.opnfv.org/browse/APEX-236
08:41:57 <morgan_orange> #info rally: heat issue fixed
08:42:41 <morgan_orange> any question on the scenarios?
08:42:57 <morgan_orange> #topic JIRAs
08:43:10 <morgan_orange> #link https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=59
08:43:31 <morgan_orange> let's have a look at the JIRA and see if some may not be postponed to D
08:43:48 <morgan_orange> #info multisite: still integration issue reported
08:43:53 <morgan_orange> #link https://jira.opnfv.org/browse/FUNCTEST-179
08:44:12 <morgan_orange> viktor_t: was your patch to create resources earlier in tempest addressing this issue?
08:44:32 <viktor_t> no
08:44:38 <morgan_orange> #info Copper integration: OK with joid, ko with fuel
08:45:07 <morgan_orange> #info JIRA-267 and 268: connected to healthcheck issue on lxd scenarios mentioned earlier
08:45:37 <viktor_t> should FUNCTEST-377 be addressed to D release?
08:45:38 <morgan_orange> boucherv_orange: you confirm that vPings, tempest-smoke and rally-sanity tests were OK?
08:45:59 <boucherv_orange> morgan_orange: yes
08:46:37 <morgan_orange> #info vPings, tempest-smoke and rally-sanity tests successfully tested with lxd scenarios on Orange POD 1
08:47:18 <morgan_orange> viktor_t: yes makes sense, need dangerous changes...
08:47:42 <boucherv_orange> morgan_orange: It's ok for vping_ssh, tempest-smoke and rally-sanity
08:47:44 <morgan_orange> there are also some refactoring to be planned for openstack_utiols and run_tests
08:47:57 <boucherv_orange> morgan_orange: i'm not sure for vping_userdata
08:48:02 <morgan_orange> boucherv_orange: ok
08:48:19 <morgan_orange> viktor_t: I move FUNCTEST-377 to D release
08:49:03 <morgan_orange> SerenaFeng: shall we also assign FUNCTEST-385 to D?
08:49:14 <morgan_orange> it is for the reporting from CLI
08:49:32 <SerenaFeng> okey
08:49:44 <SerenaFeng> when will release C over?
08:49:44 <morgan_orange> #info FUNCTEST-385 move to D
08:50:01 <morgan_orange> i would say that since we branche C release is almost over
08:50:12 <SerenaFeng> ok
08:50:13 <morgan_orange> we should now focus on patch/troubleshooting to optimize the results in CI
08:50:20 <morgan_orange> and adapt the doc accordingly
08:50:41 <morgan_orange> changes can be done in Master but new feature must not be cherry picked, only fixed and C related stuff
08:51:32 <morgan_orange> raghu_: I saw your last comment, as it is a php front end calling the API, I am pretty confident
08:51:54 <morgan_orange> but as far as I saw there is no authentication by default so I hesitate to put it on testresults.opnfv.org
08:52:10 <raghu_> yeah i need database for authentication
08:52:27 <raghu_> so i didn't added , login part
08:52:37 <morgan_orange> I think we can close the JIRA for C release
08:52:57 <morgan_orange> we should decide whether we should improve it or not for D
08:53:08 <raghu_> oh kk
08:53:14 <morgan_orange> ok to close it now?
08:53:24 <raghu_> yes
08:53:41 <morgan_orange> #info FUNCTEST-26 to be closed for C release
08:54:30 <morgan_orange> #info FUNCTEST-162 to be postponed to D release or C.2 or even close (assuming that it was used for Brahmaputra)
08:54:37 <morgan_orange> a new one coudl be created for next release
08:54:59 <raghu_> JIRA #FUNCTEST-176, same as FUNCTEST-26?
08:55:22 <morgan_orange> #info FUNCTEST-324 could be also close, discussion by mail with Frank, test for these scenarios done by default Functest tests, no specific ones
08:55:48 <morgan_orange> raghu_: ok I will clean it this afternoon
08:56:01 <raghu_> ok
08:56:14 <morgan_orange> #info FUNCTEST-382; it is for Rally and return code
08:56:25 <morgan_orange> juhak: is it not already the case?
08:56:47 <morgan_orange> #info JURA-388 lhinds I think you fixed this issue, so JIRA could be closed
08:57:17 <morgan_orange> #info JIRA 184, 185 (parser related)
08:57:23 <morgan_orange> SerenaFeng: do you know the status?
08:57:33 <lhinds> morgan_orange: agree, trozet wanted to just keep it open to monitor, but I will poll him again to close at the end of the week
08:57:40 <juhak> morgan_orange: i think FUNCTEST-382 can be closed
08:57:43 <morgan_orange> #info JIRA 271,272 postponed to D
08:57:52 <SerenaFeng> no
08:57:58 <SerenaFeng> I will confirm it later
08:58:13 <morgan_orange> there is a non assigned JIRA due to a problem reported by joid
08:58:27 <morgan_orange> he faced issues when we list docker with none tag
08:58:35 <ollivier> #info https://jira.opnfv.org/browse/FUNCTEST-431
08:58:39 <morgan_orange> I will discuss with Jose (he is back on the 25th)
08:59:26 <SerenaFeng> none tag also happened with testapi docker
08:59:32 <SerenaFeng> strange thing
08:59:58 <viktor_t> #info FUNCTEST-377 move to D
09:00:24 <morgan_orange> #info recent JIRA 425,426,427,431 corresponds to improvements needed for C release (patchs in progress for the first ones, last one to be added to the sprint))
09:00:38 <morgan_orange> #action morgan_orange clean JIRAs
09:00:55 <morgan_orange> we will not have time for the intern discussions => let's do it offline
09:01:04 <morgan_orange> #topic Admin
09:01:50 <morgan_orange> I do not know what is the usual procedure for commiters ratio, but I would like to suggest to add SerenaFeng and ollivier as committers
09:02:11 <morgan_orange> there is an official procedure but before launching it, is there any objection?
09:02:21 <viktor_t> no :)
09:03:15 <morgan_orange> #action morgan_orange lauch commiter promotion procedure for SerenaFeng and ollivier
09:03:43 <morgan_orange> we need a +2 in Asia and every ollivier review reminds me that I should keep humble :)
09:04:01 <morgan_orange> we are alreday late
09:04:05 <morgan_orange> #topic AoB
09:04:13 <morgan_orange> any topic/question
09:04:30 <SerenaFeng> nope from my side
09:05:31 <morgan_orange> ok so main focus for Colorado (scenarios/troubleshooting/support feature project,..)...have a good week
09:05:48 <morgan_orange> happy cherry picking
09:05:53 <morgan_orange> #endmeeting