Network name parameter while creating a instance using nova boot command

Bug #1569840 reported by Shashwat Srivastava
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-novaclient
Invalid
Undecided
Unassigned

Bug Description

While creating a new instance in a setup where you have multiple networks. System gives error
"ERROR (Conflict): Multiple possible networks found, use a Network ID to be more specific. "

In this case if user remembers the network name but not the id, then he has to run 1 more command (neutron net-list) to get the network id.

I think we should add the support to include network name to be given with the nova boot command like
nova boot --nic net-name=TestNetwork

Changed in python-novaclient:
assignee: nobody → gundarapu kalyan reddy (gundarapu-reddy)
Revision history for this message
melanie witt (melwitt) wrote :

Usually this error occurs only if the given name is ambiguous. If multiple network names match the specified name, you will get the conflict error. It should work if the specified name can uniquely identify one network.

Can you give an example of the names of the multiple networks you have and the net-name you requested?

Changed in python-novaclient:
status: New → Incomplete
Revision history for this message
Shashwat Srivastava (shashwat-srivastava) wrote :

I am talking about case when you run this command to boot a vm.

nova boot --image cirros-0.3.4-x86_64-uec --flavor m1.small test1

and you have 2 or more networks.
Then system throws a error as stated in bug description.

And then to run the command we have to add the parameter "--nic net-id=" to attach the vm to a specific network.
I suggested in place of --nic net-id= can't we have "--nic net-name" variable where putting the name of the network will be easy as compared to getting the id of the network after running another command.

Revision history for this message
gundarapu kalyan reddy (gundarapu-reddy) wrote :

I think we can use network name when we are booting an instance. But instead of nova boot we have to go with openstack server create command in which you can pass network name (--nic net-id=private). And this support should be developed for nova boot command also. I verified on liberty version. Please correct me if i am wrong.

Revision history for this message
melanie witt (melwitt) wrote :

I think you can specify a network name with nova boot like this example:

  nova boot --image cirros-0.3.4-x86_64-uec --flavor m1.nano --nic net-name=private --poll hello

Revision history for this message
melanie witt (melwitt) wrote :

Here is the documentation, by the way:

http://docs.openstack.org/cli-reference/nova.html#nova-boot

which can also be seen by running 'nova help boot'

Revision history for this message
gundarapu kalyan reddy (gundarapu-reddy) wrote :

Thanks for that. Just now verified in mitaka version it is working fine using --nic net-name=network-name. Earlier we tried in liberty nova help boot shows but it didn't work.

Changed in python-novaclient:
assignee: gundarapu kalyan reddy (gundarapu-reddy) → nobody
Revision history for this message
Shashwat Srivastava (shashwat-srivastava) wrote :

I too raised the bug as I was working on Liberty release.

If it there in Mitaka release its well and good.

Changed in python-novaclient:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.