Bug 143107 - up2date lost it channels
Summary: up2date lost it channels
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Ken Reilly
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-16 16:00 UTC by Bill Brown
Modified: 2013-02-27 00:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:26:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bill Brown 2004-12-16 16:00:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Firefox/0.10.1

Description of problem:
A some point when up2date was updating beta 1 to beta 2(?) the channel
info was lost. I downloaded the Beta 2 CD's and updated but that
didn't fix the problem. The website tells me that I have 130 updates
but the tool on the desktop tell me that all is up to date. The
channel area in up2date is blank in both areas.

I need to know how to repair up2date to get all of the new files.

Thanks in advance.
Bill

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


How reproducible:
Always

Steps to Reproduce:
1.unable to reproduce the cause
2.
3.
    

Additional info:

Comment 1 Adrian Likins 2005-01-11 18:02:57 UTC
You should be able to log into the RHN website, (rhn.redhat.com)
select that machine from the systems list, and on the
"system detail" screen, on the right, should be an option
to "Alter Channel Subscriptions". 

On that screen, you can reassign it to a channel.

Comment 3 Jiri Pallich 2012-06-20 13:26:22 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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