Bug 1207165

Summary: Unable to provision new VM in VMWare: failed to create vm: undefined method `resourcePool' for nil:NilClass
Product: Red Hat Satellite Reporter: DipenDevra <ddevra>
Component: Compute Resources - VMWareAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.8CC: aagrawal, aupadhye, bkearney, chrobert, cwelton, dlobatog, londrack, mhulan, mmccune, ohadlevy, scott.higgins, suprabhu, tbhowmik
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
URL: http://projects.theforeman.org/issues/11274
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-12 16:53:00 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:

Comment 1 RHEL Program Management 2015-03-30 11:23:08 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 6 Bryan Kearney 2016-08-04 20:15:17 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 8 Daniel Lobato Garcia 2017-06-07 08:33:38 UTC
https://github.com/theforeman/foreman/pull/2589 and https://github.com/theforeman/foreman/pull/2307 are covering this, linking them to this BZ and closing as POST.

Comment 9 Daniel Lobato Garcia 2017-06-07 08:42:09 UTC
Connecting redmine issue http://projects.theforeman.org/issues/10151 from this bug

Comment 10 Daniel Lobato Garcia 2017-06-07 08:42:29 UTC
Connecting redmine issue http://projects.theforeman.org/issues/11274 from this bug

Comment 11 Satellite Program 2017-06-07 10:13:21 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/11274 has been resolved.

Comment 13 Mike McCune 2018-04-12 16:53:00 UTC
This is resolved in 6.3.0 GA. If you still see this issue occurring, feel free to re-open.