Network name parameter while creating a instance using nova boot command
Bug #1569840 reported by
Shashwat Srivastava
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=
Changed in python-novaclient: | |
assignee: | nobody → gundarapu kalyan reddy (gundarapu-reddy) |
Changed in python-novaclient: | |
status: | Incomplete → Invalid |
To post a comment you must log in.
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?