Hide Forgot
Created attachment 1208062 [details] screenshot 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: Section 1 Describe the issue: Modify the following paragraph. You should have upgraded to the latest minor release of Red Hat Satellite Server 6.1. Direct upgrade from earlier minor versions is not supported. Add more detail, for instance the link to upgrade to the latest minor version --> https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/chap-Red_Hat_Satellite-Installation_Guide-Upgrading_Red_Hat_Satellite_Server_and_Capsule_Server.html In that section a very important steps is missing. 1) Confirm that no other repositories are active i.e epel and others that customer may have installed yum repolist enabled repo id repo name status --------------------------------------------------------- rhel-6-server-rpms Red Hat Enterprise Linux 6 Server (RPMs) 18,267 rhel-6-server-satellite-6.1-rpms Red Hat Satellite 6.1 (for RHEL 6 Server) (RPMs) 684 rhel-server-rhscl-6-rpms Red Hat Software Collections RPMs for Red Hat Enterprise Linux 6 Server 6,135 2) Click on Gui and check on tasks currently running or paused If tasks are in that state, apart from candlepin, it can cause issues with future upgrades. screenshot attached
Hello OK, add link after: You should have upgraded to the latest minor release of Red Hat Satellite Server 6.1. Direct upgrade from earlier minor versions is not supported. which occurs in: Upgrading Satellite Server Upgrading To Disconnected Satellite Server version 6.2 Upgrading Capsule Servers Upgrading a Self-Registered Satellite Server this is the link to use: ct-Red_Hat_Satellite-Installation_Guide-Upgrading_Red_Hat_Satellite_Server_and_Capsule_Server-Upgrading_Between_Minor_Versions.html Re the section "Upgrading To Disconnected Satellite Server version 6.2", you will notice just above it the section "Upgrading Satellite Server 6.1" which contains "To perform the upgrade to the latest minor version, follow the Upgrading Between Minor Versions of Satellite procedures in the Red Hat Satellite 6.1 Installation Guide." So there is going to be some duplication there after we add the link. I will look at that issue later. Re: point "1" the step to check for repos: I was recently asked to add that for the section "Upgrading Between Minor Versions of Satellite"[1] and have a review bug to get me to replicate this to the other procedures[2] I need to add that improvement to the 6.1 version too Re: point "2" the need to check for running or paused tasks This step: foreman-rake katello:upgrade_check (and associated explanation) Occurs in: Upgrading Satellite Server Upgrading To Disconnected Satellite Server version 6.2 Upgrading a Self-Registered Satellite Server I cannot understand the purpose of the screenshot attached. Thank you [1] 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 [2] Bug 1367674 – Review upgrade procedures
Is is possible to add this to 6.1 upgrade satellite section. --> foreman-rake katello:upgrade_check I've searched 6.1 in https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Installation_Guide/index.html but it doesn't appear to have it. Apologies screenshot is wrong, but it was just to show paused tasks
(In reply to jnikolak from comment #2) > > Is is possible to add this to 6.1 upgrade satellite section. > --> foreman-rake katello:upgrade_check > I've searched 6.1 in > https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html- > single/Installation_Guide/index.html > > but it doesn't appear to have it. Yes, I can add that, but we need to confirm that the KBase[1] that explains the foreman rake commands for dealing with paused tasks is still valid for 6.1 as I saw it was recently updated. I notice: Environment Red Hat Satellite v 6.* But see https://access.redhat.com/solutions/2089951#comment-1104971 "In 6.2.2 and, probably before, Actions::Katello::System calls were replaced by Host" Does that apply to 6.1.X ? I can check it later. > > > Apologies screenshot is wrong, but it was just to show paused tasks OK, thank you. [1] How to manage paused tasks on Red Hat Satellite 6. - Red Hat Customer Portal - https://access.redhat.com/solutions/2089951
(In reply to Stephen Wadeley from comment #3) > (In reply to jnikolak from comment #2) > > > > Is is possible to add this to 6.1 upgrade satellite section. > > --> foreman-rake katello:upgrade_check > > I've searched 6.1 in > > https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html- > > single/Installation_Guide/index.html > > > > but it doesn't appear to have it. > Yes, I can add that, but we need to confirm that the KBase[1] that explains > the foreman rake commands for dealing with paused tasks is still valid for > 6.1 as I saw it was recently updated. > > I notice: Environment Red Hat Satellite v 6.* > > But see https://access.redhat.com/solutions/2089951#comment-1104971 > "In 6.2.2 and, probably before, Actions::Katello::System calls were replaced > by Host" > > Does that apply to 6.1.X ? I can check it later. > > > I see updated "Safe to kill tasks" section with commands: Actions::Katello::System::GenerateApplicability #on Sat6.0 and 6.1 Actions::Host::GenerateApplicability #on Sat6.2 and above But I am a little confused because I see older command for "planned" task and newer command for "paused" task: ForemanTasks::Task.where(:state => :planned).where(:label => "Actions::Katello::System::GenerateApplicability").destroy_all ForemanTasks::Task.where(:state => :paused).where(:label => "Actions::Host::GenerateApplicability").destroy_all Will ask for confirmation but that does not stop me documenting this by linking to KBase.
(In reply to jnikolak from comment #2) > > Is is possible to add this to 6.1 upgrade satellite section. > --> foreman-rake katello:upgrade_check > I've searched 6.1 in > https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html- > single/Installation_Guide/index.html > > but it doesn't appear to have it. > Hello This is not a trivial task as the foreman-rake katello:upgrade_check script requires Katello Ruby RPM greater than or equal to 2.2.0.90 Can we find out in what minor version of Sat6.1.X the Ruby RPM was version 2.2.0.90? Thank you
6.1.8 = ruby193-rubygem-katello-2.2.0.85-1.el7sat.src.rpm 6.1.9 = ruby193-rubygem-katello-2.2.0.89-1.el7sat.noarch.rpm 6.1.10 = ruby193-rubygem-katello-2.2.0.93-1.el7sat.noarch.rpm That would not be useful for customers running older versions. Before they can upgrade to 6.1.9 and now 6.1.10 they need to know how to fix their paused tasks As they may be running 6.1.5 --> this second part of the solution is not recommended by engineering. https://access.redhat.com/solutions/208995 Customer should log into gui and check for running/paused tasks Perhaps documentation could take some screenshots to show how this can be done. It will also help future troubleshooting.
However if the gui cannot resume the tasks, even after restarting the associated services. then the only option would be to kill them, if you could check with engineering about this part, as a last option.
Re comment 8 , comment 5 The katello:upgrade_check was specifically introduced to support the upgrade from 6.1 to 6.2 as part of RHBA-2016:1499-03. It is not currently supported for upgrading from 6.0 to 6.1; therefore, it does not need to be added to the 6.1 upgrade documentation.
Thank you Brad Jon If I understand correctly, 6.1 user can be asked to check for incomplete tasks in GUI: Monitor > Tasks and set search filter "not stopped" and then follow [1] [1] How to manage paused tasks on Red Hat Satellite 6. - Red Hat Customer Portal - https://access.redhat.com/solutions/2089951
thanks stephen, sorry if my explanation didn't make sense. It seems that engineering has verified killing tasks when tasks wont resume as per:https://access.redhat.com/solutions/2089951 If that is the case, could you mention that on the documentation.