Bug 2039489
| Summary: | KubePersistentVolumeFillingUp Firing for VM disk Filesystem PVCs | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Alex Kalenyuk <akalenyu> |
| Component: | Storage | Assignee: | Alex Kalenyuk <akalenyu> |
| Status: | CLOSED ERRATA | QA Contact: | Yan Du <yadu> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.10.0 | CC: | alitke, cnv-qe-bugs, mrashish, yadu |
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-cdi-controller v4.10.0-77, CNV v4.10.0-600 | Doc Type: | Bug Fix |
| Doc Text: |
When provisioning a virtual machine disk OpenShift Virtualization allocates a PVC that is just large enough to accommodate the requested disk size. In previous releases this could result in a KubePersistentVolumeFillingUp alert for each VM disk PVC. Since the PVC is deliberately filled, this alert is now silenced automatically. Disk usage can be monitored from within the virtual machine itself.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-16 16:06:09 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: | |||
Test on CNV v4.10.0-605, KubePersistentVolumeFillingUp is not firing, issue has been fixed. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Virtualization 4.10.0 Images security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0947 |
Description of problem: KubePersistentVolumeFillingUp is firing for Filesystem PVCs that hold a VM disk although them being filled is by design Version-Release number of selected component (if applicable): 4.10.0 How reproducible: 100% Steps to Reproduce: 1. Create DV, VM (manifests below) 2. Observe alerts Actual results: KubePersistentVolumeFillingUp firing Expected results: KubePersistentVolumeFillingUp not firing Additional info: We can now use the following label on PVCs to prevent the alert from going off: alerts.k8s.io/KubePersistentVolumeFillingUp: disabled Manifests: apiVersion: cdi.kubevirt.io/v1beta1 kind: DataVolume metadata: name: simple-dv-cephfs spec: source: http: url: "http://.../Fedora-Cloud-Base-34-1.2.x86_64.qcow2" pvc: storageClassName: ocs-storagecluster-cephfs volumeMode: Filesystem accessModes: - ReadWriteOnce resources: requests: storage: 5Gi --- apiVersion: kubevirt.io/v1 kind: VirtualMachine metadata: name: simple-vm namespace: default spec: running: true template: metadata: labels: {kubevirt.io/domain: simple-vm, kubevirt.io/vm: simple-vm} spec: domain: devices: disks: - disk: {bus: virtio} name: dv-disk - disk: {bus: virtio} name: cloudinitdisk resources: requests: {memory: 2048M} volumes: - dataVolume: {name: simple-dv-cephfs} name: dv-disk - cloudInitNoCloud: userData: | #cloud-config password: fedora chpasswd: { expire: False } name: cloudinitdisk