Bug 1462069 - Provide feedback on progression for "Receiving source from STDIN as archive..."
Provide feedback on progression for "Receiving source from STDIN as archive..."
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
Unspecified Unspecified
high Severity medium
: ---
: ---
Assigned To: Ben Parees
Xiaoli Tian
Depends On:
  Show dependency treegraph
Reported: 2017-06-16 01:33 EDT by Kenjiro Nakayama
Modified: 2018-03-12 09:54 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-03-12 09:54:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kenjiro Nakayama 2017-06-16 01:33:42 EDT
Description of problem:
- Same request with https://github.com/openshift/origin/issues/13612, we would like to open bz ticket as enterprise customer filed an issue with stacking the pod with "Receiving source from STDIN as archive ..." message.

Version-Release number of selected component (if applicable):
- 3.x

How reproducible:
- it is not 100% reproduciable problem.

Steps to Reproduce:
1. start binary build with huge war file.

Actual results:
- Build pod is stuck with ""Receiving source from STDIN as archive ..."".

Expected results:
- Need progress or more verbose log output.
Comment 3 Eric Rich 2018-03-12 09:54:36 EDT
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.

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