Bug 874387 - system is marked broken if configure_netboot command fails due to missing image
Summary: system is marked broken if configure_netboot command fails due to missing image
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.9
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 23.3
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard: Misc
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-08 04:03 UTC by Dan Callaghan
Modified: 2018-02-06 00:41 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-11-07 06:44:51 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.