Bug 1756794 - After logging upgraded, new elasticsearch deployment object recreated with new pvc
Summary: After logging upgraded, new elasticsearch deployment object recreated with ne...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.1.z
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.1.z
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1757858
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-30 01:54 UTC by Wang Haoran
Modified: 2020-10-06 22:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1757858 (view as bug list)
Environment:
Last Closed: 2020-01-22 09:46:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
elasticsearch object (2.95 KB, text/plain)
2019-09-30 01:56 UTC, Wang Haoran 		no flags Details
es pod description (4.44 KB, text/plain)
2019-09-30 01:56 UTC, Wang Haoran 		no flags Details
cluster logging operator logs (31.85 KB, text/plain)
2019-09-30 01:57 UTC, Wang Haoran 		no flags Details
elastic operator logs (3.72 MB, text/plain)
2019-09-30 01:58 UTC, Wang Haoran 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 187 0 None closed Bug 1751320: Recreate nodes that have been deleted during upgrade 2021-01-14 09:57:31 UTC
Red Hat Product Errata RHBA-2020:0115 0 None None None 2020-01-22 09:46:32 UTC

Description Wang Haoran 2019-09-30 01:54:05 UTC 
Description of problem:
After the operatorsource updated, it trigger an automic logging upgrade,it looks like the elasticsearch operator was upgraded, the Elastic Deployment objects were recreated using new pvc, but the pvcs are not created because of the limited quota we have for the pvs, which keeps the pods stuck in pending status.

Version-Release number of selected component (if applicable):
registry.redhat.io/openshift4/ose-cluster-logging-operator:v4.1.4-201906271212
registry.redhat.io/openshift4/ose-elasticsearch-operator:v4.1.4-201906271212
How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Wang Haoran 2019-09-30 01:56:00 UTC 
Created attachment 1620914 [details]
elasticsearch object
Comment 2 Wang Haoran 2019-09-30 01:56:40 UTC 
Created attachment 1620915 [details]
es pod description
Comment 3 Wang Haoran 2019-09-30 01:57:23 UTC 
Created attachment 1620916 [details]
cluster logging operator logs
Comment 4 Wang Haoran 2019-09-30 01:58:00 UTC 
Created attachment 1620917 [details]
elastic operator logs
Comment 9 Jeff Cantrill 2020-01-02 15:56:48 UTC 
Moving to ON_QA per #c6 and https://bugzilla.redhat.com/show_bug.cgi?id=1751320 is closed errata
Comment 10 Anping Li 2020-01-07 01:27:35 UTC 
Verified in elasticsearch-operartor 4.1.19
Comment 12 errata-xmlrpc 2020-01-22 09:46:27 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, 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-2020:0115
Note You need to log in before you can comment on or make changes to this bug.