When admins set up HA in OAG via the Management Console, they may get an error like:
Instance is not ready for HA.
There could be multiple reasons why it can happen. The article shows two of the common scenarios with the solution.
- Okta Access Gateway (OAG)
- High Availability (HA)
- The worker node cannot resolve its hostname; that is, SSH to the same host does not work. In that case, the error will look like the following:
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
- The worker node cannot resolve the admin node, OR SSH connectivity is blocked to/from the admin node. In that case, the error will look like the following:
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
- Make sure the complete string is copied from the admin that was generated by the Prepare Admin option. It will be in the format <hostname>:<authorization_code>.
- Make sure the hostname is set on the new node.
- This will create the needed loopback entries in the host file.
- Make sure the admin and worker nodes are resolvable from each other through DNS, and SSH connectivity is not blocked between the two.
In case DNS entries cannot be made, then the following steps can be used to add IP and Hostname in /etc/hosts on both admin and worker nodes:- From the Management Console, press 1 - Network
- Press 3 - Edit /etc/hosts
- Press a > [a]dd entry
- Enter the IP address > ENTER > enter the hostname > ENTER
- Press c > [c]ommit changes
- Repeat the same for other node(s)
- Make sure HTTPS connectivity is not blocked from the worker node to the Admin.
- Try to set up High Availability again.
Related References
- Firewall Requirements- Access Gateway High Availability section
