Description of problem: Resolving an instance with an assertion containing an invalid value continues resolution when it should raise an error. How reproducible: Create a writable domain. Copy a class to the writable domain. Add an assertion to the class schema. Create an instance, giving the assertion an invalid substitution like ${/#this_value_does_not_exist} Use simulate to call instance. (Use /system/request/call_instance) and provide namespace, class, instance in the attribute value pairs. Actual results: The instance continues as if there was no assertion Expected results: An error should be raised.
Created PR https://github.com/ManageIQ/manageiq/pull/9737
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/56f561367418b7999cf109056730123c6c383bef commit 56f561367418b7999cf109056730123c6c383bef Author: Madhu Kanoor <mkanoor> AuthorDate: Mon Jul 11 18:25:16 2016 -0400 Commit: Madhu Kanoor <mkanoor> CommitDate: Mon Jul 11 18:25:16 2016 -0400 Raise exception in assertion processing https://bugzilla.redhat.com/show_bug.cgi?id=1335669 If an attribute is not found during assertion processing raise an exception instead of continuing silently lib/miq_automation_engine/engine/miq_ae_object.rb | 17 +++--- lib/miq_automation_engine/miq_ae_exception.rb | 1 + .../miq_automation_engine/miq_ae_assertion_spec.rb | 60 ++++++++++++++++++++++ 3 files changed, 72 insertions(+), 6 deletions(-) create mode 100644 spec/lib/miq_automation_engine/miq_ae_assertion_spec.rb
Verified in 5.6.1.0 Automation Error: Attribute xyz not found for object [] When putting ${#xyz} in the assertion.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-1634.html