question

UdayKiranReddyureddy-2664 avatar image
0 Votes"
UdayKiranReddyureddy-2664 asked UdayKiranReddyureddy-2664 edited

Error: ERROR: 'bytes' object has no attribute 'get' with azure bicep

When trying to run azure bicep deployment, I am getting error as

 Error: ERROR: 'bytes' object has no attribute 'get'
    
 Run azure/arm-deploy@v1
 Validating template...
 Creating deployment...
 Error: ERROR: 'bytes' object has no attribute 'get'
    
 Error: Deployment failed.

And sometimes getting this.

 Validating template...
 Creating deployment...
 Error: ERROR: {"error":{"code":"InternalServerError","message":"Encountered internal server error. Diagnostic information: timestamp '20220401T161715Z', subscription id '***', tracking id '89a94ed9-ccee-45d0-856d-c16258e886a5', request correlation id '89a94ed9-ccee-45d0-856d-c16258e886a5'."}}
    
 Error: Deployment failed.

Please suggest how to fix that?

azure-lab-services-templates-virtual-machines
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

karishmatiwari-msft avatar image
0 Votes"
karishmatiwari-msft answered UdayKiranReddyureddy-2664 edited

Thanks for posting your query.

Issue Summary:
You are seeing the error : 'bytes' object has no attribute 'get' when trying to run azure bicep deployment.

Recommended solution:
We have encountered this issue before and looks like updating to the latest CLI version fixed the issue.
Could you please let me know the AzCLI version you are using? Also, please run the same above command with the parameter --debug and share the results.


Let me know and I can further investigate. Thanks.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

No it doesn't.

I am not using any external runners, I am using direct runners provided by github actions.

Even, I kept the azure cli update command before this step and it has shown console output as the version is already up to date.

 Building dependency tree...
 Reading state information...
 azure-cli is already the newest version (2.33.1-1~focal).
 0 upgraded, 0 newly installed, 0 to remove and 145 not upgraded.






0 Votes 0 ·