Hi there, We were creating temporary cluster by using cloudera-director. After moving to private/local repos I am encountering issues when installing the cloudera-manager-agent for cm6. (cm5 works fine). Here is what I tested: cloudera-director 2.8.1: using an an template and setting: enableEnterpriseTrial: true repository: "https://XXXXXXX:YYYYY@archive.cloudera.com/p/cm6/6.3.4/redhat7/yum/" repositoryKeyUrl: "https://XXXXXX:YYYYYYY@archive.cloudera.com/p/cm6/6.3.4/redhat7/yum/RPM-GPG-KEY-cloudera" With this setup it will fail at: Cloudera Manager agent installation failed on instance 'IP' after 5 tries. ... Checking the manager logs (same result when using the private repo option with auth: 2021-02-15 06:30:04,433 INFO NodeConfiguratorThread-8-0:com.cloudera.server.cmf.node.NodeConfigurator: Using key bundle from URL: https://a.privaterepo.com/artifactory/cm6/6.3.4/redhat7/yum/RPM-GPG-KEY-cloudera 2021-02-15 06:30:04,488 WARN NodeConfiguratorThread-8-0:com.cloudera.server.cmf.node.NodeConfigurator: Unhandled exception java.lang.SecurityException: Could not verify key bundle I tested with Cloudera Altus Director and get a similar error for the directory, although it seems the issue here that it still point to the public repos (and not the ones I configured in the conf file)   So my question is, is director still supported and if so were there any changes I should be aware of?   thanks      ... View more