yahoo-eng-team team mailing list archive

[yalei wang <yalei.wang@xxxxxxxxx>]

Public bug reported:

-------
Request body: {u'security_group_rule': {u'remote_group_id': None, u'direction': u'ingress', u'protocol': u'icmp', u'ethertype': u'IPv4', u'port_range_max': None, u'security_group_id': u'b2f57cd6-e466-4e92-9670-571334188394', u'port_range_min': None, u'remote_ip_prefix': u'0.0.0.0/0'}} from (pid=13486) prepare_request_body /opt/stack/neutron/neutron/api/v2/base.py:654

will create rules

    0     0 RETURN     icmp --  *      *       0.0.0.0/0
0.0.0.0/0            icmptype 0 code 0


------

Request body: {u'security_group_rule': {u'remote_group_id': None,
u'direction': u'ingress', u'protocol': u'icmp', u'remote_ip_prefix':
u'0.0.0.0/0', u'port_range_max': u'0', u'security_group_id': u'2a5124cf-
527d-4812-8d1a-17b78dee0cea', u'port_range_min': u'0', u'ethertype':
u'IPv4'}} from (pid=13486) prepare_request_body
/opt/stack/neutron/neutron/api/v2/base.py:654

will create rules
    1    84 RETURN     icmp --  *      *       0.0.0.0/0            0.0.0.0/0

----
the difference is that the input arg in request: 'port_range_max': '0' or 'None', I guess it's a bug, we need clear definition on the arg in API.

** Affects: neutron
     Importance: Undecided
     Assignee: yalei wang (yalei-wang)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => yalei wang (yalei-wang)

** Description changed:

- 2016-02-29 16:46:09.381 DEBUG neutron.api.v2.base [req-0a7d0cac-a8a5-4e09-bf24-6adf3cc34f84 admin 804f4686ab1541fc89d0a12eda7c292b] Request body: {u'security_group_rule': {u'remote_group_id': None, u'direction': u'ingress', u'protocol': u'icmp', u'ethertype': u'IPv4', u'port_range_max': None, u'security_group_id': u'b2f57cd6-e466-4e92-9670-571334188394', u'port_range_min': None, u'remote_ip_prefix': u'0.0.0.0/0'}} from (pid=13486) prepare_request_body /opt/stack/neutron/neutron/api/v2/base.py:654
- will create rules 
+ -------
+ Request body: {u'security_group_rule': {u'remote_group_id': None, u'direction': u'ingress', u'protocol': u'icmp', u'ethertype': u'IPv4', u'port_range_max': None, u'security_group_id': u'b2f57cd6-e466-4e92-9670-571334188394', u'port_range_min': None, u'remote_ip_prefix': u'0.0.0.0/0'}} from (pid=13486) prepare_request_body /opt/stack/neutron/neutron/api/v2/base.py:654
  
-     0     0 RETURN     icmp --  *      *       0.0.0.0/0
+ will create rules
+ 
+     0     0 RETURN     icmp --  *      *       0.0.0.0/0
  0.0.0.0/0            icmptype 0 code 0
  
- 2016-02-29 17:15:46.011 DEBUG neutron.api.v2.base [req-
- 22ebbba7-e670-4bd3-838b-ca61b3902071 admin
- 804f4686ab1541fc89d0a12eda7c292b] Request body: {u'security_group_rule':
- {u'remote_group_id': None, u'direction': u'ingress', u'protocol':
- u'icmp', u'remote_ip_prefix': u'0.0.0.0/0', u'port_range_max': u'0',
- u'security_group_id': u'2a5124cf-527d-4812-8d1a-17b78dee0cea',
- u'port_range_min': u'0', u'ethertype': u'IPv4'}} from (pid=13486)
- prepare_request_body /opt/stack/neutron/neutron/api/v2/base.py:654
+ 
+ ------
+ 
+ Request body: {u'security_group_rule': {u'remote_group_id': None,
+ u'direction': u'ingress', u'protocol': u'icmp', u'remote_ip_prefix':
+ u'0.0.0.0/0', u'port_range_max': u'0', u'security_group_id': u'2a5124cf-
+ 527d-4812-8d1a-17b78dee0cea', u'port_range_min': u'0', u'ethertype':
+ u'IPv4'}} from (pid=13486) prepare_request_body
+ /opt/stack/neutron/neutron/api/v2/base.py:654
  
  will create rules
-     1    84 RETURN     icmp --  *      *       0.0.0.0/0            0.0.0.0/0      
+     1    84 RETURN     icmp --  *      *       0.0.0.0/0            0.0.0.0/0
  
- 
+ ----
  the difference is that the input arg in request: 'port_range_max': '0' or 'None', I guess it's a bug, we need clear definition on the arg in API.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1551163

Title:
  confusion on security group rules on icmp setting

Status in neutron:
  New

Bug description:
  -------
  Request body: {u'security_group_rule': {u'remote_group_id': None, u'direction': u'ingress', u'protocol': u'icmp', u'ethertype': u'IPv4', u'port_range_max': None, u'security_group_id': u'b2f57cd6-e466-4e92-9670-571334188394', u'port_range_min': None, u'remote_ip_prefix': u'0.0.0.0/0'}} from (pid=13486) prepare_request_body /opt/stack/neutron/neutron/api/v2/base.py:654

  will create rules

      0     0 RETURN     icmp --  *      *       0.0.0.0/0
  0.0.0.0/0            icmptype 0 code 0


  ------

  Request body: {u'security_group_rule': {u'remote_group_id': None,
  u'direction': u'ingress', u'protocol': u'icmp', u'remote_ip_prefix':
  u'0.0.0.0/0', u'port_range_max': u'0', u'security_group_id': u
  '2a5124cf-527d-4812-8d1a-17b78dee0cea', u'port_range_min': u'0',
  u'ethertype': u'IPv4'}} from (pid=13486) prepare_request_body
  /opt/stack/neutron/neutron/api/v2/base.py:654

  will create rules
      1    84 RETURN     icmp --  *      *       0.0.0.0/0            0.0.0.0/0

  ----
  the difference is that the input arg in request: 'port_range_max': '0' or 'None', I guess it's a bug, we need clear definition on the arg in API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1551163/+subscriptions