-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata rework #3637
Metadata rework #3637
Conversation
a801fa0
to
7b5a294
Compare
@jbaublitz Plz rebase and resolve conflicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two requests...still working.
2fc437e
to
57470ba
Compare
2cab794
to
8924c5c
Compare
8924c5c
to
795ee44
Compare
/packit test |
Please go ahead and extend the TMT-based udev and bind tests for v2 pools. #3643 is an indication of how to do that. The actual test changes are not at all considerable, feel free to choose something else if you want. |
9eef69e
to
6839415
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In pool-level metadata, "features" is double-nested. Here is an excerpt from the metadata print out.
"features": {
"features": [
"Encryption"
]
},
This is not a bug, but rather the result of the default behavior for serde derive. We chose to wrap the features in a new-type struct which is resulting in the double nesting. To change the behavior you're seeing if it's important to you, I think we could either replace the new-type struct with a Vector in the metadata or we could rename one of the keys. |
It is certainly a consequence of the default behavior for |
This commit adds a linear device in between the thin pool and linear device containing all of the data devices. This will later be used when the cryptsetup layer is moved on top of the cap device. This way, the backing device for the crypt device will never change. Changing the backing device for the dm-crypt device outside of cryptsetup could result in future problems.
I'm going to try rerunning the tests here. I've been unable to reproduce the failures I'm seeing locally in a VM with the same code. |
/packit test |
I think this might be a timing issue which is why I can't reproduce it locally. Last time rawhide succeeded. |
76e6ccb
to
e8cb1b4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo located...
7d083c2
to
f611762
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more...
f611762
to
5f121e0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, modulo the requirement to remove temporary test redirects.
Signed-off-by: mulhern <amulhern@redhat.com>
5f121e0
to
d69a78f
Compare
Follow up on #3274