Project

General

Profile

Actions

Bug #11395

closed

Unable To Create New VMWare Host due to Error undefined method `hardware_version' for #<Fog::Compute::Vsphere::Server:XXXXXX>

Added by shankar janagoud over 8 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

While creating new vm host observed "Error loading virtual machine information: Internal Server Error" in "virtual machine" tab of foreman gui.

1. Login to foreman
2. Select New host and provide all attributes needed.
3. Select VMware for DeployOn field

From the trace I can see below error message
2015-08-14 10:41:35 [W] Operation FAILED: undefined method `hardware_version' for #<Fog::Compute::Vsphere::Server:0x0000000c3f0e10>
2015-08-14 10:41:35 [D] /opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/helpers/form_helper.rb:1154:in `value'

PFA production.log for more details


Files

production.log production.log 30.1 KB shankar janagoud, 08/18/2015 03:09 AM
temp.log temp.log 80.2 KB shankar janagoud, 08/18/2015 05:03 AM
Actions #1

Updated by shankar janagoud over 8 years ago

ESXi Version: 5.5
Foreman: 1.8.2
Fog : 1.29

Actions #2

Updated by Dominic Cleal over 8 years ago

  • Category set to Compute resources - VMware
  • Status changed from New to Need more information

Could you check if this command provides any further logs?

grep -A50 "Fog initialization failed" /var/log/foreman/production.log

The output from these would also be useful:

rpm -qaV ruby193-rubygem-fog\*
rpm -qa foreman\* ruby193-rubygem-fog\*

Actions #3

Updated by shankar janagoud over 8 years ago

The previously attached production log was old. With new log I can see the "Fog initialization failure"

For "grep -A50 "Fog initialization failed" /var/log/foreman/production.log" please find the file attached(temp.log).

[xxx@xxx]# rpm -qaV ruby193-rubygem-fog\*
.......T. /opt/rh/ruby193/root/usr/share/gems/gems/fog-1.29.0/lib/fog/vsphere/models/compute/interface.rb
.......T. /opt/rh/ruby193/root/usr/share/gems/gems/fog-1.29.0/lib/fog/vsphere/requests/compute/vm_clone.rb
[xxx@xxx]# rpm -qa foreman\* ruby193-rubygem-fog\*
foreman-debug-1.8.2-1.el6.noarch
foreman-release-1.8.2-1.el6.noarch
ruby193-rubygem-fog-xml-0.1.1-1.el6.noarch
ruby193-rubygem-fog-1.29.0-1.el6.noarch
foreman-ovirt-1.8.2-1.el6.noarch
ruby193-rubygem-fog-json-1.0.0-2.el6.noarch
ruby193-rubygem-fog-aws-0.1.0-1.el6.noarch
foreman-selinux-1.8.2-1.el6.noarch
foreman-proxy-1.8.2-2.el6.noarch
foreman-1.8.2-1.el6.noarch
foreman-vmware-1.8.2-1.el6.noarch
foreman-postgresql-1.8.2-1.el6.noarch
ruby193-rubygem-fog-brightbox-0.0.1-1.el6.noarch
foreman-compute-1.8.2-1.el6.noarch
foreman-libvirt-1.8.2-1.el6.noarch
foreman-cli-1.8.2-1.el6.noarch
foreman-installer-1.8.2-1.el6.noarch
ruby193-rubygem-fog-softlayer-0.3.9-1.el6.noarch
ruby193-rubygem-fog-core-1.29.0-1.el6.noarch
foreman-ec2-1.8.2-1.el6.noarch
foreman-console-1.8.2-1.el6.noarch

Actions #4

Updated by Dominic Cleal over 8 years ago

I can't reproduce this yet, and have an almost identical setup, so I'm not sure what's going on. It would appear that part of Fog's not loading correctly (/opt/rh/ruby193/root/usr/share/gems/gems/fog-1.29.0/lib/fog/vsphere/requests/compute/get_virtual_machine.rb, called from ~foreman/app/models/concerns/fog_extensions.rb.

My only other thought is, do you have any plugins installed? Output from "foreman-rake plugins" and/or "rpm -qa ruby193-rubygem-foreman\*" should show.

Actions #5

Updated by shankar janagoud over 8 years ago

[xxx@xxx]# rpm -qa ruby193-rubygem-foreman\*
ruby193-rubygem-foreman_param_lookup-0.2.0-1.el6.noarch
ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch
ruby193-rubygem-foreman_hooks-doc-0.3.7-3.el6.noarch
ruby193-rubygem-foreman_bootdisk-5.0.0-1.el6.noarch
ruby193-rubygem-foreman_column_view-doc-0.2.0-1.el6.noarch
ruby193-rubygem-foreman_hooks-0.3.7-3.el6.noarch
ruby193-rubygem-foreman_docker-doc-1.4.0-1.fm1_8.el6.noarch
ruby193-rubygem-foreman_column_view-0.2.0-1.el6.noarch
ruby193-rubygem-foreman_openstack_cluster-0.0.1-1.el6.noarch
ruby193-rubygem-foreman_salt-2.1.0-1.el6.noarch
ruby193-rubygem-foreman_discovery-3.0.0-1.el6.noarch
ruby193-rubygem-foreman_docker-1.4.0-1.fm1_8.el6.noarch
ruby193-rubygem-foreman_dhcp_browser-doc-0.0.6-1.el6.noarch
ruby193-rubygem-foreman_param_lookup-doc-0.2.0-1.el6.noarch
ruby193-rubygem-foreman_setup-doc-2.1.1-1.el6.noarch
ruby193-rubygem-foreman_discovery-doc-3.0.0-1.el6.noarch
ruby193-rubygem-foreman_salt-doc-2.1.0-1.el6.noarch
ruby193-rubygem-foreman_dhcp_browser-0.0.6-1.el6.noarch
ruby193-rubygem-foreman_setup-2.1.1-1.el6.noarch
ruby193-rubygem-foreman_templates-1.5.0-1.el6.noarch
ruby193-rubygem-foreman_chef-doc-0.1.3-2.el6.noarch
ruby193-rubygem-foreman_openstack_cluster-doc-0.0.1-1.el6.noarch
ruby193-rubygem-foreman_chef-0.1.3-2.el6.noarch
ruby193-rubygem-foreman_templates-doc-1.5.0-1.el6.noarch
[root@foreman foreman]# cd /etc/puppet/modules/ceph/
[root@foreman ceph]# foreman-rake plugins

Actions #6

Updated by Anonymous almost 8 years ago

what's the status here?

Actions #7

Updated by Anonymous over 7 years ago

  • Status changed from Need more information to Rejected

no reaction, closing.

Actions

Also available in: Atom PDF