@Paramesh malla You can use an Azure Shared Access Signature to restrict the access to your VHD based on time or access policy. You can generate the URL with Azure Storage Explorer like documented here and replace the original in arm-images.yml. ... View more

@Cibi Chakaravarthi If your original question was answered, would you please consider accepting the answer? Thanks! ... View more

@Airawat If you consider your original question answered, would you please consider accepting the answer? Thanks! ... View more

@Abhishek Sakhuja Do you have any updates on this one, have you managed to get this working? If you consider your original question answered, would you pls. consider accepting the answer? ... View more

@Airawat Have you had the chance to have a look at this one? Thanks! ... View more

@Cibi Chakaravarthi I suggest you to try with the new 1.16.5 version as it has this part of code refactored. The update should not affect your running clusters and it can be run with one command "cbd update". Hope this helps! ... View more

@Cibi Chakaravarthi There should be some useful information in the logs (there is no sensitive data in it), so please attach it to the case to be able to investigate. ... View more

@Abhishek Sakhuja The error message is an indication of your HDFS running out of space. The amount of free space is fetched from Ambari and calculated like the following: def Map<String, Map<Long, Long>> getDFSSpace() { def result = [:] def response = utils.slurp("clusters/${getClusterName()}/services/HDFS/components/NAMENODE", 'metrics/dfs') log.info("Returned metrics/dfs: {}", response) def liveNodes = slurper.parseText(response?.metrics?.dfs?.namenode?.LiveNodes as String) if (liveNodes) { liveNodes.each { if (it.value.adminState == 'In Service') { result << [(it.key.split(':')[0]): [(it.value.remaining as Long): it.value.usedSpace as Long]] } } } result } Please check Ambari UI, it can be that Ambari calculates the free space incorrectly. Hope this helps! ... View more