Chapter 3. Upgrading Each MBaaS Project 4.6 to 4.7.0

3.1. Overview

Upgrading your deployment of Red Hat Mobile Application Platform from version 4.7 to version 4.7.0:

  • Adds the MONGODB_ENDPOINT_COUNT to the Nagios deployment configuration.
  • Adds annotations to group related services together in the OpenShift UI.
  • Adds the node-proxy ConfigMap Volume mount to fh-statsd.
  • Existing images versions are updated to RHMAP 4.7 versions by modifying the deployment configurations for all objects in the RHMAP MBaaS, which triggers a redeployment of each component.
  • Updates the version in fh-mbaas-info-info ConfigMap in the RHMAP MBaaS project to 4.7
Warning

Before proceeding with the upgrade:

  • Ensure you have administrator permissions for the OpenShift cluster hosting RHMAP.

3.2. Upgrading to RHMAP MBaaS Version 4.7

  1. If you are using the docker image option, mount an inventory file and a valid SSH key for targeting that inventory, for example: 

    docker run -it \
       -v ~/.ssh/id_rsa:/opt/app-root/src/.ssh/id_rsa:Z \
       -v ${HOME}/Desktop/rhmap-ansible/inventories:/opt/app-root/src/inventories \
       -e ANSIBLE_PRIVATE_KEY_FILE=/opt/app-root/src/.ssh/id_rsa \
	   rhmap47/installer bash

  2. With all pods running, back up all persistent volumes using the following commands: 

    oc exec `oc get po --selector='deploymentconfig=mongodb-1' --template="(index .items 0).metadata.name"` bash – -c '/opt/rh/rh-mongodb32/root/usr/bin/mongodump -u admin -p ${MONGODB_ADMIN_PASSWORD} --gzip --archive' > ./core7_mongodb.gz

  3. To upgrade your existing RHMAP MBaaS from 4.6 to 4.7 you must specify:

    • the name of the current project
    • an inventory file

    • project_type which must be set to 1-node-mbaas or 3-node-mbaas.

      An example command is shown below: 

      cd /opt/rhmap/4.7/rhmap-installer
ansible-playbook -i my-inventory-file playbooks/upgrade.yml -e project_type=3-node-mbaas -e project_name=my-rhmap-mbaas-project

      This command reads the current deployment information and chooses the next available upgrade path. A warning message is displayed advising you to back up your data before proceeding. Press Enter to confirm that you have backed up and to continue with the upgrade.

3.3. Verifying RHMAP MBaaS Upgrade

  1. Review the output to verify there were no failures.
  2. Verify all Nagios checks are healthy.
  3. Make sure the component versions match those in the Container Catalog for the erratum.

  4. Verify the mongo replica set has persisted throughout the upgrade. On any mongo pod:

    1. Run oc rsh {{MONGO_POD}}

    2. Log in to the mongo cli:

      mongo admin -u admin -p $MONGODB_ADMIN_PASSWORD

    3. Run rs.status()

      Review the json output and make sure there is one PRIMARY and two SECONDARY members.

See the troubleshooting documentation in cases where the upgrade fails.