Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1843738

Summary:	The ZeroRedundancy is not honored during upgrade clo-first
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.5	CC:	aos-bugs, ewolinet, lvlcek
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:43:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1838153
Bug Blocks:

Comment 3 Anping Li 2020-06-16 10:28:43 UTC

Before EO upgrade, the replicas shard are allocated. after EO upgraded, the template is reset. No replicas shard.  as the UNASSIGNED Shard can be cured after the upgrade, move to verified.

1) Before EO upgrade.
.operations.2020.06.16                                           0 p STARTED    22395  38.4mb 10.128.2.229 elasticsearch-cdm-po0e0564-1
.kibana                                                          0 p STARTED        1   3.2kb 10.128.2.229 elasticsearch-cdm-po0e0564-1
infra-write                                                      4 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
infra-write                                                      4 r UNASSIGNED                            
infra-write                                                      3 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
infra-write                                                      3 r UNASSIGNED                            
infra-write                                                      1 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
infra-write                                                      1 r UNASSIGNED                            
infra-write                                                      2 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
infra-write                                                      2 r UNASSIGNED                            
infra-write                                                      0 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
infra-write                                                      0 r UNASSIGNED                            
test1                                                            4 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
test1                                                            4 r UNASSIGNED                            
test1                                                            3 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
test1                                                            3 r UNASSIGNED                            
test1                                                            1 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
test1                                                            1 r UNASSIGNED                            
test1                                                            2 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
test1                                                            2 r UNASSIGNED                            
test1                                                            0 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
test1                                                            0 r UNASSIGNED                            
app-write                                                        4 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
app-write                                                        4 r UNASSIGNED                            
app-write                                                        3 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
app-write                                                        3 r UNASSIGNED                            
app-write                                                        1 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
app-write                                                        1 r UNASSIGNED                            
app-write                                                        2 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
app-write                                                        2 r UNASSIGNED                            
app-write                                                        0 p STARTED        0    162b 10.128.2.229 elasticsearch-cdm-po0e0564-1
app-write                                                        0 r UNASSIGNED                            


2) After EO Upgraded.

+ oc exec -c elasticsearch elasticsearch-cdm-po0e0564-1-85fb479d6f-wq7tm -- es_util --query=_cat/shards
app-write                                                        2 p STARTED    14  32.1kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
app-write                                                        1 p STARTED    16   102kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
app-write                                                        3 p STARTED    13  54.4kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
app-write                                                        4 p STARTED    25  86.2kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
app-write                                                        0 p STARTED    20  81.6kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
project.logjson1.3b1f132f-9d99-45fb-8b78-5a0870a3d2ca.2020.06.16 0 p STARTED  1080 658.3kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
.kibana                                                          0 p STARTED     1   3.2kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
.searchguard                                                     0 p STARTED     5  85.8kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
.kibana.647a750f1787408bf50088234ec0edd5a6a9b2ac                 0 p STARTED     2  27.3kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
infra-write                                                      2 p STARTED  3696   3.9mb 10.128.2.232 elasticsearch-cdm-po0e0564-1
infra-write                                                      1 p STARTED  3644   3.9mb 10.128.2.232 elasticsearch-cdm-po0e0564-1
infra-write                                                      3 p STARTED  3745   3.6mb 10.128.2.232 elasticsearch-cdm-po0e0564-1
infra-write                                                      4 p STARTED  3509   3.6mb 10.128.2.232 elasticsearch-cdm-po0e0564-1
infra-write                                                      0 p STARTED  3651   3.8mb 10.128.2.232 elasticsearch-cdm-po0e0564-1
test1                                                            2 p STARTED     0    259b 10.128.2.232 elasticsearch-cdm-po0e0564-1
test1                                                            1 p STARTED     0    259b 10.128.2.232 elasticsearch-cdm-po0e0564-1
test1                                                            3 p STARTED     0    259b 10.128.2.232 elasticsearch-cdm-po0e0564-1
test1                                                            4 p STARTED     0    259b 10.128.2.232 elasticsearch-cdm-po0e0564-1
test1                                                            0 p STARTED     0    259b 10.128.2.232 elasticsearch-cdm-po0e0564-1
.operations.2020.06.16                                           0 p STARTED 22395  22.4mb 10.128.2.232 elasticsearch-cdm-po0e0564-1
.security                                                        0 p STARTED     5  29.6kb 10.128.2.232 elasticsearch-cdm-po0e0564-1
+ es_run '_cluster/settings?pretty'

Comment 4 errata-xmlrpc 2020-07-13 17:43:10 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:2409