bay-update failed with a 409 (Conflict) error

[hongbin]

Steps to reproduce:

$ magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 1
$ magnum bay-update k8sbay replace node_count=2
$ magnum bay-show k8sbay
....
| status_reason | resources.kube_masters: resources[0]: Conflict: resources.kube_master: Port 971a0cd5-9d5f-4da3-989d-d4e8c8a1a2db is still in use. (HTTP 409) (Request-ID: req-398c4042-a636-471d-9c7c-d8184be93ca3) |
....

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/233319
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=23ee8f5711b642617e739c963eee3aeec460e012
Submitter: Jenkins
Branch: master

commit 23ee8f5711b642617e739c963eee3aeec460e012
Author: Hongbin Lu <email address hidden>
Date: Fri Oct 9 21:55:27 2015 -0400

    Fix a 409 failure on bay-update

    The error is caused by change of user_token on bay-update. In
    particular, when a bay is created, magnum pass user token to heat
    as a parameter. Heat in term pass the token to each bay node via
    user_data. When a bay is scaled up/down, another token is generated
    and passed to heat, which changes the user_data of each bay nodes.
    As a result, heat have to replace all the bay nodes to update the
    user_data, which cause the error.

    Change-Id: If3c3a0d435893d4fa4ed96f7ffd3c414200770f8
    Closes-Bug: #1504689