Bug 2313515 - After upgrade to 4.17 there are two ocs-metrics-exporter where one is in 2/3 Running, reason: OOMKilled
Summary: After upgrade to 4.17 there are two ocs-metrics-exporter where one is in 2/3 ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.17
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ODF 4.17.0
Assignee: Divyansh Kamboj
QA Contact: Petr Balogh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-19 11:31 UTC by Petr Balogh
Modified: 2025-02-28 04:25 UTC (History)
6 users (show)

Fixed In Version: 4.17.0-117
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-10-30 14:35:43 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ocs-operator pull 2814 0 None open Bug 2313515: [release-4.17] remove resource limits on ocs-metrics-exporter 2024-09-20 12:16:02 UTC
Github red-hat-storage ocs-operator pull 2835 0 None open Bug 2313515: Revert "Merge pull request #2679 from umangachapagain/metrics-secure" 2024-10-04 11:13:10 UTC
Red Hat Issue Tracker OCSBZM-9249 0 None None None 2024-09-19 14:47:40 UTC
Red Hat Issue Tracker OCSBZM-9300 0 None None None 2024-10-03 20:15:56 UTC
Red Hat Product Errata RHSA-2024:8676 0 None None None 2024-10-30 14:35:47 UTC

Description Petr Balogh 2024-09-19 11:31:33 UTC
Description of problem (please be detailed as possible and provide log
snippests):
After upgrade to 4.17.0-97 from 4.16.2
One of container in pod ocs-metrics-exporter doesn't run because of reason: OOMKilled

See private comment with links to exact logs.

Anyway, there should be only 1 such pod I think, not 2

Version of all relevant components (if applicable):
ODF v4.17.0-97

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Upgrade test failed because of unexpected state.

Is there any workaround available to the best of your knowledge?
Don't know


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
Not sure yet

Can this issue reproduce from the UI?
haven't tried

If this is a regression, please provide more details to justify this:
yes

Steps to Reproduce:
1. Install ODF 4.16.2 GAed version
2. Upgrade to ODF 4.17.0-97
3.


Actual results:
2 ocs-metrics-exporter - and one container failed with OOM

Expected results:
1 ocs-metrics-exporter pod - running OK

Additional info:

Comment 17 Sunil Kumar Acharya 2024-10-08 13:17:11 UTC
Please update the RDT flag/text appropriately.

Comment 19 errata-xmlrpc 2024-10-30 14:35:43 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: Red Hat OpenShift Data Foundation 4.17.0 Security, Enhancement, & 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-2024:8676

Comment 20 Red Hat Bugzilla 2025-02-28 04:25:37 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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