Revision history [back]

click to hide/show revision 1
initial version

Heat stack falling with volume in use

We have a heat stack up and running , after extending the disk size I have run the heat stack update but its falled with volume is in use must be available,

When I check heat engine logs, instead of update its trying to delete the instance for recreating so volume is in use deletion is failing. Actually it should update instead of deleting.

When I run stack with dry run , there is replacement happened on network level when i check neutron port update for 1 vm updated on date is different compare to another vms, I am thinking someone might have updated from command line level. So is because of entire stack resources getting creating instead of update? If someone update the port with same id will it also fail stack.

Advanced thanks for the clarification

Heat stack falling with volume in use

We have a heat stack up and running , after extending the disk size I have run the heat stack update but its falled with volume is in use must be available,

When I check heat engine logs, instead of update its trying to delete the instance for recreating so volume is in use deletion is failing. Actually it should update instead of deleting.

When I run stack with dry run , there is replacement happened on network level when i check neutron port update for 1 vm updated on date is different compare to another vms, I am thinking someone might have updated from command line level. So is because of entire stack resources getting creating instead of update? If someone update the port with same id will it also fail stack.

Advanced Advance thanks for the clarification clarification

Heat stack falling with volume in use

We have a heat stack up and running , after extending the disk size I have run the heat stack update but its falled with volume is in use must be available,

When I check heat engine logs, instead of update its trying to delete the instance for recreating so volume is in use deletion is failing. Actually it should update instead of deleting.

When I run stack with dry run , there is replacement happened on network level when i check neutron port update for 1 vm updated on date is different compare to another vms, I am thinking someone might have updated from command line level. So is because of entire stack resources getting creating instead of update? If someone update the port with same id will it also fail stack.

Advance thanks for the clarification