Bug Tags

Note: This page should be kept in sync with each PROJECT official tags (see https://bugs.launchpad.net/PROJECT/+manage-official-tags)

All projects

 * low-hanging-fruit: Bugs that are easy to fix, ideal for beginners to get familiar with the workflow and to have their first contact with the code in OpenStack development.
 * documentation: Bug is about documentation or has an impact on documentation.
 * i18n: Translations / i18n issues.
 * security: Fix for the bug would make OpenStack more resilient to future security issues.
 * ops: Fix for the bug would significantly ease OpenStack operation.
 * SERIES-rc-potential: During the SERIES pre-release period, mark the bug as a potential release-critical blocker
 * SERIES-backport-potential: Mark the bug as a potential backport target to a specific SERIES (grizzly, havana...)

Nova
This section got moved to Nova/BugTriage

Neutron
This section has been moved here

Cinder

 * rootwrap: Problems with run-as-root commands or the rootwrap framework.

Horizon
Horizon bug tags are basically related to backend OpenStack projects.


 * ux: User experience issues.
 * horizon-core : related to horizon modules (not specific to openstack_dashboard) (it seems horizon now. Which is better?)
 * dashboard-core : OpenStack dashboard general issues
 * i18n : I18N or translation related issues in Horizon which is common to multiple languages.
 * translation : translation bugs in each language. It is actually not a bug of Horizon. It is to track translation bugs until I18N team decides the bug triaging policy.


 * nova : Instance (mainly Nova) related
 * image : Image related (not limited to glance)
 * volume : Volume related (not limited to cinder)
 * sg-fip : Security Group or Floating IP related (if specific to neutron neutron tag is also recommended)
 * keystone : Identity and user management related
 * neutron : Network panel related issues (including lbaas, fwaas, vpnaas)
 * topology-view : Topology panel related issues
 * heat : Heat (Stack panel) related
 * swift : Swift (Container panel) related
 * ceilometer : Ceilometer (Resource Usage) related
 * trove : Database panel related
 * sahara: Data processing panels related

Glance

 * api: API, request validation and WSGI routing issues.
 * cli: CLI caused by server request/response handling.
 * db: Database (datastore) issues, including migrations.
 * domain/proxy: Issues about the middle domain/proxy layer of v2.
 * gate: Issues affecting/blocking the gate.
 * propose-close : Tagged with meaningful bug comment to to indicate bugs that probably should be closed but need a little more review.
 * task: Issues about async tasks.
 * metadef: Issues about metadata definitions. can be combined with above tags for more specificity (e.g. api, db, etc).
 * testing: Only tests related.
 * ntt: Related to/ Directly affects the ntt team.
 * security: Self explanatory.
 * ops: Self explanatory.
 * cache: Self explanatory.
 * catalog-index-service: Related to the Catalog Index Service service.
 * low-hanging-fruit: A simple bug that does not have any (or has only tiny) impact.
 * documentation: Self explanatory.
 * kilo-rc-potential: Proposed to potentially be back-ported to Kilo release.
 * juno-backport-potential: Proposed to potentially be back-ported to Juno release.
 * icehouse-backport-potential: Proposed to potentially be back-ported to Icehouse release.
 * i18n: Related to Internationalization and localization.
 * artifacts: Related to the Artifacts service.
 * scrubber: Related to the Glance scrubber module(s).

Ironic

 * api: related to the REST API or the ironic-api service
 * conductor: related to the ironic-conductor service
 * db: bugs in the data structure, db api, or migration code
 * nova-driver: related specifically to the nova.virt.ironic driver and our integration with Nova
 * ipmi: related to ipmi drivers (ipmitool and ipminative)
 * pxe: related specifically to the PXE driver
 * agent: related to ironic-python-agent or its driver
 * driver: related to other drivers, the use of drivers, the driver API, etc. Basically, anything not specific to a single driver but still related to drivers.
 * oslo: related to the use of oslo common libraries or oslo-incubator code. If the bug is determined to be in the upstream oslo source, the oslo project should also be added to the "Affects" list.

Murano

 * agent: Murano-agent-related issues
 * api: REST api related issues
 * cli: Issues related to command-line interface
 * client-library: issues related to python-muranoclient use as a library
 * dashboard: Murano-dashboard related issues
 * db: Database (datastore) issues, including migrations.
 * engine: Murano-engine related issues
 * gate: Issues affecting/blocking the gate. (already used in Glance)
 * muranopl: bugs related to MuranoPL and core library
 * tests: bugs related to issues in tests and test infrastructure

TripleO
The list of tags is over there.