Feature #25377
closed[RFE] Upgrade fails on finding capsule-certs.tar file
Description
Description of problem:
When issuing upgrade on Satellite Capsule 6.3.2, the installer fails if it is unable to find the referenced certs.tar file in the capsule-answers.yaml file.
Version-Release number of selected component (if applicable):
6.3.2
How reproducible:
Everytime
Steps to Reproduce:
1. Remove the certs.tar file from the Capsule
2. Run the installer with the '--upgrade' flag
3.
Actual results:
Installer fails to find the certs.tar file and exits with the following:
The certs tar file generated by the server is not present at /root/capsule.redhat.com-certs.tar, exiting.
[ERROR 2018-07-09 16:15:54 verbose] The certs tar file generated by the server is not present at /root/capsule.redhat.com-certs.tar, exiting.
Expected results:
No issues
Additional info:
This is not a fresh install, and the Capsule server was already at version 6.3.2. The server has been a Capsule server since 6.2.0.
Workaround is to either comment out the 'certs_tar:' parameter in the /etc/foreman-installer/scenarios.d/capsule-answers.yaml file or remove the value from the parameter, then continue with the upgrade.
We could try some logic that says if /root/ssl-build exists, skip the certs tarball existence check.
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello-installer/pull/711 added
Updated by The Foreman Bot over 5 years ago
- Pull request https://github.com/Katello/katello-installer/pull/717 added
Updated by Chris Roberts over 5 years ago
- Pull request deleted (
https://github.com/Katello/katello-installer/pull/711)
Updated by Eric Helms almost 4 years ago
- Project changed from Katello to Installer
- Category deleted (
Installer) - Status changed from Ready For Testing to New
- Pull request deleted (
https://github.com/Katello/katello-installer/pull/717)
Updated by Chris Roberts almost 4 years ago
- Category set to foreman-installer script
- Status changed from New to Assigned
- Assignee set to Chris Roberts
- Triaged changed from Yes to No
Updated by Chris Roberts almost 4 years ago
- Status changed from Assigned to Rejected
Since the --upgrade flag is being removed, I have resolved this downstream with a KCS article: