> I'm using cobbler 2.0.3.1 with Spacewalk 1.0 and having a strange problem > with system registration after kickstart. I cloned a kickstart profile, > changed the Base channel, and used it to kickstart a system. After it > finished I noticed it wasn't registered to spacewalk. Looking at the > ks-post.log I see this:
> Error Message: > Conflicting base channels > Error Class Code: 63 > Error Class Info: Conflicting activation tokens > So, I check the profile and see that an activation key is selected that > specifies the Base channel from the profile. So, as a test, I changed that to > "Spacewalk Default" and tried again. This time no conflict, but the system is > registered to the old Base channel. My question is how can I determine what > is specified by the Redhat Management Key in the cobbler profile report: > - cut - > Owners : ['admin'] > Parent Profile : > Red Hat Management Key : > 1-e7d85809b7913c1c8df27d923f3471da,1-prod-rhel-5-64 > Red Hat Management Server : <<inherit>> > Repos : [] > Server Override : <<inherit>> > - cut - > The second key I know, but what about 1-e7d85809b7913c1c8df27d923f3471da? How > can I find out what channel that key is specifying? Hey Bill, Did you ever get any satisfaction on this issue? I'm having the same issue trying to get a new kickstart profile working for RHEL 6 under Spacewalk v1.2 .. Thanks, Andy Speagle _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
