A verbose configure trace should list all the "def" steps performed by name (like "performing Foo.baz on host H" or "performing Foo.bar on prototype image for cloud Foop" or "performing Foo.fum on provisioner host).
The basic idea is that looking at verbose output should give amble clues as to what def section of which rb source file:
is being performed
is executing on what machine
is probably emitting subsequent verbose logging messages
is affecting which hosts
The would go a long way for troubleshooting and debugging.
A verbose configure trace should list all the "def" steps performed by name (like "performing Foo.baz on host H" or "performing Foo.bar on prototype image for cloud Foop" or "performing Foo.fum on provisioner host).
The basic idea is that looking at verbose output should give amble clues as to what def section of which rb source file:
The would go a long way for troubleshooting and debugging.