-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Platform]Availibility zones change depending on region selection order during Universe creation #8003
Comments
cc @skahler-yuga Let me know if anything else has to be added. |
hi @mjoshi0923 - please check if this issue reproduces for other providers as well (AWS, GCP, etc). |
Sure
…On Mon, 19 Apr, 2021, 7:55 pm streddy-yb, ***@***.***> wrote:
hi @mjoshi0923 <https://github.com/mjoshi0923> - please check if this
issue reproduces for other providers as well (AWS, GCP, etc).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8003 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASVVB6WCZ27GEJ7XTK2LNQTTJQ4PNANCNFSM42Z6S2VQ>
.
|
@adil246 Do we have this issue? This was resolved long back, it's duplicate issue I guess. |
@mjoshi0923 Yes, I do not see the issue now in 2.6.3 and AZ’s placement info is not switching to other zones when additional regions are added. I tested with a couple of regions adding them consecutively in google cloud and placement info stayed the same. I could go back and select Az’s based on preference after adding all regions. This can be closed. Thanks for the follow-up.
|
Description
Az's disappear from the list when a new region is added. This issue appears for the on-prem config provider. If the order is changed when adding regions(for example East first and then Central), the AZ's populate the way they should. Depending on the order you enter the regions, the availability zone list/behavior changes.
To Reproduce
Reference ticket
1081
The text was updated successfully, but these errors were encountered: