* * * READ ME * * *
                 * * * Veritas CloudPoint 2.2.2.8303 * * *
                         * * * Hot Fix 1 * * *
                         Patch Date: 2019-12-20

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.2.8303 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.2


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch 2.2.2.8303 
STESC-3774 (C3PM-16415): Cloud Point's Windows Agent that is registered can sometime fail and become unavailable.
STESC-3774 (C3PM-16324): Onhost agent registration can fail due to request timeout.

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

*STESC-3774 (Tracking ID: C3PM-16415)

SYMPTOM:
Cloud Point's Windows Agent that is registered can sometime fail and become unavailable.
Following errors can be seen in CloudPoint logs:

flexsnap-agent-onhost MainThread flexsnap.connectors.rabbitmq: ERROR - Channel 1 closed unexpectedly: (405) RESOURCE_LOCKED - cannot obtain exclusive access to locked queue '<agent_name>' in vhost '/'

DESCRIPTION:
Windows Agent that is registered can fail and become unavailable. The issue is seen after the agent machine restart. The rabbitmq exclusive queue running before machine restart still exists after the machine is up. Hence, new exclusive queue cannot be acquired and  due to this the operation fails with RESOURCE_LOCKED error.

RESOLUTION:
Code changes are done to close the agent connection is at time of graceful system shutdown.

*STESC-3774 (Tracking ID: C3PM-16324) 

SYMPTOM:
Onhost agent registeration can fail with following error:
flexsnap-agent-onhost Thread-3 agent: ERROR - Request timed out.

DESCRIPTION:
Onhost agent registeration can fail due to timeout error.
Coordinator sends all the files in /lib folder and all the plugins to on-host agent when the agent comes online first time.
This quite a big data transfer, due to which the agent can hit it's timeout value and registration can fail.

RESOLUTION:
Code changes have been done to send only required library files and supported plugins to the agent.

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.2.8303 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:<installed_cp_version> 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.2.8303 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.2.8303 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.2.8303 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.2.8303 
  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.2.8303 stop
    # docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.2.2.8303 uninstall
    # docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:<previous_cloud_point_version> install
2. The previous version(s) of Docker container images are not removed. You can remove them to save your CloudPoint instance disk space.