Bug 1509227 - [DOCKER] JBoss image build on OCP randomly fails due to a "no such file or directory".
Summary: [DOCKER] JBoss image build on OCP randomly fails due to a "no such file or di...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.9.z
Assignee: Tom Sweeney
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-03 11:19 UTC by Jaspreet Kaur
Modified: 2021-03-11 16:11 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-31 18:41:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1468681 0 unspecified CLOSED [DOCKER] stat /usr/bin/openshift-deploy: no such file or directory 2021-06-10 12:33:36 UTC

Internal Links: 1468681

Description Jaspreet Kaur 2017-11-03 11:19:29 UTC 
Description of problem: JBoss image build on OCP randomly fails due to a "no such file or directory".

Registry server Address: 
Registry server User Name: serviceaccount
Registry server Email: serviceaccount
Registry server Password: <<non-empty>>
F1103 09:40:25.095148       1 helpers.go:115] error: build error: Failed to push image: open /var/lib/docker/devicemapper/mnt/efb766d0ac732221cbc0fcdee423cdb75990bcb52d7ea7ab548dfba72f6b657c/rootfs/deployments/example.war: no such file or directory


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: It fails most of the time.


Expected results: It should succeed without any issue.


Additional info:
Comment 10 Tom Sweeney 2017-12-07 14:48:48 UTC 
Vivek, suggested next step(s)?
Comment 11 Vivek Goyal 2017-12-07 14:54:02 UTC 
Create a small cluster in lab and try to reproduce it. We need a reproducer now. And try to narrow it down the problem.


Also upgrade to latest docker and see if problem automatically goes away.
Note You need to log in before you can comment on or make changes to this bug.