Article ID: 126661, created on Aug 23, 2015, last review on Aug 23, 2015

  • Applies to:
  • Operations Automation 5.5

Symptoms

OA Management node was migrated from to Centos 6 node, and it was found that Windows Azure pack application parts are missing:

  • no 'WAP - 1.4-*.parallels.noarch' RPM

  • no 'WAPKeyStore' files on new management node

    # ls -lt /usr/local/share/WAP/
    ...
    -rw-r--r-- 1 root root      4 Jun 10 11:40 WAP.jmx
    -rw-r--r-- 1 root root   2193 Jun 10 11:33 wap-config.xml
    drwxr-xr-x 2 root root   4096 Jun 10 11:33 scripts
    drwxr-xr-x 2 root root   4096 Jun 10 11:33 lib
    drwxr-xr-x 2 root root   4096 Jun 10 11:33 config
    -rw-r--r-- 1 root root    218 Feb 27 08:55 build.properties
    -rw-r--r-- 1 root root   1469 Feb 27 08:55 IaaSKeyStore
    -rw-r--r-- 1 root root   2292 Feb 27 08:55 logback.xml
    -rw-r--r-- 1 root root 116140 Feb 27 08:55 WAP.app.zip
    -rw-r--r-- 1 root root 243577 Feb 27 08:55 WAP.jar
    

Cause

WAP data is not migrated during OA MN migration.

Resolution

  1. Install the same WAP RPM as was installed on the original Management Node

  2. Check for the following files:

    /usr/local/share/WAP/wap-config.xml /usr/local/share/WAP/WAPKeyStore /usr/local/share/WAP/IaaSKeyStore

    If they are absent or delivered within RPM package, backup them first and then replace with original files from previous MN installation

  3. Restart WAP service:

    # service WAP restart
    Stopping WAP                                            [ OK ]
    Starting WAP                                            [ OK ]
    
  4. Re-add Admin portal and Tenant portal settings via Services > Cloud Infrastructure > Windows Azure Pack > Settings

Search Words

Windows Azure Pack

MN migration

WAP APS

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF