0.7.4 Upgrade procedure

Run platform upgrade script

Applying this upgrade will stop and reboot your nodes. Therefore, you should reserve a window of at least 3 hours for the upgrade.

The upgrade script supports upgrading TAP 0.7.3 to TAP 0.7.4 with no CDH pre-work.

1. Make sure the CDH cluster state is green.

2. Back up your mission-critical data (CDH, Docker DBMS, etc.).

3. Back up all ELK data if needed, as the upgrade process will clear all indices.

4. Log in to your JumpBox instance using SSH and become root:

   ssh ubuntu@<JumpBoxEIP> -i <key.pem>

5. Use your virtual terminal to copy the upgrade script to:

   /root/upgrade_to_v0.7.4.sh

6. As root, run the following command:

   chmod +x /root/upgrade_to_v0.7.4.sh; /root/upgrade_to_v0.7.4.sh

• with Kerberos disabled:

sudo -i curl -Sso upgrade_to_v0.7.4.sh https://s3.amazonaws.com/trustedanalytics/upgrade_to_v0.7.4.sh && sudo -i bash upgrade_to_v0.7.4.sh ```

• with Kerberos enabled:

sudo -i curl -Sso upgrade_to_v0.7.4.sh https://s3.amazonaws.com/trustedanalytics/upgrade_to_v0.7.4.sh && sudo -i KERBEROS_ENABLED=True bash upgrade_to_v0.7.4.sh ```

7. Monitor the upgrade process. If the command fails, try again. When done, all your nodes, including your JumpBox, will be rebooted.

8. Check the integrity of your data. Restore any data of bad or suspect integrity from the backups you made in step 2.

Openstack/Bare Metal Troubleshooting

If you cannot create organizations or users, the auth-gateway service is having issues with the Znode connection. The following procedure will synchronize organizations and repair the problem.

cf se auth-gateway ENGINE_TIMEOUT 6000
cf restage auth-gateway
curl -X PUT -H "Authorization: $(cf oauth-token |grep bearer)" -v auth-gateway.<tap_domain>/synchronize?async=true -f

Wait ~45 minutes.

curl -X PUT -H "Authorization: $(cf oauth-token |grep bearer)" -v auth-gateway.<tap_domain>/jobs/<jobId from synchronize output>