config validation for network fails in other regions that are not default #955
Labels
area/networking
Networking related
area/robustness
Robustness, reliability, resilience related
kind/bug
Bug
platform/openstack
OpenStack platform/infrastructure
status/closed
Issue is closed (either delivered or triaged)
Comments
gardener-robot
added
area/networking
|
Hi, I have created a pull request to fix this issue that I am facing, please review it and tell me if there are any other changes that need to be made. |
gardener-robot
added
the
status/closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to categorize this issue?
/area robustness
/area networking
/kind bug
/platform openstack
What happened: Tried creating shoot in other regions than the default with OpenStack configuration of our infrastructure, but it refused to discover network from the selected region.
What you expected to happen: Healthy creation of infrastructure.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: I have also created and tested a fix for this issue. Currently while creating networking client for terraform validations, region is not being used as parameter for the function.
Environment:
kubectl version):The text was updated successfully, but these errors were encountered: