Floating ips not available to instances after upgrade

[Andrew Glen-Young]

I have recently upgraded my Openstack installation from the version packaged in Oneiric to the one packaged in Precise.
After the installation, no floating ip addresses were available to instances.

When running "euca-allocate-address" returns a NoMoreFloatingIps exception.

Before the upgrade, I shutdown all running instances but I did not unallocate and unassign floating ip addresses. After the upgrade the floating_ips table in the Nova database had entries, but clearly these entries where seen as reserved by Nova. It seems as though the database migrations do not handle this case.

Workaround:

I needed to run the following SQL query to free up the floating ip addresses for allocation to instances:

sql> UPDATE floating_ips SET deleted_at = NULL, fixed_ip_id = NULL, project_id = NULL, host = NULL where floating_ips.deleted = 0 AND floating_ips.auto_assigned = 0 and host is NULL;

[Mark McLoughlin (markmc)]

> Before the upgrade, I shutdown all running instances but I did not unallocate and unassign floating ip addresses.

Hmm, why would you expect the upgrade to automatically unallocate floating IPs? i.e. when you shutdown an instance, the floating IP is unassigned but not unallocated

Marking as Invalid, but do re-open if I misunderstood

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dave Walker (davewalker)]

@Andrew, can you expand on the expected behaviour and what you believe the issue might be?

Is it that the FloatingIp's became 'lost' and were not seemingly associated to users?

Thanks.

[Launchpad Janitor (janitor)]

[Expired for nova (Ubuntu) because there has been no activity for 60 days.]