Comment 3 for bug 1493900

@Sergey,

this bug is not about network configuration failure due to incorrect transformations order in networking template. It's about the `puppet apply` command behaviour - it returns 0 even when task failed due to 'dependency cycle' error. Environment deployment continues and fails later on another task, so for cloud administrator it's not obvious what went wrong.
I mentioned an example with networking template, because it's the easiest way for end users to cause such issue - just provide incorrect order of transformations.