-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
8
-
False
-
-
False
-
- CDI PR to tighten alert conditions - merged including tier-1 tests
- Test plan updated
- Runbooks updated and merged
-
---
-
---
-
-
Storage Core Sprint 250, Storage Core Sprint 251, Storage Core Sprint 252, Storage Core Sprint 253, Storage Core Sprint 254
-
No
This is a follow-up to CNV-30695. See linked bugs for reference field noisy alerts to be covered by this story.
Suggested changes:
- CDIDefaultStorageClassDegraded - shouldn't fire when no default SC (k8s/virt)
- CDIDataImportCronOutdated - shouldn't fire when no default SC (k8s/virt) as DIC import DVs use default SC
- CDIStorageProfilesIncomplete - should we alert on local SC? (e.g. provisioner: kubernetes.io/no-provisioner)
- CDINoDefaultStorageClass - fire not only when there is a pending DV (& PVC) but also when DV has an empty status (waiting for default SC etc.)
- incorporates
-
CNV-28956 [2209014] CDIDataImportCronOutdated alert is firing in ~50% of the clusters that report to Telemetry
- Closed
-
CNV-28958 [2209032] CDIStorageProfilesIncomplete is firing in 42% of external clusters that are reporting to Telemetry
- Closed
- is cloned by
-
CNV-40356 [4.16] Suppress alerts to reduce noise of dependent ones
- Closed
-
CNV-40360 [4.14] Suppress alerts to reduce noise of dependent ones
- Closed
- links to
- mentioned on
(2 links to, 1 mentioned on)