Bug 1828198
Summary: | CDI: scratch space looks for default storage class even when scratchSpaceStorageClass is configured | |||
---|---|---|---|---|
Product: | Container Native Virtualization (CNV) | Reporter: | Natalie Gavrielov <ngavrilo> | |
Component: | Storage | Assignee: | Alexander Wels <awels> | |
Status: | CLOSED NOTABUG | QA Contact: | Natalie Gavrielov <ngavrilo> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 2.3.0 | CC: | alitke, cnv-qe-bugs, ncredi | |
Target Milestone: | --- | Keywords: | Automation | |
Target Release: | 2.4.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: |
Cause:
scratchSpaceStorageClass is defined to be hostpath-provisioner while hostpath-provisioner is not set as default storage
Consequence:
upload pod doesnt become ready
Workaround (if any):
Set hostpath-provisioner Storage class to be default
Result:
|
Story Points: | --- | |
Clone Of: | ||||
: | 1828265 (view as bug list) | Environment: | ||
Last Closed: | 2020-05-20 11:23:47 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1828265 |
Description
Natalie Gavrielov
2020-04-27 09:56:00 UTC
I do not consider this as a blocker, but I do think we should add it as a known issue in 2.3 docs I have added suggeted doc @Adam, @Natalie please review I think this issue is not hpp specific. I assume that it will probably happen regardless of any storage type used. The main issue here is that scratchSpaceStorageClass configuration is being ignored and not having default storage class defined reveals it. Agreed this looks like an issue with CDI and would therefore be storage agnostic. I agree that it should be documented for 2.3. Alexander, please take a look. So this is not a bug, here is what happened: 1. You ran: virtctl image-upload dv dv-name --size=1Gi --image-path=cirros-0.4.0-x86_64-disk.qcow2 --insecure 2. You have no default storage class. 3. The PVCs are created as expected, and in the yaml of the PVCs you can see that the scratch space PVC is using the hostpath-provisioner storage class, but the target PVC has no storage class, and no storage class is defined. 4. The POD cannot run, because the target PVC cannot be bound. The scratch space PVC is not bound because of WaitForFirstConsumer waiting for a consumer (which would normally be the upload pod, but it cannot run because the target PVC cannot be bound due to no storage class). In short it is doing exactly what it is supposed to do. If you specify the storage class in the virtcl image-upload command to be hostpath-provisioner, then this will all work. Please close after verifying that adding the storage class to the target PVC in the upload command works as expected. Alexander is right, I was probably too tired when opening this one :), sorry for the hassle. |