yahoo-eng-team team mailing list archive

[OpenStack Infra <1494358@xxxxxxxxxxxxxxxxxx>]

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

commit 42ae3dbf058c7a02dbb9d61a8e924ec1e06af3c3
Author: eric <eric.peterson1@xxxxxxxxxxx>
Date:   Thu Sep 10 09:26:13 2015 -0600

    Topology filter out non tenant ports
    
    This change filters out ports presented to the topology view which
    are connected to networks which are not visible to the tenant.  Such
    ports can be present when an admin creates an instance and ties and instance
    into two networks.
    
    Change-Id: Ib0e7ea38b42b580a65455c344f100e5aad67954e
    Closes-bug: #1494358


** 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/1494358

Title:
  topology view does not support multi-networked instances where 1
  network is outside of tenant

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  We have instances which have multiple ports, one port goes into the
  tenant network - and the other port goes into a network which is not
  visible to the tenant.  ( This other network is used as a control
  plane for lbaas management)

  With these instances, they only *sometimes* show up in the topology
  view.  I believe this is due to the order of the ports on the
  instance.  If this first port listed is attached to a tenant network,
  it shows up in topology.... if the first port is attached to that
  outside network - then the instance will not show up.

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