Jump to: navigation, search

Difference between revisions of "Nova/BugTriage"

(adds "pci")
(add "live-migration" as new subteam)
Line 51: Line 51:
| libvirt || kchamart, directxman12 || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+ All]
| libvirt || kchamart, directxman12 || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+ All]
| live-migration || PaulMurray || [https://bugs.launchpad.net/nova/+bugs?field.tag=live-migration+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=live-migration+ All]
| lxc || zul || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+ All]
| lxc || zul || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+ All]

Revision as of 16:50, 6 November 2015

Nova Bug Triage

The triage of Nova bugs follows the OpenStack-wide process documented on BugTriage. Since Nova is such an active project with a high number of incoming bug reports, we have a separate process for categorizing bugs and distributing the load of triage to a larger group of people.

There is also a weekly Nova bug meeting here: Meetings/NovaBugScrub (not active currently)

Nova specific triaging steps

Step 0: Join nova-bugs team

There is an open group you need to join to get permissions to set bug priorities: https://launchpad.net/~nova-bugs

Step 1: Tagging

All new bugs should be tagged to reflect which part of Nova they are related to. The current list of tags can be found on BugTags. Note that it is fine for a bug to receive more than one tag if appropriate.

Launchpad Query: Untriaged Bugs Without Tags

Anyone is welcome to help with tagging bugs. However, the nova bug scrub team has committed to checking this on a regular basis to keep the untagged bug queue under control. See the meeting link for more information

Step 2: Triage Tagged Bugs

Once new bugs have been tagged, they should be triaged as described on BugTriage. To help make sure that the triage queue stays under control, the following table lists the people that have committed to regularly triaging bugs for a given tag. For a description of each tag, see BugTags.

Bug tag Owner(s) Untriaged Query All Query
api Untriaged All
baremetal devananda Untriaged All
cells alaski Untriaged All
compute melwitt Untriaged All
conductor dansmith Untriaged All
console Untriaged All
db Untriaged All
docker ewindisch Untriaged All
ec2 zul Untriaged All
hyper-v alexpilotti Untriaged All
ironic jlvillal / mrda / devananda (Ironic PTL) Untriaged All
libvirt kchamart, directxman12 Untriaged All
live-migration PaulMurray Untriaged All
lxc zul Untriaged All
network Untriaged All
nova-manage melwitt Untriaged All
novaclient1 melwitt Untriaged All
oslo wendar Untriaged All
pci Untriaged All
postgresql Untriaged All
rootwrap ttx Untriaged All
scheduler bauzas Untriaged All
testing wendar, jogo, and others Untriaged All
unified-objects dansmith Untriaged All
vmware tjones Untriaged All
volumes ndipanov Untriaged All
xen anthonyper, openstack-ci@xenproject.org Untriaged All
xenserver bobba Untriaged All

1. novaclient bugs exist in their own project on launchpad, python-novaclient. They are not tagged bugs in the nova project. However, we still need one or more people signed up to make sure novaclient bugs get triaged and looked after.

Step 3: Spotting Bug "Themes"

While the above looks at the area of the code, lets also consider tags for key bug "themes":

  • quotas
  • availability_zones
  • live_migrate

Bug Triage Day

bug triage day is a special day per cycle where we try to shift our focus especially to bug triage.


The "bug triage day" for liberty took place at August the 5th, one week before the bug review day. The results are below. We did a good job to prioritize "undecided" bugs, which is a good thing for the following bug review day. We could also reduce the "new" bugs, which could have the potential to be serious issues.