Bug 2034003 - NooBaa endpoint pod Terminated before new one comes in Running state after editing the configmap
Summary: NooBaa endpoint pod Terminated before new one comes in Running state after ed...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ODF 4.10.0
Assignee: Liran Mauda
QA Contact: Ben Eli
URL:
Whiteboard:
Depends On:
Blocks: 2034005
TreeView+ depends on / blocked
 
Reported: 2021-12-19 12:55 UTC by Liran Mauda
Modified: 2023-08-09 16:49 UTC (History)
7 users (show)

Fixed In Version: 4.10.0-50
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2034005 (view as bug list)
Environment:
Last Closed: 2022-04-13 18:50:46 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github noobaa noobaa-operator pull 815 0 None Merged Moved configmap annotation to change the deployment strategies of the endpoint from recreate to ramped 2021-12-19 13:00:27 UTC
Red Hat Product Errata RHSA-2022:1372 0 None None None 2022-04-13 18:53:23 UTC

Description Liran Mauda 2021-12-19 12:55:31 UTC
Description of problem (please be detailed as possible and provide log
snippests):


Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


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


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


Can this issue reproducible?


Can this issue reproduce from the UI?


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


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 2 Liran Mauda 2021-12-19 13:00:28 UTC
Description of problem (please be detailed as possible and provide log
snippests):

After editing the config map the endpoint is not respecting the deployment strategies and use recreate strategy instead of ramped


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

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?
Yes

Steps to Reproduce:
1. edit the configmap
2. see that the endpoint pod is terminating before a new one is up.

Comment 12 errata-xmlrpc 2022-04-13 18:50:46 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.10.0 enhancement, security & 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-2022:1372

Comment 13 errata-xmlrpc 2022-04-13 18: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: Red Hat OpenShift Data Foundation 4.10.0 enhancement, security & 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-2022:1372


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