Server UpdateReplace with existing port resource fails first time

[Rabi Mishra]

A Server resource with reference to Port resource always fails during UpdateReplace. Subsequent update completes successfully.

server_port.yaml:

heat_template_version: 2013-05-23

parameters:
  image:
    type: string
    default: cirros-0.3.1-x86_64-uec
  flavor:
    type: string
    default: m1.nano
  key_name:
    type: string
    default: heat_key
  private_net:
    type: string
    default: private
  private_subnet:
    type: string
    default: private-subnet

resources:
  port1:
    type: OS::Neutron::Port
    properties:
      network: {get_param: private_net}
      fixed_ips:
      - subnet: {get_param: private_subnet}

  server1:
    type: OS::Nova::Server
    properties:
      image: {get_param: image}
      flavor: {get_param: flavor}
      flavor_update_policy: REPLACE
      key_name: {get_param: key_name}
      networks:
      - port: {get_resource: port1}

#heat stack-create test_stack -f server_port.yaml
#heat stack-update test_stack -P server_port.yaml -P flavor=m1.tiny

| resource_status | CREATE_FAILED |
| resource_status_reason | Conflict: Port 6c5b73a4-6155-4885-9781-9c0873114006 is still in use. (HTTP 409) (Request-ID: req-7a03ff9c-8c61-44c9-b335-2ecfaa6d3781) |

If you update again it goes through.

[Sergey Kraynev (skraynev)]

Probably we may handle this case in this series https://review.openstack.org/#/c/220502/

[Steven Hardy (shardy)]

Can this be marked as fix committed now that https://review.openstack.org/#/c/220502/ has merged?

Or, should this be marked as a duplicate of bug #1455100?