You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/06/08 01:54:57 UTC
[GitHub] [apisix-ingress-controller] jackey20200402 opened a new issue, #1076: bug: 无法写入upstream
jackey20200402 opened a new issue, #1076:
URL: https://github.com/apache/apisix-ingress-controller/issues/1076
### Issue description
一直报这个错：
2022-06-08T09:43:04+08:00 error apisix/upstream.go:122 failed to convert upstream item {"url": "http://sit-apisix-admin.remac-open-cloud.svc.cluster.local:9180/apisix/admin/upstreams", "upstream_key": "/apisix/upstreams/00000000000000000177", "error": "unexpected non-empty object"}
手动删除这00000000000000000177 这个upstream后才恢复正常，00000000000000000177是通过Admin的Post方式配置的upstream。
### Environment
- your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.4.0
- your Kubernetes cluster version (output of kubectl version): 1.20.11-aliyun.1
- if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):
### Minimal test code / Steps to reproduce
1. 通过Admin api的方式配置upstream、route
2. 部署ingress control后通过yaml方式配置upstream、route
### Actual result
通过yaml方式配置的upstream、route无法写入etcd
### Error log
2022-06-08T09:43:04+08:00 error apisix/upstream.go:122 failed to convert upstream item {"url": "http://sit-apisix-admin.remac-open-cloud.svc.cluster.local:9180/apisix/admin/upstreams", "upstream_key": "/apisix/upstreams/00000000000000000177", "error": "unexpected non-empty object"}
2022-06-08T09:43:04+08:00 error apisix/cluster.go:213 failed to list upstreams in APISIX: unexpected non-empty object
2022-06-08T09:43:06+08:00 error apisix/upstream.go:122 failed to convert upstream item {"url": "http://sit-apisix-admin.remac-open-cloud.svc.cluster.local:9180/apisix/admin/upstreams", "upstream_key": "/apisix/upstreams/00000000000000000177", "error": "unexpected non-empty object"}
2022-06-08T09:43:06+08:00 error apisix/cluster.go:213 failed to list upstreams in APISIX: unexpected non-empty object
2022-06-08T09:43:09+08:00 error apisix/upstream.go:122 failed to convert upstream item {"url": "http://sit-apisix-admin.remac-open-cloud.svc.cluster.local:9180/apisix/admin/upstreams", "upstream_key": "/apisix/upstreams/00000000000000000177", "error": "unexpected non-empty object"}
2022-06-08T09:43:09+08:00 error apisix/cluster.go:213 failed to list upstreams in APISIX: unexpected non-empty object
### Expected result
_No response_
--
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] tao12345666333 commented on issue #1076: question: Inconsistent data format when mixed with other configurations
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1076:
URL: https://github.com/apache/apisix-ingress-controller/issues/1076#issuecomment-1250685195
#1222 has been merged. I will close this one. thanks
--
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] github-actions[bot] commented on issue #1076: question: Inconsistent data format when mixed with other configurations
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #1076:
URL: https://github.com/apache/apisix-ingress-controller/issues/1076#issuecomment-1238807807
This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions.
--
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 #1076: bug: 无法写入upstream
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1076:
URL: https://github.com/apache/apisix-ingress-controller/issues/1076#issuecomment-1149411715
If you are using APISIX Ingress, you should use this as the only source of configuration.
The error you encountered above is often encountered when you mix APISIX Ingress and APISIX Dashboard. The error message is because the data format is different.
--
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 closed issue #1076: question: Inconsistent data format when mixed with other configurations
Posted by GitBox <gi...@apache.org>.
tao12345666333 closed issue #1076: question: Inconsistent data format when mixed with other configurations
URL: https://github.com/apache/apisix-ingress-controller/issues/1076
--
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