Bug 1280462 - Automate | Orchestration Provisioning parsing inconsistent with Service Dialog parsing
Automate | Orchestration Provisioning parsing inconsistent with Service Dialo...
Status: CLOSED NOTABUG
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate (Show other bugs)
5.5.0
Unspecified Unspecified
medium Severity medium
: GA
: 5.5.0
Assigned To: Tina Fitzgerald
Dave Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-11 14:34 EST by Tina Fitzgerald
Modified: 2015-11-17 16:13 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-17 16:13:56 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tina Fitzgerald 2015-11-11 14:34:27 EST
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 16:13:56 EST
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.

Note You need to log in before you can comment on or make changes to this bug.