18:00:27 <auggy> #startmeeting nova-bugs-team 18:00:28 <openstack> Meeting started Tue May 31 18:00:27 2016 UTC and is due to finish in 60 minutes. The chair is auggy. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:30 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:32 <openstack> The meeting name has been set to 'nova_bugs_team' 18:00:38 <auggy> o/ 18:00:42 <pumaranikar> o/ 18:00:44 <siva_krishnan> o/ 18:01:10 <auggy> small group today! this should be pretty quick :) 18:01:27 <raj_singh> o/ 18:01:36 <auggy> the first thing is just a reminder that we need help with bug skimming duty this week 18:01:43 <auggy> https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty 18:01:47 <auggy> #link https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty 18:02:06 <siva_krishnan> me adn pumaranikar will be doing that for this week 18:02:16 <auggy> great! thanks! 18:02:16 <pumaranikar> +1 siva_krishnan 18:02:16 <siva_krishnan> *and 18:02:20 <claudiub> o/ 18:02:38 <auggy> how is that going? do you have any questions so far about bug skimming or any issues you've run into? 18:03:19 <pumaranikar> auggy, not right now. we will ping if needed 18:03:26 <auggy> ok great, feel free to reach out 18:03:37 <auggy> i'm on US Pacific time and markus_z is on CET 18:03:55 <pumaranikar> auggy, ok 18:04:04 <auggy> the next thing is just a reminder that if you're looking for other ways to help out, we have the bug maintenance stuff 18:04:06 <auggy> http://45.55.105.55:8082/bugs-dashboard.html 18:04:39 <auggy> i think the formal thing to do is update the etherpad if you pick one up, but most of them are pretty quick 18:05:03 <pumaranikar> auggy, we did refer this in our last skimming duty 18:05:08 <auggy> great 18:05:34 <auggy> also some additional useful queries are in the Meetings wiki: https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam#Queries 18:05:41 <auggy> along with instructions on what to do with each of those 18:05:50 <auggy> i should probably move that to the main wiki page :) 18:06:52 <auggy> so the next thing, did any noteworthy items come up from skimming this past week? 18:07:44 <auggy> i'll take the silence as a negative :) 18:08:05 <raj_singh> well there were some bugs which I didn't know how to verify, so I just made sure that bug had enough info otherwise marked it as incomplete 18:08:28 <auggy> raj_singh: perfect, if there's not enough info for you to reproduce it then definitely mark it as incomplete 18:08:38 <auggy> just make sure it gets marked as new again if the OP updates it 18:08:52 <raj_singh> auggy: alright 18:09:08 <raj_singh> auggy: One Q 18:09:12 <auggy> sure! 18:09:26 <raj_singh> When and who decides the importance of a bug, like high, low? 18:09:47 <auggy> the triage team 18:10:02 <auggy> the point of skimming is to verify and tag the bug so it gets to the triage team 18:10:15 <raj_singh> auggy: ahhh, got it. 18:10:19 <auggy> the triagers can then investigate root cause and make a decision 18:10:26 <auggy> we just try to help out to spread the work load 18:10:45 <auggy> oh another thing, if you can't verify a bug because you don't have the right setup or whatever, you can tag it as "needs-attention" 18:11:18 <auggy> so for instance if someone is having an issue with ceph and you don't have an instance with ceph set up to verify, you can tag as "ceph" and "needs-assistance" with a comment that you need someone to verify it that has a ceph setup 18:11:33 <pumaranikar> auggy, ok. didn't know that :) 18:11:53 <auggy> sorry "needs-attention", not "needs-assistance" 18:12:28 <auggy> yeah we set that up specifically so we could get skimming help from others that might have those things set up 18:13:03 <raj_singh> auggy: What is your usual setup to reproduce most of bugs? 18:13:18 <auggy> raj_singh: i have a basic default devstack i spin up 18:13:27 <raj_singh> 2 node cluster? 18:13:40 <auggy> depends on the bug, usually just 1 node barebones basic setup 18:13:50 <raj_singh> ok 18:13:51 <auggy> if it's something networking related i'll turn on neutron 18:14:12 <auggy> or if the reporter specifically says it's an issue with a multinode setup then i might do that 18:14:38 <auggy> but yeah depends on the bug 18:14:47 <raj_singh> ok thx 18:15:17 <auggy> i'm currently learning how to use a tool that the gate uses called devstack-gate 18:15:31 <auggy> it lets you spin up a devstack that looks exactly like what one of the gate tests uses 18:15:51 <auggy> so once i have some idea of how to do that i can share that to see if that's useful for doing bug reproduction 18:15:54 <raj_singh> auggy: nice, it will be good to have that info in wiki, one you know it 18:16:03 <raj_singh> s/one/once 18:16:21 <auggy> yeah, i know sometimes to reproduce a bug i end up speding like 2 days figuring out how to configure my devstack to do what they are doing ;) 18:16:29 <pumaranikar> +1 raj_singh 18:16:42 <raj_singh> auggy: that is why I was asking about your setup. 18:16:46 <siva_krishnan> +1 raj_singh 18:17:02 <auggy> alright so the only other thing i had was a reminder that we have a team etherpad with some bug related projects on it - https://etherpad.openstack.org/p/nova-bugs-team 18:17:31 <auggy> i'm not sure about the status of some these since i didn't add them, but they are mostly just ideas for how to improve bug management 18:17:47 <auggy> so if you are looking for other things to do, there might be items in here worth exploring 18:18:46 <auggy> i don't have anything else for today's meeting, does anyone else have anything? 18:18:53 <auggy> #topic open discussion 18:20:10 <auggy> alright well i'll take that as no one has anything else 18:20:23 <auggy> thanks to everyone who is helping out, and remember feel free to reach out via irc or email if you have any questions 18:20:39 <raj_singh> auggy: Thx 18:20:42 <siva_krishnan> thanks auggy! 18:20:43 <pumaranikar> yes. thanks auggy . 18:21:01 <auggy> #endmeeting