-
Notifications
You must be signed in to change notification settings - Fork 251
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
[main] Recreate missing backingFsBlockDev on setting xfs project quota #1325
[main] Recreate missing backingFsBlockDev on setting xfs project quota #1325
Conversation
b17adb7
to
2e79f8d
Compare
LGTM |
@saschagrunert Whats up with this one? |
The QA needs to verify that it works with CRI-O (see https://issues.redhat.com/browse/OCPBUGS-773) |
86caf99
to
e1eaada
Compare
There is the rare case that something removed the backingFsBlockDev, which usually points to `/var/lib/containers/storage/overlay/backingFsBlockDev`. In that case, all `SetQuota` operations would fail on overlay layer creation. We now work around that error by recreating the backingFsBlockDev. Signed-off-by: Sascha Grunert <[email protected]>
e1eaada
to
aa0d394
Compare
Manually verified that the patch works with CRI-O. Ready for review @rhatdan. |
LGTM |
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.
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.
LGTM
There is the rare case that something removed the backingFsBlockDev, which usually points to
/var/lib/containers/storage/overlay/backingFsBlockDev
. In that case, allSetQuota
operations would fail on overlay layer creation.We now work around that error by recreating the backingFsBlockDev.
/hold
I have to test this on CRI-O and rebase the change to c/storage v1.37.0
Refers to #1326