Azure-cli: When tagging the Azure HDInsight Cluster using az resource tag --tags environment=development --ids $rid, it is failing

Created on 25 Oct 2018  ·  10Comments  ·  Source: Azure/azure-cli

When tag the Azure HDInsight Cluster using

az resource tag --tags environment=development --ids $rid

it fails with the following error message

“Operation failed with status: 'Bad Request'. Details: 'BlueprintUri' cannot be used together with 'Kind'. Please specify only one of the properties during create.,Both 'password' and 'sshProfile' cannot be null,Both 'password' and 'sshProfile' cannot be null,Both 'password' and 'sshProfile' cannot be null”

To reproduce this issue, ensure that you have a hdinsight cluster

try to tag it from az cli / Cloudshell using the command

az resource tag --tags environment=development --ids $rid

I am using the same command to tag all the resources in my subscription and it works well. But when trying to tag the HDInsight Cluster the issue happens..

Environment summary
Azure Subscription and a HD Insight Cluster.

Please help me fix this issue. (Created a ticket with Microsoft Azure Support and they confirmed that it is a bug.)

HDInsight Service Attention bug

Most helpful comment

This is a server-side bug where our RP has issues updating via PUT from the contents of a GET on the cluster resource. We're tracking this item internally.

Note that this isn't an issue with the HDInsight command module itself, as az resource uses the resource command module and the actual bug is RP-side. This could be avoided if PATCH was used instead, though the right approach is to fix the RP bug.

All 10 comments

Please note: I am able to tag the same HD Insight Cluster using Azure PowerShell command and the Azure Portal (Portal.azure.com).

any updates?

This is a server-side bug where our RP has issues updating via PUT from the contents of a GET on the cluster resource. We're tracking this item internally.

Note that this isn't an issue with the HDInsight command module itself, as az resource uses the resource command module and the actual bug is RP-side. This could be avoided if PATCH was used instead, though the right approach is to fix the RP bug.

any updates after 5 months

any updates?

@wawon-msft

Are there any updates on this? Also can you please patch if there is one?

getting same Both 'password' and 'sshProfile' cannot be null,Both 'password' and 'sshProfile' cannot be null when trying to create a cluster.

getting same Both 'password' and 'sshProfile' cannot be null,Both 'password' and 'sshProfile' cannot be null when trying to create a cluster.

Hi @pacuna , would you mind sharing the command that ran into the issue? Looks like this is a different issue.

To tag an HDInsight cluster, please use az hdinsight update --tags

Was this page helpful?
0 / 5 - 0 ratings