Bug 460816
Summary: | rhnreg_ks no xen | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | ITT Tech <tech> |
Component: | rhn-client-tools | Assignee: | Pradeep Kilambi <pkilambi> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | berrange, cperry |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://rhn.redhat.com | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-21 03:12:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
ITT Tech
2008-09-01 14:11:46 UTC
This isn't a Xen bug - needs to be assigned to RHN. This is not a bug. rhnreg_ks with username/password with register you to just the base channel, and not the virtualization child channel. If you use an activation key with rhnreg_ks, it will subscribe you to the channels associated with the activation key. The usage of rhn_register though is a different beast - it is designed to understand and subscribe to additional channels on registration. We recommend to use rhnreg_ks with activation keys for en-mass registrations within automated fashion where you wish to register a lot of systems to the same set of channels. Cliff. |