Bug 707658

Summary: wrong errata cache when cloning errata
Product: Red Hat Satellite 5 Reporter: Tomas Lestach <tlestach>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED ERRATA QA Contact: Šimon Lukašík <slukasik>
Severity: high Docs Contact:
Priority: high    
Version: 540CC: cperry, jhutar, slukasik
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-java-1.2.39-82 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-17 02:32:07 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:
Bug Depends On:    
Bug Blocks: 677501    

Description Tomas Lestach 2011-05-25 16:24:16 UTC 
Description of problem:
When cloning errata, newly generated cache contains the original erratum, not the clone.

Version-Release number of selected component (if applicable):
sat54

How reproducible:
always

Steps to Reproduce:
1. sync a rhel channel
2. create custom channel and set this custom channel as base of a your system
3. push some packages into the custom channel, for them there's an errata update (from the rhel channel) and make sure your system has the non-errata packages installed
4. Add Red Hat Erratum into your custom channel using the 
<custom_channel> - Errata - Add Red Hat Errata
page that contains upgrades for the packages in the custom channel
5. Check <system> - Software - Errata page

Actual results:
Very baaad.
In the errata list, that shall be applicable to your system you see the original Red Hat erratum (that isn't accessible for the system, because it's not pushed into the custom channel)
I better do not try to apply the erratum to the system.

Expected results:
I'd like to see the clone erratum in the system applicable errata list.
Comment 1 Tomas Lestach 2011-05-25 16:33:34 UTC 
spacewalk.git: 6e2282aa431e12e66e6d202956695550822568e8
Comment 7 Šimon Lukašík 2011-05-30 07:33:53 UTC 
Moving to Verified:

Testing procedure:
As per comment 0. Comparing the id of resulting errata.
They are same with with spacewalk-java-1.2.39-80.el6sat.noarch
They are distinct with spacewalk-java-1.2.39-82.el6sat.noarch

Verified against:
spacewalk-java-1.2.39-82
Comment 8 Milan Zázrivec 2011-06-01 09:38:24 UTC 
Verified in stage according to the procedure in initial comment
w/ spacewalk-java-1.2.39-82 -> release pending.
Comment 9 Clifford Perry 2011-06-17 02:32:07 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

https://rhn.redhat.com/errata/RHSA-2011-0879.html