Project

General

Profile

Actions

Feature #2214

closed

Specifying host IP address should not be mandatory for unmanaged DNS/DHCP subnets

Added by Jon Fautley about 11 years ago. Updated over 10 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Host creation
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

We have a setup whereby we deploy (RHEL) virtual machines (using libvirt+foreman) onto networks where we are only able to control the TFTP server via the smart-proxy.

When creating a new host, it is mandatory to specify an IP address for the primary interface of the new host - this should be made optional, and updated once the build is in progress.

Foreman already knows the MAC address of the system being built, so requests for the provision (kickstart) template are successful, and Foreman is then aware of the assigned IP for the host. Once Foreman is aware of the IP of the host, it should update the record in order for the 'build complete' status to be updated correctly.


Related issues 2 (0 open2 closed)

Related to Foreman - Feature #2576: Optionally update Host.ip as part of /unattended/builtClosedGreg Sutcliffe05/28/2013Actions
Is duplicate of Foreman - Feature #3182: Remove requirement for entering an IP address when creating a new hostClosedGreg Sutcliffe10/02/2013Actions
Actions #1

Updated by Dominic Cleal over 10 years ago

  • Is duplicate of Feature #3182: Remove requirement for entering an IP address when creating a new host added
Actions #2

Updated by Dominic Cleal over 10 years ago

  • Related to Feature #2576: Optionally update Host.ip as part of /unattended/built added
Actions #3

Updated by Dominic Cleal over 10 years ago

  • Description updated (diff)
  • Status changed from New to Duplicate

Being implemented via #3182.

Actions

Also available in: Atom PDF