Troubleshooting
Problem
Heat stack updates to a VM may fail if the heat stack attempts to change an existing object by removing the object then adding it back to the VM. The heat stack update will fail as the object name cannot be reused
Symptom
Heat engine log may report an error that the object attempting to update via a delete/add
NeutronError:Port could not be found would be returned if attempting to update the port for a vm via a heat stack update by deleting the existing port, then adding the port with the same name..
Cause
Heat does not support the ruese of object names (deleted then recreated).
Environment
ICM 4.3
Diagnosing The Problem
heat template attempts to delete then re-add the same object name
Resolving The Problem
There are 2 options:
1. Run 2 heat updates...
a) The first update deletes the object,
b) Run a second update (at least 1 hour later) to recreate the object
or
2. create the new object with a new name.
resources:
VM1:
properties:
flavor: m1.medium
image: RHEL72_IMG
networks:
-
port:
get_resource: VM1_NIC2
type: "OS::Nova::Server"
VM1_NIC2:
properties:
fixed_ips:
-
ip_address: "some address"
mac_address: "some address"
network: "New Network"
type: "OS::Neutron::Port"
[{"Product":{"code":"SST55W","label":"IBM Cloud Manager with OpenStack"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.3","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
nas8N1022332