On 12 June 2015 at 14:34, Mark Brown broonie@kernel.org wrote:
On Fri, Jun 12, 2015 at 01:59:31PM +0300, Fathi Boudra wrote:
The lab configuration has updated boot_cmds to match the new firmware. Most likely the fix here is to get rid of the custom boot_cmds used by the LAVA job definition in order to use the lab configuration, which is good now... until next firmware upgrade that will break the UEFI menu...
Well, presumably when there's a new firmware update the machine integration rather than the jobs should be updated?
Both. The lab configuration is updated and if the LAVA job definition contains custom boot_cmds, it has to be updated as well. You can submit a build job using a specific firmware and use custom boot_cmds for this specific firmware.
Lesson learned: when a new firmware is deployed and the boot_cmds are updated, review the LAVA job definitions and update them if necessary.