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 issue with multiple volume refs with same name #20381
Conversation
Signed-off-by: Brian Goff <cpuguy83@gmail.com>
be288d6
to
0fe3130
Compare
@tiborvass @cpuguy83 given that we have two "panic" issues, should we have a 1.10.2 branch, and open these fixes on that branch? |
refs, exists := s.refs[v.Name()] | ||
if !exists { | ||
return | ||
} |
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.
I think this check is still need. Or else if s.refs[v.Name()]
does not exists, the s.refs[v.Name()] = refs
will make it exists, this may cause issue if some other operation relay on _, exists := s.refs[v.Name()]
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.
We aren't tracking existence anywhere as it's not what matters. What matters here is length (ie, 0 length it has no references, > 0 length it has references).
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.
make sense if we aren't tracking existence anywhere :)
https://jenkins.dockerproject.org/job/Docker-PRs-WoW-TP4/1137/console
|
@coolljt0725 does this LGTY? |
@thaJeztah Yes, LGTM |
LGTM |
Fix issue with multiple volume refs with same name
Fixes #20378