← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1515896] [NEW] Update port of admin state to False for neutron floating IP port does not take effect

 

Public bug reported:

It is expected that when the admin-state of the port is down, it should
seize all the operations specific to that port. But this is not the case
with a floating IP port. When the port's admin-state is made False,
floating IP continues to be operational.

root@controller:~# neutron port-show bc3f8bf6-c4bf-451a-8b5a-0d0b7624b5ca
+-----------------------+----------------------------------------------------------------------------------+
| Field                 | Value                                                                            |
+-----------------------+----------------------------------------------------------------------------------+
| admin_state_up        | False                                                                             |
| allowed_address_pairs |                                                                                  |
| binding:host_id       |                                                                                  |
| binding:profile       | {}                                                                               |
| binding:vif_details   | {}                                                                               |
| binding:vif_type      | unbound                                                                          |
| binding:vnic_type     | normal                                                                           |
| device_id             | ca0d0355-9ebe-46c5-9a31-2e2253da2d40                                             |
| device_owner          | network:floatingip                                                               |
| extra_dhcp_opts       |                                                                                  |
| fixed_ips             | {"subnet_id": "eb1339bd-b552-4207-8856-ccff1de04f47", "ip_address": "10.0.2.18"} |
| id                    | bc3f8bf6-c4bf-451a-8b5a-0d0b7624b5ca                                             |
| mac_address           | fa:16:3e:c7:0a:98                                                                |
| name                  |                                                                                  |
| network_id            | dda8f089-25b0-4e13-886e-b0b1bc8f5801                                             |
| security_groups       |                                                                                  |
| status                | DOWN                                                                             |
| tenant_id             |                                                                                  |
+-----------------------+----------------------------------------------------------------------------------+
root@controller:~# ping 10.0.2.18
PING 10.0.2.18 (10.0.2.18) 56(84) bytes of data.
64 bytes from 10.0.2.18: icmp_seq=1 ttl=63 time=2.46 ms
64 bytes from 10.0.2.18: icmp_seq=2 ttl=63 time=23.4 ms
^C
--- 10.0.2.18 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 2.466/12.949/23.433/10.484 ms

Observation:

1) neutron port-update FLOATING_IP_PORT --admin-state-up False
2) neutron port-update PRIVATE_IP_PORT --admin-state-up False
3) neutron port-update PRIVATE_IP_PORT --admin-state-up True
4) Ping of Floating IP does not work now. 
5) neutron port-update FLOATING_IP_PORT --admin-state-up True
6) Ping of Floating IP should start working now.

Also, this results in the failure of tempest test:
tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_update_instance_port_admin_state

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Update port of admin state to False for neutron floating IP port does
  not take effect

Status in neutron:
  New

Bug description:
  It is expected that when the admin-state of the port is down, it
  should seize all the operations specific to that port. But this is not
  the case with a floating IP port. When the port's admin-state is made
  False, floating IP continues to be operational.

  root@controller:~# neutron port-show bc3f8bf6-c4bf-451a-8b5a-0d0b7624b5ca
  +-----------------------+----------------------------------------------------------------------------------+
  | Field                 | Value                                                                            |
  +-----------------------+----------------------------------------------------------------------------------+
  | admin_state_up        | False                                                                             |
  | allowed_address_pairs |                                                                                  |
  | binding:host_id       |                                                                                  |
  | binding:profile       | {}                                                                               |
  | binding:vif_details   | {}                                                                               |
  | binding:vif_type      | unbound                                                                          |
  | binding:vnic_type     | normal                                                                           |
  | device_id             | ca0d0355-9ebe-46c5-9a31-2e2253da2d40                                             |
  | device_owner          | network:floatingip                                                               |
  | extra_dhcp_opts       |                                                                                  |
  | fixed_ips             | {"subnet_id": "eb1339bd-b552-4207-8856-ccff1de04f47", "ip_address": "10.0.2.18"} |
  | id                    | bc3f8bf6-c4bf-451a-8b5a-0d0b7624b5ca                                             |
  | mac_address           | fa:16:3e:c7:0a:98                                                                |
  | name                  |                                                                                  |
  | network_id            | dda8f089-25b0-4e13-886e-b0b1bc8f5801                                             |
  | security_groups       |                                                                                  |
  | status                | DOWN                                                                             |
  | tenant_id             |                                                                                  |
  +-----------------------+----------------------------------------------------------------------------------+
  root@controller:~# ping 10.0.2.18
  PING 10.0.2.18 (10.0.2.18) 56(84) bytes of data.
  64 bytes from 10.0.2.18: icmp_seq=1 ttl=63 time=2.46 ms
  64 bytes from 10.0.2.18: icmp_seq=2 ttl=63 time=23.4 ms
  ^C
  --- 10.0.2.18 ping statistics ---
  2 packets transmitted, 2 received, 0% packet loss, time 1001ms
  rtt min/avg/max/mdev = 2.466/12.949/23.433/10.484 ms

  Observation:

  1) neutron port-update FLOATING_IP_PORT --admin-state-up False
  2) neutron port-update PRIVATE_IP_PORT --admin-state-up False
  3) neutron port-update PRIVATE_IP_PORT --admin-state-up True
  4) Ping of Floating IP does not work now. 
  5) neutron port-update FLOATING_IP_PORT --admin-state-up True
  6) Ping of Floating IP should start working now.

  Also, this results in the failure of tempest test:
  tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_update_instance_port_admin_state

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


Follow ups