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:
We need to document upgrade steps for sat server and capsule. I'm not sure where this can be fit, may be upgrade guide ?
I'll share the internal doc that include upgrade steps which is still under testing.
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Under section: Procedure 7.2. Upgrading Red Hat Satellite Capsule
==================================================================
Step3 should be: Stop services:
================================
Stop following services on capsule otherwise you will see errors about missing dependencies for docker and stuff until the db migration is done.
# for i in qpidd pulp_workers pulp_celerybeat pulp_resource_manager httpd; do service $i stop; done
Step4: Update Packages
step5: Check for the capsule-installer package
step6: Move the previous answers file to the new capsule-installer directory
Command in this step needs to be updated from mv to cp. Because after "yum update" all yaml files will be renamed with .rpmsave.
#cp /etc/katello-installer/answers.capsule-installer.yaml.rpmsave /etc/capsule-installer/answers.capsule-installer.yaml
step7: Regenerate certs for all capsules on sat6 and copy them over from sat6 server to respective capsules
on sat6 server:
===============
#capsule-certs-generate --capsule-fqdn $CAPSULE_FQDN --certs-tar ~/$CAPSULE_FQDN-certs.tar
#scp /root/$CAPSULE_FQDN-certs.tar root@$CAPSULE_FQDN:.
on capsule node:
===============
capsule-installer --upgrade --certs-tar $CAPSULE_FQDN-certs.tar