Bug 1881957 - ElasticSearch operator upgrade created new PVCs
Summary: ElasticSearch operator upgrade created new PVCs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.5.z
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard: logging-exploration osd-45-logging
: 1884444 (view as bug list)
Depends On: 1868300
Blocks: 1723620 1883355
TreeView+ depends on / blocked
 
Reported: 2020-09-23 13:40 UTC by ewolinet
Modified: 2024-03-25 16:34 UTC (History)
27 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1868300
: 1883355 (view as bug list)
Environment:
Last Closed: 2020-10-12 15:43:46 UTC
Target Upstream Version:
Embargoed:
jcantril: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 495 0 None closed [release-4.5] Bug 1881957: updating EO to adopt an existing cluster if cr nodes uuid is nil 2021-02-18 08:49:55 UTC
Red Hat Product Errata RHBA-2020:3845 0 None None None 2020-10-12 15:43:58 UTC

Comment 7 Jeff Cantrill 2020-10-02 13:10:41 UTC 
*** Bug 1884444 has been marked as a duplicate of this bug. ***
Comment 8 Masaki Furuta ( RH ) 2020-10-09 06:15:00 UTC 
Hello Jeff Cantrill, 

Thank you for your help on this BZ and previous one.
This is great help.

We had regular TAM conference call with NEC yesterday, and I have received following feedback from NEC,,

As per CLOSED DUPLICATE on Bug 1884444 owing to the Bug 1881957, NEC requested me to clarify following questions.

Would you please find the comment below on previous BZ and answer to it, to clarify their concern ?

  - https://bugzilla.redhat.com/show_bug.cgi?id=1884444#c2
    ~~~
    Dear Jeff,
    
    Thank you for your reply.
    
    But, really is it the same as Bug 1881957?
    Bug 188195 mentions that the problem happened during upgrade while our customer hadn't tried to upgrade.
    We think Bug 1882450 is more similar to the issue we reported.
    
    In either cases, we would like to know the workaround of this issue since this is a big problem for out customr.
    The issue happened again in our customer env a few days ago...
    
    Best Regards,
    Masaki Hatada
    ~~~

I am grateful for your help and clarification.

Thank you so much,

BR,
Masaki
Comment 9 Anping Li 2020-10-09 13:04:22 UTC 
Verified:
1.  labels:    logging-cluster: elasticsearch were added to pvc
2.  the the pvc have label above. the Elasticsearch will reuse the uuid in the PVC.
Comment 10 Anping Li 2020-10-09 13:18:04 UTC 
Verified on CSV below:
clusterserviceversion.operators.coreos.com/clusterlogging.4.5.0-202009240830.p0
clusterserviceversion.operators.coreos.com/elasticsearch-operator.4.5.0-202009260615.p0
Comment 14 errata-xmlrpc 2020-10-12 15:43: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 (OpenShift Container Platform 4.5.14 extras 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-2020:3845
Comment 15 Anping Li 2020-10-13 15:35:41 UTC 
Reproduce this time after upgrade from 4.3.37 -> 4.4.26 -> 4.5.13. The New PVC appears after upgraded from 4.4.26 to 4.5.13.
Comment 16 Armin Kunaschik 2020-10-13 16:01:02 UTC 
Update from 4.5.13 to 4.5.14 (including the automatic update of logging and elastic operators to the mentioned version) is still creating new pvcs.
Note You need to log in before you can comment on or make changes to this bug.