Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2062713

Summary:	Special Resource Operator(SRO) - No sro_used_nodes metric
Product:	OpenShift Container Platform	Reporter:	yevgeny shnaidman <yshnaidm>
Component:	Special Resource Operator	Assignee:	yevgeny shnaidman <yshnaidm>
Status:	CLOSED ERRATA	QA Contact:	Udi Kalifon <ukalifon>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	bthurber, liqcui, ukalifon, yshnaidm
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2059843	Environment:
Last Closed:	2022-08-10 10:53:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2059843

Description yevgeny shnaidman 2022-03-10 12:00:56 UTC

+++ This bug was initially created as a clone of Bug #2059843 +++

Description of problem:

SRO telemetry metric have issue, missing sro_used_nodes metrics in SRO4.10

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


How reproducible:


Steps to Reproduce:
1. Deploy SRO from source code
git clone https://github.com/openshift/special-resource-operator.git
cd special-resource-operator
export CONTAINER_COMMAND=podman
make local-image-build
TAG=master make deploy

2.Login OCP console, check observe=>metrics, search sro_, only three metrics, expect 4 sro_* metrics

--- Additional comment from  on 2022-03-02 07:52:46 UTC ---

Expected Metrics
sro_used_nodes
Returns the nodes that are running pods created by a SRO custom resource (CR). This metric is available for DaemonSet and Deployment objects only.
sro_kind_completed_info
Represents whether a kind of an object defined by the Helm Charts in a SRO CR has been successfully uploaded in the cluster (value 1) or not (value 0). Examples of objects are DaemonSet, Deployment or BuildConfig.
sro_states_completed_info
Represents whether the SRO has finished processing a CR successfully (value 1) or the SRO has not processed the CR yet (value 0).
sro_managed_resources_total
Returns the number of SRO CRs in the cluster, regardless of their state.

Comment 3 errata-xmlrpc 2022-08-10 10:53:13 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 Container Platform 4.11.0 bug fix and security 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:5069