| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't assume that we can get the physical IDs of all of the
SoftwareDeployment resources as soon as the stack becomes
CREATE_IN_PROGRESS. 4dd67bb1aa2df4f5270f79600ac1f888b0bd9a5f reads them
again once the stack is COMPLETE; this patch also uses the same physical
resource IDs to verify the update.
Also, make sure all of the resources are IN_PROGRESS before trying to
signal them, because the signal_resources() utility method only signals
resources that are IN_PROGRESS.
Change-Id: I9787a5de5e4272a3ab370f653182aa9283ae01c0
Closes-Bug: #1697794
Closes-Bug: #1626073
Closes-Bug: #1625921
|
| |
|
|
|
|
|
|
|
|
| |
We seem to get the list of group resources for signaling (there
is possibility that resource_id is not set for some resources)
and then use the same list to get the deployments. It would be
good to get the resources again after they are created.
Change-Id: I908d1d13abe8e59a65308e883591abca2b1c7a9a
Partial-Bug: #1625921
|
| |
|
|
|
|
|
| |
Adds functional test for SoftwareDeploymentGroup
rolling_update.
Change-Id: Id575765d52c84e3c29f443a18417b5f14d9331cc
|
|
|
Adds an initial test which tests create/delete for this resource,
and that signalling works.
Also tests deleting an in-progress stack as this has been a repeated
source of bugs related to deleting the child stack correctly.
Change-Id: I0d5acdca50467da344388d6c262e61aaaaae22eb
Related-Bug: #1592374
|
