Red Hat Bugzilla – 1194162 – capsule-certs-generate asks me to register capsule, but usually I already am registered because I had to install capsule-installer
Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
capsule-certs-generate asks me to register capsule, but usually capsule is already registered because you had to install capsule-installer
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150217.0-Satellite-x86_64
How reproducible:
always
Steps to Reproduce:
1. On a Satellite run:
# capsule-certs-generate --capsule-fqdn <capsule_fqdn> \
--certs-tar ~/<capsule_fqdn>-certs.tar'
Actual results:
The utility advices me:
To finish the installation, follow these steps:
1. Ensure that the capsule-installer package is installed on the system.
2. Copy /root/<capsule_fqdn>-certs.tar to the system <capsule_fqdn>
3. Run the following commands on the capsule (possibly with the customized
parameters, see capsule-installer --help and
documentation for more info on setting up additional services):
rpm -Uvh http://<satellite_fqdn>/pub/katello-ca-consumer-latest.noarch.rpm
subscription-manager register --org "Default_Organization"
capsule-installer --parent-fqdn "<satellite_fqdn>"\
--register-in-foreman "true"\
--foreman-oauth-key "i6n...wgP"\
--foreman-oauth-secret "C56...p2n"\
--pulp-oauth-secret "6s4...SX2"\
--certs-tar "/root/<capsule_fqdn>-certs.tar"\
--puppet "true"\
--puppetca "true"\
--pulp "true"
The full log is at /var/log/katello-installer/capsule-certs-generate.log
Expected results:
Maybe first and second step should be somehow conditional like "if you already do not have your capsule registered to your satellite, do it using something like these commands"
Comment 1RHEL Program Management
2015-02-19 10:23:30 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
capsule-certs-generate output is now updated as below,
To finish the installation, follow these steps:
If you do not have the smartproxy registered to the Katello instance, then please do the following:
1. yum -y localinstall http://abc.redhat.com/pub/katello-ca-consumer-latest.noarch.rpm
2. subscription-manager register --org "Default_Organization"
Once this is completed run the steps below to start the smartproxy installation:
1. Ensure that the foreman-installer-katello package is installed on the system.
2. Copy /root/lmn.redhat.com-certs.tar to the system lmn.redhat.com
3. Run the following commands on the capsule (possibly with the customized
parameters, see foreman-installer --scenario capsule --help and
documentation for more info on setting up additional services):
VERIFIED with sat62-snap12.1
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1501
Description of problem: capsule-certs-generate asks me to register capsule, but usually capsule is already registered because you had to install capsule-installer Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-6-20150217.0-Satellite-x86_64 How reproducible: always Steps to Reproduce: 1. On a Satellite run: # capsule-certs-generate --capsule-fqdn <capsule_fqdn> \ --certs-tar ~/<capsule_fqdn>-certs.tar' Actual results: The utility advices me: To finish the installation, follow these steps: 1. Ensure that the capsule-installer package is installed on the system. 2. Copy /root/<capsule_fqdn>-certs.tar to the system <capsule_fqdn> 3. Run the following commands on the capsule (possibly with the customized parameters, see capsule-installer --help and documentation for more info on setting up additional services): rpm -Uvh http://<satellite_fqdn>/pub/katello-ca-consumer-latest.noarch.rpm subscription-manager register --org "Default_Organization" capsule-installer --parent-fqdn "<satellite_fqdn>"\ --register-in-foreman "true"\ --foreman-oauth-key "i6n...wgP"\ --foreman-oauth-secret "C56...p2n"\ --pulp-oauth-secret "6s4...SX2"\ --certs-tar "/root/<capsule_fqdn>-certs.tar"\ --puppet "true"\ --puppetca "true"\ --pulp "true" The full log is at /var/log/katello-installer/capsule-certs-generate.log Expected results: Maybe first and second step should be somehow conditional like "if you already do not have your capsule registered to your satellite, do it using something like these commands"