VolumeAttachment cannot be updated
Bug #1269686 reported by
Liang Chen
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Pavlo Shchelokovskyy |
Bug Description
Our current logic for UpdateReplace is to create the replacement before the existing/backup resource is deleted. That works most of time as long as the replacement can be created while the backup resource still exists. But the UpdateReplace logic fails when it comes to a resource like VolumeAttachment where a volume cannot be attached again before it's detached from its previous mount point.
Changed in heat: | |
assignee: | nobody → Pavlo Shchelokovskyy (pshchelo) |
tags: | added: icehouse-rc-potential |
Changed in heat: | |
milestone: | none → icehouse-rc2 |
importance: | Undecided → Medium |
tags: | removed: icehouse-rc-potential |
Changed in heat: | |
milestone: | icehouse-rc2 → 2014.1 |
To post a comment you must log in.
Yeah, UpdateReplace seems to be not the right thing to do for that resource. Unfortunately it breaks most of the rules of a good resource model in order to avoid a circular dependency when a volume's availability zone is determined by doing Fn::GetAtt on the server.
The AWS docs are silent on the question of what VolumeAttachment does on update, but it seems like we should allow in-place updates of the properties.
(As an aside, this is one of those things that will probably never _really_ work, because it requires the server to unmount the volume before detaching it in order to be safe.)