Brilliant. Ran it like this: nova --os-username demo --os-password demo --os-tenant-name demoProject boot --image aefa581f-47b0-4d46-8dbc-1a1f7f02dfa0 --flavor 2 --nic net-id=3de1e780-07d1-42af-89cc-0feaf1ece6e9 server-01
And it spawned! Into an ERROR state, perhaps, but it spawned! I'm telling you, it's like whack-a-mole with thing. I'll kick off a new email with the new problem if I can't fix it soon. Thanks for your help though. On Mon, Feb 11, 2013 at 12:40 AM, Aaron Rosen <aro...@nicira.com> wrote: > Hi Greg, > > I checked out why this can happen and I think the reason you are getting > this is because you are trying to create a vm as an admin user on a network > that you are not the owner. > > > https://github.com/openstack/nova/blob/master/nova/network/quantumv2/api.py#L95 > > Thanks, > > Aaron > > > On Sun, Feb 10, 2013 at 4:28 PM, Greg Chavez <greg.cha...@gmail.com>wrote: > >> This has me utterly befuddled. All I'm trying to do is bring up a Cirros >> VM on my 3-node controller+network+compute Folsom setup. So nova is >> configured on the controller to use quantum: >> >> network_api_class = nova.network.quantumv2.api.API >> quantum_admin_username = quantum >> quantum_admin_password = quantum >> quantum_admin_auth_url = http://192.168.241.100:35357/v2.0 >> quantum_auth_strategy = keystone >> quantum_admin_tenant_name = service >> quantum_url = http://192.168.241.100:9696 >> >> 192.168.241.100 is the controller management port IP. >> >> I have the following network available: >> >> # quantum net-list | grep demo-net >> | 3de1e780-07d1-42af-89cc-0feaf1ece6e9 | demo-net | >> 7f54d28f-b87a-43f7-a15f-1c0d20569e2a | >> >> # quantum subnet-list | grep 7f54d28f >> | 7f54d28f-b87a-43f7-a15f-1c0d20569e2a | | 192.168.1.0/24 | >> {"start": "192.168.1.2", "end": "192.168.1.254"} | >> >> # quantum net-show 3de1e780-07d1-42af-89cc-0feaf1ece6e9 >> +---------------------------+--------------------------------------+ >> | Field | Value | >> +---------------------------+--------------------------------------+ >> | admin_state_up | True | >> | id | 3de1e780-07d1-42af-89cc-0feaf1ece6e9 | >> | name | demo-net | >> | provider:network_type | vlan | >> | provider:physical_network | physnet1 | >> | provider:segmentation_id | 2001 | >> | router:external | False | >> | shared | False | >> | status | ACTIVE | >> | subnets | 7f54d28f-b87a-43f7-a15f-1c0d20569e2a | >> | tenant_id | 6ea263cf12ce44e29d4d7baefacb9689 | >> +---------------------------+--------------------------------------+ >> >> # quantum router-port-list 37d3b2dd-ad19-435b-b4b9-3edbcd812f58 >> <..snip snip..> >> {"subnet_id": "7f54d28f-b87a-43f7-a15f-1c0d20569e2a", "ip_address": >> "192.168.1.1"} | >> {"subnet_id": "e45987aa-2f3a-45e7-b9c8-7499d8eb93e6", "ip_address": >> "10.21.166.2"} >> >> So far so good. From my perspective everything looks good. But when I >> try to boot a vm it fails: >> >> # nova boot --image aefa581f-47b0-4d46-8dbc-1a1f7f02dfa0 --flavor 2 --nic >> net-id=3de1e780-07d1-42af-89cc-0feaf1ece6e9 --key-name demo-key server-01 >> ERROR: The resource could not be found. (HTTP 404) (Request-ID: >> req-b0badcb3-244a-4e76-92b2-8bbabc645f3b) >> >> Looking in api.log I find this error: >> >> Caught error: Network 3de1e780-07d1-42af-89cc-0feaf1ece6e9 could not be >> found. >> >> WHAT! How is it not found? It clearly exists, unless net-id is expecting >> something else as its value. Argh. >> >> Thanks in advance. >> >> -- >> \*..+.- >> --Greg Chavez >> +//..;}; >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
