Changing a Port's MAC address doesn't take a lock on the Node

[aeva black]

Changing Port data should be handled the same way as changing Node data -- it should require a TaskManager lock (of the related Node), particularly if changing the Port's address field. This may also need to trigger specific driver actions, such as updating Neutron.

[Rohan (kanaderohan)]

Hey Digambar, are you still working on this, any updates?

[OpenStack Infra (hudson-openstack)]

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

[Digambar (digambarpatil15)]

Guys this bug is fixed but not able to commit the code due to gerrit issues.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/77623
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=d4f77b66ea766aa17f7cdbf8a4bcc6188998e33b
Submitter: Jenkins
Branch: master

commit d4f77b66ea766aa17f7cdbf8a4bcc6188998e33b
Author: Yuriy Zveryanskyy <email address hidden>
Date: Mon Mar 3 10:29:18 2014 +0200

    Add TaskManager lock on change port data

    Updating port data may require driver actions on the related node
    (if address changed for example). New method 'update_port' added
    to conductor manager and rpcapi.

    Partial-Bug: #1276393
    Related-Bug: #1236714
    Change-Id: I1f817a8b3c80630f40fd36c82e533d5358225150