Description of problem: Cloning erratum to cloned child channel (as original state, no errata) makes Packages -> Compare hide all differences Version-Release number of selected component (if applicable): Satellite-5.7.0-RHEL6-re20150108.2 How reproducible: always Steps to Reproduce: 1. Sync rhel-x86_64-server-7 and rhn-tools-rhel-x86_64-server-7 (in tools channel there is 62 packages and 11 erratas) 2. Clone tools channel with "Original state of the channel (no errata)" (now you have 0 packages and 0 erratas in it) 3. Check how it differs from its source channel: Channels -> Manage Software Channels -> clone-rhn-tools-rhel-x86_64-server-7 -> Packages -> Compare -> Compare to: rhn-tools-rhel-x86_64-server-7 -> -> click to [View Packages] => no differences (FAIL) 4. Add some package Channels -> Manage Software Channels -> clone-rhn-tools-rhel-x86_64-server-7 -> Packages -> Add -> python-rhsm-1.13.2-1.el7.x86_64 -> [Add Package(s)] -> -> [Confirm Addition] 5. Check how it differs from its source channel => only 26 differences is shown (FAIL, should be 61 if I understand it correctly: 62 packages in source channel - 1 already added to the clone) 6. Clone one of the erratas Channels -> Manage Software Channels -> clone-rhn-tools-rhel-x86_64-server-7 -> Errata -> Clone -> mark all erratas there as "Do nothing" and only set RHEA-2014:1364 as "Clone as..." -> [Clone Errata] -> [Update Errata] 5. Check how it differs from its source channel => no differences is shown (FAIL) Actual results: "Compare" page does not behave as I expect it to behave. Expected results: IMO if channels do not have identical package sets, these differences should be shown there. Section below that where you can merge differences suggests that. Additional info: Maybe I'm just missing purpose of the "Compare" page
Tried with both embedded PostgreSQL and external Oracle 10. Also note that nothing strange appears in the logs.
(In reply to Jan Hutař from comment #0) > Additional info: > Maybe I'm just missing purpose of the "Compare" page No, I agree that this is a valid bug.
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.