Bug 2213255 - HPP wrongly reporting Available status
Summary: HPP wrongly reporting Available status
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 4.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.14.0
Assignee: Arnon Gilboa
QA Contact: Harel Meir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-07 16:11 UTC by Ohad
Modified: 2023-11-08 14:06 UTC (History)
6 users (show)

Fixed In Version: v4.14.0.rhel9-1722
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 14:05:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt hostpath-provisioner-operator pull 357 0 None Merged Update HPP CR conditions correctly when degraded 2023-08-16 13:31:31 UTC
Github kubevirt hostpath-provisioner-operator pull 363 0 None Merged [release-v0.16] Update HPP CR conditions correctly when degraded 2023-08-24 07:04:59 UTC
Github kubevirt hostpath-provisioner pull 241 0 None Merged Fix HPPNotReady test to Update the CR 2023-08-17 10:48:04 UTC
Red Hat Issue Tracker CNV-29498 0 None None None 2023-06-07 16:14:07 UTC
Red Hat Product Errata RHSA-2023:6817 0 None None None 2023-11-08 14:06:05 UTC

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.

Comment 4 Harel Meir 2023-08-28 11:18:18 UTC
Verified on 4.14.0

After broke the HPP using the steps above,
HppNotReady alert did fire & reported as Unavailable as expected

Comment 6 errata-xmlrpc 2023-11-08 14:05:49 UTC
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 (Important: OpenShift Virtualization 4.14.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-2023:6817


Note You need to log in before you can comment on or make changes to this bug.