18:00:29 #startmeeting nova-bugs-team 18:00:29 Meeting started Tue Jul 26 18:00:29 2016 UTC and is due to finish in 60 minutes. The chair is markus_z. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:33 The meeting name has been set to 'nova_bugs_team' 18:00:38 o/ 18:00:46 o/ 18:01:04 hey ho, let's wait a second for others 18:01:39 #topic info round 18:01:53 #info 635 bug reports overall 18:02:03 #info 34 new untriaged bugs 18:02:10 #info no criticals 18:02:58 #info the review pipeline proposal didn't get yet attention from the cores: http://lists.openstack.org/pipermail/openstack-dev/2016-July/099096.html 18:03:24 midcycle was last week, I guess there was more important things to do 18:03:30 haha 18:03:33 I'll ping folks end of this week if we want to try that 18:03:48 was it on the agenda for discussion? 18:03:55 i don't remember if it came up 18:04:17 I added it on short notice, but it's OK, there was a lot of other things which need more attention right now 18:05:06 #info the story board folks make some progress: https://storyboard-dev.openstack.org/ 18:05:17 If you want to play around, there is a "sandbox" project 18:05:43 auggy: you got any news from the midcycle? 18:05:46 markus_z thanks for link 18:05:58 nothing bug related came up that i recall 18:06:15 it felt like a really big midcycle compared to bristol though 18:06:19 like, more people there 18:06:30 OK, I hope I can attend next time again 18:06:43 lots of topics on the table and a number of cross team items that got a lot of discussion 18:06:50 yeah me too! 18:07:16 i didn't see any new contributors there so i didn't push to have a bugs process session 18:08:11 #topic last weeks action items 18:09:03 nothing serious, to be honest. The usual cleanup and asking for more information 18:09:38 unfortunately we didn't find a volunteer to look for new bug reports 18:09:57 #topic new action items 18:10:18 so, yeah, the usual question. Anyone got some time to look at a few bug reports? 18:10:26 i can help out 18:10:36 like, bug skimming or something more? 18:10:40 eil397: If you want to help, I can assist you when you got questions 18:10:50 s/got/get 18:10:51 markus_z. I would like to help. yes 18:11:40 I can try to work with bug skimming 18:11:51 eil397_: awesome, thanks! It's basically checking https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New&orderby=-datecreated&start=0 for new stuff 18:12:14 Here's a short FAQ: https://wiki.openstack.org/wiki/Nova/BugTriage#FAQ 18:12:46 markus_z. ok . 34 in queue. : - ) 18:12:49 which timezone are you in? 18:13:05 markus_z i'm in pst 18:13:15 north cal 18:13:25 eil397_: yeah, no worries, just look at the most recent things. nobody expects you to clean that all up :) 18:13:48 markus_z. one is mine. it means only 33 in queue : - ) 18:13:54 eil397_: OK, then I hope auggy will assist you when I'm in my bed? 18:14:01 sure! happy to 18:14:05 i'll work on some as well 18:14:17 auggy I will appreciate : - ) thanks 18:14:29 :) 18:14:45 which one is yours? just out of curiosity. 18:15:01 https://bugs.launchpad.net/nova/+bug/1605742 18:15:01 Launchpad bug 1605742 in OpenStack Compute (nova) "Unexpected API Error. TypeError. Code: 500. os-keypairs v2.1 " [Undecided,New] 18:15:19 markus_z catch this on CI 18:15:42 s\catch\caught\g 18:16:03 markus_z . just Paramiko2.0 with mitaka. 18:16:06 Ah, very good one. The "unexpected API error", you will see that often in the next days :) 18:16:24 i just skimmed it, looks like someone responded 18:16:31 markus_z. yeaah. I assumes that 99% of them are invalid : - ) 18:16:32 also they didn't mark it as a duplicate even though the mentioned it 18:16:53 oh wait that was you 18:16:53 haha 18:17:07 * auggy confused irc and launchpad names 18:17:17 auggy: not yeat 18:17:18 eil397_: no, not necessarily, but very unspecific. That's the "something went wrong" issue besides the "no host found" error message. 18:18:06 auggy : - ) I was nto sure who can amrk it as duplciated : - ) 18:18:08 I'm going to check that report tomorrow and can give you hints how to improve the report so that you get help faster. 18:18:30 markus_z cool. thanks 18:19:01 If you don't have "Mark as duplicate" on the top right corner, you need to be part of the nova bugs team LP group. 18:19:13 * markus_z looks for the link 18:19:47 #link https://launchpad.net/~nova-bugs 18:19:54 it's not entirely a duplicate because the other bug was for newton 18:20:03 and this one is about backporting the compatibility change to mitaka 18:20:37 markus_z: I don't have "Mark as duplicate" 18:20:48 i think the next step is to find out if Paramiko compatability was an issue in mitaka and if so, see what steps are necessary to resolve that issue 18:21:06 eil397_: Then you need to use https://launchpad.net/~nova-bugs and subscribe there 18:21:35 #action markus_z check https://bugs.launchpad.net/nova/+bug/1605742 for better bug report description 18:21:35 Launchpad bug 1605742 in OpenStack Compute (nova) "Unexpected API Error. TypeError. Code: 500. os-keypairs v2.1 " [Undecided,New] 18:21:36 markus_z: ok. thanks. 18:22:06 markus_z: I will subscribe 18:22:11 #action eil397_ does the bug skimming (auggy and markus_z support when necessary) 18:22:11 i wouldn't mark this one as a duplicate of that bug 18:22:31 the issue is more like, backport paramiko compatiblity fix to mitaka 18:22:33 auggy: I'm sure that mitaka nova is not compatible. because i 18:23:08 i've checked it in source code. 18:23:52 auggy: not sure about policy. is it possible to backport from newton to mitaka ? 18:24:10 eil397_: yes, we have a tag for bugs that fall into that category 18:24:21 auggy: ok. cool. thanks. 18:24:42 auggy: looks like i need to study categories : - ) 18:25:22 before this can be confirmed, someone other that the person who reported needs to verify 18:25:22 eil397_: The categories are these: https://wiki.openstack.org/wiki/Nova/BugTriage#Tag_Owner_List 18:25:52 auggy: tyvm for link. 18:26:14 markus_z: you don't happen to know if the paramiko issue is in mitaka? i'm surprised it hasn't shown up in the gate before if so 18:26:36 auggy: does it mean that when/if someone will confirm it, it will be possible to start work on bacpport/cherrypick commit from newton ? 18:26:58 yes, but it goes through 2 stages 18:27:00 I think I remember something from half a year ago, but nothing current 18:27:07 1) skimming, which is confirming the bug is a problem 18:27:12 and reproduceable 18:27:29 auggy: paramiko20 with mitaka will not appear in gate becasue of requirements. right now there is upper constrain for it 18:27:29 2) triage, where a subteam does root cause analysis and prioritiezes it 18:28:12 auggy: ok. 18:28:33 let's just do the last agenda point and wrap up the meeting 18:28:41 #topic open round 18:29:11 Anyone has anything for the "big" round? 18:29:37 i don't have anything for "bug"round. 18:30:06 FWIW, I need 2 days to work on a "serial console" thing in Nova and have hopefully the Friday for bug reports. 18:30:49 eil397_: I'm in the timezone UTC+1, in case you're an early bird. 18:31:01 OK, closing in 3... 18:31:10 markus_z: ok .I'm early bird 18:31:22 markus_z:have a good evening 18:31:35 auggy: have a good one 18:31:36 thanks, have a good day you both 18:31:41 thanks! you all too! 18:31:51 next meeting August 2nd (Tuesday) 0800 UTC, #openstack-meeting-4 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160802T080000) 18:31:59 #endmeeting