yahoo-eng-team team mailing list archive

[Akihiro Motoki <1760832@xxxxxxxxxxxxxxxxxx>]

According to the reply in #3, the original bug report cannot be
addressed in CLI output even if we have a new setting per the bug
report. Considering this situation, I mark this as Invalid as neutron
liaison.

** Changed in: horizon
       Status: New => Invalid

-- 
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/1760832

Title:
  Shows external networks even if they are not shared

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Hi,

  I think, that this case might be somehow related to the one, described
  here: https://bugs.launchpad.net/horizon/+bug/1384975

  Steps to reproduce are the same:
  Login as tenant "A", create couple of networks:
  - Network 1, external network shared.
  - Network 2, external network (not-shared).

  Now Login as tenant "B", go to project and network listing page:
  - We see as well as shared external networks, as not shared ones. 
  - Not shared networks are displayed without subnets, and they are not available for instance/port creation

  I was able to hide not shared external networks (while shared ones are
  still present) with setting include_external=False here
  https://github.com/openstack/horizon/blob/9ca9b5cd81db29bddf6dbcc5fc535009a9ec63b0/openstack_dashboard/dashboards/project/networks/views.py#L55

  So this setting makes expected changes and behaviour. Probably, there
  is a reason, why this was hardcoded, and current behaviour is required
  for some features. But probably it's worth to consider to move this to
  the settings section?

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