-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Do not surface left servers #6420
Conversation
706e7ba
to
fcf8421
Compare
fcf8421
to
f0cb17f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall I think this looks good, made one minor comment inline but it's not a blocker.
d38f2ee
to
b3eb511
Compare
This feels like a small breaking change since the output of an endpoint is changing. Maybe we should get it into 1.7.0 but not 1.6.x? |
@freddygv Well, this change the output in very rare occasions (when DC is dead for more than 72 hours or operator did force-leave the servers), so it looks to me like a very reasonable choice that would unlikely break workflows (while helping a lot during decommission). |
I agree with @pierresouchay on this one. I think this a bugfix, what would anyone want to do with decommissioned datacenters... And thus I think it would be fine to include it into 1.6.x series. |
I noticed the other functions that are returning datacenters and I want to make sure to make them all behave similarly. |
Hey there, This issue has been automatically locked because it is closed and there hasn't been any activity for at least 30 days. If you are still experiencing problems, or still have questions, feel free to open a new one 👍. |
Left servers will never come back so there is no reason to surface them in
GetDatacentersByDistance
. One of the results is that dcs with only left servers will no longer show up inv1/catalog/datacenters
, which is the right thing to do since this dc is not reachable.