Project

General

Profile

Feature #824

Unattended installation monitoring

Added by Mohit Chawla about 8 years ago. Updated about 3 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Unattended installations
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

To avoid manual troubleshooting for hosts that could not be brought up for some reason or brought up in a possibly bad/incomplete state,it would be nice to know where things went wrong. In Kickstart/preseed itself this might be not be possible ( not entirely sure ), but for eg., ( fsweetser on irc mentioned this ) a summary page listing status of hosts - whether the build process has started or not, in transition, complete, complete with warnings/errors etc. could be useful.

History

#1 Updated by Jochen Schalanda about 8 years ago

Not really Foreman specific but really useful:

The Debian/Ubuntu installer and RHEL Kickstart support logging to a remote syslog host during installation.

For RHEL/CentOS it's documented in 28.10. Starting a Kickstart Installation (see syslog parameter).

For Debian/Ubuntu Linux the necessary kernel parameters are unfortunately not documented but you can simply add the log_host and if necessary the log_port (default is 514) parameters to the kernel line in your boot loader.

Prerequisite for this is a central log host listening on 514/udp which will aggregate the log messages.

#2 Updated by Ohad Levy about 3 years ago

  • Category set to Unattended installations

Also available in: Atom PDF