souzens commented on issue #2695:
URL: https://github.com/apache/apisix/issues/2695#issuecomment-725324569


   the same wrong
   use k8s & apache/apisix:latest dcoker image
   
   `./etcdctl --endpoints=10.111.9.154:2379 get --prefix "/apisix"
   /apisix/routes/328088132001988967
   
{"id":"328088132001988967","create_time":1605085365,"update_time":1605086330,"uris":["/*"],"name":"test-pre","methods":["GET","HEAD","POST","PUT","DELETE","OPTIONS","PATCH"],"hosts":["venice.test-pre.com"],"vars":[],"upstream":{"nodes":[{"host":"venice.test-pre.svc.cluster.local","port":80,"weight":1}],"timeout":{"connect":6000,"read":6000,"send":6000},"type":"roundrobin"}}`
   
   `/usr/local/apisix $ curl 
http://127.0.0.1:9080/apisix/admin/routes/328088132001988967 -H 'X-AP
   I-KEY: edd1c9f034335f136f87ad84b625c8f1'
   <html>
   <head><title>500 Internal Server Error</title></head>
   <body>
   <center><h1>500 Internal Server Error</h1></center>
   <hr><center>openresty</center>
   </body>
   </html>`
   
   `2020/11/11 17:53:56 [error] 34#34: *185774 lua entry thread aborted: 
runtime error: /usr/local/apisix/apisix/core/etcd.lua:80: attempt to index 
field 'body' (a nil value)
   stack traceback:
   coroutine 0:
           /usr/local/apisix/apisix/core/etcd.lua: in function 'get'
           /usr/local/apisix/apisix/admin/routes.lua:166: in function 
</usr/local/apisix/apisix/admin/routes.lua:160>
           /usr/local/apisix/apisix/admin/init.lua:146: in function 'handler'
           /usr/local/apisix//deps/share/lua/5.1/resty/radixtree.lua:730: in 
function 'dispatch'
           /usr/local/apisix/apisix/init.lua:754: in function 'http_admin'
           content_by_lua(nginx.conf:148):2: in main chunk, client: 127.0.0.1, 
server: , request: "GET /apisix/admin/routes/328088132001988967 HTTP/1.1", 
host: "127.0.0.1:9080"`
   
   can't work now on 2.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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to