Bug 1446499
Summary: | Logging upgrade failed, can't recover logging after upgrade to OCP 3.4 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Miheer Salunke <misalunk> |
Component: | Logging | Assignee: | Peter Portante <pportant> |
Status: | CLOSED DUPLICATE | QA Contact: | Xia Zhao <xiazhao> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0 | CC: | aos-bugs, jcantril, misalunk, pportant, rmeggins |
Target Milestone: | --- | ||
Target Release: | --- | ||
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: | 2017-05-11 17:33:53 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: |
Comment 1
Miheer Salunke
2017-04-28 08:53:52 UTC
This appears to be an upgrade from 3.3 to 3.4.1, correct? Can you attach all of the deployer logs to this BZ for inspection? Workaround is: oc edit configmap logging-elasticsearch Make min master setting be the same as: https://github.com/openshift/origin-aggregated-logging/commit/56793ee729196f4b3c43769141f2b78df47d1a39#diff-bb1ad2cd0b762aef9387d3b94258a8a9R32 I stand corrected. This issue is available with the release of 3.4.1-19 which needs to be pushed out. *** This bug has been marked as a duplicate of bug 1439356 *** |