Okta Access Gateway "Instance is not ready for HA" Error Occurs When Adding a Worker Node
Last Updated:
Overview
When adding a worker node to Okta Access Gateway (OAG) High Availability (HA), OAG generates an "nstance is not ready for HA error. This occurs when the worker node cannot resolve its hostname or the admin node, or when firewalls block Secure Shell (SSH) connectivity. Copy the authorization token, configure the hostname, and ensure Domain Name System (DNS), SSH, and HTTPS connectivity between nodes to resolve the error. The following error messages appear during the HA setup process:
Instance is not ready for HA.
Checking HA readiness for host <worker_hostname> Instance is not ready for HA. See details below:
SSH connectivity is blocked to masterNode: <worker_hostname>
Exiting.
FAILURE RC=1
Enter the authorization token displayed on admin node: <admin_hostname>:<auth_code>
Checking HA readiness for host <admin_hostname> Instance is not ready for HA. See details below:
Unable to resolve masterNode: <admin_hostname>
Fix DNS or add to local hosts file
Exiting.
FAILURE RC=1
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Access Gateway (OAG) High Availability (HA)
Cause
The worker node cannot resolve its hostname, the worker node cannot resolve the admin node, or firewalls block SSH connectivity to or from the admin node.
Solution
What steps resolve the instance is not ready for High Availability error?
Copy the authorization token, configure the hostname, verify DNS resolution, and ensure firewalls allow SSH and HTTPS connectivity between the worker and admin nodes.
- Copy the complete string that the Prepare Admin option generates from the admin node in the
<hostname>:<authorization_code>format. - Configure the hostname on the new node to create the required loopback entries in the host file.
- Configure DNS to ensure the admin and worker nodes resolve each other, and verify that firewalls do not block SSH connectivity between the two nodes.
- Verify that firewalls do not block HTTPS connectivity from the worker node to the admin node.
- Set up High Availability again.
What steps add the IP address and hostname to the hosts file without DNS entries?
Add the IP address and hostname to the /etc/hosts file on both the admin and worker nodes using the Management Console.
- Select 1 - Network from the Management Console.
- Select 3 - Edit /etc/hosts.
- Select a to add an entry.
- Enter the IP address, press Enter, enter the hostname, and press Enter.
- Select c to commit the changes.
- Repeat these steps for the other nodes.
