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: main #164

Closed
pulumi-bot opened this issue Sep 7, 2024 · 2 comments
Closed

Workflow failure: main #164

pulumi-bot opened this issue Sep 7, 2024 · 2 comments
Assignees
@flostadler
Labels
kind/engineering Work that is not visible to an external user p1 A bug severe enough to be the next item assigned to an engineer resolution/no-repro This issue wasn't able to be reproduced

Comments

@pulumi-bot
Copy link
Contributor

Workflow Failure

main 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 7, 2024
@flostadler
Copy link
Contributor

flostadler commented Sep 9, 2024 •
edited
Loading 

  aws-native:ec2:SubnetRouteTableAssociation (MyVpcPrivateSubnet2RouteTableAssociation86A610DA):
    error: creating resource: reading resource state: operation error CloudControl: GetResource, https response error StatusCode: 400, RequestID: e141bcd0-3958-4e1f-ba97-dfcb19b351ca, ResourceNotFoundException: AWS::EC2::SubnetRouteTableAssociation Handler returned status FAILED: No route tables Found with association rtbassoc-055d01a67275742da (HandlerErrorCode: NotFound, RequestToken: b95a9099-43fa-49b4-a313-edf027a6e9bb)

Maybe an intermittent issue. Will retry

@flostadler flostadler removed the needs-triage Needs attention from the triage team label Sep 9, 2024
@flostadler flostadler self-assigned this Sep 9, 2024
@flostadler
Copy link
Contributor

Retry worked

@flostadler flostadler added the resolution/no-repro This issue wasn't able to be reproduced label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flostadler flostadler

Labels
kind/engineering Work that is not visible to an external user p1 A bug severe enough to be the next item assigned to an engineer resolution/no-repro This issue wasn't able to be reproduced
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@flostadler @pulumi-bot