[Error] Could not find the image either in docker hub or locally: docker.io/kabanero/nodejs-express:0.2 #160
Comments
|
Could you please double check you have the correct credentials specified in your dockerhub secret? Have seen this fail if that was not right. |
|
I am using local openshift registry to push image to i.e image-registry.openshift-image-registry.svc:5000, do i also need to specify credentials in a secret for the local openshift registry before during webhook creation? |
|
Docker is not available in the containers/openshift. So the pipelines use
a tool called buildah instead. Also you should not need to specify
dockerhub credentials if you are pushing to the internal registry. Could
you please walk me through the steps you followed to setup the webhook?
…On Thu, Feb 13, 2020 at 3:40 AM karimbzu ***@***.***> wrote:
i think the command which is causing the error is: "buildah pull
docker.io/kabanero/java-microprofile:0.2", it should be docker pull
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#160?email_source=notifications&email_token=ADBUMTOFKSC4E3UYV6GV57TRCUBPRA5CNFSM4KSCOV3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELT4COY#issuecomment-585613627>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADBUMTITCPPM5KBRBS7R2W3RCUBPRANCNFSM4KSCOV3A>
.
|
|
Thanks for your reply. Please see below the webhook settings: |
|
Could you please change the `service account` to `kabanero-pipelines`?
…On Thu, Feb 13, 2020 at 9:42 AM karimbzu ***@***.***> wrote:
Thanks for your reply. Please see below the webhook settings:
[image: image]
<https://user-images.githubusercontent.com/34478122/74445860-0435c780-4eb2-11ea-8266-6905e6c4311b.png>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#160?email_source=notifications&email_token=ADBUMTPLARDEKR5ZV4R34QLRCVL4DA5CNFSM4KSCOV3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELVG3KQ#issuecomment-585788842>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADBUMTNKQTQ6AUA5ZD33PZ3RCVL4DANCNFSM4KSCOV3A>
.
|
|
I dont know what happened with my configuration, suddenly i am unable to create webhook, last time i did: |
|
able to create webhook using "kabanero-pipeline" service account, however, it does not trigger event from github. Similarly, if i create webhook using "kabanero-operator" service account, then trigger initiated a new pipelinerun, however the same build issue appears. |
|
Either `pipeline` or `kabanero-pipeline` service accounts are recommended
to use with pipelines. We have not tested with `kabanero-operator` and are
not sure if it works with pipelines. That one is intended to be used by
the Kabanero operator.
If you are not seeing events in github getting triggered then it might be a
different issue. Did you delete the other webhook before creating the one
with the `kabanero-pipeline` service account? Could you also please check
the status of the webhook in your github repo and see if it's sending
events?
…On Thu, Feb 13, 2020 at 11:06 AM karimbzu ***@***.***> wrote:
able to create webhook using "kabanero-pipeline" service account, however,
it does not trigger event from github. Similarly, if i create webhook using
"kabanero-operator" service account, then trigger initiated a new
pipelinerun, however the same build issue appears.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#160?email_source=notifications&email_token=ADBUMTIQIWFJHL5S2NFERTTRCVVZBA5CNFSM4KSCOV3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELVSDFY#issuecomment-585834903>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADBUMTLPEXTJVRVZYMBZAJTRCVVZBANCNFSM4KSCOV3A>
.
|
|
Thanks for your reply. Yes whenever i created new webhook with new service account i always delete the existing one. Similarly, github repo status: |
|
Just now i tried "pipeline" service account and building started successfully. But why "kabanero-pipeline" service account does not initiate trigger? Anyways, thanks a lot for your support, effort and time. |
|
Oh that's interesting. I use The main drawback of |
|
Can I see the log of the tekton-webhookd-extension-validator pod? |
|
[root@bastion 0.5]# oc logs -f tekton-webhooks-extension-validator-5d8dbffdc8-rpvcl |
|
again tried with "kabanero-pipeline" and failed: |
|
I see 2 executions in the log 2020/02/13 16:08:08 one with "kabanero-pipeline" and the other with "kabanero-operator"? |
|
@akihikokuroda yes initially i tried with "kabanero-operator" and build failed, and then "kabanero-pipeline" with the same result. |
|
Let's focus of the latest execution. Can I see the log of the tasks in the pipelinerun? |
|
The succeeded one was build using "pipeline" service account :: |
|
@kvijai82 I remember I saw this error before. This is an issue in the task or Appsody. |
|
[root@bastion 0.5]# tkn taskrun list |
|
Would you do ? |
|
|
|
@kvijai82 I'm not familiar with the Appsody / kabanero stack but this looks suspicious. |
|
I think i found the issue. Knative eventing is not successfully initialized in kabanero |
|
Oh interesting. Not sure why that happened. Keep us posted on how things go with the new install. Thanks! |
|
@karimbzu - Can the issue be closed or the problem still exists? |
|
The issue is still there, we are running two OCP 4.2 clusters simultaneously, one for staging and one for production. The pipelines in production cluster are able to use "kabanero-pipeline" service account whereas other cluster showing the same error as described. However, "pipeline" service account is working in both clusters but this causes another issue which is we cannot deploy pipeline apps on namespaces other than "kabanero". |
|
@karimbzu @marikaj123 @kvijai82 It is unclear to me at the moment what exactly we are blocked on. Does the description of this issue still match the problem in the second cluster? |
|
@karimbzu did you reinstall the staging cluster to get around the kNative issues you mentioned earlier and you are still having issues after that? |
|
@stephenkinder @kvijai82 @marikaj123, knative issue was resolved after reinstalling the whole kabanero 0.5. However, the previous issue is the same |
|
@karimbzu could you please run the must gather script on both your working and failing cluster and upload the logs? There is also a new 0.6.0 release published if you want to give that a shot. There are lot of changes in that release. https://github.com/kabanero-io/kabanero-operator/releases/tag/0.6.0 |
|
@karimbzu - Please view the above comment from Vijai in order to provide you with better assistance. |
Kindly help me to resolve the subject issue. I am using openshift 4.2.16 with kabanero 0.5. Trying to deploy nodejs-express using github webhooks.
Thanks
The text was updated successfully, but these errors were encountered: