Bug 1361174 - VMware-Cloning a template fails when the target datacenter is nested below multiple folders
Summary: VMware-Cloning a template fails when the target datacenter is nested below mu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.6.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: GA
: 5.6.3
Assignee: Drew Bomhof
QA Contact: Shveta
URL:
Whiteboard: provision:vmware
Depends On: 1358474
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-28 12:44 UTC by John Prause
Modified: 2022-07-09 07:58 UTC (History)
10 users (show)

Fixed In Version: 5.6.3.0
Doc Type: Bug Fix
Doc Text:
In the previous version of CloudForms, cloning a VMware template failed when the target datacenter was nested below multiple folders. This was because if the datacenter was nested logically under various folders, users were unable to find the placement ID during an autoplacement VMware provision request. This fix always does a lookup of the folder path from the host datacenter instead of statically setting a possible wrong default value which has resolved the issue.
Clone Of: 1358474
Environment:
Last Closed: 2016-11-30 19:52:42 UTC
Category: ---
Cloudforms Team: VMware
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
automation log (13.71 MB, application/zip)
2016-09-20 18:24 UTC, Shveta 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2839 0 normal SHIPPED_LIVE Important: CFME 5.6.3 security, bug fix, and enhancement update 2016-12-01 00:51:49 UTC

Comment 4 Shveta 2016-09-20 18:15:43 UTC 
Cloning this template works fine but "provision from VM" fails with error "
[RuntimeError]: A specified parameter was not correct. spec.location.folder "
Comment 5 Shveta 2016-09-20 18:24:55 UTC 
Created attachment 1202996 [details]
automation log
Comment 8 Shveta 2016-10-04 18:44:58 UTC 
@Drew : Please see https://10.8.199.36

Request number 8
Comment 9 Shveta 2016-10-10 16:20:21 UTC 
Not alive anymore . 
All appliance stay for a day or two max (until they hit the SWAP memory issue, once they hit SWAP we have to kill them )

I will try and recreate on another appliance .
Comment 11 Shveta 2016-11-19 11:15:06 UTC 
Fixed.
Verified in 5.6.3.0.20161108115816_66df924
Comment 13 errata-xmlrpc 2016-11-30 19:52:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2839.html
Note You need to log in before you can comment on or make changes to this bug.