Comment 4 for bug 1276371

Reviewed: https://review.openstack.org/71315
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=b2259b352fd1e00a269b8275afa8093223598235
Submitter: Jenkins
Branch: stable/havana

commit b2259b352fd1e00a269b8275afa8093223598235
Author: Nicolas Simonds <email address hidden>
Date: Tue Feb 4 15:15:29 2014 -0800

    Don't copy the flavorid when updating flavors

    The Nova API makes the implicit assumption that flavorids are unique,
    so if one creates two flavors with the same flavorid, subsequent
    requests for flavor information can vary between "inaccurate" and
    "wildly f*cking inaccurate"

    From an end-user perspective, it makes it look like data such as
    flavor access settings get lost between edits (because the API pulls
    the access list from the wrong flavor)

    Let the API assign a new flavorid on changes. The comments around
    the handler code imply that is the desired behaviour, anyhow.

    Cherry-picked from 4100a1cbc24184b58d5049dfb601b18e29e6107d

    Change-Id: I5403202396a7b136b0ae8637d6aae1cf32550747
    Closes-Bug: 1276371