Project

General

Profile

Actions

Bug #37723

open

Registering a new vmware guest fails if Foreman has never put a machine on that network before

Added by Steven Shockley 2 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

On my existing Katello installation I somehow screwed up all the certificates, as one does. I built a new Foreman server (without Katello) and I'm moving the clients over. I'm not using Puppet except on the Foreman box itself, just Ansible.

When I try to import an existing machine into the new Foreman box it fails. I tried Hosts > Register Host and pasting the command into the VMWare guest, and I tried Infrastructure > vSphere > Virtual Machines > Actions button > Import as managed Host. Both fail.

Based on the logs I suspected Foreman didn't understand the VM's network connection, even though I had already created the Subnets in Foreman. I created a new Host in Foreman on one of the other subnets (didn't even power it on) and then I could import machines on those networks.

The error is:
2024-08-11T19:04:40 [W|app|a6b4e900] Failed to create a compute vSphere (VMware) instance emby.example.net: Unknown Network ID:
a6b4e900 |

The code is at https://github.com/theforeman/foreman/blob/develop/app/models/compute_resources/foreman/model/vmware.rb line 507, but I'm not sure what that's doing there or how to fix it.

I'll attach the relevant logs, let me know if you need anything else. Thanks.


Files

FormanLogs.txt FormanLogs.txt 22.4 KB Steven Shockley, 08/12/2024 07:34 PM

No data to display

Actions

Also available in: Atom PDF