Bug 1550140 - [free-int] error during logging upgrade "Getting ES version for logging-es cluster" rc=35
Summary: [free-int] error during logging upgrade "Getting ES version for logging-es cl...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.9.0
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-28 15:49 UTC by Justin Pierce
Modified: 2018-03-28 14:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: When trying to determine the version of ES running, we would just make sure the pod is running and not verify that both containers were ready. Consequence: The ES pod may not be ready and we try to query it. Fix: Verify that both containers are ready before we attempt to pull the ES version. Result: We do not receive a rc 35 from curling the ES end point.
Clone Of:
Environment:
Last Closed: 2018-03-28 14:30:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Ansible output (3.29 KB, text/plain)
2018-02-28 15:49 UTC, Justin Pierce
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:30:51 UTC

Description Justin Pierce 2018-02-28 15:49:13 UTC
Created attachment 1401928 [details]
Ansible output

Description of problem:
openshift-ansible playbooks exited during logging upgrade (see attachment for log output)

Version-Release number of the following components:
v3.9.1

How reproducible:
Re-running the playbooks did not help

Comment 2 Jeff Cantrill 2018-02-28 16:54:27 UTC
Storage attach issue that was resolved by scaling down and scaling up: http://pastebin.test.redhat.com/560103

Comment 7 Anping Li 2018-03-06 07:27:52 UTC
The logging deploy/redeploy works well with openshift3/ose-ansible/images/v3.9.2-1". so move bug to verified

Comment 10 errata-xmlrpc 2018-03-28 14:30:19 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-2018:0489


Note You need to log in before you can comment on or make changes to this bug.