Hide Forgot
Document URL: https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server Section Number and Name: 6.7. Upgrading Between Minor Versions of Satellite Describe the issue: This does a great job telling us how to upgrade between minors of a self registered satellite, but not a "normal" registered to red hat satellite, which is more common. We need to have it say # yum update # satellite-installer --scenario satellite --upgrade. Suggestions for improvement: like on this errata page https://access.redhat.com/errata/RHBA-2016:1885 Solution.. To update this system to include these fixes, ensure your system has access to the latest Red Hat packages. For instructions on how to apply this update, refer to: https://access.redhat.com/articles/11258 Then re-run the installer to complete the upgrade: # satellite-installer --scenario satellite --upgrade or # satellite-installer --scenario capsule --upgrade Additional information:
(In reply to Kathryn Dixon from comment #0) > Document URL: > > https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/ > installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server > > Section Number and Name: 6.7. Upgrading Between Minor Versions of Satellite > > Describe the issue: > > This does a great job telling us how to upgrade between minors of a self > registered satellite, but not a "normal" registered to red hat satellite, > which is more common. > Hello this is an unfortunate misunderstanding. The first line says "On a self-registered Satellite, download all packages before stopping Satellite Server: " Which means: If you are on .... The procedure is meant to cover both cases. If I change "On a self-registered Satellite" to "If you have a self-registered Satellite" would that be clear enough? Thank you
lowering priority as this is an imperfection rather than an omission
I think that this item should be listed as a prerequisite if they are running a self-registered Satellite. It would be simple, and more clear if it were NOT included in steps 1..6. This is the primary idea here, since customers are the ones we are worried about interpreting the information. It would also be ideal and more clear here for support-ability and decreasing support case load if we could indicate for users to ensure they have ONLY the proper repositories enabled: Satellite: rhel-{6,7}-server-rpms rhel-{6,7}-server-satellite-6.2-rpms rhel-server-rhscl-{6,7}-rpms Capsule: rhel-{6,7}-server-rpms rhel-{6,7}-server-satellite-capsule-6.2-rpms Thanks.
(In reply to Craig Donnelly from comment #3) > I think that this item should be listed as a prerequisite I think it needs to be part of the procedure, but if after my updates it is still is not clear, then we can expand to two separate procedures. > if they are > running a self-registered Satellite. It would be simple, and more clear if > it were NOT included in steps 1..6. > > This is the primary idea here, since customers are the ones we are worried > about interpreting the information. > > It would also be ideal and more clear here for support-ability and > decreasing support case load if we could indicate for users to ensure they > have ONLY the proper repositories enabled: > > Satellite: > > rhel-{6,7}-server-rpms > rhel-{6,7}-server-satellite-6.2-rpms > rhel-server-rhscl-{6,7}-rpms > > Capsule: > > rhel-{6,7}-server-rpms > rhel-{6,7}-server-satellite-capsule-6.2-rpms > > Thanks. According to the existing guide[1], rhel-server-rhscl-X-rpms is required on a Capsule Server. Is that incorrect? We also need to mention the tools repo for Katello Agent[2]. Thank you [1] https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-4-installing-capsule-server#configuring_repositories_capsule [2] https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-4-installing-capsule-server#installing_katello_agent
Hey Stephen, That looks fine to me. I do recognize now that they want rhscl for remote execution, just keeping in mind that it is not a /requirement/. Necessity depends on customer implementation of the plugin to their capsules I believe, but I am not opposed to just instructing it be on (as this repo will not cause issues with a capsule otherwise, unlike other possibilities). There is one small typo where X should replace 6 in section Upgrading the Capsule to next minor release 1.b. The 6.1 procedure should not include RHSCL for capsules (No need), but should contain the same clarification. There is one final thing here that is currently up for debate, and that is stopping the services during the 'yum update' process. Currently, some packages that get updated in these processes trigger RPM Postscripts that can cause long delays in the yum transaction finishing, and may even hang -> I think this might be in part due to stopping of the services. Perhaps not all Satellite services, but more specifically postgresql. (In the case of postscripts containing 'foreman-rake db:{migrate,seed}', we would assume that the database must be present and online, but some of the postscripts do NOT check service status prior to just running..) With that said, I will point this toward Mike McCune to see if we want to start addressing this.
(In reply to Craig Donnelly from comment #10) > Hey Stephen, > > That looks fine to me. > > I do recognize now that they want rhscl for remote execution, just keeping > in mind that it is not a /requirement/. Necessity depends on customer > implementation of the plugin to their capsules I believe, but I am not > opposed to just instructing it be on (as this repo will not cause issues > with a capsule otherwise, unlike other possibilities). We can point out it is optional and what it is required for > > There is one small typo where X should replace 6 in section Upgrading the > Capsule to next minor release 1.b. I think you are referring to: rhel-server-rhscl-X-rpms that occurs in the Satellite section above as well as in the Capsule section. Note the text explanation underneath "Where X is the major version of Red Hat Enterprise Linux you are using.". > > The 6.1 procedure should not include RHSCL for capsules (No need), but > should contain the same clarification. ACK > > There is one final thing here that is currently up for debate, and that is > stopping the services during the 'yum update' process. Currently, some > packages that get updated in these processes trigger RPM Postscripts that > can cause long delays in the yum transaction finishing, and may even hang -> > I think this might be in part due to stopping of the services. Perhaps not > all Satellite services, but more specifically postgresql. (In the case of > postscripts containing 'foreman-rake db:{migrate,seed}', we would assume > that the database must be present and online, but some of the postscripts do > NOT check service status prior to just running..) > > With that said, I will point this toward Mike McCune to see if we want to > start addressing this. Right, we could publish the updates we have so far. Thank you
I found this text in "Identifying and Attaching the Capsule Server Subscription" "Configuring Repositories": The Red Hat Software Collections repository provides a later version of Ruby required by some Red Hat Satellite features, including the Remote Execution feature. sounds a little vague.
Hello changes as agreed so far are now live on the customer portal https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server#upgrading_between_minor_versions
Hello Brad Can you help with the question to Mike in comment 10 ? As this doc bug's work is done I would like to close this but not with unanswered questions if possible.
Stephen, Comment 18 preview looks great to me. Thanks.