Bug 874387

Summary: system is marked broken if configure_netboot command fails due to missing image
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: schedulerAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: medium    
Version: 0.9CC: dcallagh, dowang, ebaak, rjoost, tools-bugs
Target Milestone: 23.3Keywords: Patch, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Misc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-07 06:44:51 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 Dan Callaghan 2012-11-08 04:03:01 UTC 
Currently a system is unconditionally marked broken if any of its "power" commands fail. Except these commands now include configure_netboot, which fetches kernel+initrd images from the distro tree. If that fails (for example because the tree has been removed but beaker_expire_distros hasn't picked up on it yet) the system will be marked broken, even though there's nothing wrong with it.

The difficult part here is that *some* failures from configure_netboot (for example inability to resolve the system's FQDN, or insufficient permissions to write a pxelinux config for it) do indicate an unrecoverable problem which should cause the system to be taken out of service until an administrator can correct them. But some other failures from configure_netboot, like an HTTP error fetching the images, are a problem with the distro tree and do not affect the system itself. We might need some way to distinguish these.
Comment 2 Dan Callaghan 2016-09-19 04:04:58 UTC 
http://gerrit.beaker-project.org/5239
Comment 5 Dan Callaghan 2016-11-07 06:44:51 UTC 
Beaker 23.3 has been released.