[DOCS-11872] Additional step needed for Ops Manager upgrade instructions on RHEL7.1 and RHEL7.2 Created: 12/Jul/18 Updated: 29/Oct/23 Resolved: 27/Sep/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Roger McCoy (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
RHEL7.1 RHEL7.2 |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 5 years, 19 weeks, 6 days ago | ||||
| Epic Link: | DOCSP-1743 | ||||
| Story Points: | 0.2 | ||||
| Description |
|
---------------------------- Original DescriptionIn earlier Ops Manager installation documents, a step is provided to workaround a symlink issue on RHEL7.1 and RHEL7.2: The documentation to upgrade Ops Manager should also mention the workaround for RHEL7.1 and RHEL7.2 because the RPM upgrades will not update the copied files. It's included in the 3.4 upgrade instructions This should also be included for the 3.6 and 4.0 upgrade instructions too. ---------------------------- DescriptionScope of changes (files that need work and how much)Impact to other docs outside of this productMVP (work and date?)Resources (e.g. Scope Docs, Invision) |
| Comments |
| Comment by Anthony Sansone (Inactive) [ 27/Sep/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
james.broadhead: If I am reading the code correctly (see below), any symlinks or files for mongodb-mms* in /etc/init.d are deleted. mihai.bojin@mongodb.com replaced these correctly for both SystemD and SystemV per PR 14391. That said, nothing needs to be added to this page. I am going to put this ticket as Resolved and will close COB tomorrow unless you or Mihai disagree. Remove old files / symlinks
Create new files
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by James Broadhead (Inactive) [ 26/Sep/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
(following up from slack) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Anthony Sansone (Inactive) [ 26/Sep/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I added the step back to the upgrade docs only. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by James Broadhead (Inactive) [ 25/Sep/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
tony.sansone Yeah, because of the old instructions, we should add an item to the upgrade docs to revert. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Ravind Kumar (Inactive) [ 14/Jul/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
alan.mccoy The 3.6 docs install page now has the symlink instructions restored. That also seems to have fixed the link in the upgrade instructions Am I correct in thinking that, while the overall issue is fixed in 4.0, users upgrading from 3.6 to 4.0 still have to take some steps to avoid issues? cc tony.sansone | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Ravind Kumar (Inactive) [ 13/Jul/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Publishing shortly. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Ravind Kumar (Inactive) [ 13/Jul/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
tony.sansone can you handle from here? you have the most familiarity with this subject. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Roger McCoy (Inactive) [ 12/Jul/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
See the linked HELP-7074 for note to open a docs ticket.
Also, I understand if the symlink workaround is longer needed in 4.0. However for the upgrade instructions, it seems a note is needed for RHEL7.1 and RHEL7.2 customers that applied the workaround earlier. The older, copied scripts will still be under `/etc/init.d`. Should the symlink be put back?
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Ravind Kumar (Inactive) [ 12/Jul/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
These instructions are no longer required for OM 4.0 as per this DOCSP-2539 / CLOUDP-30146
The pull for DOCSP-2539 had v3.6 included. Did engineering confirm these instructions are no longer an issue for 3.6? |