many: add ephemeral-mount-namespace feature #14726
Draft
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
|
To test this you have to enable the feature: sudo snap set core experimental.ephemeral-mount-namespace=trueEDIT: I've made that the default behavior now, to see how tests fare. You can still set it to false explicitly, to disable the feature. |
When the feature is enabled no mount namespace persistence is attempted. This is done in response to problematic behavior of ongoing updates, even under a frozen control group. This change is disruptive and does not account for tests that currently observe this behavior. Signed-off-by: Zygmunt Krynicki <[email protected]>
This is for testing in spread, so that I see something useful when I wake up tomorrow. Signed-off-by: Zygmunt Krynicki <[email protected]>
zyga
force-pushed
the
rfc/disable-ns-persistence
branch
from
db936ed
to
94d48bf
Compare
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.
When the feature is enabled no mount namespace persistence is attempted. This is done in response to problematic behavior of ongoing updates, even under a frozen control group.
This change is disruptive and does not account for tests that currently observe this behavior.
For context: this is one of the two follow-ups identified in #14714