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 currently generates certs and helper steps to setup capsule-installer.
This could be automated a bit more.
The request here is to establish ssh passwordless configuraiton to the capsule.
Once that is done the steps can be further automated.
first any capsule pre-requisites should be validated
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Installation_Guide/index.html#idp12547336yum
see section
6.2. Red Hat Satellite Capsule Server Prerequisites
e.g.
1. Ensure that the capsule-installer package is installed on the system.
2. Copy sun-x4-2l-1-certs.tar to the system sun-x4-2l-1.gsslab.rdu2.redhat.com
Once ssh password is configured these two steps above can be automated
Also this can be automated.
rpm -Uvh http://cragsat61.usersys.redhat.com/pub/katello-ca-consumer-latest.noarch.rpm
Next part needs to query user on which [Organization/Environment]s they want to register to
1. acme_org/dev_app1
2. acme_org/dev_app2
Assumming a capsule can hook up to more than one organization/environment.
Next the the user needs to be queried on which type of capsule to install.
see section 6.4.1, 6.4.2, 6.4.
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Installation_Guide/index.html#idp12547336yum
This should supply a validated capsule-installer command that can be auto run against the capsule server now that we have supplied passwordless access.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.