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

Bug 1876236

Summary: The label [tuned.openshift.io/elasticsearch: "true"] is still present in the ElasticSearch Deployment
Product: OpenShift Container Platform Reporter: Anshul Verma <ansverma>
Component: LoggingAssignee: Periklis Tsirakidis <periklis>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, periklis
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 15:10:28 UTC Type: Bug
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:    
Bug Blocks: 1878035    

Description Anshul Verma 2020-09-06 15:42:55 UTC 
Description of problem:

From OpenShift 4.4 onwards there is no `openshift-node-es` tuned profile to have vm.max_map_count's value to 262144. The current tuned configuration has 262144 as it's the default value for all the nodes, so there is no need to create a profile explicitly and hence it is not there.

But still, the ES deployment has the label tuned.openshift.io/elasticsearch: "true" which was used to map the tuned profile. Now since the tuned profile is not there there is no use of it.

This Bugzilla is for removing the label.
Comment 4 Anping Li 2020-09-11 03:04:15 UTC 
Verified on elasticsearch-operator.4.6.0-202009100728.p0
Comment 5 Anshul Verma 2020-10-20 13:27:18 UTC 
Team,

Any Update on this?
Comment 7 errata-xmlrpc 2020-10-27 15:10:28 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.6.1 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:4198