Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 668539

Summary: Cannot Add Red Hat Errata when choosing only Channel Version
Product: Red Hat Satellite 5 Reporter: Tomas Lestach <tlestach>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED ERRATA QA Contact: Šimon Lukašík <slukasik>
Severity: medium Docs Contact:
Priority: medium    
Version: 540CC: cperry, slukasik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-java-1.2.39-101 Doc Type: Bug Fix
Doc Text:
Consequence: No errata will be offered to clone when setting only the "Channel Version" on the AddRedHarErrata.do page. Result: Now, it's possible to clone selected errata even if setting only "Channel Version" on the AddRedHarErrata.do page.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-20 08:21:36 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: 646546, 715348    

Description Tomas Lestach 2011-01-10 18:44:09 UTC
Description of problem:
There're two combos on the AddRedHarErrata.do page - "Channel Version" and "Channel" with appropriate confirm buttons. When setting only the channel version, no errata will be offered to clone on the ConfirmErrataAdd.do page.

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

How reproducible:
always

Steps to Reproduce:
1. have a synced rhel5 channel and a custom channel of the same arch
2. try to add a red hat erratum to the custom channel:
- Manage Software Channels - <custom channel> - Errata - Add - Add Red Hat Errata
3. Uncheck "Package Association"
4. Pick up any Channel Version from the combo and hit "View Associated Channels"
(Make sure you do not touch "View Associated Errata" button)
5. hit "Select All" and Confirm

Actual results:
"Clone Errata" button on the ConfirmErrataAdd.do page is disabled. Total Packages count states: 0.

Expected results:
Possible to clone selected errata.

Additional info:
This might be a regression, but definitely not against sat53.

Comment 1 Tomas Lestach 2011-01-10 18:49:04 UTC
Fixed DB query ...

spacewalk.git: 1211435f5022379aeff01d6118d389641f4a4af6

Comment 4 Tomas Lestach 2011-09-27 15:12:56 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Consequence:
No errata will be offered to clone when setting only the "Channel Version" on the AddRedHarErrata.do page.
Result:
Now, it's possible to clone selected errata even if setting only "Channel Version" on the AddRedHarErrata.do page.

Comment 5 Šimon Lukašík 2011-10-11 13:39:34 UTC
Moving to Verified:

Amended query is only exposed on ConfirmErrataAdd.do page, which is
common path for AddRedHatErrataAction.do and AddCustomErrataAction.do.
Which implies the testing procedure to cover both paths. To test
given query, the channel listbox needs to be unchecked.

Testing procedure:
 - AddRedHatErrataAction:
     - reproducer as per comment 0
        - the errata count matches as previous
        - the packages count is amended
     - clone 1 redhat errata
     - clone multiple redhat errata containing same package
     - clone all redhat errata with different arch
        - cloned only noarch packages and all erratas 
          (even empty ones (!))
 - AddCustomErrataAction (Without selecting source channel:
    - add all costom errata
        - results are same as for the first scenario
    - add single custom errata
    - add multiple custom errata containing same package
    - clone all custom errata with different arch
 - all scenarios worked as expected
 - with the exception of bug 744801

Verified against 
spacewalk-java-1.2.39-101

Comment 6 errata-xmlrpc 2011-10-20 08:21:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1388.html