AutoYaST: avoid repeating filesystem elements for Btrfs multidevice filesystems #993
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
imobachgs
changed the title
imobachgs
changed the title
joseivanlopez
approved these changes
Nov 7, 2019
|
✔️ Public Jenkins job #225 successfully finished |
|
✔️ Internal Jenkins job #48 successfully finished |
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 exporting a Btrfs multidevice filesystem, the filesystem related information will be repeated for each component. For instance, the list of subvolumes will appear in all
<partition>elements which are part of the Btrfs filesystem. See bsc#1148578.Additionally, this PR prevents exporting the
enable_snapshotselement when thedrivesection does not contain the root filesystem. The reason for this change is that snapshots will be applied only to the root filesystem, so it does not make sense in any other drive.