Router set --route option does not work

[Richard Theis]

The router set --route option does not work.

$ openstack router set --route destination=10.10.10.0/24,gateway=10.10.10.1 foo
HttpException: Bad Request

Neutron error details:
RESP BODY: {"NeutronError": {"message": "Invalid input for routes. Reason: Validation of dictionary's keys failed. Expected keys: set(['nexthop', 'destination']) Provided keys: set([u'destination', u'gateway']).", "type": "HTTPBadRequest", "detail": ""}}

Fixing this bug must follow devref https://review.openstack.org/#/c/297718/ to ensure new values are appended.

Note: Unset support for this option is tracked under the following blueprint: https://blueprints.launchpad.net/python-openstackclient/+spec/network-property-unset

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/301870

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/301870
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=a90c824e0407f931b5c45df53103b43aa564de12
Submitter: Jenkins
Branch: master

commit a90c824e0407f931b5c45df53103b43aa564de12
Author: Richard Theis <email address hidden>
Date: Tue Apr 5 13:27:42 2016 -0500

    Fix router set --route option

    Fix the "--route" option on the "os router set" command. The
    option did not properly format the new routes to set which
    resulted in a "HttpException: Bad Request" error. In addition,
    the output for routes was fixed to improve readability and to
    align with the "--route" option on the "os router set" command.

    Change-Id: I9c514153ec201e2feae32be6dd281771e3298b9c
    Closes-Bug: #1564460

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/python-openstackclient 2.5.0 release.