Pivotal Knowledge Base

Follow

How to Edit Operations Manager actual-installation.yml

Environment

Operations Manager versions 1.12 and 2.x

Purpose

In some cases, it is necessary to directly edit the operations manager actual-installation.yml. The most common use case is when a static IP reference needs to be changed or when there is an IP conflict on one of the errand jobs.

Risks

Editing the actual-installation.yml incorrectly can result in unexpected behavior which could lead to corruption of existing deployments. We do not recommend editing this file as part of a standard operating procedure. One should only edit this file under the guidance and instruction of a Pivotal Engineer.

Procedure

1. ssh into the Operations Manager VM and backup the actual-installation.yml

cp /var/tempest/workspaces/default/actual-installation.yml ~/actual-installation.yml

2. Decrypt the actual-installation.yml. Make sure to use the operations manager decryption passphrase when prompted

ubuntu@pivotal-ops-manager:/tmp$ sudo -u tempest-web RAILS_ENV=production /home/tempest-web/tempest/web/scripts/decrypt /var/tempest/workspaces/default/actual-installation.yml /tmp/actual-installation.yml Passphrase:

3. Locate the object you are instructed to change and make the edit.

4. Encrypt the modified actual-installation.yml and replace the existing one. Make sure to use the operations manager decryption passphrase when prompted

ubuntu@pivotal-ops-manager:/tmp$ sudo -u tempest-web RAILS_ENV=production /home/tempest-web/tempest/web/scripts/encrypt /tmp/actual-installation.yml /var/tempest/workspaces/default/actual-installation.yml Passphrase:

5. Continue with the next steps in your supplied procedure.

Additional Information

Refer to the article, I have forgotten the decrypt passphrase for Ops Manager.

Comments

Powered by Zendesk