-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
None
-
False
-
-
False
-
1
-
None
-
None
-
uShift Sprint 276
I see cases related to storage are failing due to the issues below
storage: size of the vm is small (while creating vm may be we need to increase space, also i see a pod is missing, may be we creating this as part of our feature_config may be ?
oc --kubeconfig=/home/ec2-user/microshift/_output/test-images/scenario-info/el96-lrel@ginkgo-tests/kubeconfig get pod -n openshift-lvm-storage -l app.kubernetes.io/part-of=lvms-provisioner -o=jsonpath=
{.items[*].metadata.name}Failing cases:
===================
[sig-storage] STORAGE Author:rdeore-MicroShiftOnly-High-75652-[MicroShift] CSI Plugability: Check both CSI Snapshotting & Storage are togglable independently [Disruptive] [Serial] -> oc --kubeconfig=/home/ec2-user/microshift/_output/test-images/scenario-info/el96-lrel@ginkgo-tests/kubeconfig get pod -n openshift-lvm-storage -l app.kubernetes.io/part-of=lvms-provisioner -o=jsonpath={.items[*].metadata.name}
[sig-storage] STORAGE MicroShiftOnly-Author:rdeore-LEVEL0-Critical-59658-[MicroShift] User can create PVC with Block VolumeMode -> Not enough storage
[sig-storage] STORAGE MicroShiftOnly-Author:rdeore-LEVEL0-Critical-59660-[MicroShift] Volumes resize on-line [Serial] -> expand timed out, so may be no enough storage here too ?
- clones
-
USHIFT-6089 Fix network gingko cases that are failing when run them through microshift ci in prow
-
- Closed
-
- links to