** Also affects: horizon (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1476417
Title:
FloatingIpManager in neutron.py
** Description changed:
The latest update to neutron (Version: 1:2014.1.5-0ubuntu1) caused the
following error every time an instance is launched:
Unable to connect to Neutron.
The logs didn't show any more errors.
I traced down that string to the servers_update_addresses method
** Changed in: horizon (Ubuntu)
Assignee: (unassigned) = Billy Olsen (billy-olsen)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1476417
Title:
FloatingIpManager in
Thanks TimS for the analysis. It looks like this backport included a
portion of a blueprint which was not fully backported (namely not
showing the Floating IPs when they are not available). Rather than
backporting the full blueprint, dropping the checks for the is_supported
and simply assuming it
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: horizon (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
This affects us as well. I did some investigation to see what was going on.
The new FloatingIpManager code was added in this commit:
https://github.com/openstack/horizon/commit/86a66283ccfe146a9743bb7db9433e1f2166b509.
It was added for bug https://bugs.launchpad.net/horizon/+bug/1349841
