Bug 1352903

Summary: Owner is not set for azure instances when provisioned through service catalog (type orchestration)
Product: Red Hat CloudForms Management Engine Reporter: Prasad Mukhedkar <pmukhedk>
Component: ProvisioningAssignee: Bill Wei <bilwei>
Status: CLOSED WONTFIX QA Contact: Shveta <sshveta>
Severity: high Docs Contact:
Priority: high    
Version: 5.5.0CC: cpelland, dajohnso, gblomqui, jfrey, jhardy, obarenbo, pmukhedk
Target Milestone: GAKeywords: ZStream
Target Release: 5.7.0Flags: pmukhedk: needinfo-
Hardware: x86_64   
OS: Linux   
Whiteboard: azure:service:provision
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1353932 (view as bug list) Environment:
Last Closed: 2017-08-28 14:46:19 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:
Bug Depends On:    
Bug Blocks: 1353932    
Attachments:
Description Flags
VM_owner_not_specified-2
none
service_owner_ok-1
none
orchestration-post-provision-script none

Description Prasad Mukhedkar 2016-07-05 12:27:47 UTC 
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:
Comment 3 Prasad Mukhedkar 2016-07-05 12:32:19 UTC 
Created attachment 1176412 [details]
VM_owner_not_specified-2
Comment 4 Prasad Mukhedkar 2016-07-05 12:32:40 UTC 
Created attachment 1176413 [details]
service_owner_ok-1
Comment 6 Bill Wei 2016-07-08 15:46:25 UTC 
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.
Comment 7 Bill Wei 2016-07-08 15:47:54 UTC 
Created attachment 1177697 [details]
orchestration-post-provision-script

Please verify whether you have the fix
Comment 11 Bill Wei 2016-07-18 13:56:42 UTC 
Prasad,

I have uploaded a hotfix for 5.5. Please close this PR if this works for you,
Comment 12 Chris Pelland 2017-08-28 14:46:19 UTC 
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.