Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: If the instances are provisioned through service catalog using orchestration template. At the service level, The user is assigned properly but no user is assigned to the actual instances spawned by the service catalog. User is assigned at services level but not to the instances spawned this causes problem in instance lifecycle email worlflow. User should be assigned to the instances spawned by the service. If you use native azure catalog, user are assigned to the instances similarly the users should be assigned when orchestration template is used. Version-Release number of selected component (if applicable): Cloudforms 4.0 How reproducible: always at customer end Steps to Reproduce: - Create a orchestration type service catalog using an azure template. ( can use "azure-single-vm-from-user-image" provided in-built with cloudforms) - Attach the service dialog created using the azure template. - Order the service. Actual results: User is assigned at services level but not to the instances spawned this causes problem in instance lifecycle email worlflow. See attached snapshots Expected results: User should be assigned to the instances spawned by the service. If you use native azure catalog, user are assigned to the instances similarly the users should be assigned when orchestration template is used. Additional info:
Created attachment 1176412 [details] VM_owner_not_specified-2
Created attachment 1176413 [details] service_owner_ok-1
This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1318032. Can you verify you already have the fix? One way to verify is to examine whether the post-provision script has the line service.post_provision_configure I have attached the screenshot for your reference.
Created attachment 1177697 [details] orchestration-post-provision-script Please verify whether you have the fix
Prasad, I have uploaded a hotfix for 5.5. Please close this PR if this works for you,
This bug has been open for more than a year and is assigned to an older release of CloudForms. If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.