|
---|
Release type: | P-patch |
Release date: | 2019-02-18 |
OS update support: | None |
Technote: | None |
Documentation: | None |
Popularity: | 3004 viewed downloaded |
Download size: | 1.88 GB |
Checksum: | 3621902389 |
CloudPoint 2.1.2 On Ubuntu 16.04 x86-64
|
None.
|
3943759
|
None.
|
* * * READ ME * * * * * * Veritas CloudPoint 2.1.2.7546 * * * * * * Hot Fix 2 * * * Patch Date: 2019-02-15 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.1.2.7546 Hot Fix 2 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- Ubuntu 16.04 x86-64 RHEL 7.5 BASE PRODUCT VERSION FOR THE PATCH ----------------------------------- * Veritas CloudPoint 2.1.2 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch 2.1.2.7546 C3PM-13040 : (C3PM-13041) Allow install when rootfs is mounted in non shared mode Patch 2.1.2.7545: C3PM-12968 : (C3PM-12970) CloudPoint with Proxy Support DETAILS OF INCIDENTS FIXED BY THE PATCH -------------------------------------------- This patch fixes the following JIRA incidents: *C3PM-13040 (Tracking ID: C3PM-13041) SYMPTOM: When using Amazon Linux AMI 2018.03 as the CloudPoint host, the deployment fails due to "Configuration Failed. Error Details: Failed to start flexsnap-vic." This occurs because the rootfs or / shared subtree operation is set to private. findmnt / -o TARGET, PROPAGATION TARGET PROPAGATION / private This appears to be a docker limitation when trying to mount a volumes with the shared docker option. DESCRIPTION: CloudPoint deployment fails if mount propagation is not set as shared on host. In such case, vic and onhostagent containers fail to start during deployment due to insufficient mount priviledge. RESOLUTION: Allow CloudPoint installation with specific parameter if user wants to continue and disable indexing & classification features *C3PM-12968 (Tracking ID: C3PM-12970) SYMPTOM: Plugin configuration in CloudPoint within Proxy environment fails with stack below: HTTPSConnectionPool(host='sts.amazonaws.com', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<botocore.awsrequest.AWSHTTPSConnection object at 0x7f2f9199f550>, 'Connection to sts.amazonaws.com timed out. (connect timeout=60)')) DESCRIPTION: CloudPoint is installed on EC2 instance which is in private network and it is communicating outside through the proxy server. Agent containers are unaware about proxy settings, so the communication with cloud services fail. RESOLUTION: CloudPoint containers would start with these proxy env variables set. When a new plugin is added, new agent container will get spawned with these environment variables set and would be able to communicate with cloud plugins through proxy. User needs to pass all 3 below variables with respective values in the CloudPoint installation command, VX_HTTP_PROXY VX_HTTPS_PROXY NO_PROXY 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.1.2.7546 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.1.2.7542 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.1.2.7546 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.1.2.7546 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.1.2.7546 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.1.2.7546 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.1.2.7546 stop # docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.1.2.7546 uninstall # docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:2.1.2.7542 install 2. The previous version(s) of Docker container images are not removed. You can remove them to save your CloudPoint instance disk space. |
Why Register?
Get notifications about ASLs/APMs, HCLs, patches, and high availability agents
As a registered user, you can create notifications to receive updates about NetBackup Future Platform and Feature Plans, NetBackup hot fixes/EEBs in released versions, Array Support Libraries (ASLs)/Array Policy Modules (APMs), hardware compatibility lists (HCLs), patches and high availability agents. In addition, you can create system-specific notifications customized to your environment.
Compare configurations
The Compare Configurations feature lets you compare different system scans by the data collector. When you sign in, you can choose a target system, compare reports run at different times, and easily see how the system's configuration has changed.
Save configurations
After logging in, you can retrieve past reports, share reports with colleagues, review notifications you received, and retain custom settings. Anonymous users cannot access these features.
Bulk uploader
As a registered user,you can upload multiple reports, using the Bulk Uploader.