controller/scanner: should consider the wwn of the added blockdevice #136
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tserong
approved these changes
Sep 23, 2024
- We should also consider the wwn of the added blockdevice in
the same round.
Signed-off-by: Vicente Cheng <vicente.cheng@suse.com>
Vicente-Cheng
force-pushed
the
fix-duplicated-wwn-disks
branch
from
c81c6f7
to
e221d5f
Compare
|
@Mergifyio backport v0.7.x |
✅ Backports have been created
|
bk201
approved these changes
Sep 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
It would not work well if two duplicate WWN devices wanted to join simultaneously.
Solution:
Should consider the WWNs even if in the same round
Related Issue:
harvester/harvester#6604
Test plan: