Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure CLI use_dynamic_install throws Unhandled promise rejection #72

Closed
briglx opened this issue Mar 3, 2022 · 8 comments
Closed

Azure CLI use_dynamic_install throws Unhandled promise rejection #72

briglx opened this issue Mar 3, 2022 · 8 comments
Assignees
Labels
idle Inactive for 14 days stale 90 days old waiting-for-customer Waiting for inputs from customer

Comments

@briglx
Copy link

briglx commented Mar 3, 2022

I'm trying to run code that requires the az automation extension.

I'm calling az config set extension.use_dynamic_install=yes_without_prompt

Related Issue here Azure/azure-cli#21505

- name: Clean Up Resources
        uses: azure/CLI@v1
        with:
          azcliversion: 2.30.0
          inlineScript: |
            
            # Allow Dynamic installation of extensions
            az config set extension.use_dynamic_install=yes_without_prompt

However it throws the following error:

UnhandledPromiseRejectionWarning: Error: az cli script failed.
    at /home/runner/work/_actions/azure/CLI/v1/dist/index.js:1:2[39](https://github.com/xxx/xxx/runs/5400826457?check_suite_focus=true#step:8:39)64
    at Generator.throw (<anonymous>)
    at rejected (/home/runner/work/_actions/azure/CLI/v1/dist/index.js:1:20436)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:1861) 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(). (rejection id: 1)
(node:1861) [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.
@briglx briglx added the need-to-triage Requires investigation label Mar 3, 2022
@briglx briglx changed the title use_dynamic_install throws Unhandled promise rejection Azure CLI use_dynamic_install throws Unhandled promise rejection Mar 3, 2022
@aparna-ravindra
Copy link

Hey @briglx,
I see that you have already linked the related issue in Azure/azure-cli. Can you please help me understand your expectation from the action?

From your description, my understanding is that the action should continue fail if azure-cli fails but the failure should be handled gracefully so that we do not see the UnhandledPromiseRejectionWarning message. Is my understanding correct?

@briglx
Copy link
Author

briglx commented Mar 3, 2022

Ideally, the solution should not fail. It's not clear what the root cause is for the failure. Is it the Action container version or is it the CLI

@OmpahDev
Copy link

OmpahDev commented Mar 7, 2022

I'm also receiving this error when using the Azure/cli githu action.

@t-dedah
Copy link
Contributor

t-dedah commented Mar 8, 2022

Hi @briglx @tdevopsottawa Can you please provide us with complete logs as there should be a ERROR field with correct error message.

image

@t-dedah t-dedah added waiting-for-customer Waiting for inputs from customer and removed need-to-triage Requires investigation labels Mar 8, 2022
@github-actions
Copy link

This issue is idle because it has been open for 14 days with no activity.

@github-actions github-actions bot added the idle Inactive for 14 days label Mar 15, 2022
@github-actions
Copy link

This issue is stale because it has been open for 7 days with no activity.

@github-actions github-actions bot added the stale 90 days old label Mar 22, 2022
@t-dedah
Copy link
Contributor

t-dedah commented Mar 28, 2022

Hi @briglx Are you still facing this issue?

@briglx
Copy link
Author

briglx commented Apr 12, 2022

Hi, I think there was an error happening above this line.... I've been able to either work around or resolve the issue.

@briglx briglx closed this as completed Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idle Inactive for 14 days stale 90 days old waiting-for-customer Waiting for inputs from customer
Projects
None yet
Development

No branches or pull requests

5 participants