-
Notifications
You must be signed in to change notification settings - Fork 929
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stage-Build Image failure #112
Comments
Almost the same issue but when is making the deployment to stage: ERROR: rollout:latest returned an error; It says that the task is not found. |
i am facing problem in Dev environment itself, Is it working for you Dev environment(deployment script) ? if yes, Could you please share your Dev deployment script. |
Hello Babujii, I'm using the same script from the project. I'm not replacing project values because I found several errors during the process. The problem I was having is when i was deploying to stage and the script do not create the deployment config for that project, so I got " task not found".. |
Thanks for update Rperezsnap ! |
We have followed with installation script instructions and working fines . It's solved issue. Thanks for your support. |
Hello Babujii, |
Hi Rperezsnap, Yes, It is working fine now(Dev,Stage). step2:git clone https://github.com/siamaksade/openshift-cd-demo.git (locally) Step3:go to script path and run the script. ./provision.sh deploy Step4: Deployment Stage(just click promote button) Done ... Enjoy !! |
you have to login : #oc login http://:8443 |
I get the same:
What did you do to fix this? |
Seems that the buildconfig named "tasks" on the project dev, do not exists.
Maybe you need to recreate the builconfig with oc new-build
Those steps are inside the job in the yaml file. Maybe when you run the yaml it was not created.
You can check if the build config exists using the following command:
oc get bc -n dev
The script to create the build config is the following:
oc new-build --name=tasks --image-stream=wildfly:latest --binary=true -n dev
…________________________________
From: Johnny Johnson <notifications@github.com>
Sent: Tuesday, November 27, 2018 9:30:27 AM
To: siamaksade/openshift-cd-demo
Cc: Ronny Perez Picado; Comment
Subject: Re: [siamaksade/openshift-cd-demo] stage-Build Image failure (#112)
i get the same:
Error running start-build on at least one item: [buildconfig/tasks];
{reference={}, err=Uploading file "target/ROOT.war" as binary input for the build ...
Error from server (NotFound): buildconfigs.build.openshift.io "tasks" not found, verb=start-build, cmd=oc --server=https://172.30.0.1:443 --certificate-authority=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt --namespace=dev --token=XXXXX start-build buildconfig/tasks --from-file=target/ROOT.war --wait=true -o=name , out=, status=1}
What did you do to fix this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#112 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Aqg3wkKylHuP6_zvKoQwM3yYJXkksVEQks5uzVqTgaJpZM4YBnLu>.
|
I tried that
|
So is this in a windows env or linux? |
Well now I got past build but failed on deploy to dev:
|
I still have same error [cicd-admin-tasks-pipeline] Running shell script
[Pipeline] _OcContextInit Finished: FAILURE |
docker pull openshift/wildfly-120-centos7@sha256:a1fbd1b235102ae18344527b44201c34ad4c2181b0b4cbf295b1a8f0cbde8e73 |
no wildfly-120-centos7 image |
While executing this step in the pipeline,
ERROR: Error running start-build on at least one item: [buildconfig/tasks];
{reference={}, err=Uploading file "target/ROOT.war" as binary input for the build ...
Error from server (NotFound): buildconfigs.build.openshift.io "tasks" not found, verb=start-build, cmd=oc --server=https://172.30.0.1:443 --certificate-authority=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt --namespace=dev --token=XXXXX start-build buildconfig/tasks --from-file=target/ROOT.war --wait=true -o=name , out=, status=1}
Finished: FAILURE
The text was updated successfully, but these errors were encountered: