Bug 506158

Summary: channel management tool doesn't allow setting end of life
Product: [Retired] Red Hat Network Reporter: James Bowes <jbowes>
Component: RHN/BackendAssignee: Bryan Kearney <bkearney>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Network Quality Assurance <rhn-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: rhn511CC: acarter, bkearney, dhughes, rhn-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: US=105432
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-10 13:02:34 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: 506596    

Description James Bowes 2009-06-15 19:11:15 UTC
I suspect that particular field has never been tested, as only 38 channels have it set.

Comment 1 Denise Hughes 2009-06-24 17:47:09 UTC
Steps to Recreate:
1. Open command window and run: rhn-manage-channel-internal --server dev -l rhel-i386-server-5
2. Copy and paste the output in a new file
3. In the new file, change label and name information
4. In the new file, enter End of Life date (YYYY-MM-DD)
5. Save the file and run the following command: rhn-manage-channel-internal --server dev --csv=/home/dhughes/RHN/DeniseTestEOL062409 --update --commit
6. Verify the information in the database
select * from RHNCHANNEL where NAME = 'DeniseTestingName1'
7. Verify the information on the Retired Channels page in the UI

Results:
The RHNCHANNEL table is updated properly with the EOL date.  But the channel is not displayed under the Retired Channels page in the UI.

Comment 2 Denise Hughes 2009-06-26 19:27:50 UTC
Verified on webdev.
(Note: I changed the label and the name back to it's original state)

A unique constraint error was displayed.  It did not affect the UI and database update.  A separate bug was open for this issue.  See bug #508325

Comment 3 Stephen Herr 2009-07-30 15:53:24 UTC
verified in qa