Upgrading fails on step 4 of 9 in vRealize Operations Manager 6.x
search cancel

Upgrading fails on step 4 of 9 in vRealize Operations Manager 6.x

book

Article ID: 344404

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • Running either the Virtual Appliance OS or product upgrade PAK (any platform) to upgrade vRealize Operations fails on step 4 of 9 in the Admin UI on using custom certificates.
  • In the /storage/log/vcops/log/pakManager/vcopsPakManager.root.apply_system_ update.log file, you see entries similar to:

    INFO - Making CaSA call to indicate tc server will be restarted
    INFO - Entering return Pak ID from the manifest: "/storage/db/pakRepoLocal/vRealizeOperationsManagerEnterpriseVAOSUpgrade-6203542056/extracted/manifest.txt"
    Traceback (most recent call last):
    File "updateCoordinator.py", line 647, in <module>
    main()
    File "updateCoordinator.py", line 630, in main
    CasaManager().notify_casa_of_tc_restart()
    File "updateCoordinator.py", line 319, in notify_casa_of_tc_restart
    connection.request(call_type, casa_url, body=request_data, headers=self.headers)
    File "/usr/lib/vmware-vcopssuite/python/lib/python2.7/httplib.py", line 1001, in request
    .
    .
    .
    ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Environment

VMware vRealize Operations Manager 6.2.x
VMware vRealize Operations Manager 6.4.x
VMware vRealize Operations Manager 6.1.x
VMware vRealize Operations Manager 6.3.x

Cause

This issue occurs because the Webchain file is empty which is expected when you use a self signed certificate, however the upgrade coordinator scripts do not expect this Webchain file to be empty on using custom certificates.

Resolution

This is a known issue affecting vRealize Operations Manager 6.x.

Currently, there is no resolution.

To work around this issue:

  1. Log in to vRealize Operations Manager node as root user through SSH or console.
  2. Run this command to make cluster to use the default certificate:

    curl --request POST 'https://master_ip/casa/security/cluster/activewebservercert' --insecure --data '{"certificate_type": "DEFAULT"}' --header 'Content-Type: application/json' --user admin:admin_password

    Note: Replace master_ip and admin_password with the correct values for your cluster.

  3. Log in to vRealize Operations Manager UI as admin user.
  4. Install the pak file again by selecting Install the pak file even if it is already installed.

    Note: Do not click Finish install. Let the upgrade complete and wait for the cluster to come back online.

  5. Run this command to change your cluster back to using the custom certificate:

    curl --request POST 'https://master_ip/casa/security/cluster/activewebservercert' --insecure --data '{"certificate_type": "CUSTOM"}' --header 'Content-Type: application/json' --user admin:admin_password

    Note: Replace master_ip and admin_password with the correct values for your cluster.

    Note: From the vRealize Operations Manager admin UI verify the custom certificate being used.

If the issue persists, contact VMware Support and note this Knowledge Base article ID (2147205) in the problem description. For more information, see How to Submitt a Support Request(2006985).



Additional Information

vRealize Operations Manager 6.x 中的升级在第 4 步(共 9 步)失败
手順 4/9 で vRealize Operations Manager 6.x のアップグレードが失敗する