OpenStack Compute (nova)

on nova-network's node reboot floating-ips do not get redefined by iputils

Bug #965030 reported by Giuseppe Civitella
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Medium
Unassigned

Bug Description

Already existing floating ips are lost on nova-network's node reboot.
On restart, nova-network does not check if a floating ip actually exists on its node, so, if a system's reboot happened, at the service restart floating ips do not get recreated. I have to disassociate and then reassociate all of them to have them redefined by iptutils.
This does not allow me to setup a quick way to fail over a nova-network service.

Thanks

Giuseppe Civitella (gcivitella)
summary: - on nova-network's node reboot floating-ips do not get recreated and
- associated
+ on nova-network's node reboot floating-ips do not get redefined by
+ iputils
Revision history for this message
Giuseppe Civitella (gcivitella) wrote :

I'm running Essex4.

Revision history for this message
Chuck Short (zulcss) wrote :

 I have not able to reproduce this, can you provide the steps to reproduce this?

thanks
chuck

Changed in nova:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Thierry Carrez (ttx) wrote :

We cannot solve the issue you reported without more information. Could you please provide the requested information ?

Revision history for this message
Thierry Carrez (ttx) wrote :

This bug lacks the necessary information to effectively reproduce and fix it, therefore it has been closed. Feel free to reopen the bug by providing the requested information and set the bug status back to ''New''.

Changed in nova:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.