[jboss-jira] [JBoss JIRA] (SWSQE-975) Jaeger operator fails to deploy because of registry puller not being accessible yet

Filip Brychta (Jira) issues at jboss.org
Thu Oct 10 12:53:00 EDT 2019


     [ https://issues.jboss.org/browse/SWSQE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filip Brychta resolved SWSQE-975.
---------------------------------
    Resolution: Done


https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/commit/50f22822a3629e62913bb2f1c08ed78b67c3f236

> Jaeger operator fails to deploy because of registry puller not being accessible yet
> -----------------------------------------------------------------------------------
>
>                 Key: SWSQE-975
>                 URL: https://issues.jboss.org/browse/SWSQE-975
>             Project: Kiali QE
>          Issue Type: Bug
>            Reporter: Filip Brychta
>            Assignee: Filip Brychta
>            Priority: Major
>              Labels: infrastructure
>
> Jaeger operator installation fails with:
> Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "registry-puller.kevinconner.io": Post https://registry-puller.registry-puller.svc:443/webhook?timeout=30s: no endpoints available for service "registry-puller"
> It's happening only sometimes so I guess it depends on registry puller pod startup time.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list