Project

General

Profile

Actions

Feature #10467

closed

gracefully fail jobs if packages are not found

Added by Zack Cerza over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:

Description

This was inspired by #10112. It was raised that refusing to schedule entire runs because one of the required distros is missing packages is not ideal.

Initially I thought it might be good enough to schedule those jobs whose packages were already present, and email a warning for the others. Yuri then added that it would be nice to have the doomed jobs still present in pulpito, so that we could see what we were missing. Of course, since we still use beanstalkd and rely on it for job_id generation, that wouldn't work out so well.

But what if, instead of dropping the jobs we know will fail, we schedule them anyway - and then make them fail far earlier than they do currently?

It would mean adding similar checks to, most likely, task.internal - probably even using the functions in teuthology.suite.

Actions #1

Updated by Andrew Schoen over 9 years ago

  • Assignee set to Andrew Schoen
Actions #2

Updated by Andrew Schoen over 9 years ago

Per Zack: if --dry-run is used with teuthology-suite still fail before the run schedules. If it's not a dry run, let it schedule and then fail first thing during the run.

Actions #4

Updated by Andrew Schoen over 9 years ago

  • Status changed from New to In Progress
Actions #5

Updated by Andrew Schoen over 9 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF