You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "Padmabishek (via GitHub)" <gi...@apache.org> on 2023/08/23 02:25:37 UTC
[GitHub] [apisix-ingress-controller] Padmabishek opened a new issue, #1928: Latest apisix ingress controller doesn't work after helm installation fails with error 'failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}' #595request help:
Padmabishek opened a new issue, #1928:
URL: https://github.com/apache/apisix-ingress-controller/issues/1928
### Issue description
I had tried installing latest apisix ingress-controller with appVersion: 1.6.1 with the latest apisix-gateway installation with appVersion: 3.4.1
The installation of apisix-gateway was fine and the pods are up and running . But after the apisix-ingress-controller installation , saw few errors in the logs and ingress-controller was not able to load the tls resources, Please find the logs below
Defaulted container "apisix-ingress-controller" out of: apisix-ingress-controller, wait-apisix-admin (init)
2023-08-12T03:45:52+08:00 info ingress/ingress.go:128 init apisix ingress controller
2023-08-12T03:45:52+08:00 info ingress/ingress.go:130 version:
Version: 1.6.1
Git SHA: no-git-module
Go Version: go1.19.8
Building OS/Arch: linux/amd64
Running OS/Arch: linux/amd64
2023-08-12T03:45:52+08:00 info ingress/ingress.go:140 use configuration
{
"cert_file": "/etc/webhook/certs/cert.pem",
"key_file": "/etc/webhook/certs/key.pem",
"log_level": "info",
"log_output": "stderr",
"log_rotate_output_path": "",
"log_rotation_max_size": 100,
"log_rotation_max_age": 0,
"log_rotation_max_backups": 0,
"http_listen": ":8080",
"https_listen": ":8443",
"ingress_publish_service": "",
"ingress_status_address": [],
"enable_profiling": true,
"kubernetes": {
"kubeconfig": "",
"resync_interval": "6h0m0s",
"namespace_selector": [],
"election_id": "ingress-apisix-leader",
"ingress_class": "apisix",
"ingress_version": "networking/v1",
"watch_endpoint_slices": false,
"api_version": "apisix.apache.org/v2",
"enable_gateway_api": false
},
"apisix": {
"admin_api_version": "v2",
"default_cluster_name": "default",
"default_cluster_base_url": "http://apisix-admin.apisix:9180/apisix/admin",
"default_cluster_admin_key": "******"
},
"apisix-resource-sync-interval": "5m0s",
"plugin_metadata_cm": ""
}
2023-08-12T03:45:52+08:00 warn api/server.go:76 failed to load x509 key pair, will not start admission server {"Error": "open /etc/webhook/certs/cert.pem: no such file or directory", "CertFilePath": "/etc/webhook/certs/cert.pem", "KeyFilePath": "/etc/webhook/certs/key.pem"}
2023-08-12T03:45:52+08:00 info ingress/ingress.go:152 start ingress controller
I0812 03:45:52.820063 1 leaderelection.go:248] attempting to acquire leader lease apisix/ingress-apisix-leader...
2023-08-12T03:45:52+08:00 info providers/controller.go:151 start api server
2023-08-12T03:45:52+08:00 warn providers/controller.go:176 found a new leader apisix-ingress-apisix-ingress-controller-5b8679d5d9-kpm6d
2023-08-12T03:45:52+08:00 info providers/controller.go:178 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc"}
2023-08-12T03:45:54+08:00 info gin@v1.8.1/context.go:173 path: /healthz, status: 200, method: GET, query: , ip: 172.26.32.136, user-agent: kube-probe/1.24, errors: , cost: 71.718µs
2023-08-12T03:46:00+08:00 info gin@v1.8.1/context.go:173 path: /healthz, status: 200, method: GET, query: , ip: 172.26.32.136, user-agent: kube-probe/1.24, errors: , cost: 75.819µs
2023-08-12T03:46:00+08:00 info gin@v1.8.1/context.go:173 path: /healthz, status: 200, method: GET, query: , ip: 172.26.32.136, user-agent: kube-probe/1.24, errors: , cost: 32.592µs
2023-08-12T03:46:10+08:00 info providers/controller.go:137 LeaderElection {"message": "apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc became leader", "event_type": "Normal"}
I0812 03:46:10.230659 1 leaderelection.go:258] successfully acquired lease apisix/ingress-apisix-leader
2023-08-12T03:46:10+08:00 warn providers/controller.go:176 found a new leader apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc
2023-08-12T03:46:10+08:00 info providers/controller.go:360 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc"}
2023-08-12T03:46:10+08:00 info apisix/stream_route.go:38 resource stream_routes is disabled
2023-08-12T03:46:10+08:00 warn apisix/cluster.go:344 waiting cluster default to ready, it may takes a while
2023-08-12T03:46:10+08:00 info apisix/cluster.go:384 syncing schema {"cluster": "default"}
2023-08-12T03:46:10+08:00 info apisix/cluster.go:172 syncing cache {"cluster": "default"}
2023-08-12T03:46:10+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:10+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:10+08:00 info gin@v1.8.1/context.go:173 path: /healthz, status: 200, method: GET, query: , ip: 172.26.32.136, user-agent: kube-probe/1.24, errors: , cost: 46.47µs
2023-08-12T03:46:10+08:00 info gin@v1.8.1/context.go:173 path: /healthz, status: 200, method: GET, query: , ip: 172.26.32.136, user-agent: kube-probe/1.24, errors: , cost: 38.036µs
2023-08-12T03:46:12+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:12+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:14+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:14+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:16+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:16+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:18+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:18+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:18+08:00 error apisix/cluster.go:182 failed to sync cache {"cost_time": "8.063523557s", "cluster": "default"}
2023-08-12T03:46:18+08:00 error providers/controller.go:388 failed to wait the default cluster to be ready: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:18+08:00 info apisix/stream_route.go:38 resource stream_routes is disabled
2023-08-12T03:46:18+08:00 info apisix/cluster.go:172 syncing cache {"cluster": "default"}
2023-08-12T03:46:18+08:00 error apisix/route.go:118 failed to list routes: Get "http://apisix-admin.apisix:9180/apisix/admin/routes": context canceled
2023-08-12T03:46:18+08:00 error apisix/cluster.go:222 failed to list routes in APISIX: Get "http://apisix-admin.apisix:9180/apisix/admin/routes": context canceled
2023-08-12T03:46:18+08:00 error apisix/cluster.go:182 failed to sync cache {"cost_time": "151.04µs", "cluster": "default"}
2023-08-12T03:46:18+08:00 info apisix/cluster.go:384 syncing schema {"cluster": "default"}
2023-08-12T03:46:18+08:00 error apisix/plugin.go:46 failed to list plugins' names: Get "http://apisix-admin.apisix:9180/apisix/admin/plugins?all=true": context canceled
2023-08-12T03:46:18+08:00 error apisix/cluster.go:404 failed to list plugin names in APISIX: Get "http://apisix-admin.apisix:9180/apisix/admin/plugins?all=true": context canceled
2023-08-12T03:46:18+08:00 error apisix/cluster.go:367 failed to sync schema: Get "http://apisix-admin.apisix:9180/apisix/admin/plugins?all=true": context canceled
2023-08-12T03:46:18+08:00 info providers/controller.go:190 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc"}
I0812 03:46:18.331741 1 leaderelection.go:248] attempting to acquire leader lease apisix/ingress-apisix-leader...
2023-08-12T03:46:18+08:00 info providers/controller.go:137 LeaderElection {"message": "apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc became leader", "event_type": "Normal"}
I0812 03:46:18.338912 1 leaderelection.go:258] successfully acquired lease apisix/ingress-apisix-leader
2023-08-12T03:46:18+08:00 info providers/controller.go:360 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc"}
2023-08-12T03:46:18+08:00 info apisix/stream_route.go:38 resource stream_routes is disabled
2023-08-12T03:46:18+08:00 warn apisix/cluster.go:344 waiting cluster default to ready, it may takes a while
2023-08-12T03:46:18+08:00 info apisix/cluster.go:384 syncing schema {"cluster": "default"}
2023-08-12T03:46:18+08:00 info apisix/cluster.go:172 syncing cache {"cluster": "default"}
2023-08-12T03:46:18+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:18+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:20+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:20+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:20+08:00 info gin@v1.8.1/context.go:173 path: /healthz, status: 200, method: GET, query: , ip: 172.26.32.136, user-agent: kube-probe/1.24, errors: , cost: 46.967µs
2023-08-12T03:46:20+08:00 info gin@v1.8.1/context.go:173 path: /healthz, status: 200, method: GET, query: , ip: 172.26.32.136, user-agent: kube-probe/1.24, errors: , cost: 38.699µs
2023-08-12T03:46:22+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:22+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:24+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:24+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:26+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:26+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:26+08:00 error apisix/cluster.go:182 failed to sync cache {"cost_time": "8.05904106s", "cluster": "default"}
2023-08-12T03:46:26+08:00 error providers/controller.go:388 failed to wait the default cluster to be ready: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:26+08:00 info apisix/stream_route.go:38 resource stream_routes is disabled
2023-08-12T03:46:26+08:00 info apisix/cluster.go:172 syncing cache {"cluster": "default"}
2023-08-12T03:46:26+08:00 error apisix/route.go:118 failed to list routes: Get "http://apisix-admin.apisix:9180/apisix/admin/routes": context canceled
2023-08-12T03:46:26+08:00 error apisix/cluster.go:222 failed to list routes in APISIX: Get "http://apisix-admin.apisix:9180/apisix/admin/routes": context canceled
2023-08-12T03:46:26+08:00 error apisix/cluster.go:182 failed to sync cache {"cost_time": "64.05µs", "cluster": "default"}
2023-08-12T03:46:26+08:00 info apisix/cluster.go:384 syncing schema {"cluster": "default"}
2023-08-12T03:46:26+08:00 error apisix/plugin.go:46 failed to list plugins' names: Get "http://apisix-admin.apisix:9180/apisix/admin/plugins?all=true": context canceled
2023-08-12T03:46:26+08:00 error apisix/cluster.go:404 failed to list plugin names in APISIX: Get "http://apisix-admin.apisix:9180/apisix/admin/plugins?all=true": context canceled
2023-08-12T03:46:26+08:00 error apisix/cluster.go:367 failed to sync schema: Get "http://apisix-admin.apisix:9180/apisix/admin/plugins?all=true": context canceled
2023-08-12T03:46:26+08:00 info providers/controller.go:190 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc"}
I0812 03:46:26.403284 1 leaderelection.go:248] attempting to acquire leader lease apisix/ingress-apisix-leader...
2023-08-12T03:46:26+08:00 info providers/controller.go:137 LeaderElection {"message": "apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc became leader", "event_type": "Normal"}
I0812 03:46:26.409206 1 leaderelection.go:258] successfully acquired lease apisix/ingress-apisix-leader
2023-08-12T03:46:26+08:00 info providers/controller.go:360 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-apisix-ingress-controller-5b8679d5d9-272cc"}
2023-08-12T03:46:26+08:00 info apisix/stream_route.go:38 resource stream_routes is disabled
2023-08-12T03:46:26+08:00 warn apisix/cluster.go:344 waiting cluster default to ready, it may takes a while
2023-08-12T03:46:26+08:00 info apisix/cluster.go:384 syncing schema {"cluster": "default"}
2023-08-12T03:46:26+08:00 info apisix/cluster.go:172 syncing cache {"cluster": "default"}
2023-08-12T03:46:26+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:26+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:28+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:28+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:30+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:30+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:30+08:00 info gin@v1.8.1/context.go:173 path: /healthz, status: 200, method: GET, query: , ip: 172.26.32.136, user-agent: kube-probe/1.24, errors: , cost: 35.076µs
2023-08-12T03:46:30+08:00 info gin@v1.8.1/context.go:173 path: /healthz, status: 200, method: GET, query: , ip: 172.26.32.136, user-agent: kube-probe/1.24, errors: , cost: 47.513µs
2023-08-12T03:46:32+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:32+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:34+08:00 error apisix/ssl.go:120 failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:34+08:00 error apisix/cluster.go:232 failed to list ssl in APISIX: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:34+08:00 error apisix/cluster.go:182 failed to sync cache {"cost_time": "8.054114273s", "cluster": "default"}
2023-08-12T03:46:34+08:00 error providers/controller.go:388 failed to wait the default cluster to be ready: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}
2023-08-12T03:46:34+08:00 info apisix/stream_route.go:38 resource stream_routes is disabled
2023-08-12T03:46:34+08:00 info apisix/cluster.go:172 syncing cache {"cluster": "default"}
2023-08-12T03:46:34+08:00 error apisix/route.go:118 failed to list routes: Get "http://apisix-admin.apisix:9180/apisix/admin/routes": context canceled
2023-08-12T03:46:34+08:00 error apisix/cluster.go:222 failed to list routes in APISIX: Get "http://apisix-admin.apisix:9180/apisix/admin/routes": context canceled
2023-08-12T03:46:34+08:00 error apisix/cluster.go:182 failed to sync cache {"cost_time": "52.811µs", "cluster": "default"}
2023-08-12T03:46:34+08:00 info apisix/cluster.go:384 syncing schema {"cluster": "default"}
2023-08-12T03:46:34+08:00 error apisix/plugin.go:46 failed to list plugins' names: Get "http://apisix-admin.apisix:9180/apisix/admin/plugins?all=true": context canceled
2023-08-12T03:46:34+08:00 error apisix/cluster.go:404 failed to list plugin names in APISIX: Get "http://apisix-admin.apisix:9180/apisix/admin/plugins?all=true": context canceled
2023-08-12T03:46:34+08:00 error apisix/cluster.go:367 failed to sync schema: Get "http://apisix-admin.apisix:9180/apisix/admin/plugins?all=true
Saw a change in release 3.0 , not sure if this had caused an issue and corresponding changes where done for ingress , ssl resource was renamed to ssls https://github.com/apache/apisix/blame/4d03794f669e3bd101b9ca242c2d2db404a0a372/apisix/admin/init.lua#L50
### Environment
apisix-ingress-controller version - 1.6.1 (Helm chart version: 0.11.7)
Kubernetes cluster version
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.14", GitCommit:"0018fa8af8ffaff22f36d3bd86289753ca61da81", GitTreeState:"clean", BuildDate:"2023-05-17T16:28:57Z", GoVersion:"go1.19.9", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.14", GitCommit:"0018fa8af8ffaff22f36d3bd86289753ca61da81", GitTreeState:"clean", BuildDate:"2023-05-17T16:21:16Z", GoVersion:"go1.19.9", Compiler:"gc", Platform:"linux/amd64"}
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] Padmabishek commented on issue #1928: Latest apisix ingress controller doesn't work after helm installation fails with error 'failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}' #595request help:
Posted by "Padmabishek (via GitHub)" <gi...@apache.org>.
Padmabishek commented on issue #1928:
URL: https://github.com/apache/apisix-ingress-controller/issues/1928#issuecomment-1702273703
@tao12345666333 , Thanks a lot for helping
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] Padmabishek closed issue #1928: Latest apisix ingress controller doesn't work after helm installation fails with error 'failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}' #595request help:
Posted by "Padmabishek (via GitHub)" <gi...@apache.org>.
Padmabishek closed issue #1928: Latest apisix ingress controller doesn't work after helm installation fails with error 'failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}' #595request help:
URL: https://github.com/apache/apisix-ingress-controller/issues/1928
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #1928: Latest apisix ingress controller doesn't work after helm installation fails with error 'failed to list ssl: unexpected status code 404; error message: {"error_msg":"Unsupported resource type: ssl"}' #595request help:
Posted by "tao12345666333 (via GitHub)" <gi...@apache.org>.
tao12345666333 commented on issue #1928:
URL: https://github.com/apache/apisix-ingress-controller/issues/1928#issuecomment-1692623904
Due to your use of APISIX v3 version, please pay attention to this configuration.
https://github.com/apache/apisix-ingress-controller/blob/fa07c662e6cb18bffea89423efb0e716fd72ccdd/conf/config-default.yaml#L92
You should use admin API v3 version.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org