Unable to create onmetal-io2

[jacripe]

A customer chat recently reported that they were unable to create onmetal-io2 flavor servers using rack-cli due to it stating the disk was 0 & requiring a block storage volume, which also appeared to be unsupported.

This issue appears to be specific to Windows as I was able to successfully create onmetal-io2 with the same image ID and without a block storage volume. It may also be related to their use of a custom network on a rackconnected environment.

Sample commands & output from customer:
rack servers instance create --name db_master --flavor-id onmetal-io2 --networks "RC-192-50,ServiceNet" --block-device "source-type=image,source-id=dc1a3708-b4d9-44db-98ae-f768f6218f27,volume-size=200,destination-type=local,delete-on-termination=false"

Invalid request due to incorrect syntax or missing required parameters.

---

rack servers instance create --name db_master --flavor-id onmetal-io2 --networks "RC-192-50,ServiceNet" --image-name "OnMetal - CentOS 7" --keypair amunger-rsa
error The flavor you've chosen has a disk size of 0, so an image can't be created on it directly. To boot with this flavor, creating a 100 GB volume and not deleting that volume when the server is deleted, run this command:
rack servers instance create --name db_master --flavor-id onmetal-io2 --block-device "source-type=image,source-id=dc1a3708-b4d9-44db-98ae-f768f6218f27,volume-size=100,destination-type=volume,delete-on-termination=false" For more information please run: rack servers instance create --help

[jrperritt]

Please have a look at rack servers instance --help. Of note from the help output:
--networks [optional] A comma-separated string of IDs of the networks to attach to this server. If not provided, a public and private network will be attached

We're working on providing more informative error messages. The master branch of this repo does provide the exact error that Rackspace provides if you provide the --log info flag to the command. In this case, the error coming back is:
{"badRequest": {"message": "Bad networks format: network uuid is not in proper format (RC-192-50)", "code": 400}}