Azure bootstrap failure: Altus v6.1

Question

Basic error on the created notes is that the resolve.conf fails to parse.

in looking at a failed node, the resolve.conf file was poorly created - see below:

# Generated by NetworkManager
nameserver [an ip address]
search

Note that there's nothing after above "search". I fixed this issue by running the setup script on the Altus host.

Problem is that the generated nodes fail to create well constucted "resolve.conf" files - which then leads to the parse error.

GaryS · Accepted Answer

The Azure DNS workaround fixed the connectivity issue. working on a different problem - this one is fixed.

GaryS · Answer

Think I may have found a bad script... isn't setting up the host (in Azure) for a correctly configured "/etc/resolv.conf"

Does anybody know where the scripts are simply located on the Altus server? Prefer to simply fix it rathern than upload something through the web-ui.

Sign up

Please use your Cloudera account.

Login to the community

Please use your Cloudera account.