Bug 483248

Summary: Initial erratum pushes do not populate the reporegenqueue
Product: [Retired] Red Hat Network Reporter: James Bowes <jbowes>
Component: RHN/BackendAssignee: Bryan Kearney <bkearney>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Network Quality Assurance <rhn-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: RHN StableCC: bkearney, rhn-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-02-04 13:18:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description James Bowes 2009-01-30 14:29:46 UTC
The first push of an erratum will not cause an entry to be put into the reporegenqueue for taskomatic, so we won't regenerate repodata for affected channels. Subsequent modifications of the erratum will cause an entry. however.

To Test:
 * Follow the directions at https://engineering.redhat.com/trac/rhn-hosted/wiki/CreateYourOwnErrata to create a dummy errata. Note that you can use an existing package for this.
 * Make sure to change the deployed_by email! I spammed poor thoger  
   all yesterday by accident.
 * Push your erratum to an environment. Note that the reporegenqueue is *not*  
   populated.
 * Modify the erratum (just add another channel for one of the rpms) and repush.
   Note that the queue is now populated.

Comment 1 Stephen Herr 2009-02-02 19:49:34 UTC
verified in qa, the channel refresh appeared in the queue after the first errata push.

Comment 2 Amy Owens 2009-02-04 13:18:28 UTC
pushed to prod on 2/3/09- 509 branch