Bug 442630
| Summary: | In Satellite 5.1, when kickstarting a new system using an activation key that changes the system's base channel, rhnreg_ks fails and new system not being registered to the satellite. | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Stuart R. Kirk <Stuart.Kirk> |
| Component: | Registration | Assignee: | Justin Sherrill <jsherril> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 510 | CC: | alfredo.horta, danny.howard, degts, dherrman, jschrode, pep, tao, tscherf |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | sat511 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-08-13 19:03:09 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 429319, 448773 | ||
| Attachments: | |||
Created attachment 302526 [details]
Kickstart post-install log.
Created attachment 302527 [details]
Actual kickstart file being used as shown from WEBUI
Created attachment 302529 [details]
Kickstart viewed from URL with two activation keys
Created attachment 302530 [details]
Output from SQL queries confirming the base channel conflict
fixed in rev 171299 (can be reverted if needed) backported to 5.1 in 171324. Flip from ON_DEV to MODIFIED. MASS move for Sat bugs. Preethi, we had talked and I can't seem to reproduce this, and your reproducer wasn't working either, so you are going to re-qa this bug. -Justin I can repro this bug by following the test procedure on the latest build of 511.
/root/ks-post.log reports:
Error Message:
Conflicting base channels
Error Class Code: 63
Error Class Info: Conflicting activation tokens
Explanation:
An error has occurred while processing your request. If this problem
persists please enter a bug report at bugzilla.redhat.com.
If you choose to submit the bug report, please be sure to include
details of what you were trying to do when this error occurred and
details on how to reproduce this problem.
ERROR: unable to read system id.
ERROR: unable to read system id.
As thus, moving to FAILS_QA.
I'm gonna to clone this bug for provisioning (non-baremetal) and align with 5.3. this passes with bare metal kickstarts, fails w/ standard kickstarts.. standard kickstart, meaning via the webui.. on a system w/ rhel... he he verified buil3 Workaround I am using: add rhnreg_ks with --force to %post. That does the trick. So the first rhnreg_ks fails, but in %post it works. The --force option did the trick. Jan Note that the workaround in #7 cannot be used when using the WebUI to deploy VMs, as you don't get to specify any ks arguments. You must instead use the workaround in #17. I'm using: rhnreg_ks --force --activationkey=1-3c4dfb3831e6a2bc9261d09c4ff06339 rhn_check yum -y update rhn_check after running a related test..
I was able to reproduce this bug using base rhel 4 w/ no errata
Error Message:
Conflicting base channels
Error Class Code: 63
Error Class Info: Conflicting activation tokens
Explanation:
An error has occurred while processing your request. If this problem
persists please enter a bug report at bugzilla.redhat.com.
If you choose to submit the bug report, please be sure to include
details of what you were trying to do when this error occurred and
details on how to reproduce this problem.
ERROR: unable to read system id.
ERROR: unable to read system id.
[root@fjs-0-18 ~]#
I'm double checking a rhel 4 channel w/ full errata
same issue w/ full errata, however the customer only had issues w/ baremetal kickstarts.. making sure we have a clone for 5.3. Ok.. I verified this bug is fixed for bare metal kickstarts, so I'll clone it for 5.3 moving back to verified. cloned bug is https://bugzilla.redhat.com/show_bug.cgi?id=449846 validated 5.1.1 Satellite is now GA, bugs Closed for Current Release. 5.1.1 Satellite is now GA, bugs Closed for Current Release. |
Description of problem: When an activation key is used during a kickstart to change the base channel of the newly built system the system fails to register to the satellite server as rhnreg_ks errors out with a "Conflicting base channels" message. Version-Release number of selected component (if applicable): RHNS 5.1.0-181 (upgraded from 5.0) OS being built using kickstart tree: RHEL4.6 AS x86_64 U6 How reproducible: See below. Steps to Reproduce: 1. Install RHNS 5.1-181 2. Sync in a RHEL channel 3. Clone the RHEL channel you sync'd in to create a custom base channel 4. Create an activation key that points to this new custom base channel 5. Create a kickstart that builds off of the proper ks tree but uses the above activation key to switch base channels at system build time 6. Kickstart a new system Actual results: Output from the rhnreg_ks command in the kickstart file: Error Message: Conflicting base channels Error Class Code: 63 Error Class Info: Conflicting activation tokens Explanation: An error has occurred while processing your request. If this problem persists please enter a bug report at bugzilla.redhat.com. If you choose to submit the bug report, please be sure to include details of what you were trying to do when this error occurred and details on how to reproduce this problem. Output from the two rhn_check commands in the kickstart file: ERROR: unable to read system id. ERROR: unable to read system id. If you are running any up2date/yum updates in custom post install scripts, this will of course cause the build to hang since it will be prompting the user to register to rhn. Expected results: I would expect the system's base channel to modify when the rhnreg_ks directive is issued and subsequently register the newly built system to the satellite server allowing the following two rhn_check commands to succedd. Additional info: It appears that the URL that is actually called to obtain the kickstart file produces a different rhnreg_ks line than the one that is displayed when you look at the "kickstart file" tab in the WebUI. In the latter, there is only the singular activation key that is present which is what the user has selected via the WebUI. However viewing the actual URL, there are two different activation keys present which have different base channels associated with them which causes this error.