NAS-132742 / 24.10.1 / fix key collision in zpool.status (by yocalebo) #15047
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
(cherry picked from commit 4595210)
yocalebo
force-pushed
the
NAS-132742-24.10.1
branch
from
7712fa1
to
421a67e
Compare
yocalebo
approved these changes
Nov 26, 2024
|
This PR has been merged and conversations have been locked. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Someone named one of their zpools
disks..... A strange zpool name but it caused a key collision inzpool.status. Place all zpools underneath a top-levelpoolskey to prevent this scenario.Original PR: #15043
Jira URL: https://ixsystems.atlassian.net/browse/NAS-132742