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

Bug 2010174: Fix duplicate PVs for disk by-names #292

Merged
merged 1 commit into from Nov 9, 2021

Conversation

gnufied
Copy link
Member

@gnufied gnufied commented Nov 2, 2021

@gnufied gnufied changed the title Fix duplicate PVs for disk by-names Bug 2010174: Fix duplicate PVs for disk by-names Nov 2, 2021
@openshift-ci openshift-ci bot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Nov 2, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

@gnufied: This pull request references Bugzilla bug 2010174, which is invalid:

  • expected the bug to target the "4.10.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 2010174: Fix duplicate PVs for disk by-names

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gnufied

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 2, 2021
@gnufied
Copy link
Member Author

gnufied commented Nov 2, 2021

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2021

@gnufied: This pull request references Bugzilla bug 2010174, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.0) matches configured target release for branch (4.10.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (wduan@redhat.com), skipping review request.

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Nov 2, 2021
deviceName := filepath.Base(deviceNameLocation.diskNamePath)

for i := range pvs {
pv := pvs[i]
Copy link
Member

Choose a reason for hiding this comment

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

Minor nit: you could use for _, pv := range pvs like you did on line 276 and avoid the extra pv := pvs[i] line. Purely optional.

Copy link
Member Author

Choose a reason for hiding this comment

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

I was doing that on purpose to avoid globbering of loop variables by goroutines. I know that is not the case here, but I am trying to adopt this pattern as matter of style rather than only when needed.

Copy link
Member

Choose a reason for hiding this comment

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

Ok that's fine, just caught my eye.

if !found || name != r.runtimeConfig.Name {
continue
}
addOrUpdatePV(r.runtimeConfig, pv)
Copy link
Member

Choose a reason for hiding this comment

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

When we're populating the cache here, is it possible to get a competing addOrUpdatePV call via CreateFunc?

CreateFunc: func(e event.CreateEvent, q workqueue.RateLimitingInterface) {
pv, ok := e.Object.(*corev1.PersistentVolume)
if ok {
handlePVChange(runtimeConfig, pv, q, false)
}
},

If so, what would happen in that case? Could we end up with the same PV added twice?

Copy link
Member Author

Choose a reason for hiding this comment

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

The PVs in cache are keyed by volume names, which is supposed to be a unique string cluster-wide and hence last update will win I think. For our purpose here, it won't matter I think.

@dobsonj
Copy link
Member

dobsonj commented Nov 8, 2021

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 8, 2021
@openshift-merge-robot openshift-merge-robot merged commit e3dc9f4 into openshift:master Nov 9, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 9, 2021

@gnufied: All pull requests linked via external trackers have merged:

Bugzilla bug 2010174 has been moved to the MODIFIED state.

In response to this:

Bug 2010174: Fix duplicate PVs for disk by-names

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants