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.

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

Fix flapping Plant region #2582

Merged
merged 1 commit into from
Jul 13, 2020
Merged

Conversation

timebertt
Copy link
Member

How to categorize this PR?

/area quality
/kind bug
/priority normal

What this PR does / why we need it:
Previously, the Plant controller falsely tried to obtain the region of the Plant cluster from the zone Node label, although this is supposed to be a fallback to the region label.
As maps are unsorted in go, the plant controller sometimes used the zone and sometimes the region for reporting the Plant's CloudInfo.
This PR fixes this behaviour and adds an additional cross-check to the Plant integration test.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Release note:

A bug has been fixed, which caused the discovered Plant region to alternate between region and zone of the Nodes.

@timebertt timebertt requested review from a team as code owners July 13, 2020 14:59
@gardener-robot gardener-robot added area/quality Output qualification (tests, checks, scans, automation in general, etc.) related kind/bug Bug priority/normal labels Jul 13, 2020
Copy link
Contributor

@timuthy timuthy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
Nice catch!

@timuthy timuthy merged commit 7ca3755 into gardener:master Jul 13, 2020
@timebertt timebertt deleted the fix/plant-region branch July 13, 2020 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/quality Output qualification (tests, checks, scans, automation in general, etc.) related kind/bug Bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants