rbd: update PV metadata#6059
Merged
Merged
Conversation
When regenerating journal pass the requestName parameter to PrepareVolumeMetadata instead of an empty string. Signed-off-by: Praveen M <m.praveen@ibm.com>
Member
|
I am not sure the PV has the same name on both clusters. Maybe the empty name is intentional (which would definitely deserve a comment in the code). |
Madhu-1
approved these changes
Feb 16, 2026
Collaborator
It was a miss when we added support for it. |
Rakshith-R
approved these changes
Feb 16, 2026
Member
|
@Mergifyio queue |
Contributor
Merge Queue StatusRule:
This pull request spent 2 hours 46 minutes 32 seconds in the queue, including 2 hours 46 minutes 17 seconds running CI. Required conditions to merge
|
This file contains hidden or 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
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.
Describe what this PR does
Am not sure why we didn't set the PV metadata during RegenerateJournal. I tried to find from git blame and PR which introduced it but couldn't find any conversation around it. May be we missed noticing it?
Checklist:
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)