Description of problem:
Apparently a very recent change in jdk policies disabled TLSv1, which is used by default by Ambari agents to communicate with the Ambari server.
This means that the Ambari plugins is not working anymore. Recent change because it was working until (at least) the end of April 2018, and one of the document describing the issue was published on May 3th.
After some digging, its seems that this issue is fixed or at least can be workarounded only from Ambari 126.96.36.199 or >=2.5. More details in this ticket: https://issues.apache.org/jira/browse/AMBARI-17666
This is the relevant commit: https://github.com/apache/ambari/commit/b9de1383cd714ccc132e84abb80e8760d75a573e
The important document from Hortonworks describing the issue is: https://community.hortonworks.com/articles/188269/javapython-updates-and-ambari-agent-tls-settings.html
In addition to the patch, the agents should be configured to use a newer version of TLS. This means changing /etc/ambari-agent/conf/ambari-agent.ini on the images and adding a new key in the [security] section:
This means the the Ambari images can be fixed only upgrading to 188.8.131.52; that means sahara-image-pack can be used without problems; sahara-image-elements defaults to older versions for older versions of HDP for historical reasons, even if 2.4 could be used too even for HDP 2.4 and HDP 2.3, but it may require more time.
Version-Release number of selected component (if applicable):
All versions of Sahara.
The fix which bumps the version of TLS used by ambari-agent to 1.2 is available. In an image generated by sahara-image-pack, the Ambari agents can talk to ambari-server, thus allowing the creation of the cluster.
Verified with (source package):
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.