Description of problem:
Save the capsule installer command in a file for capsule installation/upgrade automation
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. On Satellite generate the capsule certs:
# capsule-certs-generate --capsule-fqdn "capsule.example.com" --certs-tar "~/capsule.example.com-certs.tar"
Installing Done [100%] [..................................................................................]
To finish the installation, follow these steps:
3. Run the following commands on the capsule (possibly with the customized
parameters, see satellite-installer --scenario capsule --help and
documentation for more info on setting up additional services):
satellite-installer --scenario capsule\
The full log is at /var/log/capsule-certs-generate.log
As shown above. After running the above command, the user needs to copy the installer command provided by the above output and run in Capsule. This is not user-friendly for automation.
The capsule installer command output provided by the capsule-certs-generate command should be saved as a script in the same path where the certs tar is created.
capsule-install is a new project for easy install/upgrade of capsules. In this, we are currently extracting the installer command provided by capsule-certs-generate using regex as shown in:
Although this works okay, this will not be a long-term viable solution and we need to save the installer command as proposed above.
At the moment /var/log/foreman-installer/capsule.log has this information in it. Does accomplish the goal of this BZ?
Nope, it is not very helpful for automated deployments. If we can save that info from capsule.log in a file called $capsule.out or $capsule.sh in the current directory, this will help automate the capsules deployment easier and straightforward using Ansible or Puppet.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.