https://bentoml.com logo
Join Slack
Powered by
This message was deleted.
# ask-for-help
s
This message was deleted.
🦄 1
🏁 1
j
FYI, this is the screenshot of error msg.
kubectl -n yatai-deployment logs -f deploy/yatai-deployment
shows the following error:
Copy code
1.6723846516673543e+09  ERROR   conversion-webhook      failed to convert       {"request": "eb03cb85-4f56-4820-b0a0-6748bad4b329", "error": "no kind \"BentoDeployment\" is registered for version \"<http://serving.yatai.ai/v2alpha1\|serving.yatai.ai/v2alpha1\>" in scheme \"pkg/runtime/scheme.go:100\""}
<http://sigs.k8s.io/controller-runtime/pkg/webhook/conversion.(*Webhook).ServeHTTP|sigs.k8s.io/controller-runtime/pkg/webhook/conversion.(*Webhook).ServeHTTP>
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/webhook/conversion/conversion.go:76
<http://github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerInFlight.func1|github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerInFlight.func1>
        /go/pkg/mod/github.com/prometheus/client_golang@v1.12.2/prometheus/promhttp/instrument_server.go:40
net/http.HandlerFunc.ServeHTTP
        /usr/local/go/src/net/http/server.go:2109
<http://github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerCounter.func1|github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerCounter.func1>
        /go/pkg/mod/github.com/prometheus/client_golang@v1.12.2/prometheus/promhttp/instrument_server.go:117
net/http.HandlerFunc.ServeHTTP
        /usr/local/go/src/net/http/server.go:2109
<http://github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerDuration.func2|github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerDuration.func2>
        /go/pkg/mod/github.com/prometheus/client_golang@v1.12.2/prometheus/promhttp/instrument_server.go:84
net/http.HandlerFunc.ServeHTTP
        /usr/local/go/src/net/http/server.go:2109
net/http.(*ServeMux).ServeHTTP
        /usr/local/go/src/net/http/server.go:2487
net/http.serverHandler.ServeHTTP
        /usr/local/go/src/net/http/server.go:2947
net/http.(*conn).serve
        /usr/local/go/src/net/http/server.go:1991
b
You might be missing a step during the install
x
Thank you for your feedback, this is caused by yatai-deployment merging unreleased branches, you can fix this issue with this command:
Copy code
kubectl apply -f <https://raw.githubusercontent.com/bentoml/yatai-deployment/v1.0.x/helm/yatai-deployment/crds/bentodeployment.yaml>
👍 1
j
I resolved the issue. Thanks! 👍
k
Hi Guys, sorry for bringing back an old topic. I have the same issue. We had yatai working on bare-metal and then added a node to our cluster. Now the `yatai-deployments`does not work and I get the following error:
Copy code
ERROR	conversion-webhook	failed to convert	{"request": "7ead9a5b-ad1c-489a-82f3-83ed615211b8", "error": "*v1alpha1.BentoDeployment failed to convert from hub version *v2alpha1.BentoDeployment : get Bento CR absa-service--tnembzuyug-3-thkfb: <http://bentoes.resources.yatai.ai|bentoes.resources.yatai.ai> \"absa-service--tnembzuyug-3-thkfb\" not found"}
So we do not understand where this is coming from. We updated yatai and yatai-deployments in an effort to fix it but nothing so far. 
yatai-1.1.1
and 
yatai-deployment-1.1.4
Copy code
$ kubectl get crd | grep bento
<http://bentodeployments.serving.yatai.ai|bentodeployments.serving.yatai.ai>            2022-12-12T22:53:22Z
<http://bentoes.resources.yatai.ai|bentoes.resources.yatai.ai>                   2023-01-25T20:04:44Z
<http://bentorequests.resources.yatai.ai|bentorequests.resources.yatai.ai>             2023-01-25T20:04:44Z
Copy code
$ kubectl api-resources | grep bento
bentoes                                              <http://resources.yatai.ai/v1alpha1|resources.yatai.ai/v1alpha1>            true         Bento
bentorequests                                        <http://resources.yatai.ai/v1alpha1|resources.yatai.ai/v1alpha1>            true         BentoRequest
bentodeployments                                     <http://serving.yatai.ai/v2alpha1|serving.yatai.ai/v2alpha1>              true         BentoDeployment
This is the extensive log.
yatai-deployment-6dbdd5b9c9-vq44x.log
x
@Kostas Vasilopoulos Can you tell me the version of yatai you installed? helm list -A
k
Copy code
yatai                           yatai-system            2               2023-01-25 20:34:58.18440672 +0000 UTC  deployed        yatai-1.1.1                        1.1.1
yatai-deployment                yatai-deployment        1               2023-01-25 20:27:25.502561524 +0000 UTC deployed        yatai-deployment-1.1.4             1.1.4
yatai-deployment-crds           yatai-deployment        1               2023-01-25 20:09:00.285988774 +0000 UTC deployed        yatai-deployment-crds-0.1.0        1.16.0
yatai-image-builder-crds        yatai-image-builder     1               2023-01-25 20:04:43.957698013 +0000 UTC deployed        yatai-image-builder-crds-1.1.3     1.1.3
x
@Kostas Vasilopoulos It's so strange, why yatai-deployment-crds and yatai-deployment versions are not the same?
@Kostas Vasilopoulos And why is yatai-image-builder not installed?
k
@Xipeng Guan good questions. Let me do a quick exploration and get back to you.
@Xipeng Guan as for the version we installed yesterday from the helm-chart repo ... is it possible to have a mismatch there?
x
@Kostas Vasilopoulos The latest versions of yatai-deployment-crds and yatai-deployment are always the same version number
k
@Xipeng Guan. Thanks for all your help. I am trying to install 
yatai-iamge-builders
and I get the following error 
Unable to attach or mount volumes: unmounted volumes=[cert], unattached volumes=[cert kube-api-access-f9rjg]: timed out waiting for the condition
Hi @Xipeng Guan I have installed everything from the start:
Copy code
helm list -A | grep yatai
docker-registry                 yatai-image-builder     1               2023-01-26 18:59:46.02923505 +0000 UTC  deployedocker-registry-2.2.2            2.8.1
minio-operator                  yatai-system            1               2023-01-26 18:27:22.626852258 +0000 UTC deployeminio-operator-4.3.7             v4.3.7
postgresql-ha                   yatai-system            1               2023-01-26 17:33:07.527883013 +0000 UTC deployepostgresql-ha-10.0.6             15.1.0
yatai                           yatai-system            1               2023-01-26 18:46:43.499596155 +0000 UTC deployeyatai-1.1.3                      1.1.3
yatai-deployment                yatai-deployment        1               2023-01-26 19:33:14.135281825 +0000 UTC deployeyatai-deployment-1.1.4           1.1.4
yatai-deployment-crds           yatai-deployment        1               2023-01-26 19:32:37.867821934 +0000 UTC deployeyatai-deployment-crds-1.1.4      1.1.4
yatai-image-builder             yatai-image-builder     1               2023-01-26 19:05:23.571724689 +0000 UTC deployeyatai-image-builder-1.1.3        1.1.3
yatai-image-builder-crds        yatai-image-builder     1               2023-01-26 19:04:02.509968517 +0000 UTC deployeyatai-image-builder-crds-1.1.3   1.1.3
but I get the following error from 
yatai-deployment
and 
yatai-image-builder
Copy code
Unable to attach or mount volumes: unmounted volumes=[cert], unattached volumes=[cert kube-api-access-djbg8]: timed out waiting for the condition
2 Views
Open in Slack
PreviousNext
Powered by