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 2021/09/03 08:05:04 UTC
[GitHub] [apisix-ingress-controller] riskgod opened a new issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
riskgod opened a new issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663
hey in k8s（helm chart install version 2.7）
my apisix-ingress-controller always through this err. What is this mean?
```
failed to list upstreams in APISIX: unexpected non-empty object
```
--
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] gxthrj commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
gxthrj commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-919660840
@riskgod Is there any update? Has this problem been resolved in your environment?
--
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] tokers commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-913117418
This result was caused by the marshal process of apisix upstream.
@riskgod Could you try to send requests to apisix admin service and see the result? The request likes:
```shell
curl http://apisix-admin:9180/apisix/admin/upstreams
```
`X-API-Key` should be carried so that the authentication can be passed.
--
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] gxthrj closed issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
gxthrj closed issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663
--
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] riskgod commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
riskgod commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-912413352
> So what's the version of your apisix-ingress-controller?
```
apache/apisix-ingress-controller:1.0.0
```
--
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] tokers commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-918184090
> If the Apache APISIX cluster is managed **only** by the APISIX Ingress controller, there won't have any object-like nodes, are there some legacy data in the cluster before the ingress controller takes over it.
By the way, we can consider to support object like nodes.
--
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 #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-913069913
@gxthrj PTAL
--
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] Donghui0 commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
Donghui0 commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-918127808
@riskgod It should be the format of Upstream.nodes is wrong.
Wrong format:
{"1.1.1.1:8080": 1, "2.2.2.2:8080": 1}
Correct format:
[{"host": "1.1.1.1", "port": 8080, "weight": 100, "priority": 0}]
Use the following command to query:
curl http://apisix-admin:9180/apisix/admin/upstreams -H "X-API-KEY: secretKey" | python -m json.tool
--
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] Donghui0 edited a comment on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
Donghui0 edited a comment on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-918127808
@riskgod It should be the format of Upstream.nodes is wrong.
Wrong format:
{"1.1.1.1:8080": 1, "2.2.2.2:8080": 1}
Correct format:
[{"host": "1.1.1.1", "port": 8080, "weight": 100, "priority": 0}]
Use the following command to query:
`curl http://apisix-admin:9180/apisix/admin/upstreams -H "X-API-KEY: secretKey" | python -m json.tool
`
--
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] riskgod commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
riskgod commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-912415946
The err also shows
```
failed to convert upstream item
```
--
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] gxthrj commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
gxthrj commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-927213489
The stale issue, feel free to reopen.
--
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] tokers commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-918183616
If the Apache APISIX cluster is managed **only** by the APISIX Ingress controller, there won't have any object-like nodes, are there some legacy data in the cluster before the ingress controller takes over it.
--
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] gxthrj commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
gxthrj commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-917888568
@riskgod any update? please show the configuration of ingress controller.
--
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] tokers commented on issue #663: request help: failed to list upstreams in APISIX: unexpected non-empty object
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #663:
URL: https://github.com/apache/apisix-ingress-controller/issues/663#issuecomment-912392493
So what's the version of your apisix-ingress-controller?
--
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