Jump to: navigation, search

Difference between revisions of "Nova/BugTriage"

(→‎Step 2: Triage Tagged Bugs)
(A bigger reorganization of the content. The tags are now up-to-date too.)
Line 1: Line 1:
 
= Nova Bug Triage =
 
= 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.
+
The triage of Nova bugs follows the OpenStack-wide process documented on [[BugTriage]].
  
−
There is also a weekly Nova bug meeting here: [[Meetings/NovaBugScrub]] (not active currently)
+
There is an open group you need to join to get permissions to set bug priorities: https://launchpad.net/~nova-bugs
  
−
== Nova specific triaging steps ==
+
There is also a weekly Nova bug meeting here: [[Meetings/Nova/BugsTeam]]
  
−
=== Weekly bug skimming duty ===
+
= Tags  =
  
−
In short, do as much as possible before the expertise of the subteams is needed. Also, if you spot potential critical bugs, shout out in the #openstack-nova channel (for markus_z or one of the core reviewers).
+
All new bugs should be tagged to reflect which part of Nova they are related to. The current list of tags can be found below. Note that it is fine for a bug to receive more than one tag if appropriate. Launchpad Query: [https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW Untriaged Bugs Without Tags]
−
 
 
−
As a longer clarification, the duty includes:
 
−
* Switch the bug to "incomplete" when crucial information is missing and ask the reporter to provide more information. This includes:
 
−
** steps to reproduce
 
−
** the version of Nova and the novaclient (or os-client)
 
−
** logs (on debug level)
 
−
** environment details depending on the bug
 
−
*** libvirt/kvm versions, VMWare version, ...
 
−
*** storage type (ceph, LVM, GPFS, ...)
 
−
*** network type (nova-network or neutron)
 
−
 
 
−
I subscribe myself to bugs when I switch them to "incomplete" to see when responses come in. See "You are not directly subscribed to this bug's notifications." on the right hand side of a Launchpad bug report.
 
−
 
 
−
* Close as "invalid" if it is a support request or feature request.
 
−
* Switch to "confirm" if you could reproduce the described issue. This is not always possible for you because of missing resources like a ceph storage or something like that.  
 
−
* Add a tag (or more tags) if the report allows you to narrow down the area which potentially contains the issue. This should be the entry point for subteams to dig deeper to find the root cause and potential solutions.
 
−
* Bring critical bugs to the attention of the other contributors. The #openstack-nova channel and/or a ML post is useful.
 
  
 +
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. The official (and inofficial) tags are at: https://bugs.launchpad.net/nova/+manage-official-tags
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! From date !! To date !! Contributors
+
! Bug tag  !! Description !! Owner(s) !! Untriaged Query !! All Query
 +
|-
 +
| api || Bugs related to the compute REST API implementation || sdague || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+ All]
 +
|-
 +
| availability-zones || Issues when segregating resources with availability zones. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=availability-zones+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=availability-zones+ All]
 +
|-
 +
| cells || Bugs with Nova cells || alaski || [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+ All]
 +
|-
 +
| ceph || Bugs related to the ceph storage solution || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ceph+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ceph+ All]
 +
|-
 +
| cinder || Bugs related to the nova-cinder interaction. If the bug is determined to be in the upstream cinder source, the cinder project should also be added to the "Affects" list || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=cinder+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=cinder+ All]
 +
|-
 +
| compute || Bugs in the nova-compute service that are not specific to a virt driver. || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+ All]
 +
|-
 +
| conductor || Bugs in the nova-conductor service || dansmith || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+ All]
 +
|-
 +
| config || All bugs related to the config options  || [https://launchpad.net/~mzoeller markus_z] || [https://bugs.launchpad.net/nova/+bugs?field.tag=config+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=config+ All]
 +
|-
 +
| console || Bugs in the nova-console service (including nova-consoleauth, novncproxy, etc) || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+ All]
 +
|-
 +
| doc || Bugs which should affect the manuals project or nova internal docs  || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=doc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=doc+ All]
 +
|-
 +
| db || Database (datastore) issues, including migrations || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+ All]
 +
|-
 +
| ec2 || Issues specific to EC2 API support. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ec2+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ec2+ All]
 +
|-
 +
| gate-failure || Bug reports which are used to categorize failures in the gate || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure+ All]
 +
|-
 +
| hyper-v || Problems specific to the hyper-v driver || alexpilotti || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+ All]
 +
|-
 +
| i18n || Issues with internationalization || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=i18n+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=i18n+ All]
 +
|-
 +
| ironic || Problems specific to the ironic driver || jlvillal / mrda / devananda (Ironic PTL) || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+ All]
 
|-
 
|-
−
| 2016-01-07 || 2016-01-14 || cihand
+
| kilo-backport-potential || Fixes to those bugs should potentially be backported to Kilo || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-backport-potential+ All]
 
|-
 
|-
−
| 2016-01-14 || 2016-01-21 || auggy rpodolyaka
+
| kilo-rc-potential || Blocks (potentially) the release of (another) Kilo release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential+ All]
 
|-
 
|-
−
| 2016-01-21 || 2016-01-28 || markus_z, auggy,
+
| liberty-backport-potential || Fixes to those bugs should potentially be backported to Liberty || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-backport-potential+ All]
 
|-
 
|-
−
| 2016-01-28 || 2016-02-04 || <your-name-here>, <your-name-here>,
+
| liberty-rc-potential || Blocks (potentially) the release of (another) Liberty release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential+ All]
 
|-
 
|-
−
| 2016-02-04 || 2016-02-11 || auggy
+
| libvirt || Problems specific to the libvirt driver || kashyapc || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+ All]
 
|-
 
|-
−
| 2016-02-11 || 2016-02-18 || <your-name-here>, <your-name-here>,
+
| live-migration || Problems specific when doing 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]
 
|-
 
|-
−
| 2016-02-18 || 2016-02-25 || <your-name-here>, <your-name-here>,
+
| low-hanging-fruit || Should be an easy goal for new contributors || free for all || [https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit+ All]
 
|-
 
|-
−
| 2016-02-25 || 2016-03-03 || <your-name-here>, <your-name-here>,
+
| lxc || Issues specific to LXC virtualization support || [https://launchpad.net/~thomas-maddox thomasem] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+ All]
 
|-
 
|-
−
| 2016-03-03 || 2016-03-10 || <your-name-here>, <your-name-here>,
+
| mitaka-backport-potential || Fixes to those bugs should potentially be backported to Mitaka || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-backport-potential+ All]
−
|}
 
−
 
 
−
=== 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: [https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 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 [https://wiki.openstack.org/wiki/Meetings#Nova_Bug_Scrub_Meeting 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]].
 
−
 
 
−
{| class="wikitable"
 
 
|-
 
|-
−
! Bug tag !! Owner(s) !! Untriaged Query !! All Query
+
| mitaka-rc-potential || Blocks (potentially) the release of (another) Mitaka release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential+ All]
 
|-
 
|-
−
| api || sdague || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+ All]
+
| needs-attention || Bugs which came up during the bug skimming duty and further steps are unclear. || [https://launchpad.net/~mzoeller markus_z] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-attention+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-attention+ All]
 
|-
 
|-
−
| cells || alaski|| [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+ All]
+
| needs-functional-test || We need a functional test for this to avoid regression. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-functional-test+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-functional-test+ All]
 
|-
 
|-
−
| compute || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+ All]
+
| network || Issues in nova-network ||(maybe dansmith?) || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+ All]
 
|-
 
|-
−
| conductor || dansmith || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+ All]
+
| neutron || Issues with the nova-neutron-interaction. If the bug is determined to be in the upstream neutron source, the neutron project should also be added to the "Affects" list || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=neutron+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=neutron+ All]
 
|-
 
|-
−
| console || || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+ All]
+
| nova-manage || Bugs in the nova-manage utility ([http://docs.openstack.org/developer/nova/man/nova-manage.html docs]) || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+ All]
 
|-
 
|-
−
| db || || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+ All]
+
| numa || Issues where NUMA is involved  || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=numa+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=numa+ All]
 
|-
 
|-
−
| hyper-v || alexpilotti || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+ All]
+
| novaclient || 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. || melwitt || [https://bugs.launchpad.net/python-novaclient/+bugs?search=Search&field.status=New Untriaged] || [https://bugs.launchpad.net/python-novaclient All]
 
|-
 
|-
−
| ironic || jlvillal / mrda / devananda (Ironic PTL) || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+ All]
+
| ops || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ops+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ops+ All]
 
|-
 
|-
−
| libvirt || kashyapc || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+ All]
+
| oslo || Bugs related to Oslo integration (oslo-incubator or Oslo libraries). If the bug is determined to be in the upstream oslo source, the oslo project should also be added to the "Affects" list. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+ 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]
+
| pci || Bugs regarding pci-devices (includes "pci-passthrough") || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+ All]
 
|-
 
|-
−
| lxc || [https://launchpad.net/~thomas-maddox thomasem] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+ All]
+
| postgresql || PostgreSQL specific bugs. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+ All]
 
|-
 
|-
−
| network || (maybe dansmith) || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+ All]
+
| quotas || Bugs related to restricting access to resources with quotas || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=quotas+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=quotas+ All]
 
|-
 
|-
−
| nova-manage || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+ All]
+
| race-condition || Issues which are hard to reproduce due to race conditions. Probably only useful in combination with other tags. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=race-condition+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=race-condition+ All]
 
|-
 
|-
−
| novaclient<sup>1</sup> || melwitt || [https://bugs.launchpad.net/python-novaclient/+bugs?search=Search&field.status=New Untriaged] || [https://bugs.launchpad.net/python-novaclient All]
+
| resource-tracker || Issues with the tracking when and where we claim resources. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=resource-tracker+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=resource-tracker+ All]
 
|-
 
|-
−
| oslo || || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+ All]
+
| rootwrap || Problems with run-as-root commands or the rootwrap framework. || ttx || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+ All]
 
|-
 
|-
−
| pci || || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+ All]
+
| scheduler || Bugs in the nova-scheduler service || bauzas || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+ All]
 
|-
 
|-
−
| postgresql || || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+ All]
+
| security || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=security+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=security+ All]
 
|-
 
|-
−
| rootwrap || ttx || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+ All]
+
| security-groups || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=security-groups+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=security-groups+ All]
 
|-
 
|-
−
| scheduler || bauzas || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+ All]
+
| testing || Bugs related to testing (unit tests, tempest integration) || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+ All]
 
|-
 
|-
−
| testing || || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+ All]
+
| unified-objects || Bugs related to the unified-objects work || [https://launchpad.net/~danms dansmith] || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+ All]
 
|-
 
|-
−
| unified-objects || dansmith || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+ All]
+
| upgrades || Issues with upgrades from one release to another. Those are usually critical bugs! || [https://launchpad.net/~danms dansmith] || [https://bugs.launchpad.net/nova/+bugs?field.tag=upgrades+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=upgrades+ All]
 
|-
 
|-
−
| vmware || tjones || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+ All]
+
| vmware || Issues specific to VMware virtualization support. || tjones || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+ All]
 
|-
 
|-
−
| volumes || ndipanov || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+ All]
+
| volumes || Issues related to volume support (Cinder integration) || ndipanov || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+ All]
 
|-
 
|-
−
| xen || anthonyper, openstack-ci@xenproject.org || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen All]
+
| xen || Issues with the xen driver || anthonyper, openstack-ci@xenproject.org || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen All]
 
|-
 
|-
−
| xenserver || bobba || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver All]
+
| xenserver || Issues specific to XenServer/XenAPI virtualization support || bobba || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver 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.
+
= Weekly bug skimming duty =
  
−
=== Step 3: Spotting Bug "Themes" ===
+
Nova gets a lot of new bug report each day. Each bug report needs to be skimmed if it is a valid report, if crucial information is missing and so on. The weekly bug skimming duty should spread the knowledge and effort of that task to multiple people.
  
−
While the above looks at the area of the code, lets also consider tags for key bug "themes":
+
The duty includes:
−
* quotas
+
* Switch the bug to "incomplete" when crucial information is missing and ask the reporter to provide more information. This includes:
−
* availability_zones
+
** steps to reproduce
−
* live_migrate
+
** the version of Nova and the novaclient (or os-client)
 +
** logs (on debug level)
 +
** environment details depending on the bug
 +
*** libvirt/kvm versions, VMWare version, ...
 +
*** storage type (ceph, LVM, GPFS, ...)
 +
*** network type (nova-network or neutron)
 +
* Close as "invalid" if it is a support request or feature request.
 +
* Switch to "confirm" if you could reproduce the described issue or can otherwise say that this bug report seems valid. This is not always possible for you because of missing resources like a ceph storage or something like that.
 +
* Add a tag (or more tags) if the report allows you to narrow down the area which potentially contains the issue. This should be the entry point for subteams to dig deeper to find the root cause and potential solutions.
 +
* Bring critical bugs to the attention of the other contributors. The #openstack-nova channel and/or a ML post is useful.
  
−
== Bug Triage Day ==
+
In short, do as much as possible before the expertise of the subteams is needed. Also, if you spot potential critical bugs, shout out in the #openstack-nova channel (for markus_z or one of the core reviewers).
−
[[Nova/Liberty_Release_Schedule#Special_review_days|bug triage day]] is a special day per cycle where we try to shift our focus especially to bug triage.
 
  
−
=== Liberty ===
+
{| class="wikitable"
−
The "bug triage day" for liberty took place at [http://lists.openstack.org/pipermail/openstack-dev/2015-July/070904.html 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.
+
|-
−
 
+
! From date !! To date !! Contributors
−
[[File:Bug-triage-day-liberty.png|600px|thumbnail|left|source: http://status.openstack.org/bugday/]]
+
|-
 +
| 2016-01-07 || 2016-01-14 || cihand
 +
|-
 +
|  2016-01-14 ||  2016-01-21 || auggy rpodolyaka
 +
|-
 +
|  2016-01-21 ||  2016-01-28 || markus_z, auggy,
 +
|-
 +
|  2016-01-28 ||  2016-02-04 || <your-name-here>, <your-name-here>,
 +
|-
 +
|  2016-02-04 ||  2016-02-11 || auggy
 +
|-
 +
|  2016-02-11 ||  2016-02-18 || <your-name-here>, <your-name-here>,
 +
|-
 +
|  2016-02-18 ||  2016-02-25 || <your-name-here>, <your-name-here>,
 +
|-
 +
|  2016-02-25 ||  2016-03-03 || <your-name-here>, <your-name-here>,
 +
|-
 +
|  2016-03-03 ||  2016-03-10 || <your-name-here>, <your-name-here>,
 +
|-
 +
|  2016-03-10 ||  2016-03-17 || <your-name-here>, <your-name-here>,  
 +
|-
 +
|  2016-03-17 ||  2016-03-24 || <your-name-here>, <your-name-here>,
 +
|-
 +
|  2016-03-24 || 2016-03-31 || <your-name-here>, <your-name-here>,
 +
|}

Revision as of 16:05, 4 March 2016

Nova Bug Triage

The triage of Nova bugs follows the OpenStack-wide process documented on BugTriage.

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

There is also a weekly Nova bug meeting here: Meetings/Nova/BugsTeam

Tags

All new bugs should be tagged to reflect which part of Nova they are related to. The current list of tags can be found below. Note that it is fine for a bug to receive more than one tag if appropriate. Launchpad Query: Untriaged Bugs Without Tags

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. The official (and inofficial) tags are at: https://bugs.launchpad.net/nova/+manage-official-tags

Bug tag Description Owner(s) Untriaged Query All Query
api Bugs related to the compute REST API implementation sdague Untriaged All
availability-zones Issues when segregating resources with availability zones.  ? Untriaged All
cells Bugs with Nova cells alaski Untriaged All
ceph Bugs related to the ceph storage solution  ? Untriaged All
cinder Bugs related to the nova-cinder interaction. If the bug is determined to be in the upstream cinder source, the cinder project should also be added to the "Affects" list  ? Untriaged All
compute Bugs in the nova-compute service that are not specific to a virt driver. melwitt Untriaged All
conductor Bugs in the nova-conductor service dansmith Untriaged All
config All bugs related to the config options markus_z Untriaged All
console Bugs in the nova-console service (including nova-consoleauth, novncproxy, etc)  ? Untriaged All
doc Bugs which should affect the manuals project or nova internal docs  ? Untriaged All
db Database (datastore) issues, including migrations  ? Untriaged All
ec2 Issues specific to EC2 API support.  ? Untriaged All
gate-failure Bug reports which are used to categorize failures in the gate  ? Untriaged All
hyper-v Problems specific to the hyper-v driver alexpilotti Untriaged All
i18n Issues with internationalization  ? Untriaged All
ironic Problems specific to the ironic driver jlvillal / mrda / devananda (Ironic PTL) Untriaged All
kilo-backport-potential Fixes to those bugs should potentially be backported to Kilo  ? Untriaged All
kilo-rc-potential Blocks (potentially) the release of (another) Kilo release  ? Untriaged All
liberty-backport-potential Fixes to those bugs should potentially be backported to Liberty  ? Untriaged All
liberty-rc-potential Blocks (potentially) the release of (another) Liberty release  ? Untriaged All
libvirt Problems specific to the libvirt driver kashyapc Untriaged All
live-migration Problems specific when doing live migration. PaulMurray Untriaged All
low-hanging-fruit Should be an easy goal for new contributors free for all Untriaged All
lxc Issues specific to LXC virtualization support thomasem Untriaged All
mitaka-backport-potential Fixes to those bugs should potentially be backported to Mitaka  ? Untriaged All
mitaka-rc-potential Blocks (potentially) the release of (another) Mitaka release  ? Untriaged All
needs-attention Bugs which came up during the bug skimming duty and further steps are unclear. markus_z Untriaged All
needs-functional-test We need a functional test for this to avoid regression.  ? Untriaged All
network Issues in nova-network (maybe dansmith?) Untriaged All
neutron Issues with the nova-neutron-interaction. If the bug is determined to be in the upstream neutron source, the neutron project should also be added to the "Affects" list  ? Untriaged All
nova-manage Bugs in the nova-manage utility (docs) melwitt Untriaged All
numa Issues where NUMA is involved  ? Untriaged All
novaclient 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. melwitt Untriaged All
ops  ?  ? Untriaged All
oslo Bugs related to Oslo integration (oslo-incubator or Oslo libraries). If the bug is determined to be in the upstream oslo source, the oslo project should also be added to the "Affects" list.  ? Untriaged All
pci Bugs regarding pci-devices (includes "pci-passthrough")  ? Untriaged All
postgresql PostgreSQL specific bugs.  ? Untriaged All
quotas Bugs related to restricting access to resources with quotas  ? Untriaged All
race-condition Issues which are hard to reproduce due to race conditions. Probably only useful in combination with other tags.  ? Untriaged All
resource-tracker Issues with the tracking when and where we claim resources.  ? Untriaged All
rootwrap Problems with run-as-root commands or the rootwrap framework. ttx Untriaged All
scheduler Bugs in the nova-scheduler service bauzas Untriaged All
security  ?  ? Untriaged All
security-groups  ?  ? Untriaged All
testing Bugs related to testing (unit tests, tempest integration)  ? Untriaged All
unified-objects Bugs related to the unified-objects work dansmith Untriaged All
upgrades Issues with upgrades from one release to another. Those are usually critical bugs! dansmith Untriaged All
vmware Issues specific to VMware virtualization support. tjones Untriaged All
volumes Issues related to volume support (Cinder integration) ndipanov Untriaged All
xen Issues with the xen driver anthonyper, openstack-ci@xenproject.org Untriaged All
xenserver Issues specific to XenServer/XenAPI virtualization support bobba Untriaged All

Weekly bug skimming duty

Nova gets a lot of new bug report each day. Each bug report needs to be skimmed if it is a valid report, if crucial information is missing and so on. The weekly bug skimming duty should spread the knowledge and effort of that task to multiple people.

The duty includes:

  • Switch the bug to "incomplete" when crucial information is missing and ask the reporter to provide more information. This includes:
    • steps to reproduce
    • the version of Nova and the novaclient (or os-client)
    • logs (on debug level)
    • environment details depending on the bug
      • libvirt/kvm versions, VMWare version, ...
      • storage type (ceph, LVM, GPFS, ...)
      • network type (nova-network or neutron)
  • Close as "invalid" if it is a support request or feature request.
  • Switch to "confirm" if you could reproduce the described issue or can otherwise say that this bug report seems valid. This is not always possible for you because of missing resources like a ceph storage or something like that.
  • Add a tag (or more tags) if the report allows you to narrow down the area which potentially contains the issue. This should be the entry point for subteams to dig deeper to find the root cause and potential solutions.
  • Bring critical bugs to the attention of the other contributors. The #openstack-nova channel and/or a ML post is useful.

In short, do as much as possible before the expertise of the subteams is needed. Also, if you spot potential critical bugs, shout out in the #openstack-nova channel (for markus_z or one of the core reviewers).

From date To date Contributors
2016-01-07 2016-01-14 cihand
2016-01-14 2016-01-21 auggy rpodolyaka
2016-01-21 2016-01-28 markus_z, auggy,
2016-01-28 2016-02-04 <your-name-here>, <your-name-here>,
2016-02-04 2016-02-11 auggy
2016-02-11 2016-02-18 <your-name-here>, <your-name-here>,
2016-02-18 2016-02-25 <your-name-here>, <your-name-here>,
2016-02-25 2016-03-03 <your-name-here>, <your-name-here>,
2016-03-03 2016-03-10 <your-name-here>, <your-name-here>,
2016-03-10 2016-03-17 <your-name-here>, <your-name-here>,
2016-03-17 2016-03-24 <your-name-here>, <your-name-here>,
2016-03-24 2016-03-31 <your-name-here>, <your-name-here>,
Retrieved from "https://wiki.openstack.org/w/index.php?title=Nova/BugTriage&oldid=121683"