Skip to content
This repository has been archived by the owner on May 7, 2021. It is now read-only.

Kola fails on AWS if the kola security group doesn't have a VPC attached #914

Closed
yuqi-zhang opened this issue Sep 14, 2018 · 2 comments
Closed

Kola fails on AWS if the kola security group doesn't have a VPC attached #914

yuqi-zhang opened this issue Sep 14, 2018 · 2 comments
Labels
component/kola kind/bug

Comments

@yuqi-zhang
Copy link
Contributor

Minor bug: If the VPC gets pruned, but the security group is not deleted, it will cause a failure like:

error resolving subnet: no subnets found for vpc vpc-xxxxxx

Can be worked around by deleting security group and have Kola re-create everything.
arithx added a commit to arithx/mantle that referenced this issue Oct 9, 2018
@arithx
platform/api/aws/networking: detect broken networking
5723b25 
Add detection for missing networking pieces when selecting a security
group (tearing down and recreating them if resources are missing).

Fixes coreos#914
@arithx arithx mentioned this issue Oct 9, 2018
Closed
@bgilbert
Copy link
Contributor

bgilbert commented Nov 7, 2018

I talked with @yuqi-zhang OOB and he doesn't think this is likely to be a recurring issue in our environment.

@arithx
Copy link
Contributor

arithx commented Mar 14, 2019

Closing WONTFIX. We're planning on adding ore commands to create & delete networking resources #992 rather than creating them if they're not found during a kola run. With that change the answer will be to just delete & recreate the networking resources.

@arithx arithx closed this as completed Mar 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
component/kola kind/bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bgilbert @arithx @yuqi-zhang