Currently both warnings and errors are non-fatal by default in tripleoclient. This makes very little sense since errors should be things that are pretty much guaranteed to fail the deployment. The only time an error should be ignored is if there is a bug in the validation. If a deployment can happen in spite of the problem, then that should be a warning.
For an example of where this can bite deployers, see https://bugzilla.redhat.com/show_bug.cgi?id=1360421 Because the validation error does not immediately stop the deployment, we attempt to update an invalid environment and hose the deployment.
To my knowledge, the current best practice in the field is to set validation errors to fatal anyway, so this is just aligning our defaults with the real world use case.
Fix proposed to branch: master
Review: https:/