Platform

Upgrade Alma Linux to 8.6

Feature Summary and Revision History

Table 1. Summary Data

Applicable Product(s) or Functional Area

CPS

Applicable Platform(s)

Not Applicable

Feature Default

Enabled – Always-on

Related Changes in This Release

Not Applicable

Related Documentation

Not Applicable

Revision History

Revision Details

Release

First introduced.

23.1.0

Feature Description

In CPS 23.1.0 release, Alma Linux version 8.5 is replaced with Alma Linux 8.6 along with upgrading to the latest rpm packages and their dependencies.

With Alma Linux 8.6, the kernel version is modified to:


[root@localhost ~]# rpm -qa | grep kernel-[0-9]
kernel-4.18.0-372.32.1.el8_6.x86_64
[root@localhost ~]# cat /etc/redhat-release
AlmaLinux release 8.6 (Sky Tiger)
[root@localhost ~]# uname -a
Linux localhost.localdomain 4.18.0-372.32.1.el8_6.x86_64 #1 SMP Tue Oct 25 05:53:57 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost ~]#

Upgrade MongoDB Version 4.4

Feature Summary and Revision History

Table 2. Summary Data

Applicable Product(s) or Functional Area

CPS

Applicable Platform(s)

Not Applicable

Default Setting

Enabled – Configuration Required

Related Changes in This Release

Not Applicable

Related Documentation

Not Applicable

Table 3. Revision History

Revision Details

Release

First introduced

23.1.0

Feature Description

This release provides support for MongoDB version 4.4.0.

You can upgrade CPS 22.2.0 (using mongoDB version,4.2.20) to CPS 23.1.0 (using mongoDB version,4.4.18).

Un-Supported CPS Releases for Ugrading to Mongo 4.4

Any CPS version prior to CPS 22.2.0 such as CPS 22.1.1 (using mongoDB version 4.0.27) and previous versions of CPS (using mongoDB version 3.x) does not support direct upgrade to CPS 23.1.0 (using mongoDB version 4.4.18).

To upgrade the mongoDB version to 4.4, you must upgrade to CPS version 22.2.0, which uses the mongoDB 4.2.20 version. For example, if you are running mongoDB 3.6 series in your CPS release, it is required to first upgrade to 4.0 and then to 4.2 before planning for any upgrade to 4.4.

Support for MongoDB 4.4 Version in vDRA

Feature Summary and Revision History

Table 4. Summary Data

Applicable Product(s) or Functional Area

vDRA

Applicable Platform(s)

Not Applicable

Default Setting

Enabled – Configuration Required

Related Changes in This Release

Not Applicable

Related Documentation

Not Applicable

Table 5. Revision History

Revision Details

Release

First introduced

23.1.0

Feature Description

This release provides support for MongoDB version 4.4.18

Upgrade, Migrate, and Backward Compatibility Considerations

  • Supported DRA Releases for Upgrading to 4.4: You can upgrade vDRA 22.2.0 (mongoDB version,4.2.20) to vDRA 23.1.0 (mongoDB version,4.4.18).

  • Un Supported DRA Releases for Upgrading to 4.4: Any DRA version prior to CPS 22.2.0 such as DRA 22.1 (mongo 4.0.27 MMAP storage engine), 21.2 (mongo 3.6.9) or DRA 19.4/18.2 (mongo 3.4.5) and previous versions of DRA, does not support direct upgrade to DRA 23.1 (mongoDB version, 4.4.18)


    Note

    Upgrading to DRA 23.1 is supported only from DRA 22.2.0.

Mongo Java Driver: MongoDB version 4.4 requires Mongo Java Driver version 3.12.9.

Prerequisite for upgrading to 23.1 from 22.2.0 and rollback from 23.1 to 22.2.0

The following are the common prerequisites for upgrade and roll back:

  • Run the following CLI before upgrade:

    #database genericfcvcheck 4.2

    Note

    Make sure to run the above CLI before upgrade and / or downgrade on all sites.
  • Specify any one of the CLI options:

    • Set: This option checks and sets FCV only on primary.


      Note

      We recommend to use Set option first and then Check to make sure that FCV is replicated on secondary members. Upgrade/downgrade should not be triggered if any error is found in above CLI or FCV is not replicated on secondary members. Make sure to resolve the CLI error, rerun the CLI, and then only proceed for upgrade or downgrade.
    • Check: This option only checks FCV on all members (primary, secondary, and arbiter).

Upgrade to 23.1.0

  1. Run the prerequisite steps.

  2. Follow the standard documented procedure for upgrade.

Downgrade from 23.1.0

  1. Run the steps mentioned in the prerequisite section.

  2. Follow the standard documented procedure for downgrade.