-
Notifications
You must be signed in to change notification settings - Fork 151
Open
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.
Description
According to the CreateVolume specs a volume should not set CapacityBytes
(or set it to 0) to indicate that the capacity is unknown.
// The capacity of the volume in bytes. This field is OPTIONAL. If not
// set (value of 0), it indicates that the capacity of the volume is
// unknown (e.g., NFS share).
// The value of this field MUST NOT be negative.
int64 capacity_bytes = 1;
When running the test CreateVolume [Controller Server] [It] should fail when requesting to create a volume with already exisiting name and different capacity.
it fails as it is not possible to detect this if the volume capacity is always 0.
The test CreateVolume [Controller Server] [It] should not fail when requesting to create a volume with already exisiting name and same capacity.
also fails but as far as I can see this can be fixed by setting TestVolumeSize: 0
.
Metadata
Metadata
Assignees
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.