Project

General

Profile

Bug #18988

controller_key is required for this operation

Added by Mark Gargiulo over 2 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

I am having an issue with foreman 1.14.2 and vmware vshpere 5.5.
When I clone a host in foreman and try to redeploy via vsphere iget this error:
"Failed to create a compute vCenter (VMware) instance "hostname": controller_key is required for this operation"
I do not get this on a "new host" creation. Cloning operations to other compute resources like oVirt work as expected.

I have attached the relevant section of the production.log.

production.log production.log 20 KB Mark Gargiulo, 03/22/2017 02:01 PM

History

#1 Updated by Vladimir Safronov over 2 years ago

Mark Gargiulo wrote:

I am having an issue with foreman 1.14.2 and vmware vshpere 5.5.
When I clone a host in foreman and try to redeploy via vsphere iget this error:
"Failed to create a compute vCenter (VMware) instance "hostname": controller_key is required for this operation"
I do not get this on a "new host" creation. Cloning operations to other compute resources like oVirt work as expected.

I have attached the relevant section of the production.log.

The same issue with foreman 1.14.2 and vSphere 6.5

#2 Updated by Dominic Cleal over 2 years ago

  • Category set to Compute resources - VMware

Could you please try installing a more recent version of tfm-rubygem-fog-vsphere? (http://yum.theforeman.org/nightly/el7/x86_64/tfm-rubygem-fog-vsphere-1.7.0-1.el7.noarch.rpm, and restart httpd) There are some fixes that may be related in the newer version.

#3 Updated by Mark Gargiulo over 2 years ago

I upgraded tfm-rubygem-fog-vsphere to 1.7.0 as you suggested and that seems to have fixed the issue in my dev environment. I will do the same in production later today.

#4 Updated by Mark Gargiulo over 2 years ago

Dominic,
I can verify that this also works in our production environments.
Thanks for the quick turnaround.

#5 Updated by Dominic Cleal over 2 years ago

  • Status changed from New to Closed
  • Assignee set to Dominic Cleal
  • Legacy Backlogs Release (now unused) set to 227

Thanks for confirming, the package is set now for the next patch release.

Also available in: Atom PDF