Error while building image - Uploading directory "oc-build" as binary input

[deepjyotsingh]

Has anyone seen the below error while building the tasks app?

Error running start-build on at least one item: [buildconfig/tasks];

{reference={}, err=Uploading directory "oc-build" as binary input for the build ...

Error from server (BadRequest): unable to wait for build tasks-2 to run: timed out waiting for the condition, verb=start-build, cmd=oc start-build buildconfig/tasks --from-dir=oc-build --wait=true -o=name --server=https://172.30.0.1:443 --namespace=dev-admin --token=XXXXX , out=, status=1}

[obryg]

Hi everyone,

I got similar issue:

Error running start-build on at least one item: [buildconfig/tasks];

{reference={}, err=Uploading directory "oc-build" as binary input for the build ...
error: The build dev/tasks-4 status is "Failed", verb=start-build, cmd=oc start-build buildconfig/tasks --from-dir=oc-build --wait=true -o=name --server=https://172.30.0.1:443 --namespace=dev --token=XXXXX , out=build/tasks-4, status=1}

I would be appreciated if somebody can explain this issue. Thank you.

[deepjyotsingh]

Thanks for sharing your error Alex. Dear Authors and Contributors, I’d appreciate if you can respond to us and help resolve this error ASAP. Sent from my iPhone. Please excuse the brevity and typos.

…

On Mar 11, 2018, at 4:25 PM, Alex Briginevich ***@***.***> wrote: Hi everyone, I got similar issue: Error running start-build on at least one item: [buildconfig/tasks]; {reference={}, err=Uploading directory "oc-build" as binary input for the build ... error: The build dev/tasks-4 status is "Failed", verb=start-build, cmd=oc start-build buildconfig/tasks --from-dir=oc-build --wait=true -o=name --server=https://172.30.0.1:443 --namespace=dev --token=XXXXX , out=build/tasks-4, status=1} I would be appreciated if somebody can explain this issue. Thank you. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[deepjyotsingh]

Sent from my iPhone. Please excuse the brevity and typos.

…

On Mar 11, 2018, at 4:55 PM, Deepjyot Singh ***@***.***> wrote: Thanks for sharing your error Alex. Dear Authors and Contributors, I’d appreciate if you can respond to us and help resolve this error ASAP. Sent from my iPhone. Please excuse the brevity and typos. > On Mar 11, 2018, at 4:25 PM, Alex Briginevich ***@***.***> wrote: > > Hi everyone, > > I got similar issue: > > Error running start-build on at least one item: [buildconfig/tasks]; > > {reference={}, err=Uploading directory "oc-build" as binary input for the build ... > error: The build dev/tasks-4 status is "Failed", verb=start-build, cmd=oc start-build buildconfig/tasks --from-dir=oc-build --wait=true -o=name --server=https://172.30.0.1:443 --namespace=dev --token=XXXXX , out=build/tasks-4, status=1} > > > I would be appreciated if somebody can explain this issue. Thank you. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. >

[deepjyotsingh]

@siamaksade @thoraxe @ryanj @mhausenblas @jorgemoralespou

Can either of you provide your valuable inputs on this error?

[mhausenblas]

Sorry, never used that one here …

[siamaksade]

@deepjyotsingh could you provide some more info?

• Where do you deploy the demo?
• How do you deploy the demo (script or template)?
• How much memory you have available in your OpenShift cluster?
• Is SoanrQube deployed?

[deepjyotsingh]

Please see my response inline. - Where do you deploy the demo? - *Running it on a CentOS VM in Google Cloud* - How do you deploy the demo (script or template)? - *Provision script* - How much memory you have available in your OpenShift cluster? - *12 GB* - Is SoanrQube deployed? - *Yes the pod is deployed but it doesn't start up so I'm running the build with with_sonar flag set as false.*

…

On Mon, Mar 12, 2018 at 5:09 AM, Siamak Sadeghianfar < ***@***.***> wrote: @deepjyotsingh <https://github.com/deepjyotsingh> could you provide some more info? - Where do you deploy the demo? - How do you deploy the demo (script or template)? - How much memory you have available in your OpenShift cluster? - Is SoanrQube deployed? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#79 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AjZbA9lx7wKS7pYJhDQHG3tAR4lVyJtjks5tdmWVgaJpZM4SifKg> .

[deepjyotsingh]

Do we need a docker registry to run this build? I don't see registry as a prerequisite but just wondering if that's causing the image build process to fail.

[deepjyotsingh]

Any inputs or feedback on how to get past this error?

[obryg]

Hi @mhausenblas,

I can try to answer on your questions:

Where do you deploy the demo?

Deployed Openshift-Origin on Azure public cloud.

How do you deploy the demo (script or template)?

Link to repository: https://github.com/Microsoft/openshift-origin
Parameter file:
azuredeploy.parameters.json.txt

How much memory you have available in your OpenShift cluster?

3 masters - 2 CPU - 8GB
2 Infra Nodes - 2 CPU - 8GB
2 User Nodes - 2 CPU - 8GB

Is SoanrQube deployed?

False.

[deepjyotsingh]

Any update on this error? @siamaksade - can you please review and advice?

[svsik]

Also experiencing this issue. Any update on this, please?

[niiku]

I ran into the same issue. I'm pretty sure it's because the image jboss-eap70-openshift:1.5 referenced in the Jenkinsfile is not available (maybe because there's no eap subscription). Either you make sure the image jboss-eap70-openshift:1.5 is available as image stream or you replace it with the corresponding wildfly image from docker hub.
To replace it you need to tag the image stream with a version:
oc tag openshift/wildfly-101-centos7 openshift/wildfly-101-centos7:v10.1
then you can replace the line
openshift.newBuild("--name=tasks", "--image-stream=jboss-eap70-openshift:1.5", "--binary=true")
in your Jenkinsfile with
openshift.newBuild("--name=tasks", "--image-stream=openshift/wildfly-101-centos7:v10.1", "--binary=true")

You can edit the Jenkinsfile in your web console under Builds > Pipelines > Select task-pipeline > Actions > Edit YAML

Alternatively you can checkout my fork which I created to get this CI/CD demo working on OpenShift Origin 3.9 without issues (https://github.com/niiku/openshift-origin-cicd-demo)