Bug 193169 - machines lose subchannel and base channel information
Summary: machines lose subchannel and base channel information
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
(Show other bugs)
Version: 370
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Mike McCune
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2006-05-25 20:16 UTC by Jack Neely
Modified: 2011-01-05 22:30 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-01-05 22:30:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jack Neely 2006-05-25 20:16:25 UTC
Description of problem:

It is possible to get individual registrations in upstream RHN and in the
Satellite to lose base channel and sub channel configurations.

Normally this happens with the funniness of letting your contract expire and
then re-activating it.  While that really shouldn't happen, it does and RHN and
the Satellites do not recover well from it.

The situation I had was I was given a Satellite certificate that did not have
enough entitlements for the number of registered machines.  I had more WS
machines registered than what was in the cert.  A random selection of WS
machines were marked as entitled and up to date but their base channel and all
subchannels were removed.

As I manage addtional software for production machines with subchannels it is a
show stopper when random machines lose this information.  

When a proper cert was applied the same machines automatically found their base
channel but no subchannels reappeared.

Suggestion: if there are not enough entitlements for a specific channel family
mark the machine as unentitled rather than removing parts of its configuration.

Version-Release number of selected component (if applicable):
Satellite 3.7.  Also a very similar problem happened with upstream RHN in March
of 2005.

Comment 1 Clifford Perry 2011-01-05 22:30:06 UTC
The RHN Satellite 4.x and RHN Proxy 4.x products have reached their end of life. Please see:

Satellite 4 EOL Errata
 - https://rhn.redhat.com/errata/RHSA-2011-0001.html

RHN Proxy 4 EOL Errata
 - https://rhn.redhat.com/errata/RHSA-2011-0002.html

This bugzilla was reported for a product which is no longer supported. As such we are closing this bugzilla out. If you feel this bug report should be reviewed again since it is valid for a currently supported product version, then please feel free to re-open this bug report. 

Regards,
Clifford


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