← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1530293] [NEW] demo tenant can use admin's unshared private network to create a vm successful

 

Public bug reported:

Hi, all
i encounter a problem as follows:

Environment:
neutron version is the latest version downloading from github(m), same with other openstack components.
operating system: ubuntu 14.04

procedure:
when i test the isolation of the different tenants under the private network like 192.168.50.0/24.
step 1: create a private network like 192.168.50.0/24 under admin tenant, and the network is not shared.
step 2: create a vm1 by using admin tenant together with the private network which created in step 1.
step 3: create a vm2 by using demo tenant together with the private network which created in step 1.

ps: i create vm through restclient.

Expected output
vm1 can create successful while vm2 will destroy with an error.

Actual output
vm1 and vm2 both create successful.

actually, demo could not use the private network which created by admin,
so, when demo tenant create a vm with the network, the vm should be
destroyed, but  how that above result come out, does anyone have ever
encountered such situation. Thank you.

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

- Environment: 
+ Hi, all
+ i encounter a problem as follows:
+ 
+ Environment:
  neutron version is the latest version downloading from github(m), same with other openstack components.
  operating system: ubuntu 14.04
  
  procedure:
- when i test the isolation of the different tenants under the private network like 192.168.50.0/24. 
+ when i test the isolation of the different tenants under the private network like 192.168.50.0/24.
  step 1: create a private network like 192.168.50.0/24 under admin tenant, and the network is not shared.
  step 2: create a vm1 by using admin tenant together with the private network which created in step 1.
  step 3: create a vm2 by using demo tenant together with the private network which created in step 1.
  
  ps: i create vm through restclient.
  
  Expected output
  vm1 can create successful while vm2 will destroy with an error.
  
  Actual output
  vm1 and vm2 both create successful.
  
  actually, demo could not use the private network which created by admin,
  so, when demo tenant create a vm with the network, the vm should be
  destroyed, but  how that above result come out, does anyone have ever
  encountered such situation. Thank you.

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

Title:
  demo tenant can use admin's unshared private network to create a vm
  successful

Status in neutron:
  New

Bug description:
  Hi, all
  i encounter a problem as follows:

  Environment:
  neutron version is the latest version downloading from github(m), same with other openstack components.
  operating system: ubuntu 14.04

  procedure:
  when i test the isolation of the different tenants under the private network like 192.168.50.0/24.
  step 1: create a private network like 192.168.50.0/24 under admin tenant, and the network is not shared.
  step 2: create a vm1 by using admin tenant together with the private network which created in step 1.
  step 3: create a vm2 by using demo tenant together with the private network which created in step 1.

  ps: i create vm through restclient.

  Expected output
  vm1 can create successful while vm2 will destroy with an error.

  Actual output
  vm1 and vm2 both create successful.

  actually, demo could not use the private network which created by
  admin, so, when demo tenant create a vm with the network, the vm
  should be destroyed, but  how that above result come out, does anyone
  have ever encountered such situation. Thank you.

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


Follow ups