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

client: update driver info on new driver fingerprint #4984

Merged
merged 1 commit into from
Dec 11, 2018

Conversation

notnoop
Copy link
Contributor

@notnoop notnoop commented Dec 11, 2018

Fixes a bug where a driver health and attributes are never updated from
their initial status. If a driver started unhealthy, it may never go
into a healthy status.

@@ -1186,6 +1185,7 @@ func (c *Client) updateNodeFromDriver(name string, info *structs.DriverInfo) *st
}

hasChanged = true

if newVal == "" {
delete(c.config.Node.Attributes, attrName)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is a bug in this code where node attributes are never removed if the key was removed from driver info. Fixing this requires comparing previous driver info against new one and removing old keys from node attributes. This seems somewhat complex and I suspect some of the attribute changes will be deprecated and removed by 0.10; so not sure if I should fix it here.

Fixes a bug where a driver health and attributes are never updated from
their initial status.  If a driver started unhealthy, it may never go
into a healthy status.
@notnoop notnoop force-pushed the b-client-update-driver branch from fc417fa to cae36e4 Compare December 11, 2018 19:29
@notnoop notnoop merged commit 926428f into master Dec 11, 2018
@notnoop notnoop deleted the b-client-update-driver branch December 11, 2018 23:07
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants