Feature #20090
open
WebUI Logging of Provisioning Status
Added by Josh Pavel about 7 years ago.
Updated over 2 years ago.
Description
When you provision a server, the user isn't able to ascertain the status of the build, if it's succeeding at all, until later. Some times we don't easily have console access to these servers either.
It would be better if logs were passed along to update provisioning status - DHCP requests, kernel boots and handoffs, kickstart progress and webhooks - made available for whatever user issued the build, instead of "Pending Installation".
I like the idea. We could reflect that in host build status. I think we can monitor following
- DHCP request from a given MAC based on dhcpd log, probably twice (Smart proxy patch)
- TFTP request for installation media, based on tftp log (Smart proxy patch)
- kickstart/preseed was rendered (Foreman side patch)
- templates could be extended to report progress, such as "network configured", "cfgmgmt bootstrapped" (Foreman side patch)
anything else you can think of?
Since some part require smart proxy to report status back to Foreman, Foreman would need to add API endpoint for build status updating. Also this would need separate issue for smart proxy. I suppose not all sub-updates are required, some people don't use DHCP for example. So I suppose all would be optional updates and be mostly informative.
- Triaged changed from No to Yes
Hello, we already have such call available via /unattended/failed call, when called the whole BODY of the HTTP request is stored in build_errors database column and that information is available in the UI under Properties. When /unattended/built is called, the column is cleared tho, it can be only used to track error messages (logs). Currently Anaconda post scriplet utilizes this API to send logs when provisioning fails (in some cases). Maybe this could be expanded as part of this RFE.
Also available in: Atom
PDF
Updated by 
Updated by