Comment 5 for bug 1455451

There is nothing to do with Nova:
Here is valid schenario code for 6.0: https://github.com/stackforge/fuel-ostf/blob/stable/6.0/fuel_health/nmanager.py#L546
There is attempt to create nano flavor with random id: https://github.com/stackforge/fuel-ostf/blob/stable/6.0/fuel_health/nmanager.py#L275

From nova-api.log:
2015-05-15T09:11:02.572783+00:00 info: 10.108.7.2 "GET /v2/9a32c8806842480196ac94f2d5f70cc8/os-networks HTTP/1.1" status: 200 len: 1491 time: 0.0614278
2015-05-15T09:11:03.690632+00:00 debug: Action: 'create', calling method: <bound method FlavorManageController._create of <nova.api.openstack.compute.contrib.flavormanage.FlavorManageController object at 0x37ff450>>, body: {"flavor": {"vcpus": 1, "disk": 1, "name": "ost1_test-flavor-nano236917154", "os-flavor-access:is_public": true, "rxtx_factor": 1.0, "OS-FLV-EXT-DATA:ephemeral": 0, "ram": 64, "id": 2200, "swap": 0}}
2015-05-15T09:11:03.702536+00:00 info: HTTP exception thrown: Flavor with ID 2200 already exists.
2015-05-15T09:11:03.703729+00:00 debug: Returning 409 to user: Flavor with ID 2200 already exists.
2015-05-15T09:11:03.706665+00:00 info: 10.108.7.2 "POST /v2/9a32c8806842480196ac94f2d5f70cc8/flavors HTTP/1.1" status: 409 len: 299 time: 0.0226591

As I can see, flavor creation fails during duplicate flavor.id. It's better to change random id logic for flavors to avoid such collisions in future