Bug 1388104

Summary: TFTP "built" orchestration is skipped when there is an AR error
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: Provisioning TemplatesAssignee: Lukas Zapletal <lzap>
Status: CLOSED ERRATA QA Contact: Perry Gagne <pgagne>
Severity: medium Docs Contact:
Priority: high    
Version: 6.2.2CC: garron.cartner, inecas, jcallaha, lzap, mhulan, mlele, oshtaier, pgagne
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/17083
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 18:58:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukas Zapletal 2016-10-24 13:17:02 UTC
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.

Comment 2 Bryan Kearney 2016-10-25 08:20:12 UTC
Upstream bug assigned to lzap

Comment 3 Bryan Kearney 2016-10-25 08:20:14 UTC
Upstream bug component is Provisioning Templates

Comment 5 Satellite Program 2018-02-15 11:21:50 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17083 has been resolved.

Comment 8 Lukas Zapletal 2018-08-07 09:47:54 UTC
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.

Comment 10 Bryan Kearney 2018-10-16 18:58:56 UTC
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