Position of metadata on cinder create call influences cmd parsing

[John Griffith]

Trying to create a volume with metadata doing like:
    cinder create --metadata mykey=myval 1

Fails for "error: too few arguments"

--metadata arg needs to be followed up with another arg in order for the delimiting to work correctly:
    cinder create --metadata mykey=myval --name foo 1

[Eric Harney (eharney)]

Workaround:

cinder create --metadata mykey=myval -- 1

[rajiv (rajiv-kumar)]

Hi Ivan

Have you started working on this bug. If you have not started, i want to work on this.

[rajiv (rajiv-kumar)]

Patch has been submitted

To view, visit https://review.openstack.org/156499

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/156499
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=57c9bf17b3ed9c5a2818163085704175f9324527
Submitter: Jenkins
Branch: master

commit 57c9bf17b3ed9c5a2818163085704175f9324527
Author: rajiv <email address hidden>
Date: Tue Feb 17 13:45:34 2015 +0530

    cinderclient accepts arguments after metadata without -- separator

    Added a function, which parse arguments and add -- separator
    after metadata subcommand

    Change-Id: I907eb89209d549dcdad361d88352491110eaadb9
    Closes-Bug: #1379486