deployed-server: resource group resources not in guaranteed order in resource list output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
James Slagle |
Bug Description
When listing the resources in a Heat ResourceGroup, they are not in a guaranteed order. I've only ever seen them in numerical order (based on resource_name) until I scaled down a ResourceGroup, then they were in reverse order.
For example, before scale down:
| 0 | bd1c1681-
| 1 | 0ede4a3c-
| 2 | 2abcb41b-
after scale down:
| 1 | 0ede4a3c-
| 0 | bd1c1681-
This will break the deployed-server get-occ-config.sh configuration script interface, since it assumes the list is ordered based on the order you want to apply the configurations to the various deployed-servers.
We need to sort the output before parsing it with the script.
Changed in tripleo: | |
importance: | Undecided → High |
assignee: | nobody → James Slagle (james-slagle) |
milestone: | none → ocata-rc2 |
tags: | added: ocata-backport-potential |
Changed in tripleo: | |
milestone: | ocata-rc2 → pike-1 |
Fix proposed to branch: master /review. openstack. org/435121
Review: https:/