Bug 506158 - channel management tool doesn't allow setting end of life
Summary: channel management tool doesn't allow setting end of life
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Backend
Version: rhn511
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bryan Kearney
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard: US=105432
Depends On:
Blocks: 506596
TreeView+ depends on / blocked
 
Reported: 2009-06-15 19:11 UTC by James Bowes
Modified: 2013-01-10 10:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-10 13:02:34 UTC
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.