Bug 1290271
Summary: | Services : Bundle deployment to create multiple stack at once fails | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Shveta <sshveta> | ||||
Component: | Provisioning | Assignee: | Bill Wei <bilwei> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Dave Johnson <dajohnso> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.4.0 | CC: | gmccullo, jhardy, obarenbo, sshveta | ||||
Target Milestone: | GA | ||||||
Target Release: | 5.6.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-12-15 16:48:37 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: | |||||||
Attachments: |
|
Description
Shveta
2015-12-10 00:49:29 UTC
I suspect that the bundle service might be pointing at the wrong state-machine. The bundle service should be using the entry point instance CatalogBundleInitialization in ManageIQ/Services/Provisioning/StateMachines/ServiceProvision_Template namespace. Please check this configuration. Created attachment 1104488 [details]
path
Changed the path to above mentioned .
Request fails with error
"expected string value for option stack_name (MiqException::MiqOrchestrationProvisionError) "
From the description each catalog item was created with type "Amazon". Was this a typo? To provision a stack one needs to create a catalog item with type "Orchestration", and select a provider, i.e., orchestration manager, in the dialog. When you test the catalog item alone, you should set the entry point to ManageIQ/Cloud/Orchestration/Provisioning/StateMachines/Provision.class/default. But when you include such catalog item to a bundle service, the entry point for each catalog item should change to ManageIQ/Cloud/Orchestration/Provisioning/StateMachines/Provision.class/CatalogItemInitialization. Using catalog bundle to provision multiple stacks was fixed and verified by https://bugzilla.redhat.com/show_bug.cgi?id=1260436. Please retest. You may want to modify the service dialog if you desire to pass different parameters to each sub-service as explained in comment #26. Bill , I am able to provision bundle with two different ec2 providers. Thanks. One more question ,is it possible to provision bundle with stack of two providers like RHOS and ec2? If yes what should i select in dialog field for bundle . i can only select one where as i need two dialogs for provisioning each stack type. Yes, you can provision two or more stacks through catalog bundle. The auto-generated dialog is based on a single template. It can be directly used by a catalog bundle only if all catalog items use the same template or require the same parameters. You can however modify the dialog or even manually create your own dialog, using the dialog_# prefix for field names, to feed different parameters to each catalog item template. You can use the tool to generate dialogs for each template, and manually merge two (or more) dialogs into a new dialog. Prefix dialog_1_ to parameters needed by the first catalog item, dialog_2_ to parameters needed by the second catalog item, and so on. Leave the parameters common to all catalog items unchanged. Then you can use this new dialog for the catalog bundle. |