yahoo-eng-team team mailing list archive

[Roey Dekel <rdekel@xxxxxxxxxx>]

Public bug reported:

I tried to see if admin_state_up false blocks connection via floating ip
(it worked). Then I tried to reverse it and the connection stayed
blocks.

Reproduce:
1. boot an instance:
 174  nova boot instance1 --flavor 1 --image cirros-0.3.1 --nic net-id=`neutron net-list | grep netInt | cut -d" " -f2`
2. attach floating ip to it:
  175  neutron floatingip-create netExt193
  176  neutron port-list 
  177  neutron floatingip-associate 2b3459aa-2606-42b2-ab15-4df68733b4ad 4c4f6c98-a0ad-4f04-95ef-22aef0ebcbbc
3. verify communication:
  184  ping 10.35.178.3
4. turn admin_state_up false
  186  neutron port-update 4c4f6c98-a0ad-4f04-95ef-22aef0ebcbbc --admin-state-up false
5. verify stoped connection:
  187  ping 10.35.178.3
6. return admin state to up:
  188  neutron port-update 4c4f6c98-a0ad-4f04-95ef-22aef0ebcbbc --admin-state-up true
7. see that still there is no connection: 
  189  ping 10.35.178.3

** 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/1290054

Title:
  Returning associated port to floating IP from admin state up false to
  true doesn't unblocks connection via floating ip

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I tried to see if admin_state_up false blocks connection via floating
  ip (it worked). Then I tried to reverse it and the connection stayed
  blocks.

  Reproduce:
  1. boot an instance:
   174  nova boot instance1 --flavor 1 --image cirros-0.3.1 --nic net-id=`neutron net-list | grep netInt | cut -d" " -f2`
  2. attach floating ip to it:
    175  neutron floatingip-create netExt193
    176  neutron port-list 
    177  neutron floatingip-associate 2b3459aa-2606-42b2-ab15-4df68733b4ad 4c4f6c98-a0ad-4f04-95ef-22aef0ebcbbc
  3. verify communication:
    184  ping 10.35.178.3
  4. turn admin_state_up false
    186  neutron port-update 4c4f6c98-a0ad-4f04-95ef-22aef0ebcbbc --admin-state-up false
  5. verify stoped connection:
    187  ping 10.35.178.3
  6. return admin state to up:
    188  neutron port-update 4c4f6c98-a0ad-4f04-95ef-22aef0ebcbbc --admin-state-up true
  7. see that still there is no connection: 
    189  ping 10.35.178.3

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