Feature #31585
closed
iPXE ping gateway and name server
Added by Pat Riehecky almost 4 years ago.
Updated almost 4 years ago.
Description
It would be helpful for debugging if the iPXE boot templates did a `ping --count=1 < gateway >` and `ping --count=1 < nameserver >` to help diagnose boot issues.
In theory this would delay boot by less than 1 second, when things are working as expected. And when things are not right, the connectivity failure will be fairly clear.
Would also be handy to ping the content source, but I'm not sure how easily that is exposed to the templates.
Feel free to file a PR:
[lzap@box foreman]$ g find ipxe
app/services/foreman/ipxe/message_renderer.rb
app/views/unattended/provisioning_templates/PXELinux/pxelinux_chain_ipxe.erb
app/views/unattended/provisioning_templates/PXELinux/pxelinux_chain_ipxe_undi.erb
app/views/unattended/provisioning_templates/iPXE/autoyast_default_ipxe.erb
app/views/unattended/provisioning_templates/iPXE/ipxe_default_local_boot.erb
app/views/unattended/provisioning_templates/iPXE/ipxe_global_default.erb
app/views/unattended/provisioning_templates/iPXE/ipxe_intermediate_script.erb
app/views/unattended/provisioning_templates/iPXE/kickstart_default_ipxe.erb
app/views/unattended/provisioning_templates/iPXE/preseed_default_ipxe.erb
app/views/unattended/provisioning_templates/iPXE/windows_default_ipxe.erb
[lzap@box foreman]$ ag content_source
app/views/unattended/report_templates/ansible_-_ansible_inventory.erb
130: 'content_source': content_facet.content_source,
131: 'content_source_id': content_facet.content_source_id,
132: 'content_source_name': content_facet.content_source_name,
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8240 added
- Fixed in Releases 2.4.0 added
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by