Closed OmpahDev closed 2 years ago
Hi @tdevopsottawa Can you please provide us with complete logs as there should be a ERROR
field with correct error message.
This issue is idle because it has been open for 14 days with no activity.
This issue is stale because it has been open for 7 days with no activity.
Hi @tdevopsottawa Let me know if you are still facing this problem and reopen the issue
Hi @t-dedah,
I've received this a few times today. No explanation for it. Had worked on same Self Hosted Runner (Linux) yesterday with zero code changes since.
Error:
ERROR: 'bytes' object has no attribute 'get'
Error: Error: az cli script failed.
cleaning up container...
MICROSOFT_AZURE_CLI_16488[18](https://<redacted>/runs/5788376876?check_suite_focus=true#step:5:18)864547_CONTAINER
(node:913745) UnhandledPromiseRejectionWarning: Error: az cli script failed.
at /home/cfadmin/actions-runner/_work/_actions/azure/CLI/v1/dist/index.js:1:23964
at Generator.throw (<anonymous>)
at rejected (/home/cfadmin/actions-runner/_work/_actions/azure/CLI/v1/dist/index.js:1:[20](https://github.com/<redacted>/runs/5788376876?check_suite_focus=true#step:5:20)436)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:913745) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:913745) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Versions:
az -v
azure-cli 2.34.1
core 2.34.1
telemetry 1.0.6
Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0
Python location '/opt/az/bin/python3'
Extensions directory '/home/cfadmin/.azure/cliextensions'
Python (Linux) 3.8.12 (default, Mar 2 2022, 07:26:21)
[GCC 9.3.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Issue reported here also:
When I changed
- name: WHAT-IF
id: whatif
uses: azure/CLI@v1
with:
azcliversion: 2.30.0
to
- name: WHAT-IF
id: whatif
uses: azure/CLI@v1
with:
azcliversion: 2.34.1
It worked, bu then it consistently failed. 😢 New Error (similar):
ERROR: ***'code': 'InternalServerError', 'message': "Encountered internal server error. Diagnostic information: timestamp '[20](https://github.com/<redacted>/runs/5789619701?check_suite_focus=true#step:5:20)[22](https://github.com/<redacted>/runs/5789619701?check_suite_focus=true#step:5:22)0401T143627Z', subscription id '***', tracking id '450bcfe5-da0d-4837-b0f6-9533f5fa54cb', request correlation id '450bcfe5-da0d-4837-b0f6-9533f5fa54cb'."***
Error: Error: az cli script failed.
cleaning up container...
MICROSOFT_AZURE_CLI_16488[23](https://github.com/<redacted>/runs/5789619701?check_suite_focus=true#step:5:23)769927_CONTAINER
(node:2[24](https://github.com/<redacted>/runs/5789619701?check_suite_focus=true#step:5:24)56) UnhandledPromiseRejectionWarning: Error: az cli script failed.
at /home/cfadmin/actions-runner/_work/_actions/azure/CLI/v1/dist/index.js:1:23964
at Generator.throw (<anonymous>)
at rejected (/home/cfadmin/actions-runner/_work/_actions/azure/CLI/v1/dist/index.js:1:20436)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:22456) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:22456) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Garrard.
I have a pretty simple Azure/cli step in my pipeline that's giving me the error:
This is the task code: