Red Hat Bugzilla – Bug 483248
Initial erratum pushes do not populate the reporegenqueue
Last modified: 2013-01-10 05:01:28 EST
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.
* 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 firstname.lastname@example.org
all yesterday by accident.
* Push your erratum to an environment. Note that the reporegenqueue is *not*
* Modify the erratum (just add another channel for one of the rpms) and repush.
Note that the queue is now populated.
verified in qa, the channel refresh appeared in the queue after the first errata push.
pushed to prod on 2/3/09- 509 branch