Bug 1301717
Summary: | Missing instance processing in Automate engine doesn't preserve the instance name that was missing | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | mkanoor |
Component: | Automate | Assignee: | mkanoor |
Status: | CLOSED ERRATA | QA Contact: | Milan Falešník <mfalesni> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.5.0 | CC: | dajohnso, jhardy, mkanoor, obarenbo, tfitzger |
Target Milestone: | GA | ||
Target Release: | 5.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.6.0.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-29 15:33:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
mkanoor
2016-01-25 19:30:34 UTC
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/de3fbad2eedbb6cfd52d3adff480059d762570c5 commit de3fbad2eedbb6cfd52d3adff480059d762570c5 Author: Madhu Kanoor <mkanoor> AuthorDate: Mon Jan 25 15:23:15 2016 -0500 Commit: Madhu Kanoor <mkanoor> CommitDate: Mon Jan 25 17:43:10 2016 -0500 Add _missing_instance attribute https://bugzilla.redhat.com/show_bug.cgi?id=1301717 If the .missing instance is being used for an instance, preserve the original name in an attribute called _missing_instance in the MiqAeObject. This attribute can be used in substitution. lib/miq_automation_engine/engine/miq_ae_object.rb | 1 + spec/lib/miq_automation_engine/miq_ae_engine_spec.rb | 18 ++++++++++++++++++ 2 files changed, 19 insertions(+) Assigning to add test case Verified in 5.6.0.2-beta2. I did not go the long way for verification, I just tried to call a method using .missing and _missing_instance expansion and it worked. 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://access.redhat.com/errata/RHBA-2016:1348 |