Bug 2213255

Summary: HPP wrongly reporting Available status
Product: Container Native Virtualization (CNV) Reporter: Ohad <orevah>
Component: StorageAssignee: Arnon Gilboa <agilboa>
Status: MODIFIED --- QA Contact: Natalie Gavrielov <ngavrilo>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.13.0CC: agilboa, alitke, kmajcher, stirabos, yadu
Target Milestone: ---   
Target Release: 4.14.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
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 Ohad 2023-06-07 16:11:25 UTC
Description of problem:
I'm trying to produce HppNotReady alert, when editing the node selector for getting the hpp broken , we can see it is not ready but the metric doesn't catch it and report it as available and the alert not fired

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

How reproducible:
100%

Steps to Reproduce:
1.oc get hostpathprovisioner hostpath-provisioner -o yaml
see under .Spec.Workload.NodeSelector the value
2.oc patch hostpathprovisioner hostpath-provisioner --type='json' -p='[{"op": "replace", "path": "/spec/workload/nodeSelector", "value": {"wrong": "wrong"}}]'
and check again that the value changed with the command from step 1
3.check that the hpp is not ready:
oc get daemonset -n openshift-cnv | grep -e hostpath -e hpp
4.wait for the alert

Actual results:
The alert is not firing and the metric show hpp available

Expected results:
HppNotReady should fire

Comment 1 Krzysztof Majcher 2023-06-13 12:45:30 UTC
Assigning to Storage team, as this is storage related alert. Please feel free to reach out for help if needed.