14:30:46 <debrascott> #startmeeting Brahmaputra Daily Standup 14:30:46 <collabot> Meeting started Fri Feb 12 14:30:46 2016 UTC. The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:46 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:46 <collabot> The meeting name has been set to 'brahmaputra_daily_standup' 14:30:57 <debrascott> #link agenda https://wiki.opnfv.org/releases/brahmaputra/minutes 14:31:05 <debrascott> #topic roll call 14:31:15 <narindergupta> #info narindergupta 14:31:24 <narindergupta> #info Narinder Gupta 14:31:26 <morgan_orange> #info Morgan Richomme 14:31:34 <anac1> #info Ana Cunha 14:31:44 <radez> #info Dan Radez 14:32:28 <debrascott> #info Monday is a US holiday, no meeting 14:33:17 <debrascott> #topic Status- what are you doing in the next 24 hours? Will you work the weekend? 14:33:38 <debrascott> morgan_orange: functest? 14:34:19 <morgan_orange> #info functest regression on apex scenario: no more ext network detected 14:34:31 <morgan_orange> #info functest vPing still pending 14:34:55 <morgan_orange> #info functest now almost all scenario are reproducible, still too high Tempest error rate on fuel 14:35:00 <debrascott> morgan_orange: can you provide jira #’s please? 14:35:06 <morgan_orange> for what? 14:35:14 <[1]JonasB> #info Jonas Bjurel 14:35:39 <radez> morgan_orange: is that from the latest daily? 14:35:46 <debrascott> morgan_orange: for any issues/bugs you are working, 14:35:55 <morgan_orange> radez: yest just see it a few minutes ago 14:36:08 <morgan_orange> https://build.opnfv.org/ci/job/apex-daily-brahmaputra/ 14:36:33 <debrascott> morgan_orange: we are going to begin tracking top issues to closure 14:36:49 <morgan_orange> debrascott: so I should create a Jira per remaining issue? 14:36:50 <jose_lausuch> radez: I had problems yesterday evening with the deploymetn, so I Couldnt troubleshoot vping 14:37:18 <radez> jose_lausuch: I think that another verify ran and tore down the undercloud machine 14:37:32 <jose_lausuch> ok 14:37:37 <debrascott> morgan_orange: are you working the issues without Jira tickets? How are you using Jira? 14:37:45 <radez> I wasn't able to get back to work with you on it, I'm sry it you spent too much time on it 14:38:43 <morgan_orange> debrascott: yes we are using Jira 14:38:50 <bin_> #info Bin Hu 14:41:09 <debrascott> morgan_orange: so we said yesterday that we would begin providing jira tickets for the issues in the meeting starting today. This is to ensure we are tracking top issues to closure 14:41:25 <trevor_intel> #info Trevor Cooper 14:42:05 <morgan_orange> debrascott: if Jira helps solving problem, no problem I will create a Jira 14:42:29 <[1]JonasB> There is a Jira plugin for that 14:43:04 <debrascott> morgan_orange: dont want to create extra work- just want things you are tracking in Jira 14:43:27 <debrascott> JonasB: you mean plugin for irc? 14:43:30 <morgan_orange> debrascott: got teh point I will create the jira for the remaining problems and send you the reference 14:43:59 <debrascott> morgan_orange: thank you, appreciate it 14:45:26 <debrascott> JonasB: or plugin for something else in Jira? 14:46:19 <debrascott> morgan_orange: will the functest team be working the weekend? 14:46:42 <morgan_orange> debrascott: no 14:46:50 <debrascott> thanks 14:47:00 <debrascott> anac1: yardstick? 14:47:01 <morgan_orange> debrascott: CI will work for us 14:47:18 <debrascott> morgan_orange: :) 14:47:38 <anac1> #info yardstick team got reinforced with ODL expert to work on the scenario 14:48:10 <anac1> #info instability on various scenarios - works once, stops, works, and so on 14:48:48 <anac1> #info work on-going for grafana - db reinstalled in new server 14:49:10 <anac1> #info work on-going for result documentation as requested 14:49:20 <debrascott> anac1: jira ticket #s? 14:50:05 <morgan_orange> #info functest new look & feel for the dashboard http://testresults.opnfv.org/dashboard 14:50:09 <anac1> debrascott: i have no time, will try - can't compromise (have open bugs) 14:50:44 <debrascott> anac1: I understand. Was just asking if you had them per yesterdays call 14:50:50 <anac1> morgan_orange: nice 14:51:01 <anac1> debrascott: no 14:51:21 <anac1> will do what i can 14:51:28 <debrascott> anac1: thank you 14:52:27 <debrascott> morgan_orange: cool! 14:52:30 <anac1> radez: last run - got "error validating value "external" 14:53:00 <radez> anac1: same in functest, we moved the externl network to the service tenant and it seems not to validate now, I'm look at it now 14:53:04 <anac1> narindergupta: odl l2 no longer works on orange pod2 14:53:13 <anac1> radez: k 14:53:24 <narindergupta> anac1: it should as it was working on last deployment 14:53:35 <narindergupta> anac1: is there any new deployment? 14:54:26 <narindergupta> anac1: last deployment was success https://build.opnfv.org/ci/view/joid/job/joid-deploy-orange-pod2-daily-master/111/console 14:55:08 <morgan_orange> narindergupta: deployement without test run after? 14:55:18 <anac1> narindergupta: scenario is red 14:55:26 <morgan_orange> last tests (functest and yardstick) are form yesterday with the stop of docker daemon on the jumphost 14:55:59 <morgan_orange> 111 scenario is an old one... 14:56:20 <narindergupta> morgan_orange: do we have new one? I am not seeinf UI. 14:56:22 <morgan_orange> anac1: narindergupta I restart the full sequence and we should plan something for the week end to run several times in a raw 14:56:39 <morgan_orange> narindergupta: no new deployment since yesterday 14:56:52 <narindergupta> morgan_orange: then 111 is latest 14:56:58 <anac1> morgan_orange: will you include yardstick ? 14:57:18 <morgan_orange> anac1: of course 14:57:27 <anac1> morgan_orange: ty 14:57:38 <[1]JonasB> #info For fuel most of the scenarios have 2 successful consecutive runs, some 3. Fixed the issue for the KVM and SFC scenarios which will hopefully run over the week-end. 14:57:59 <narindergupta> anac1: i want to make sure we setup deploying of maas as well in loop to have more regression 14:58:00 <[1]JonasB> #info issue with pdf rendering of docs. 14:58:03 <debrascott> JonasB: ty radez: Apex? 14:58:12 <[1]JonasB> end 14:58:27 <[1]JonasB> Is anyone looking at the rendering issues? 14:58:45 <anac1> narindergupta: ok 14:58:52 <radez> #info Apex will be working on the external network regression and continuing the vping investigation with jose_lausuch. 14:58:56 <narindergupta> morgan_orange: anac1 thanks 14:59:03 <radez> #info we closed out a few of our jira tickets yesterday 14:59:30 <anac1> radez: any time for yardstick next week ? 14:59:48 <debrascott> radez: Can you provide jira tickets for the top issues you are still working? 14:59:49 <radez> anac1: yes! 14:59:56 <anac1> radez: ty 14:59:59 <radez> debrascott: tickets already exist 15:00:16 <debrascott> radez: I mean for the meeting minutes 15:00:55 <debrascott> JonasB: likewise, can you provide jira ticket #s for your top issues? 15:01:08 <radez> #info APEX-69,81,84,94,95 15:01:18 <debrascott> radez: thank you 15:01:38 <[1]JonasB> Yes I will in the release status page for Fuel. 15:01:58 <debrascott> JonasB: looks like nobody else is seeing rendering issues, let us know if you continue seeing that 15:02:04 <debrascott> JonasB: thank you 15:02:26 <[1]JonasB> #link https://wiki.opnfv.org/fuel_opnfv/b_release_status 15:02:34 <debrascott> OK top of the hour. Please remember to add jira #s as part of your status from now on 15:03:05 <debrascott> Also, if anyone didn’t get to add your status today, please email or add them to this channel as I monitor 15:03:23 <debrascott> I wil add them to the daily status update then 15:03:31 <debrascott> Thanks for attending 15:03:53 <debrascott> #info No meeting on Monday, US holiday 15:04:06 <debrascott> #endmeeting