* * * READ ME * * *
                 * * * Veritas CloudPoint 2.2.1.8270 * * *
                         * * * Hot Fix 1 * * *
                         Patch Date: 2019-09-12
Etrack No:3984845

This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * BASE PRODUCT VERSION FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLING THE PATCH
   * KNOWN ISSUES
   * NOTE

PATCH NAME
----------
Veritas CloudPoint 2.2.1.8270 Hot Fix 1


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Ubuntu 16.04 x86-64
RHEL 7.5


BASE PRODUCT VERSION FOR THE PATCH
-----------------------------------
   * Veritas CloudPoint 2.2.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch 2.2.1.8270
STESC-3414 (C3PM-15951): Coordinator stucks in restarting state post upgrade to 2.2.1

DETAILS OF INCIDENTS FIXED BY THE PATCH
--------------------------------------------
This patch fixes the following JIRA incidents:

*STESC-3414 (Tracking ID: C3PM-15951)

SYMPTOM:
Coordinator service was stuck in running state post upgrade to CP 2.2.1.
 
DESCRIPTION:
This issue was observed post upgrade from CP 2.1.2 -> CP 2.2 -> CP 2.2.1, where CP host was installed on GCP.
GCP plugin discovery was never finished in CP 2.2 before starting CP 2.2.1 upgrade.
 
RESOLUTION:
1.	In CP 2.1.2, GCP network tags were stored as "tags" attribute in dictionary format but after CP 2.2.0 they were renamed as "networktags" because "tags" attribute was used to store user defined tags/labels in a list format to make it generic in all cloud plug-ins.
2.	As GCP plugin discovery was not finished in CP 2.2, all the required tags were not converted in expected format so after CP 2.2.1 upgrade, coordinator service failed to process the “tags” attribute as it was not in appropriate format.
3.	Fix is to ignore the processing of “tags” attribute if it is not in expected format during coordinator service start-up. GCP plugin converts those attributes in appropriate format during discovery.

INSTALLING THE PATCH
--------------------
I. Before patching:
  1. Contact Veritas Technical Support for this Hot Fix.
  2. Untar the Hot Fix file to a CloudPoint host.
  3. Run the following commands to load the patch.
    # docker load -i <veritas-cloudpoint-img.gz>
    # docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.2.1.8270 load
  4. Ensure that there are no protection policy snapshots or other operations in progress.
     Estimate the patching time will be 15 minutes to an hour.
  5. Log out from the CloudPoint UI.
  6. Run the following command as root to stop CloudPoint.
    # docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.2.0.7959 stop

II. Patching:
	Run the following command as root.
    # Check rootfs mount propagation on the CloudPoint host using "findmnt -o TARGET, PROPAGATION -n /"
    # If above command return mount propagation other than 'shared' then run following command for installation
	docker run --rm -it -e SKIP_SHARED_MNT=Yes -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.2.1.8270 install
        Else run following command
    	docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.2.1.8270 install

    # Run the following command as root when you want to setup CloudPoint with Proxy Environment.
        docker run -it --rm -v /cloudpoint:/cloudpoint -e VX_HTTP_PROXY=<http_proxy_value> -e VX_HTTPS_PROXY=<https_proxy_value> -e VX_NO_PROXY=<no_proxy_value> -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.2.1.8270 install

III. After patching:
  1. Refresh your web broswer and log in to the CloudPoint UI.
  2. Verify the CloudPoint version. Click on Settings and select About. The following information should show up.
    Current Version: 2.2.1.8270
  3. Verify the CloudPoint data.

KNOWN ISSUES
-----------
N/A

NOTE
----
1. Roll back to the previous version if needed.
  a. Log out from the CloudPoint UI.
  b. Run the following commands as root.
    # docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.2.1.8270 stop
    # docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.2.1.8270 uninstall
    # docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.2.0.7959 install
2. The previous version(s) of Docker container images are not removed. You can remove them to save your CloudPoint instance disk space.