Bug 476801 - change default QA contact for RHN client tools bugs
change default QA contact for RHN client tools bugs
Status: CLOSED CURRENTRELEASE
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs (Show other bugs)
devel
All Linux
low Severity low (vote)
: ---
: ---
Assigned To: PnT DevOps Devs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-17 03:14 EST by Jan Hutař
Modified: 2013-06-23 22:23 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-12-17 15:29:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Hutař 2008-12-17 03:14:39 EST
Description of problem:
Please change dafault "QA Contact:" for RHN client tools bugs to RHN Satellite/Proxy QA <satellite-qa-list@redhat.com>. The components in question are:

Red Hat Enterprise Linux *:
yum-utils
rhn-client-tools
rhn-applet
rhn_register
rpmdb-redhat
redhat-rpm-config
yum-metadata-parser
rhnlib
rhnsd
rpm
up2date
yum-rhn-plugin
yum-updatesd
yum

I have not foud these packages in the BZ:
(but we do ship them in the "RHN Client Tools Channel")
jabberpy
osad
auto-kickstart
rhn-kickstart
rhn-kickstart-common
rhns-certs-tools
rhn-kickstart-virtualization
rhn-virtualization-common
rhn-virtualization-host
rhncfg
rhncfg-actions
rhncfg-client
rhncfg-management
rhn-custom-info
rhnmd


Steps to Reproduce:
1. Fill bug agains one of the package above and check "QA Contact:" field


Actual results:
?


Expected results:
RHN Satellite/Proxy QA <satellite-qa-list@redhat.com>


Additional info:
Do we need approval of somebody else for this?
Thank you in advance.
Comment 1 David Lawrence 2008-12-17 15:29:25 EST
(In reply to comment #0)
> Please change dafault "QA Contact:" for RHN client tools bugs to RHN
> Satellite/Proxy QA <satellite-qa-list@redhat.com>. The components in question
> are:
> 
> Red Hat Enterprise Linux *:
> yum-utils
> rhn-client-tools
> rhn-applet
> rhn_register
> rpmdb-redhat
> redhat-rpm-config
> yum-metadata-parser
> rhnlib
> rhnsd
> rpm
> up2date
> yum-rhn-plugin
> yum-updatesd
> yum
> 

Done. The changes will only affect new bugs. To update old bugs then select the
components using the advanced query screen, and then use the mass bug edit feature of buglist.cgi to change the current qa contacts to the default value.

> I have not foud these packages in the BZ:
> (but we do ship them in the "RHN Client Tools Channel")
> jabberpy
> osad
> auto-kickstart
> rhn-kickstart
> rhn-kickstart-common
> rhns-certs-tools
> rhn-kickstart-virtualization
> rhn-virtualization-common
> rhn-virtualization-host
> rhncfg
> rhncfg-actions
> rhncfg-client
> rhncfg-management
> rhn-custom-info
> rhnmd

Bugzilla normally goes by the source rpm names for the product components, not the binary rpm names in that case that some of these are the latter. If any of these are source rpm names and need to be added to Bugzilla then follow the directions at https://engineering.redhat.com/docbot/en-US/Internal/5.0/html/Services_Plan/sect-Engineering_Services_And_Operations-Bugzilla-Adding_and_Changing_Products_and_Components.html and we will get them added.

Dave

Note You need to log in before you can comment on or make changes to this bug.