Update git submodules
* Update heat from branch 'master' - Merge "Make tags handling more robust" - Make tags handling more robust Avoid loading the tags from the DB and then re-saving every time the stack is stored when the stack has tags. Avoid attempting to lazy-load the tags from the DB multiple times when there are no tags. Avoid lazy-loading the existing tags on an update when we intend to overwrite them anyway. Avoid writing the same set of tags multiple times. e.g. in a legacy update, previously we rewrote the current set of tags when changing the state to IN_PROGRESS, then wrote the new set of tags regardless of whether they had changed, then wrote the new set of tags again when the update completed. In a convergence update we also did three writes but in a different order, so that the new tags were written every time. With this change we write the new set of tags only once. This could also have prevented stacks with tags from being updated from legacy to convergence, because the (unchanged) tag list would get rewritten from inside a DB transaction. This is not expected so the stack_tags_set() API does not pass subtransactions=True when creating a transaction, which would cause a DB error. Change-Id: Ia52818cfc9479d5fa6e3b236988694f47998acda Task: 37001
This commit is contained in:
parent
084933f8ce
commit
7cb4ca6006
2
heat
2
heat
|
@ -1 +1 @@
|
|||
Subproject commit b377a80ad51b9bdfc339790517f4ae44cfecfcee
|
||||
Subproject commit 0d4139be70823b9e4b6fa224e1d0cc42765a1e98
|
Loading…
Reference in New Issue