Bug 840035
Summary: | Changing the Base OS in a cloned kickstart profile does not change the default channel | ||
---|---|---|---|
Product: | [Community] Spacewalk | Reporter: | Bill Gunter <tulanian> |
Component: | WebUI | Assignee: | Tomas Lestach <tlestach> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.7 | CC: | jdobes, prmarino1 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-10-27 12:00:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1564160 |
Description
Bill Gunter
2012-07-13 13:50:24 UTC
Try the solution in ticket 786705 https://bugzilla.redhat.com/show_bug.cgi?id=786705 I have a feeling this is an other manifestation of the same issue by the way for " With no activation key the host will register itself to the Base OS in the profile. " to work you need to add the patches mentioned in ticket 809936 and update the dist channel map which can be done with the tool eva-dist-channel-map.pl mentioned in the ticket, however this is unsupported as of yet because the mapping is global regardless of the organization. https://bugzilla.redhat.com/show_bug.cgi?id=809936 That's not quite the same problem. To reiterate, say I have channel A and channel B. If I create a kickstart profile from scratch with base channel A, then clone it and change the base channel to B, systems kickstarted with the cloned profile will register to channel A provided there's no activation key associated with the profile. Dug through the DB a bit. Looks like a new activation key is created in rhnactivationkey when a profile is created or cloned and associated with the profile. Also, a new row is added to rhnregtokenchannels to associate the new default activation key with a channel. If the base channel in the associated profile is changed the channel_id in rhnregtokenchannels is not updated. Therefore, the default activation channel for the profile never changes. I had a rhel6 kickstart profile. I cloned it to a new ks profile and changed the base channel to rhel5. After I provisined my rhel6 system using the cloned ks profile, rhel5 was correctly installed on the system. I tried it on Spacewalk nightly. Bill, are you sure, the issue wasn't fixed in the meantime and is still present in Spacewalk? As here is no input for more than 4 years and it's reported for old version, closing this BZ. |