Bug 1750868 - All downstream 4.2 elasticsearch5 builds on brew since Sept. 5 are stuck in "building" state
Summary: All downstream 4.2 elasticsearch5 builds on brew since Sept. 5 are stuck in "...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.2.0
Assignee: Lukas Vlcek
QA Contact: Mike Fiedler
URL:
Whiteboard:
Depends On:
Blocks: 1751859
TreeView+ depends on / blocked
 
Reported: 2019-09-10 16:33 UTC by Mike Fiedler
Modified: 2019-10-16 06:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:40:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:04 UTC

Description Mike Fiedler 2019-09-10 16:33:42 UTC 
Description of problem:

All downstream 4.2 logging elasticsearch5 builds on brew are stuck in "building" state and are not completing and not producing images.   This is blocking testing of downstream logging fixes.

Last completed build:  logging-elasticsearch5-container-v4.2.0-201909050219 
First build stuck in "building": logging-elasticsearch5-container-v4.2.0-201909051819


Version-Release number of selected component (if applicable): logging-elasticsearch5-container-v4.2.0-201909051819

Those dates also match latest 4.2 images pulled from registry.svc.ci.openshift.org
Comment 14 Anping Li 2019-09-16 05:11:28 UTC 
verified as there is logging v4.2.0-201909151553
Comment 15 errata-xmlrpc 2019-10-16 06:40:52 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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.