Floating IP Attachement wiered Behaviour

asked 2017-05-23 02:52:02 -0500

loosy gravatar image

updated 2017-05-23 02:56:38 -0500

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

  1. Floating IP status shows down.
  2. No entry on qrouter-Namespace of that floating IP.
  3. 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.

  1. Both Floating IP Status changes to Active state.
  2. Both Floating IP address entry in qrouter-Namespace.
  3. 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.

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

When detach Both Floating IP Addresses

  1. Both Floating IP status changes to "down".
  2. Both Floating IP entry removed form qrouter-namespace.
  3. 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.

edit retag flag offensive close merge delete

Comments

have you checked the api logs of neutron as well?

Beny gravatar imageBeny ( 2017-05-23 07:38:19 -0500 )edit

i have checked api,server and particular network namespace logs.Neither i received Error nor warnings.

loosy gravatar imageloosy ( 2017-05-24 04:33:33 -0500 )edit