Red Hat Bugzilla – Bug 1264674
Create oVirt team custom field.
Last modified: 2016-01-19 17:34:39 EST
This should be added to both oVirt classification and the RHEV product.
Internal Name: cf_ovirt_team
Description: oVirt Team
Long Description: This records what vertical team is working on the bug.
Updated long description:
When opening bugs or RFEs on oVirt, if you don't set the oVirt team in the bug, these bugs go through some initial scrubbing mechanism, to determine which vertical is responsible for them.
However, in most cases the one opening the bug should be able to know what team it is related to. In some cases the issues are in between verticals, but in such case they can be set to one, and worst case they will be moved to another vertical, if needed.
The main values are:
• Network - network issues either originated by the host, or the engine.
• Storage - storage related issues, either originated by the host, or the engine.
• Spice - spice/virt-viewer related issues.
∘ Authentication issues.
∘ General DB issues (not ones related to specific vertical flow).
∘ Host monitoring/communication issues, host statuses, etc.
∘ Host deployment/upgrade issues.
∘ Certificate issues.
∘ engine-config issues.
∘ engine-notifier issues.
∘ Fencing issues.
∘ Scale issues.
∘ Satellite/Foreman integration issues.
∘ General REST-API issues (not ones related to specific vertical flow).
∘ Python SDK, Java SDK and CLI issues.
∘ IOPROCESS / python-pthreading / python-cpopen issues.
• Reports - Reports engine issues.
• DWH - Data warehouse issues.
∘ Engine-related SLA issues (CPU / network / storage QOS).
∘ Scheduling and load balancing issues.
∘ Placement related issues.
∘ CPU pinning.
∘ hosted engine HA issues.
∘ HA VMs issues.
∘ ovirt-node issues.
∘ oVirt appliance.
∘ VM issues.
∘ Emulated machine errors.
∘ VM console issues (VNC, SPICE, serial console).
∘ templates / instance-types issues.
∘ VM import/export, conversion via virt-v2v integration.
∘ VM life-cycle issues.
∘ general ovirt-guest-agent issues.
∘ VM Pools.
∘ engine-setup / upgrade / cleanup issues (not ones related ot other vertical rfes / flows).
∘ engine-backup / restore issues.
∘ iso/image-uploader issues.
∘ log collector issues.
∘ hosted engine setup / upgrade issues (not ones related ot other vertical rfes / flows).
∘ windows guest agent install/update issues (not virtio / spice / guest agent issues).
∘ DWH & Reporting setup / upgrade / cleanup issues.
∘ ovirt-live issues.
∘ ovirt releng issues (unless releng should be used for upstream too).
∘ debian packaging issues.
∘ CentOS Virt SIG packaging issues.
∘ General UX issues (not ones related to specific vertical flow).
∘ UI plugins.
• i18n - translation issues (i.e. issues that require a translation update, not an English-text update).
• Gluster - gluster issues.
• Docs - documentation issues.
• Rel-Eng - Anything related to product release engineering (tagging / Brew / etc).
• Sub-Eng - anything related to Red Hat support plugin.
• External - Anything that depends on another team not covered in the list above.
The long description field can't be THAT long.
The best I can do is add it to the field help page:
Is that OK?
(In reply to Matt Tyson from comment #2)
> The long description field can't be THAT long.
> The best I can do is add it to the field help page:
> Is that OK?
Field definition created.
TODO: Work with admins to populate the table when it is deployed.
QA environment(bzperfweb01.app.qa) with version(4.4.10042-1, DB: psql)
The selectable value in the custom field is only "---", seems missed the configuration of setting the selectable value.
(In reply to Rony Gong from comment #5)
> The selectable value in the custom field is only "---", seems missed the
> configuration of setting the selectable value.
As stated in comment 4, this will be done manually by the bugzilla admins once the code has gone live.
Seems I missed the link "Edit legal values for this field. " in the custom field page in the before, and we could use it to add selectable values.
Thanks for this! When will this be release?
It was going to be released about a month ago, but the database upgrade process failed.
We'll make another attempt with the next Bugzilla release. A date is yet to be scheduled, hopefully soon.
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.
The help was cut for some reason and some items are missing like network\storage.