Bug 1194162

Summary: capsule-certs-generate asks me to register capsule, but usually I already am registered because I had to install capsule-installer
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: InstallationAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Kedar Bidarkar <kbidarka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: chrobert, cwelton, kbidarka
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14098
Whiteboard:
Fixed In Version: katello-installer-base-3.0.0.20-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:22:25 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:

Description Jan Hutař 2015-02-19 08:50:55 UTC
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 1 RHEL 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.

Comment 3 Bryan Kearney 2016-03-08 17:01:54 UTC
Upstream bug component is Installer

Comment 4 Kedar Bidarkar 2016-05-24 10:02:13 UTC
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

Comment 5 Bryan Kearney 2016-07-27 11:22:25 UTC
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