Floaing IP wiered behaviour

Bug #1692831 reported by Muhammad Farooq on 2017-05-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description


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.

Can you reproduce the issue?

tags: added: l3-ipam-dhcp
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers