htwdjqr opened a new issue #4623:
URL: https://github.com/apache/apisix/issues/4623


   ### Issue description
   启用 traffic-split 做蓝绿发布时,无法正确的转发至规则匹配节点
   
   ### Environment
   
   Bug report without environment information will be ignored or closed.
   
   * apisix version (cmd: `apisix version`):2.6
   * OS (cmd: `uname -a`):Linux apisix 3.10.0-1127.19.1.el7.x86_64 #1 SMP Tue 
Aug 25 17:23:54 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
   * OpenResty / Nginx version (cmd: `nginx -V` or `openresty -V`):nginx 
version: openresty/1.19.3.2
   * etcd version, if have (cmd: run `curl 
http://127.0.0.1:9090/v1/server_info` to get the info from server-info API):3.4
   * apisix-dashboard version, if have:2.7
   * luarocks version, if the issue is about installation (cmd: `luarocks 
--version`):\/usr/local/bin/luarocks 3.4.0
   
   ### Minimal test code / Steps to reproduce the issue
   
   Bug report without steps to reproduce will be ignored or closed.
   
   1.配置 traffic-split 插件
   {
     "disable": false,
     "rules": [
       {
         "match": [
           {
             "vars": [
               [
                 "http_release",
                 "==",
                 "new_release"
               ]
             ]
           }
         ],
         "weighted_upstreams": [
           {
             "upstream": {
               "name": "upstream_A",
               "nodes": {
                 "172.18.50.234:10002": 10
               },
               "type": "roundrobin"
             }
           }
         ]
       }
     ]
   }
   2.使用postman发起请求,并且设置请求头release=new_release,使其命中配置规则。
   
   ### What's the actual result? (including assertion message & call stack if 
applicable)
   一部分请求会转发到172.18.50.234:10002节点中,另外一部分请求会转发到路由配置的上游节点中。
   
   ### What's the expected result?
   命中规则的所有请求都会转发至172.18.50.234:10002节点中。
   


-- 
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: [email protected]

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


Reply via email to