Project

General

Profile

Actions
Copy link

Bug #16216

closed

Bootdisk based imaging uses the primary interface instead of the provisioning interface

Added by Dylan Baars over 8 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Using latest version of Katello, with boot disk based imaging for VMware. I am attempting to build a VM in our DMZ with two interfaces, one that points internal and one that is an external IP exposed to the internet

When building a new host via Hosts > New Host, it is possible to add multiple network interfaces and specific a "provisioning interface" (in my case, the 'internal' interface) and a "primary interface" (the external one)
When the VM is created, it attempts to boot using the provisioning interface - great! However, it cannot find the kickstart template (screenshot attached - "connection_timeout.jpg"). Using the spoof address to check where the kickstart is, it is assigned to the primary interface IP address

http://wellkatello.niwa.local/unattended/provision?spoof=103.229.249.7

I think this should be the provisioning interface

I have attached screenshots of the interface configuration for both

Files

connection_timeout.jpg View connection_timeout.jpg 134 KB Dylan Baars, 08/21/2016 07:36 PM
external_interface_primary.JPG View external_interface_primary.JPG 56.8 KB Dylan Baars, 08/21/2016 07:43 PM
internal_inteface_provisioning.JPG View internal_inteface_provisioning.JPG 59 KB Dylan Baars, 08/21/2016 07:43 PM
Actions
Copy link

Also available in: Atom PDF