Bug 1280462

Summary: Automate | Orchestration Provisioning parsing inconsistent with Service Dialog parsing
Product: Red Hat CloudForms Management Engine Reporter: Tina Fitzgerald <tfitzger>
Component: AutomateAssignee: Tina Fitzgerald <tfitzger>
Status: CLOSED NOTABUG QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.5.0CC: jhardy, mkanoor, obarenbo, tfitzger
Target Milestone: GA   
Target Release: 5.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-17 21:13:56 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 Tina Fitzgerald 2015-11-11 19:34:27 UTC 
Description of problem:

Identified parsing dialog options differences while while working with QA to validate a dialog_parser regression issue: 
https://bugzilla.redhat.com/show_bug.cgi?id=1235975

Service dialog parsing creates 2 attributes for each of the "dialog_" generic attributes and Orchestration Service provisioning creates only one attribute.

For example, 
Using A service dialog attribute called "dialog_test_name"  
Service dialog parsing will create the "dialog_test_name" and "test_name" attributes.
Orchestration Service provisioning parsing with create only a single "dialog_test_name" attribute.

Orchestration Service provisioning doesn't need the "dialog_" prefixed attribute to provision the service, but any multi-purpose and/or custom automate code that relies on the "dialog_" stripped attribute will fail.
Comment 3 Tina Fitzgerald 2015-11-17 21:13:56 UTC 
There are 2 instances in the Orchestration service provisioning class:
* Default
* CatalogItemInitialization

The "Default" instance should be used when: It is a service item and additional dialog parsing in not necessary. 

The "CatalogItemInitialization" instance should be used when it is a part of a service bundle, or if additional dialog parsing is necessary.