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:
If the filename entered for --certs-tar is not correct, the installer will commence and eventually error out for confusing reasons. We should do some sanity checking to make sure the filename passed to --certs-tar is valid before starting install.
Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140702.0
How reproducible:
Steps to Reproduce:
1. On main instance, create cert for target capsule and copy to target
2. Attempt to install capsule, but use an incorrect string for the certs.tar file, i.e. cloud-qe-4.idm.lab.bos.redhat.com-certs.tra (note the typo)
3. View results
Actual results:
Process errors out and user has to dig pretty deep into the log to figure out why the install failed; it is not really clear that it is due to a bad value passed to --certs-tar
Expected results:
We should validate the value passed to --certs-tar before ever executing.
Additional info: