If there is an ActiveRecord error during unattended/built orchestration (queue_tftp), the method silently does not enqueue TFTP orchestration. We should print the error in logs, otherwise it is impossible to investigate the root cause. In this case the error was: Action failed | ActiveRecord::RecordInvalid: Validation failed: Medium XXX/Library/Red_Hat_Server/Red_Hat_Enterprise_Linux_7_Server_Kickstart_x86_64_7_1 does not belong to RedHat 7.2 operating system Symptoms: A host enters build mode but during exit build mode (after Anaconda finishes) it does not orchestrate TFTP files change, therefore the host ends in endless loop of installations. Requesting 6.3 only as this is a log improvement, not fix of particular bug.
Upstream bug assigned to lzap
Upstream bug component is Provisioning Templates
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17083 has been resolved.
QA NOTES: 1) Create invalid host (e.g. wrong name or MAC address) 2) Observe WARN log messages: Not queueing Nic::Managed: ["MAC address can't be blank", "Domain can't be blank", "Domain can't find domain with this id"] 3) Those log messages will be either in APP logger or in SQL depending on another patch merged (used to be SQL logger, now it should be APP logger). If it is still in SQL logger it is VERIFIED since this BZ did not change this behavior.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2927