Bug 1337049
| Summary: | Can't provision vm from template with Choose Automatically checked | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Kyrylo Zvyagintsev <kzvyahin> |
| Component: | Provisioning | Assignee: | Bill Wei <bilwei> |
| Status: | CLOSED ERRATA | QA Contact: | Kyrylo Zvyagintsev <kzvyahin> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.6.0 | CC: | jhardy, obarenbo, simaishi |
| Target Milestone: | GA | ||
| Target Release: | 5.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | vm:provisioning | ||
| Fixed In Version: | 5.6.0.8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-29 16:03:35 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: | |||
|
Comment 2
Greg McCullough
2016-05-18 14:07:41 UTC
New commit detected on cfme_productization/master: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme_productization.git;a=commit;h=542e69184814f70830dc9870d9cd582bfd9a690a commit 542e69184814f70830dc9870d9cd582bfd9a690a Merge: c5c4221 a61e0ef Author: Greg McCullough <gmccullo> AuthorDate: Wed May 18 12:17:02 2016 -0400 Commit: Greg McCullough <gmccullo> CommitDate: Wed May 18 12:17:02 2016 -0400 Merge branch 'master_remove_placement' into 'master' No longer need to determine placement_folder_name It has been set in provision/cloing.rb https://bugzilla.redhat.com/show_bug.cgi?id=1313067 https://bugzilla.redhat.com/show_bug.cgi?id=1337049 This is a clean cherry-pick from cfme_productization:5.5.z See merge request !268 .../__methods__/vmware_preprovision_clone_to_vm.rb | 24 ++-------------------- 1 file changed, 2 insertions(+), 22 deletions(-) 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://access.redhat.com/errata/RHBA-2016:1348 |