Here's the resource:
"instance": {
"Type": "OS::Nova::Server",
"Properties": {
"name": {"Fn::Join" : ["-", [ {"Ref" : "AWS::StackName"}, "cloudview01"]]},
"availability_zone": "az1",
"image": { "Ref" : "PSOStandardUbuntuLinuxImageId" },
"flavor": "standard.medium",
"key_name": { "Ref" : "StackProvisioningSSHKeyName" },
"networks": [{"port": { "Ref" : "port_floating" }}],
"metadata": {"tags": {"Fn::Join" : ["", ["Role_role::infra_services::cloudview,Stack_", {"Ref" : "AWS::StackName"}, ",Provisioner_Auto"]]}},
"flavor_update_policy" : "REPLACE"
}
}
The update changed the instance's flavor from standard.small to standard.mendium.
The final failing Heat event:
"logical_resource_id": "instance",
"resource_status_reason": "Conflict: Port 3f1e9c8e-ac1c-4d78-95b9-b10301a2690c is still in use. (HTTP 409) (Request-ID: req-46f28a5c-d795-4bb7-8d2c-8edc30ca6256)",
"resource_status": "CREATE_FAILED"
I believe this bug is related to, but possibly distinct from this defect: https://bugs.launchpad.net/heat/+bug/1280151
It's distinct because it affects "OS::Nova::Server" resources instead of "ec2::instance" resources. In addition, in my update I am trying to change the flavor, not add a new port.
I have worked with Nick on this and asked him to report this. It seems that it is a legitimate problem and likely just a cargo-culted copy of bug 1280151.