Bug 461261
Summary: | Multiple Activation keys prevent config channel deploy | |||
---|---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Nick Strugnell <nstrug> | |
Component: | Provisioning | Assignee: | Clifford Perry <cperry> | |
Status: | CLOSED WONTFIX | QA Contact: | Red Hat Satellite QA List <satqe-list> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 511 | CC: | casmith, jplans, jsherril, liko, mosvald, xdmoon | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 557581 (view as bug list) | Environment: | ||
Last Closed: | 2011-04-15 14:51:55 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: | 462714, 557581 |
Description
Nick Strugnell
2008-09-05 12:13:31 UTC
a temporary workaround could be to remove automatically generated activation key from --activatiokey parameter from ks.cfg and leave there only defined key(s) associated with configuration files, e.g.: === snip from ks.cfg === ... rhnreg_ks --serverUrl=https://satellite.server/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-84e00fdd59162dc725294322d1e74974,1-your_defined_key,1-your_second_defined_key ... === snip === and change it to: rhnreg_ks --serverUrl=https://your.satellite.server/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-your_defined_key,1-your_second_defined_key So there are really two issues presented in this bugzilla. The first: When provisioning with two activation keys with config deploy enabled, both keys try to install the rhncfg* packages. The 2nd one will fail since these packages are already installed, and thus the dependent config deploy will also fail. The second: When re-provisioning with an activation key that has config deploy enabled, deployment will not happen because the re-activation key will have it disabled. Meaning that if you use two keys and one has deploy disabled, deployment will not happen for any of the keys. Went ahead and cloned this bug to https://bugzilla.redhat.com/show_bug.cgi?id=557581 for the second issue. This bz will only concern the first issue involving two keys with config deploy enabled. I'm not able to reproduce this issue on 5.2 or 5.3. Again, this is the issue where TWO Keys are used BOTH with config deploy enabled. This was tested against a RHEL 5 client with: yum-rhn-plugin-0.5.3-30.el5 rhnlib-2.2.6-2.el5 If this is reproducible against 5.3, please let me know how :} And just to be clear, for the 2nd issue that I think most people are concerned with, please see bz 557581. |