yahoo-eng-team team mailing list archive

[OpenStack Infra <1645683@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/404233
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=c1873ea4d9dbe907c3316c24b03db0eb9ea6f694
Submitter: Jenkins
Branch:    master

commit c1873ea4d9dbe907c3316c24b03db0eb9ea6f694
Author: Rob Cresswell <robert.cresswell@xxxxxxxxxxx>
Date:   Tue Nov 29 14:08:09 2016 +0000

    Update floating IP tables instance URL check
    
    A port can be given a device owner of 'compute:nova' and associated with
    a floating IP; which will fail the current check in the floating IPs
    table to attempt to resolve an instance details URL.
    
    This patch updates the condition to actually check for the required variable.
    
    Change-Id: Ic5f78525ba41d47c1a548aeab73933f962343ebd
    Closes-bug:  1645683


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1645683

Title:
  NoReverseMatch at /project/access_and_security/

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  After associating a Floating IP via Horizon, the Access and Security
  page produces the following error:

  Reverse for 'detail' with arguments '(u'',)' and keyword arguments
  '{}' not found. 1 pattern(s) tried:
  [u'project/instances/(?P<instance_id>[^/]+)/$']

  Complete paste: http://paste.openstack.org/show/590655/

  Any attempt to reload the page produces the same error.

  This appears to be caused by an incorrect assumption that a port
  associated with a Floating IP will always belong to an instance.

  This is with a fresh pull of devstack and horizon as of 28/11/2016.

  Steps to recreate:

  This assumes a devstack with the default public/private neutron networks configured. local.conf should contain:
  http://paste.openstack.org/show/590787/

  1. On the CLI, create a port on the private network with device_owner             
     "compute:nova":

      $ neutron port-create private --device_owner compute:nova

  2. In Horizon, go to Compute > Access & Security. Allocate a Floating IP 
     from the Public pool.

  3. Associate the Floating IP with the port created in step 1.

  4. When the page reloads, you should see the error.

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