Bug 1395315 - 6.1.2. Removing Elasticsearch can break the upgrade and needs to be moved
Summary: 6.1.2. Removing Elasticsearch can break the upgrade and needs to be moved
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: 6.2.4
Hardware: Unspecified
OS: Unspecified
unspecified
urgent vote
Target Milestone: Unspecified
Assignee: Stephen Wadeley
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-15 16:24 UTC by Mike McCune
Modified: 2020-01-17 16:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-24 09:51:01 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1389164 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1389164

Description Mike McCune 2016-11-15 16:24:40 UTC
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.1.2

Describe the issue: 

We state that users should remove Elastic Search before they upgrade to 6.2. The ordering of this step blocks the user from completing other steps later in the upgrade and needs to be moved.

Suggestions for improvement: 

This step needs to be moved to the end of the upgrade *after* they are fully upgraded to 6.2, after say step 27.

"27. In the Satellite web UI, go to Configure > Discovery Rules and associate selected organizations and locations with discovery rules.
"

add it after this and mention that it is optional.

Comment 2 Stephen Wadeley 2016-11-15 16:48:46 UTC
Hello

As this section is optional and as moving it is not trivial I decided to hide for the moment.

We do not want to add this procedure to every upgrade procedure, they are already far too long.

  I propose that we create a new section for optional steps and move this "Removing Elasticsearch" section as well as the "Removing Redundant Firewall Rules" section to a new optional or post upgrade steps section after *all* the upgrade procedures.

Some other time we could move some other common steps there too. For example, the step about "If you have the OpenSCAP plugin"

Comment 3 sthirugn@redhat.com 2016-11-22 19:36:51 UTC
(In reply to Stephen Wadeley from comment #2)
> Hello
> 
> As this section is optional and as moving it is not trivial I decided to
> hide for the moment.
> 
> We do not want to add this procedure to every upgrade procedure, they are
> already far too long.
> 
>   I propose that we create a new section for optional steps and move this
> "Removing Elasticsearch" section as well as the "Removing Redundant Firewall
> Rules" section to a new optional or post upgrade steps section after *all*
> the upgrade procedures.

+1 to adding this after *all* the upgrade procedures inorder to prevent issues in the upgrade process.

Comment 4 Steve Bream 2016-11-23 01:46:14 UTC
Hello Stephen,

I agree with the suggestion to create a new section for optional post-upgrade steps. Let's put it after "Upgrading a Self-Registered Satellite Server", and break it into further sections for each step to be done ("Removing Elasticsearch", "Removing Redundant Firewall Rules", etc.) 

I'm not sure what to call the new section - if all of the procedures in it are removals, we could call it "Post Upgrade Cleanup" and specify at the beginning of the section that all of the procedures are optional, and you can choose to perform only those procedures that are suitable for your installation.

Comment 8 Stephen Wadeley 2016-11-24 09:51:01 UTC
Hello


The changes are now live on the customer portal.

Post Upgrade Cleanup


https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server#post_upgrade_cleanup


Thank you


Note You need to log in before you can comment on or make changes to this bug.