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

GKE - Unable to provision cluster with extra zones #12261

Closed
cpinjani opened this issue Oct 15, 2024 · 2 comments · Fixed by #12289
Closed

GKE - Unable to provision cluster with extra zones #12261

cpinjani opened this issue Oct 15, 2024 · 2 comments · Fixed by #12289
Assignees
@mantis-toboggan-md @yonasberhe23
Labels
area/gke kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this regression status/backport-candidate
Milestone
v2.10.0

Comments

@cpinjani
Copy link

Setup
Rancher - v2.9-99b2583e3370321a922e29a11ac5ff9f845baeb6-head
Dashboard - release-2.9 5b38045

Describe the bug
User is unable to create zonal cluster with extra zones. Its a regression from 2.8
It seems location field is not including the default selected zone (for eg. us-central-1-c)

To Reproduce

  • Provision zonal GKE cluster from Rancher UI
  • While creating select extra zones

Screenshots

image

image
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Oct 15, 2024
@richard-cox
Copy link
Member

@cpinjani no need to put the version in the title, these will all be moved to the latest milestone and a backport issue created if required

@richard-cox richard-cox changed the title [2.9] GKE - Unable to provision cluster with extra zones GKE - Unable to provision cluster with extra zones Oct 17, 2024
@richard-cox richard-cox added this to the v2.11.0 milestone Oct 17, 2024
@richard-cox richard-cox modified the milestones: v2.11.0, v2.10.0 Oct 17, 2024
@mantis-toboggan-md mantis-toboggan-md mentioned this issue Oct 17, 2024
Merged
7 tasks
@yonasberhe23 yonasberhe23 self-assigned this Oct 23, 2024
@yonasberhe23
Copy link
Contributor

Repro'd the issue in 2.9.
In 2.10, the GKE cluster came up active following the repro steps.

Tested in:

  • Rancher v2.10-24040b6dc9ae2fa6a3a49cbe126132c13c2587ba-head
  • Dashboard master 78d12f9

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

@mantis-toboggan-md mantis-toboggan-md

@yonasberhe23 yonasberhe23

Labels
area/gke kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this regression status/backport-candidate
Projects
CAPI / Turtles
Archived in project
Milestone
v2.10.0
Development

Successfully merging a pull request may close this issue.

include gke zone in list of extra locations mantis-toboggan-md/dashboard
4 participants
@richard-cox @mantis-toboggan-md @cpinjani @yonasberhe23