When does Cloudera Director's script read the /etc/issue file? Cloudera Director reads the /etc/issue prior to bootstrap script execution and as soon as SSH access to the instance is available. Does it read the result of that file as it is displayed when connecting with SSH? No Or does it read the /etc/issue file after it connects? Yes Is there another option to skip the OS check or set something in our bootstrap script (that depends on when the file is read)? We are considering smarter OS detection capabilities for future Cloudera Director releases. Unfortunately at the moment Cloudera Director relies on the /etc/issue file. Here is a proposal for example Red Hat 6: Cloudera Director needs at a bare minimum /etc/issue file contain “Red Hat release 6.”. Although this isn’t ideal, it does provide some obfuscation of the exact detailed OS type. Thanks, Cagdas
... View more
