yahoo-eng-team team mailing list archive

[Shoham Peller <shoham.peller@xxxxxxxxxxxxxxx>]

Public bug reported:

The documentation says here:
http://developer.openstack.org/api-ref-compute-v2.1.html#createServer
That if you don't specify networks to attach the new server to:
"By default, the API provisions the server instance with all isolated networks for the tenant"

But when actually trying to create a server in a tenant that has a couple of networks, nova raises error:
"Multiple possible networks found, use a Network ID to be more specific."

The exact code I've run:
$ nova net-list
+--------------------------------------+------------+------+
| ID                                   | Label      | CIDR |
+--------------------------------------+------------+------+
| d3b269ff-d9ef-4f00-926a-dcefa5583f57 | sharednet1 | None |
| b9eb2d83-77ff-4569-84f7-118646fc9963 | a          | None |
+--------------------------------------+------------+------+
$ curl -X POST http://127.0.0.1:8774/v2/6884b8e596304eca8600ef0c4c0b0d5b/os-volumes_boot -H"$TOKEN" -H"content-type:application/json" -d '{"server": {"name": "a", "imageRef": "", "block_device_mapping_v2": [{"source_type": "volume", "delete_on_termination": false, "boot_index": 0, "uuid": "0a7f5ffb-d7b5-4791-a6ac-8be8994136cf", "destination_type": "volume"}], "flavorRef": "1", "max_count": 1, "min_count": 1}}'
{"conflictingRequest": {"message": "Multiple possible networks found, use a Network ID to be more specific.", "code": 409}}

nova version is 2.30.1

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1548815

Title:
  Documentation mistaken when creating a server without specifying
  networks

Status in OpenStack Compute (nova):
  New

Bug description:
  The documentation says here:
  http://developer.openstack.org/api-ref-compute-v2.1.html#createServer
  That if you don't specify networks to attach the new server to:
  "By default, the API provisions the server instance with all isolated networks for the tenant"

  But when actually trying to create a server in a tenant that has a couple of networks, nova raises error:
  "Multiple possible networks found, use a Network ID to be more specific."

  The exact code I've run:
  $ nova net-list
  +--------------------------------------+------------+------+
  | ID                                   | Label      | CIDR |
  +--------------------------------------+------------+------+
  | d3b269ff-d9ef-4f00-926a-dcefa5583f57 | sharednet1 | None |
  | b9eb2d83-77ff-4569-84f7-118646fc9963 | a          | None |
  +--------------------------------------+------------+------+
  $ curl -X POST http://127.0.0.1:8774/v2/6884b8e596304eca8600ef0c4c0b0d5b/os-volumes_boot -H"$TOKEN" -H"content-type:application/json" -d '{"server": {"name": "a", "imageRef": "", "block_device_mapping_v2": [{"source_type": "volume", "delete_on_termination": false, "boot_index": 0, "uuid": "0a7f5ffb-d7b5-4791-a6ac-8be8994136cf", "destination_type": "volume"}], "flavorRef": "1", "max_count": 1, "min_count": 1}}'
  {"conflictingRequest": {"message": "Multiple possible networks found, use a Network ID to be more specific.", "code": 409}}

  nova version is 2.30.1

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