[Bug 1476417] Re: [SRU] FloatingIpManager in neutron.py missing is_supported method

[James Page]

I've tested and uploaded this fix to trusty proposed for the SRU team to
review - as soon as I have IRC access I'll go chase as well.

** Tags added: regression-update

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1476417

Title:
  [SRU] FloatingIpManager in neutron.py  missing is_supported method

Status in horizon package in Ubuntu:
  Invalid
Status in horizon source package in Trusty:
  Triaged

Bug description:
  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 in
  openstack-dashboard/api/neutron.py. I had to add a printout for the exception
  string to show where the exception happened:
  The modified error message now shows:
  Unable to connect to Neutron.'FloatingIpManager' object has no attribute
  'is_supported'

  It turned out that the latest neutron ubuntu package doesn't have the
  correct file update. A check is done on the fips.is_supported(),
  however the method itself is not implemented.

  The neutron.py on openstack's icehouse repository has the method implemented
  http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/api/neutron.py

  But the source code of the latest ubuntu package doesn't have the method
  http://archive.ubuntu.com/ubuntu/pool/main/h/horizon/horizon_2014.1.5.orig.tar.gz

  --------------------------------------------------------------------------
  [Impact] 

   * Unable to display floating IP information when using the horizon
  UI.

  [Test Case]

   1. Install a horizon and OpenStack.
     - bzr branch lp:openstack-charm-testing
     - cd openstack-charm-testing
     - juju-deployer -c default.yaml -v -d trusy-icehouse
   2. Launch an instance
   3. Observe the "Unable to connect to Neutron." message in the error notification bubble.
   
  [Regression Potential] 

   * None. 
   * Should a regression occur, it would result in the "Unable to connect to
     Neutron." message being shown to the user. Unfortunately, specific the
     specific causes is not easy to discern (since the data is not readily
     stored in the logs, thus the user would think this wasn't fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1476417/+subscriptions