Addnode resolv.conf Failures

Today I was trying to add a new node to an existing Oracle RAC cluster. Grid Infrastructure is version 12.1.0.2 running on Oracle Linux 5.11.

I ran through the usual Cluster Verification Utility (CVU) checks and all checks passed. To add the node, I issued the following command from the $GRID_HOME/addnode directory.

./addnode.sh -silent "CLUSTER_NEW_NODES={newnode}" "CLUSTER_NEW_VIRTUAL_HOSTNAMES={newnode-vip}"

The operation would fail. The log file showed the following error:

INFO: *********************************************
INFO: Task resolv.conf Integrity: This task checks consistency of file /etc/resolv.conf file across nodes
INFO: Severity:CRITICAL
INFO: OverallStatus:OPERATION_FAILED

I know for certain that there are no issues with resolv.conf. It has been working just fine on the two existing nodes. Everything checks out. This hasn’t been my first issue with resolv.conf over the years. Normally, I know that the OUI gets the check wrong and I ignore the condition and continue.
It should boast of a long list of satisfied clients and should deal only viagra free pill in authentic products. Although the cialis samples utilization of goji berries is considered safe, it is best to be a bit cautious. So, if you are going through impotence and looking for a true savior then blue tadalafil pharmacy online pillenis your answer. They are connected with a percentage of the main factors that levitra pills can affect the married life of both men and women.
I did find some help via Google to set the following environment variable before running addnode.sh:

export IGNORE_PREADDNODE_CHECKS=Y

This sounded promising. However, it made no difference and I received the same error. Since addnode.sh is calling the OUI in silent mode, I figured I would try the directive to ignore prerequisites.

./addnode.sh -silent "CLUSTER_NEW_NODES={drorp05}" "CLUSTER_NEW_VIRTUAL_HOSTNAMES={drorp05-vip}" -ignoreSysPrereqs

I still received the same error. So how do I get addnode.sh to get past the failed check? The solution was too obvious to be seen initially.

The addnode.sh script just calls the OUI. So the answer is to run just the following:

./addnode.sh

Run the script with no parameters. This fires up the GUI version of the OUI. The next screen asks for the new host name and its VIP, which were previously parameters to the script. The checks were run and of course, a failure was seen. But this time, I could check the box to Ignore the failures and continue with the installation.