Bug 2177325

Summary:	Noobaa-db pod is taking longer time to start up in ODF 4.13
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Tiffany Nguyen <tunguyen>
Component:	Multi-Cloud Object Gateway	Assignee:	Utkarsh Srivastava <usrivast>
Status:	CLOSED ERRATA	QA Contact:	krishnaram Karthick <kramdoss>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	ebenahar, nbecker, ocs-bugs, odf-bz-bot, usrivast
Target Milestone:	---
Target Release:	ODF 4.13.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-21 15:24:28 UTC	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 Tiffany Nguyen 2023-03-10 21:56:45 UTC

Description of problem (please be detailed as possible and provide log
snippests):
In ODF 4.13, while testing the epic RHSTOR-3355 (Fast recovery for NooBaa core and DB pods in case of node failure), noobaa-db pod doesn't meet the requirement.
It's startup time is taking 2.3% longer comparing to ODF 4.12.

Tested data is collected here: https://docs.google.com/spreadsheets/d/1Q7n-4aYNSqkyvwFaZlrmhwAynbH5DGo95UwNxNggcA0/edit#gid=1489727774

Version of all relevant components (if applicable):
ODF 4.13


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
This doesn't meet the requirement of RHSTOR-3355 (Fast recovery for NooBaa core and DB pods in case of node failure)


Is there any workaround available to the best of your knowledge?
None


Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
No

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

Steps to Reproduce:
1. Build a cluster with ODF 4.13
2. Re-spin the node which noobaa-db is running on
3. Measure the startup time of noobaa-db pod
4. Compare the startup time of noobaa-db pod on ODF 4.12


Actual results:
Noobaa-db pod startup time is increased 2.3% compare to ODF 4.12

Expected results:
Noobaa-db startup time should improve in ODF 4.13

Additional info:

Comment 7 Tiffany Nguyen 2023-04-11 02:13:36 UTC

Testing is in progress with build 4.13.0-130.  Will provide the results and logs when it is completed.

Comment 11 Tiffany Nguyen 2023-04-17 21:49:36 UTC

Re-test the issue using build 4.13..0-162, both startup time for Noobaa-core and Noobaa-db pods are improved significantly.
Testing data is captured here: https://docs.google.com/spreadsheets/d/1Q7n-4aYNSqkyvwFaZlrmhwAynbH5DGo95UwNxNggcA0/edit#gid=408017961

Closing this issue.

Comment 14 errata-xmlrpc 2023-06-21 15:24:28 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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement 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/RHBA-2023:3742