Bug 1916475 - Elasticsearch rollover pods failed with resource_already_exists_exception
Summary: Elasticsearch rollover pods failed with resource_already_exists_exception
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
: 4.6.z
Assignee: ewolinet
QA Contact: Qiaoling Tang
URL:
Whiteboard: logging-exploration
Depends On: 1893992
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-14 20:55 UTC by OpenShift BugZilla Robot
Modified: 2021-02-08 13:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-08 13:41:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 624 0 None closed [release-4.6] Bug 1916475: Improve elasticsearch indexmanagement rollover script 2021-02-10 02:12:49 UTC
Red Hat Product Errata RHSA-2021:0310 0 None None None 2021-02-08 13:41:52 UTC

Comment 2 Qiaoling Tang 2021-01-29 07:20:49 UTC 
Tested with elasticsearch-operator.4.6.0-202101280459.p0, unable to reproduce this issue.
Comment 5 errata-xmlrpc 2021-02-08 13:41:45 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 (Moderate: OpenShift Container Platform 4.6.16 extras 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-2021:0310
Note You need to log in before you can comment on or make changes to this bug.