Bug 1369981

Summary: Reschedule runs
Product: [Community] rpm-test-trigger Reporter: Roman Joost <rjoost>
Component: generalAssignee: beaker-dev-list
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unreleasedCC: jhutar, jorris
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Roman Joost 2016-08-24 23:46:58 UTC
It is important to re-schedule test runs in case of failure. There is currently no UI available (do we need one?) or any functionality of indicating a rerun.
In case of an infrastructure error, ET users will need to have the ability to re-schedule runs.

Comment 1 Dan Callaghan 2016-10-26 04:48:16 UTC
I guess this is tied to how we will be reporting results back to Errata Tool.

A related problem is that we will need a way for rpm-test-trigger to query ET to find any untested advisories when it starts up (since if it's restarted, or crashes or goes down for any other reason, there will be a time period that it is not listening for notifications on the message bus and could potentially miss advisories it should be testing).

Comment 2 Dan Callaghan 2016-10-26 06:21:35 UTC
(In reply to Dan Callaghan from comment #1)

This is bug 1388738.

Comment 4 Roman Joost 2017-08-08 01:15:03 UTC
The rpmdeplint tool is supposed to run against a brew build, but the middleware which picks the right brew builds, figures out which repositories to test against and publish the test results on the message bus is rpm-test-trigger.