Bug 81763 – registration by activation key subscribes to unspecified powertools channels.

Bug 81763 - registration by activation key subscribes to unspecified powertools channels.

Summary:	registration by activation key subscribes to unspecified powertools channels.

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Satellite 5
Classification:	Red Hat
Component:	Registration (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Mihai Ibanescu
QA Contact:	Red Hat Satellite QA List
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	78569
	Show dependency tree / graph

Reported:	2003-01-13 15:33 EST by Mike McLean
Modified:	2007-10-23 22:00 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-01-13 15:44:31 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Mike McLean 2003-01-13 15:33:56 EST

* 7.0, 7.1
* rhnreg_ks

my 7.[01] boxes are getting subscribed to the powertools subchannel (when
registered via activation key) even though the activation key has that channel
unselected.

Comment 1 Mihai Ibanescu 2003-01-13 15:42:49 EST

Yes, because:

- your registration token does not specify a base channel, because the editor
did not allow you to select one
- if no channel is present in the registration key, it computes the channels to
subscribe based on the rhnDistChannelMap rules
- all 7.[01] boxes are automatically subscribed to the powertools channels,
based on the above-mentioned rules.

Comment 2 Mihai Ibanescu 2003-01-13 15:44:31 EST

Closing. To quote gdk:

So the answer is "works as designed," although it's debatable whether it was
designed very well.  :-)

Really, not much I can do.

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