Bug 449779 - Attempts to move from Z stream to main stream fail
Attempts to move from Z stream to main stream fail
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Channels (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: rhn-dev-list
Red Hat Network Quality Assurance
Depends On:
Blocks: 428922
  Show dependency treegraph
Reported: 2008-06-03 11:05 EDT by Máirín Duffy
Modified: 2017-07-05 11:18 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-05 11:18:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Máirín Duffy 2008-06-03 11:05:43 EDT
Description of problem:

This is a bug for hosted Z stream support. This bug occurred early June 2008 in
RHN 5.05.

Customer has a GLS instructor account and has access to Z-stream channels. On
one system (has not attempted on others):

1) He attempted to switch from the mainline channel to the Z stream (5 mainline
to 5.1 Z-stream) via the webui. While this provided an error message, it
appeared to actually work and the 5.1 Z-stream appeared as the new base channel
for the system in the webui.

2) Now that the system is listed as being in the 5.1 Z-stream, he can no longer
move back to the mainline from the Z-stream. Attempts to do so do not change the
base channel listed for the system.

3) "There seems to be some inconsistencys in the channels too, like yum install
xen fails because of a missing dep on dnsmasq"

4) "yum grouplist does not give what I would expect, for instance no
Virtualization group"

5) "there were other issues too, like no yum-utils for instance"


I believe the Z-stream channel subscription logic is such that you cannot move
from the baseline to a z-stream. You can start on a Z-stream though if you
select the Z-stream when you register the machine. You may be able to move from
mainline to the *latest* z-stream though. I'm not sure. I would assume that the
dependency issues encountered were related to this protection of preventing
movement from the mainline to the Z-stream not being enforced.
Comment 3 Grant Gainey 2008-06-03 15:26:01 EDT
The only server in production registered to any 5.1.z channel, is the one I
registered this morning to test.  Can I have the sid of the affected server?
Comment 4 Thomas "Shea" DeAntonio 2017-07-05 11:18:53 EDT
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

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