CP-50026 Ensure mpathcount runs after multipath deactivate #736
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
Some orders of doing things do not trigger udev events with the right timing to get the multipath config records updated when multipath is shut down entirely. Deliberately kick the mpathcount pipe after multipath is deactivated, which will ensure that the mpathcount service runs shortly after. If it had already been kicked and had not yet run, this extra kick will have no effect. Signed-off-by: Tim Smith <[email protected]>
MarkSymsCtx
approved these changes
Mar 4, 2025
LunfanZhang
approved these changes
Mar 5, 2025
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.
Some orders of doing things do not trigger udev events with the right timing to get the multipath config records updated when multipath is shut down entirely.
Deliberately kick the mpathcount pipe after multipath is deactivated, which will ensure that the mpathcount service runs shortly after. If it had already been kicked and had not yet run, this extra kick will have no effect.