Bug 2026733

Summary:	[CNV-4.9] PodDisruptionBudgetAtLimit: The pod distuption budget is preventing further disruption to pods becuase it is at the minimum allowed level
Product:	Container Native Virtualization (CNV)	Reporter:	Mustafa Aydın <maydin>
Component:	Virtualization	Assignee:	Antonio Cardace <acardace>
Status:	ASSIGNED ---	QA Contact:	vsibirsk
Severity:	high	Docs Contact:
Priority:	high
Version:	4.9.0	CC:	acardace, fdeutsch, guchen, jortialc, kbidarka, kmajcher, ryasharz, sgott, spasquie, sradco, stirabos, ycui
Target Milestone:	---	Flags:	bgaydos: needinfo? (acardace)
Target Release:	4.14.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	The Pod Disruption Budget (PDB) prevents pod disruptions for migratable virtual machine images. If the PDB detects pod disruption, then openshift-monitoring sends a PodDisruptionBudgetAtLimit alert every 60 minutes for virtual machine images that use the LiveMigrate eviction strategy. (BZ#2026733) As a workaround, Silencing alerts.https://docs.openshift.com/container-platform/4.10/monitoring/managing-alerts.html#silencing-alerts_managing-alerts	Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

Description Mustafa Aydın 2021-11-25 16:48:14 UTC

Description of problem:

Getting "The pod distuption budget is preventing further disruption to pods becuase it is at the minimum allowed level" Warning alarm although the PDBs at the namespaces are as per design (min available=1, Allowed Disruptions=0)

Version-Release number of selected component (if applicable):
4.9.6

How reproducible:
Always


Actual results:
Warning alarm

Expected results:
No alarm

Additional info:
Silenced the alarms as the current PDBs are expected and there should be some exception alert rule for this.

Comment 1 Krzysztof Majcher 2021-11-26 14:10:55 UTC

Shirly please take a look.

Comment 2 Fabian Deutsch 2021-11-26 18:04:54 UTC

This is triggered by PDBs related to VMs, therefore moving to virt.

Comment 9 Bob Gaydos 2022-02-09 21:33:20 UTC

@acardace @sgott -

I have created this Known Issue release note for 4.10:

* `openshift-monitoring` sends an alert when an application that is protected by a Pod Disruption Budget (PDB) does not allow disruptions for migratable virtual machine images. To workaround this issue, silence the alert by setting OCP Monitoring Results.  (link:https://bugzilla.redhat.com/show_bug.cgi?id=2026733[*BZ#2026733*])

However, I am a little unclear on the last point re: OCP monitoring Results. Where can the user see these results? is there a particular field to be set?

Thanks,
Bob

Comment 11 sgott 2022-06-13 13:52:26 UTC

Deferring this to 4.12 as the fix requires some time to converge. Multiple teams are involved.

Comment 12 sgott 2022-09-07 12:38:16 UTC

Deferring this to the next release as we still haven't converged on a solution.