I installed a HDF cluster via Ambari and enabled NiFi SSL with NiFi CA. In the Ambari configurations, I put in the keystore and truststore path as: /usr/hdf/current/nifi/conf/keystore.jks # same for truststore.jks The HDF cluster seems working well but when I try to inspect the keystore / truststore file using command like below: keytool -v -list -keystore keystore.jks # also tried with absolute path even without the `current` # link folder I get a file not exist problem like below: [ec2-user@nifi01 conf]$ keytool -v -list -storepass changeit -storetype jks -keystore /usr/hdf/3.1.1.0-35/nifi/conf/keystore.jks keytool error: java.lang.Exception: Keystore file does not exist: /usr/hdf/3.1.1.0-35/nifi/conf/keystore.jks java.lang.Exception: Keystore file does not exist: /usr/hdf/3.1.1.0-35/nifi/conf/keystore.jks at sun.security.tools.keytool.Main.doCommands(Main.java:783) at sun.security.tools.keytool.Main.run(Main.java:366) at sun.security.tools.keytool.Main.main(Main.java:359) But when I do the `ls` command, the file is right there. Anything I missed? I just need to check the content within the keystore/truststore ... View more

I m trying to use Ambari API only to provision a cluster, from my understanding, I need to: Create a cluster Create a service Register hosts to cluster Create components under service Create Config with Tag & type Apply Config using Tag & Type to Cluster Assign Roles to Hosts Start everything I m currently trying to apply configs base on an existing cluster, however, what I find out is that the cluster configurations could have following different tags: versionXXXXX tag INITIAL tag TOPOLOGY_RESOLVED tag My understanding is: versionXXXX tag is probably where we putting the custom configurations, but I don't know from Ambari API point of view, how could I generate INITIAL/ TOPOLOGY_RESOLVED tags configurations? And did I missed any points from above steps? Thanks ... View more