Comment 4 for bug 1575898

Steve - Thanks for the input. One (probably more, but one for now) question:

I see in the patch where we removed the force_reload in the nested stack retrieval, replacing it with the lightweight DB call for just the status (and some other small data).

What I'm not understanding is how that would affect the parent stack. I see a reference to nested.set_parent_stack removed from _parse_nested_stack, but the latter is only called during validate, which AFAICT doesn't come into play during that status check load.

I'm waiting on a run of TripleO CI with some added logging to finish, but after that, I'll see about kicking one off with the explicit resolve call at the tail end of the nested stack creation to see if it's any more stable.