OM fails to login after AWS Elastic IP changes

Products

• Operations Manager

Issue/Introduction

If in the event you do not use a Hostname and use an Elastic IP address when configuring Ops Manager on AWS, you can run into a situation when the Elastic IP address changes and UAA fails to login due to the callback URL changing. 

When you first create your Ops Manager instance it is recommended to use a Hostname to avoid an issue with IP addresses changing, in the event you do use an Elastic IP address instead of a Hostname and the IP address changes please follow these steps.

The UAA config files for Ops Manager are stored in `/home/tempest-web/ramdisk/uaa/config`, however all of these files are overwritten upon restart of UAA process. During the startup of UAA these file's values are obtained from the Ops Manager Postgres Database, you will need to edit the Database directly to change the UAA Callback URL.

Environment

Product Version: 2.10

Resolution

1. SSH into your Ops Manager VM
2. Change into the tempest-web use

​​​​​sudo su tempest-web

3. Connect to the Ops Manager Postgres Database

/usr/local/bin/psql tempest_production

4. Check value of Hostname field in table uaa_configs

tempest_production=# select hostname from uaa_configs;

5. Update record for Hostname in table uaa_configs

tempest_production=# start transaction;
update uaa_configs set hostname='XX.XX.217.242';
commit;

6. Exit Postgres Database
7. Exit tempest-web user
8. Restart tempest-web service

sudo service tempest-web restart