-
Notifications
You must be signed in to change notification settings - Fork 244
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Corrects the validation logic for target volume. Below description of the original problem: When validating whether an image will fit into a PV we compare the image's virtual size to the filesystem's reported available space to guage whether it will fit. The current calculation reduces the apparent available space by the configured filesystem overhead value but the overhead is already (mostly) factored into the result of Statfs. This causes the check to fail for PVCs that are just large enough to accommodate an image plus overhead (ie. when using the DataVolume Storage API with filesystem PVs with capacity constrained by the PVC storage request size). This was not caught in testing because HPP does not have capacity constrained PVs and we are typically testing block volumes in the ceph lanes. It can be triggered in our CI by allocating a Filesystem PV on ceph-rbd storage because these volumes are capacity constrained and subject to filesystem overhead. Signed-off-by: Bartosz Rybacki <brybacki@redhat.com>
- Loading branch information
Showing
4 changed files
with
18 additions
and
19 deletions.
There are no files selected for viewing
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
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
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
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