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.

Sign up for GitHub

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

Jump to bottom

Workflow failure: Upgrade bridge #310

Closed
pulumi-bot opened this issue Sep 12, 2023 · 6 comments
Closed

Workflow failure: Upgrade bridge #310

pulumi-bot opened this issue Sep 12, 2023 · 6 comments
Assignees
@guineveresaenger
Labels
blocked The issue cannot be resolved without 3rd party action. kind/engineering Work that is not visible to an external user resolution/duplicate This issue is a duplicate of another issue
Milestone
0.94

Comments

@pulumi-bot
Copy link
Contributor

Workflow Failure

Upgrade bridge has failed. See the list of failures below:
@pulumi-bot pulumi-bot added kind/engineering Work that is not visible to an external user needs-triage Needs attention from the triage team p1 A bug severe enough to be the next item assigned to an engineer labels Sep 12, 2023
@guineveresaenger
Copy link
Contributor

This may be one of the upstream azure dependency blockers?

undefined: azcore.Poller

@mikhailshilkov mikhailshilkov removed the needs-triage Needs attention from the triage team label Sep 14, 2023
@mikhailshilkov mikhailshilkov added this to the 0.94 milestone Sep 14, 2023
@t0yv0
Copy link
Member

t0yv0 commented Sep 14, 2023

This is failing because pulumi/pkg brings in a dependency (SPURIOUS!) on Azure SDK which conflicts with the version that vault provider uses upstream. This proves to be quite pesky to resolve. I will try to see what happens if I upgrade upstream together with upgrading pulumi/pkg.

@t0yv0 t0yv0 mentioned this issue Sep 14, 2023
Closed
@guineveresaenger guineveresaenger mentioned this issue Sep 16, 2023
Closed
28 tasks
@t0yv0
Copy link
Member

t0yv0 commented Sep 20, 2023

I confirm this is blocked hard on #197

We need to disable the workflow for vault

@t0yv0 t0yv0 added the blocked The issue cannot be resolved without 3rd party action. label Sep 21, 2023
@guineveresaenger guineveresaenger mentioned this issue Sep 21, 2023
Merged
guineveresaenger added a commit to pulumi/ci-mgmt that referenced this issue Sep 21, 2023
@guineveresaenger
Remove pulumi-vault from regular upgrade maintenance (#602)
0102829 
Due to pulumi/pulumi-vault#197, pulumi-vault
cannot currently benefit from automation per this repository. Putting it
in a separate folder to await the resolution of the blocking issue and
avoid noise and spurious p1s caused by attempts to upgrade the bridge.

Upstream upgrades will continue to run automatically as per current
state of pulumi-vault's Workflow files.

Resolution for pulumi/pulumi-vault#310.
@guineveresaenger guineveresaenger removed the p1 A bug severe enough to be the next item assigned to an engineer label Sep 21, 2023
@guineveresaenger
Copy link
Contributor

Removing the P1 via temporary resolution reached in pulumi/ci-mgmt#602.

Leaving this issue open to track blockers.

@t0yv0
Copy link
Member

t0yv0 commented Sep 21, 2023

I'd close since you did the work. We track it in #197

@guineveresaenger guineveresaenger added the resolution/duplicate This issue is a duplicate of another issue label Sep 21, 2023
@guineveresaenger
Copy link
Contributor

Fair! Closing as resolution-duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@guineveresaenger guineveresaenger

Labels
blocked The issue cannot be resolved without 3rd party action. kind/engineering Work that is not visible to an external user resolution/duplicate This issue is a duplicate of another issue
Projects
None yet
Milestone
0.94
Development

No branches or pull requests
4 participants
@t0yv0 @mikhailshilkov @guineveresaenger @pulumi-bot