yahoo-eng-team team mailing list archive

[Muhammad Farooq <1692831@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi,

My OpenStack liberty environment deployed with packstack.This is an old
deployment like a year before everything was working fine, but currently
we have issue relevant to Floating IP attachement.As we attach floating
IP to an private network interface of VM.

Attachement of Floating IP address

    Floating IP status shows down.
    No entry on qrouter-Namespace of that floating IP.
    No Iptables rules of SNAT and DNAT in that qrouter-Namespace.

As I attach secondary private NIC to same VM and then associate another
Floating IP to new Private NIC without removing old Private NIC and
Floating IP.

    Both Floating IP Status changes to Active state.
    Both Floating IP address entry in qrouter-Namespace.
    Both Floating IP rules are in place of SNAT and DNAT in qrouter-Namespace.

Detachment Of Floating IP

As I detach one Floating IP from VM.

    Still detached floating IP status shows "active".
    Still detached Floating IP address entry exists in qrouter-namespace.
    Still detached SNAT and DNAT rules exists in qrouter-namespace.
    Still VM is accessable from detached Floating IP address.

When detach Both Floating IP Addresses

    Both Floating IP status changes to "down".
    Both Floating IP entry removed form qrouter-namespace.
    SNAT and DNAT rules removed from qrouter-namespace.

Does anyone can suggest where issue can be?I don't see any error or
warning in my logs.

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

Title:
  Floaing IP wiered behaviour

Status in neutron:
  New

Bug description:
  Hi,

  My OpenStack liberty environment deployed with packstack.This is an
  old deployment like a year before everything was working fine, but
  currently we have issue relevant to Floating IP attachement.As we
  attach floating IP to an private network interface of VM.

  Attachement of Floating IP address

      Floating IP status shows down.
      No entry on qrouter-Namespace of that floating IP.
      No Iptables rules of SNAT and DNAT in that qrouter-Namespace.

  As I attach secondary private NIC to same VM and then associate
  another Floating IP to new Private NIC without removing old Private
  NIC and Floating IP.

      Both Floating IP Status changes to Active state.
      Both Floating IP address entry in qrouter-Namespace.
      Both Floating IP rules are in place of SNAT and DNAT in qrouter-Namespace.

  Detachment Of Floating IP

  As I detach one Floating IP from VM.

      Still detached floating IP status shows "active".
      Still detached Floating IP address entry exists in qrouter-namespace.
      Still detached SNAT and DNAT rules exists in qrouter-namespace.
      Still VM is accessable from detached Floating IP address.

  When detach Both Floating IP Addresses

      Both Floating IP status changes to "down".
      Both Floating IP entry removed form qrouter-namespace.
      SNAT and DNAT rules removed from qrouter-namespace.

  Does anyone can suggest where issue can be?I don't see any error or
  warning in my logs.

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