Project

General

Custom queries

Profile

Actions

Bug #11106

closed

Foreman 1.8.2 with VMware errors with: Could not find virtual machine network interface matching x.x.x.x

Added by Seth Doty over 9 years ago. Updated over 6 years ago.

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

Description

I have been nagging the IRC channel with this one and the consensus is that its a bug. When building a VMware guest I receive: Could not find virtual machine network interface matching x.x.x.x.

Logs come back with : 2015-07-13 12:40:20 [W] Orchestration::Compute: Could not match network interface #<Nic::Managed id: nil, mac: nil, ip: "10.21.3.245", type: "Nic::Managed", name: "test.domain.local", host_id: nil, subnet_id: 1, domain_id: 1, attrs: {}, created_at: nil, updated_at: nil, provider: nil, username: nil, password: nil, virtual: false, link: true, identifier: "", tag: "", attached_to: "", managed: true, mode: "balance-rr", attached_devices: "", bond_options: "", primary: true, provision: false, compute_attributes: {"type"=>"VirtualVmxnet3", "network"=>"pg-vlan-3"}>
2015-07-13 12:40:20 [W] Could not find virtual machine network interface matching 10.21.3.245
2015-07-13 12:40:20 [W] Rolling back due to a problem: [Query instance details for test.domain.local 4 failed [#<Host::Managed id: nil, name: "test.domain.local", last_compile: nil, last_freshcheck: nil, last_report: nil, updated_at: nil, source_file_id: nil, created_at: nil, root_pass: "", serial: nil, puppet_status: 0, architecture_id: 1, operatingsystem_id: 1, environment_id: 2, ptable_id: 14, medium_id: 8, build: true, comment: "", disk: "", installed_at: nil, model_id: nil, hostgroup_id: 1, owner_id: 3, owner_type: "User", enabled: true, puppet_ca_proxy_id: 1, managed: true, use_image: nil, image_file: nil, uuid: "5032e796-3769-ee7b-3ed4-d2b036c20cb0", compute_resource_id: 1, puppet_proxy_id: 1, certname: nil, image_id: nil, organization_id: 1, location_id: 5, type: "Host::Managed", otp: nil, realm_id: nil, compute_profile_id: 4, provision_method: "build", content_source_id: 1, grub_pass: "", content_view_id: 1, lifecycle_environment_id: 1, discovery_rule_id: nil>, :setComputeDetails]]
2015-07-13 12:40:20 [I] Removing Compute instance for test.domain.local.

This is a fresh install of foreman 1.8.2 with katello.


Files

production.log production.log 261 KB Seth Doty, 07/14/2015 09:19 AM
production.log production.log 528 KB Sandro Roth, 06/16/2016 09:18 AM

Added by Ivan Necas over 8 years ago

Revision d4af7cae (diff)

Fixes #5483,#11106 - pass the virtualswitch value to fog

We can't pass the network id directly to the fog, but it accepts the
virtualswitch parameter, that we can use to point to the right value.

Also, it fixes another issue, where we used the vsphere network id to
match against the interface network value, in case of portgroup, but a
`key` value should be used instead, as the key and id might differ in
some situations.

Added by Ivan Necas about 8 years ago

Revision 443412c1 (diff)

Fixes #5483,#11106 - pass the virtualswitch value to fog

We can't pass the network id directly to the fog, but it accepts the
virtualswitch parameter, that we can use to point to the right value.

Also, it fixes another issue, where we used the vsphere network id to
match against the interface network value, in case of portgroup, but a
`key` value should be used instead, as the key and id might differ in
some situations.
(cherry picked from commit d4af7cae07f78bd047290e68af37b55122e0ed4b)

Actions

Also available in: Atom PDF