Description of problem: When ordering a service for a container provider, it errors with the following message: Generic Service Error: Server [EVM] Service [juwatts-catalog-item] Provision Step [pre4] Status [Error Processing Preprocess] Version-Release number of selected component (if applicable): 5.10.0.23.20181106165157_92dd189 How reproducible: 100% Steps to Reproduce: 1. Add an OpenShift provider in the CFME appliance 2. Create a new service dialog 3. Creating a new Service Catalog Item based on the OpenShift Template Item Type and select the new dialog 4. Select the OpenShift provider that was just added for the Provider drop down and click Add 5. Verify the Service Catalog Item was created correctly 6. Order the item Actual results: The following error is displayed: Generic Service Error: Server [EVM] Service [juwatts-catalog-item] Provision Step [pre4] Status [Error Processing Preprocess] Expected results: Catalog item is ordered successfully Additional info: Attaching tar of the logs
Created attachment 1503342 [details] Attachings log
This is also seen in 5.9.6.0.20181105224828_652732b
The automation.log reports "MiqAeServiceModelBase.ar_method raised: <RuntimeError>: <A project is required for the container template provisioning>". Was a project selected as part of the service ordering? This would likely point to so issue with dialogs. Would be helpful to get a screenshot of the dialog order before submitting as a reference.
In 5.9.6/5.10, the following options are available when adding a catalog item: Name/Description Catalog Dialog Provider Container Template There is no option to select the project. Adding screenshot of the catalog item.
Created attachment 1503365 [details] Adding screenshot of catalog item
The project selection is when you are ordering the Service item, not at configuration time. I was looking for a screenshot of the service dialog being display.
Created attachment 1503367 [details] Additional screenshots Greg, Added screenshots of all relevant pages.
Misconfiguration on my part, closing this bug.