Bug 1813381

Summary: Elasticsearch pods are not coming up after adding the LogForwarding instance.
Product: OpenShift Container Platform Reporter: Saurabh Sadhale <ssadhale>
Component: LoggingAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: high    
Version: 4.3.0CC: agabriel, aos-bugs, dahernan, ewolinet, ingvarr.zhmakin, jcantril, kkii, moddi, mszczewski, openshift-bugs-escalate, qitang, rh-container, rkshirsa, rsunog
Target Milestone: ---   
Target Release: 4.3.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-11 21:20:39 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: 1782740    
Bug Blocks:    

Comment 7 Periklis Tsirakidis 2020-04-14 11:51:59 UTC 
*** Bug 1812563 has been marked as a duplicate of this bug. ***
Comment 10 Jeff Cantrill 2020-04-15 15:18:59 UTC 
*** Bug 1823827 has been marked as a duplicate of this bug. ***
Comment 12 ewolinet 2020-04-22 20:26:53 UTC 
@Angelo,

This issue is already resolved in 4.4 [1]


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1782740
Comment 15 Anping Li 2020-04-24 09:12:26 UTC 
Verified and pass
1) The ESs cluster are ready after enabled LogForward API
2) The ES cluster are ready after refresh the certificate.
Comment 17 errata-xmlrpc 2020-05-11 21:20:39 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:2006