N2WS-24114 - N2WS AMI redeploy fails for server upgraded with patch

Issue:

Customers who upgraded their N2WS server from v4.2 to v4.3 with patch downloaded from release notes before 20th June, will not be able to redeploy the server.

When trying to redeploy from marketplace and using existing 4.3 cpmdata volume, configuration fails with following error in the logs:

ERROR: write_cpm_db_version(cpm_config_utils.py:54) Failed to set updated DB version in DB: 1
ERROR: done(views.py:291) Configuration Failed with Exception: Failed to set updated DB version in DB: 1

Solution:

1. Install attached patch for v4.3

Note: this is not needed if you upgraded using AMI

• Related Articles

• N2WS-21357 - Patch installation fails with Internal Server Error

  Issue: Patch installation fails with this error in the UI Solution: 1. Connect to the N2WS server via SSH, username is cpmuser and your selected keyPair 2. Run the following command sudo grep PrivateTmp /lib/systemd/system/apache2.service 3. If ...

• How to upgrade CPM using a patch

  Please note: upgrading using patch does not upgrade Apache/OS Upgrade Diagram General 1. It is recommended to deploy the patch when you have no active backup policies, DR or recovery running. as it will restart Apache and require few min downtime. 2. ...

• How To Install a Patch to the N2WS Instance

  How To Install a Patch on the N2WS Instance 1. Go to General Settings, then choose "Patches". 2. Click "choose file" , browse to the patch file and open it. 3. The file name should now appear in the window, then click on "upload and install". 4. You ...

• CPM in Recovery Mode error - S3 worker fails with worker i-12345678912345678 stopped communicating - terminating operation

  CPM in Recovery Mode error - S3 worker fails with worker i-12345678912345678 stopped communicating - terminating operation Issue: When CPM is in recovery mode being used for DR drills, the original CPM’s process to detect “zombie” worker’s can be ...

• N2WS-19169 - Cleanup may fail because of "Can't find mapping for account "

  Issue: Cleanup process may fail because server fails to clean cross-region AMI DR: ERROR: get_account_dict(account_utils.py:114) account PolicyName(user root) not found in account map, even after refresh. ERROR: ...