Instead of calling check_resource on all leaves in the resource graph at
once, sleep a little bit between each call. As it's a tad slower,
delegate it to a thread so that the stack_create RPC message doesn't
timeout when you have lots of resources.
Change-Id: I84d2b34d65b3ce7d8d858de106dac531aff509b7
Partial-Bug: #1566845
At the beginning, when we prepare ports for
server replacement, we store 'fixed_ips' of
server ports before update them to []. But
update 'fixed_ips' is incorrect, we just have to
detach the ports from server. we fixed it already,
but seems the code was not cleaned.
Change-Id: If925e5bf03385922ec1784ae56ec7faff7c68b21
The stack_name in request must match some regular expression, but
the code implementation and document description is inconsistent.
Change-Id: I02c09d2624253d9ce19735dbe745ff4d3321332d
Closes-Bug: #1671126
THe fix for docutils 0.13 doesn't work with 0.12, obviously. This works
around the issue handling both version of the internal API.
Change-Id: I3bebb206a3205a6f3fa77a7844e50c2e090630a4
Where strings are continued across multiple lines, it's easy to miss a
space. This fixes several incorrect strings, cleans up some formatting
(don't line break inside a format specifier) and fixes typos.
Change-Id: Id781b16cad03c32973a67c02ad22ce4459c6d126
When merging multiple envs, 0 values where ignored in later envs, not
taking precedence. This fixes it by checking for None instead.
Change-Id: Ia0da6988f92825bcc9a19dd3dcce771baa978a59
Closes-Bug: #1669442
With pbr2 landed, we should update our test requirement to prevent
package conflict.
Closes-Bug: #1669276
Change-Id: I46a357b87e67ceffd3e15040349774280b8849fc
The list_events rpc api no longer includes resource properties data
when returning multiple events. In the "show event" case where an event
uuid is included in the list_events request, the resource properties data
for that single event continues to be included in the output.
Note that there is no change in behaviour on the heat-api side (see
heat/api/openstack/v1/events.py). Previously when listing multiple
events, it had just been ignoring the resource properties data it
fetched from the list_events rpc api, not including it in the output
it returned (e.g., to python-heatclient).
Change-Id: I7ac83d848cdd0e6c313870c0a4d59a5d9b2301f5
Partial-Bug: #1665506
Save the db and memory overhead associated with fetching a
raw_template when soft-deleting a stack or getting a root stack id.
Change-Id: I8cf575e4908764c4c5eb24185ec229254e30d58b
assertIn is failing on exception messages as apparently they are bytes
in Python3. Let's encode it before the check.
Change-Id: I886a9458e72aa1ffdb2cc6dcf20331f468778032
This reverts commit d7f2d4f23e.
ostestr spews what is IMHO an unmanageable amount of mostly worthless data when running tests - at least one line per test, of which there are 6351 at last count. There doesn't seem to be an option to quiet it down, so just revert it.
Change-Id: I7b12dc249e3e7041ab6f0ef36b3e5f0b082aeb7d
If getting an output from a child stack fails with an error, we didn't pass
on the error message to the parent stack that was requesting it but instead
reported essentially that the given output did not exist.
Change-Id: I5653baf310a29dc4829ad570c769cf67ce12695e
Partial-Bug: #1599114
Add full path field for Property class. Now
properties with sub-schemas should contain properties
with path, where their parent specified. For example,
if there is schema:
"a": type map:
schema:
"b": type string,
"c": type string
Then property "a" has path == 'a', "b" has path == 'a.b',
"c" has path == 'a.c'.
Change-Id: I6d0ba022f34b925d47142669d6076ebd63a2acdc
Related-bug: #1620859
Currently Properties has arg "parent_name", which
is used for detailed path in error and allows to
build path for nested properties schemas. But on
top parent_name takes resource name as initial,
which is few incorrect - Properties should raises
with error about Properties, other info (about in
what resource this error raised) should be built out of
Properties module.
Change-Id: I36e6453a1589c02a3f8cf2c080b38693b23b0f1b
Related-bug: #1620859
Previously, if a resource was in a FAILED state Heat would set the hook
but not wait for the user to clear it before continuing. It is not clear
what case this was designed to handle, since there's no way that I know
of for the resource to go into a FAILED state while waiting for the
hook.
Change-Id: Iaacc585b9806c08fd5a57c80c10eeb31cb0a8f71
Closes-Bug: #1665699
OpenStack Proposal Bot