Comment 2 for bug 1703703

It looks like the problem was introduced by https://review.openstack.org/#/c/278231/. We take the 'convergence' path in the case that the Resource object cannot be found in the Stack's dependency graph. The dependency graph is constructed from the Resource objects found in Stack.resources. However, the Resource objects we're listing are loaded from database objects independently of the Stack, and thus *never* appear in the dependencies.

So we always take the 'convergence' path, and display of dependencies is just broken for non-convergence-mode stacks.