Bug 483248 - Initial erratum pushes do not populate the reporegenqueue
Summary: Initial erratum pushes do not populate the reporegenqueue
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Backend
Version: RHN Stable
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bryan Kearney
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-30 14:29 UTC by James Bowes
Modified: 2013-01-10 10:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-04 13:18:28 UTC
Embargoed:


Attachments (Terms of Use)

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


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