[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:
Related
Participants:
Days since reply: 5 years, 19 weeks, 6 days ago
Epic Link: DOCSP-1743
Story Points: 0.2

 Description   

----------------------------

Original Description

In 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.

----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (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

1
%preun
2
if test $1 = 0; then
3
    # Uninstall the mongodb-mms service
4
    if pidof systemd > /dev/null 2>&1; then
5
        # SystemD
6
        systemctl stop mongodb-mms.service
7
        systemctl disable mongodb-mms.service
8
        systemctl reset-failed mongodb-mms > /dev/null 2>&1
9
        rm /usr/lib/systemd/system/mongodb-mms.service
10
        systemctl daemon-reload
11
    else
12
        # SysV
13
        /sbin/chkconfig --del mongodb-mms
14
    fi
15
    rm -f /etc/init.d/mongodb-mms
16
    rm -f /etc/init.d/mongodb-mms-backup-daemon
17
fi
18
exit 0

Create new files

%post
if test $1 = 1; then
    # Create the directory for backups
    mkdir -p $RPM_BUILD_ROOT/var/lib/mongodb/backup
    chown -R mongodb-mms:mongodb-mms $RPM_BUILD_ROOT/var/lib/mongodb/backup
 
    # Link mms and the backup-daemon in /etc/init.d
    ln -s $RPM_BUILD_ROOT/opt/mongodb/mms/bin/mongodb-mms /etc/init.d/mongodb-mms
    ln -s $RPM_BUILD_ROOT/opt/mongodb/mms/bin/mongodb-mms-backup-daemon /etc/init.d/mongodb-mms-backup-daemon
 
    # Install the mongodb-mms service
    if pidof systemd > /dev/null 2>&1; then
        # SystemD
        mkdir -p /usr/lib/systemd/system/
        cp $RPM_BUILD_ROOT/opt/mongodb/mms/conf/mms.systemd /usr/lib/systemd/system/mongodb-mms.service
        systemctl enable /usr/lib/systemd/system/mongodb-mms.service
    else
        # SysV
        /sbin/chkconfig --add mongodb-mms
    fi
fi

Comment by James Broadhead (Inactive) [ 26/Sep/18 ]

(following up from slack)
something like:
"""
If you previously replaced <> symlinks with files, you should delete these files before performing the upgrade
To test: ls -la <files>
– this indicates that these are files, and you must follow this step.
Once you have installed the OM 4.0 rpm, symlinks will be created in this directory.
"""
(Tony: it'd be good if you could confirm that the delteted files get replaced with symlinks by the rpm – it should happen, but I'd like to be 100% sure)

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.
Please add an item in the upgrade docs to delete the copied systemd files & allow `rpm` to install a fresh symlink

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 ]

reverted this commit for v3.6

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?

Generated at Thu Feb 08 08:03:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.