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

Workflow failure: master #1556

Closed
pulumi-bot opened this issue Dec 23, 2024 · 7 comments · Fixed by #1565
Closed

Workflow failure: master #1556

pulumi-bot opened this issue Dec 23, 2024 · 7 comments · Fixed by #1565
Assignees
Labels
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 resolution/fixed This issue was fixed

Comments

@pulumi-bot
Copy link
Contributor

pulumi-bot commented Dec 23, 2024

Workflow Failure

master 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 Dec 23, 2024
@t0yv0 t0yv0 self-assigned this Dec 23, 2024
@t0yv0
Copy link
Member

t0yv0 commented Dec 23, 2024

RLimit related failures

+  aws:eks:Cluster extra-sg-eksCluster creating (49s) error:   sdk-v2/provider2.go:520: sdk.helper_schema: creating EKS Cluster (extra-sg-eksCluster-8cc9cc4): operation error EKS: CreateCluster, https response error StatusCode: 400, RequestID: 795a84b6-2472-4a3a-9b65-2047bf20cd92, ResourceLimitExceededException: Cluster limit exceeded for account.: provider=aws@6.65.0```

@flostadler
Copy link
Contributor

A lot of other limits as well:

api error NatGatewayLimitExceeded: Performing this operation would exceed the limit of 50 NAT gateways: provider=aws@6.59.1

Did the tests fail midway through or did you cancel some of them? They should clean those things up themselves.
I guess we just did a lot of troubleshooting with renovate yesterday?

I'm gonna kick off the account cleaner manually to quickly get to a clean slate

@flostadler
Copy link
Contributor

Worked after cleaning, but getting the following error now:

ERROR    HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/        
         The use of local versions in <Version('3.7.0a1734993898+c81c828')> is  
         not allowed. See                                                       
         https://packaging.python.org/specifications/core-metadata for more     
         information.    

I think something's wrong with the version detection

@t0yv0
Copy link
Member

t0yv0 commented Dec 27, 2024

I did not cancel anything manually.

@t0yv0
Copy link
Member

t0yv0 commented Dec 27, 2024

Having a look.

@t0yv0
Copy link
Member

t0yv0 commented Dec 27, 2024

On the succeeding job we had this:

/home/runner/work/pulumi-eks/pulumi-eks/sdk/python/bin/dist/pulumi_eks-3.6.0a1734980228.tar.gz

Run pulumi/pulumi-package-publisher@v0.0.20
  with:
    sdk: all
    version: 3.6.0-alpha.1734980228

On the failing version we had:

Run pulumi/pulumi-package-publisher@696a0fe98f86d86ada2a842d1859f3e8c40d6cd7
  with:
    sdk: all
    version: 3.7.0-alpha.1734993898+c81c828

Something changed in the version field.

What publish.yml received into version input.

What prerequisites returned as an output.

@pulumi-bot
Copy link
Contributor Author

This issue has been addressed in PR #1565 and shipped in release v3.7.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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 resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants