yahoo-eng-team team mailing list archive

[Kevin Benton <1607534@xxxxxxxxxxxxxxxxxx>]

This is the behavior in stable/liberty as well:
http://paste.openstack.org/show/543866/

Can you provide a branch that you know this works on?

** Changed in: neutron
       Status: Confirmed => Invalid

** Changed in: neutron
       Status: Invalid => Incomplete

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1607534

Title:
  Subnets not visible for admin tenant external network for non-admin
  user

Status in neutron:
  Incomplete

Bug description:
  External network subnet is not visible to non-admin users.

  External network is created under "admin" tenant.

  As an admin user,

  # neutron net-list

  | 6190b806-a05f-4394-ac2e-b646d307b8a7 | external
  | 80a88580-9986-47a3-bd3f-68e43b7edf1c 169.54.91.160/27 |

  However as a project member user,

  # neutron net-list

  | 6190b806-a05f-4394-ac2e-b646d307b8a7 | external
  | 80a88580-9986-47a3-bd3f-68e43b7edf1c |

  This is breaking the scripts that relies on subnet information from net-list output.
  Is this behavior intended?

  Also, as per the defect,

  https://github.com/openstack/neutron/pull/36/commits/391c2327c3b9de0e2b9875bab8d6f6909fa0983a

  only external "Shared" network subnets are visible.

  However if an external network is made "Shared", users can launch VMs
  directly on external network (rather than just floating ip and gateway
  ips to routers).

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