Note that the errata packages themselves are visible in the relevant channels if any systems attempt updates.
Fixed in rev 134979. Please note that this was a data population issue, so the fix will only work for any NEW errata.
verified
this still happens on stage ISO FAILS_QA
Guys, do we have a target release for the resolution of this bug? Thanks Marko
oops, outdated page. ignore my last comment please.
fixed for trunk in 171331. for 5.1 in 171332.
some additional errata fixes in rev 171720.
and backported to 5.1 branch in 171804.
To Qa, I made some change to the base code, so please test if possible all ways of publishing errata 1. Api call errata.clone() & errata.publish() 2. Web page channels->manage software channels->(custom channel name)-> errata->add-> add Red hat Errata 3. Errata->create->publish 4. Errata->clone Thanks, Justin
Flip from ON_DEV to MODIFIED. MASS move for Sat bugs.
fails_qa 1. Create a new erratum and attach a package 2. Publish the erratum 3. go to Errata -> All and select the new erratum, the select Packages
looking into this....
checked in fix in rev 172848 and backported in rev 172849.
Verified on 511. Behavior seems to handle common use case. But package only shows up when channel is modified by adding a package. Cloning a channel and adding a package already existing in the channel to the errata causes the package to show up when modifying the errata but not when looking at the errata from the ALL errata page.
5.1.1 Satellite is now GA, bugs Closed for Current Release.