Description of problem: It's possible to create a network with a wrong/non-exist project_id Version-Release number of selected component (if applicable): Folsom on RHEL6.4, FlatDHCPManager Steps to Reproduce: 1. Create a network with non-exist project id $ nova-manage network create --label=net08_36 --fixed_range_v4=192.168.8.0/24 --bridge=br100 --project_id=a75203 --num_networks=1 Actual results: Network creation passes successfully. $ mysql -u root nova -e "select id,cidr,netmask,bridge,gateway,broadcast,dhcp_start,label,project_id,bridge_interface from networks where label like 'net08_36';" +----+----------------+---------------+--------+-------------+---------------+-------------+----------+------------+------------------+ | id | cidr | netmask | bridge | gateway | broadcast | dhcp_start | label | project_id | bridge_interface | +----+----------------+---------------+--------+-------------+---------------+-------------+----------+------------+------------------+ | 10 | 192.168.8.0/24 | 255.255.255.0 | br100 | 192.168.8.1 | 192.168.8.255 | 192.168.8.2 | net08_36 | a75203 | eth2 | +----+----------------+---------------+--------+-------------+---------------+-------------+----------+------------+------------------+ $ keystone tenant-list +----------------------------------+----------+---------+ | id | name | enabled | +----------------------------------+----------+---------+ | 4d59ca3ff6114b219dead3cf818318a5 | rami | True | | 5e5ffdaf50a94a028ab6b76aacf26f3f | services | True | | a75203c3c0234ea0b3c16565e52af01e | vaknin | True | | cc85e25edce4476bbe1aa29cdb16b2ba | admin | True | +----------------------------------+----------+---------+ Expected results: Operation should fail with a proper error message/exception.
nova-manage is a very low level admin tool. It does very little validation and instead just assumes valid input from the admin in many cases. So, I don't think this is something we need to fix.