問題

Admin tries to update alerts email via the following command but the modification is not taking effect or if it does take effect, it is not retained every time the server is rebooted:

hipchat email --alerts-email=new_email@example.com

原因

There is an existing alerts email set in vApp settings in the VMware vCenter environment that will always restore this specific email for each server reboot. 

ソリューション #1

When you run the following command, the specified email address will be updated in /etc/monit/monitrc and /etc/chef/solo.json

hipchat email --alerts-email=new_email@example.com

If not, admin can work around this manually by editing these files (root access needed) and update it with the required email address as follows: 

1. Switch to root

   sudo dont-blame-hipchat

2. Update the email address in /etc/monit/monitrc, please change the addresses accordingly

   sed -i 's/old_email@example.com/new_email@example.com/g' /etc/monit/monitrc

3. Update the email address in /etc/chef/solo.json

   sed -i 's/old_email@example.com/new_email@example.com/g' /etc/chef/solo.json

4. Validate the change

   hipchat email --show

ソリューション #2

If that still didn't help and the old alerts email kept being restored, consider the next steps to tackle this issue:

1. SSH into the server and run this command:

   grep 'old_email@example.com' /etc/*.sh

2. Check the returned result. If the results have an output like the following, it means the alerts email has been set in vApp settings in the VMware vCenter environment e.g.:

   /etc/ovfenv.sh:hc_emailContact="old_email@example.com"

3. The above indicates that the alerts email address has been set in /etc/ovfenv.sh which points to the configuration in vCenter

4. The only way to properly update the alerts email without it restoring old alert email is to completely remove it from the vApp settings in the VMware vCenter environment.