Bug 1388738 - Strategy needed to find new/missed advisories in case of down time
Summary: Strategy needed to find new/missed advisories in case of down time
Keywords:
Status: NEW
Alias: None
Product: rpm-test-trigger
Classification: Community
Component: general
Version: unreleased
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard:
Depends On: 1358534
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 04:45 UTC by Roman Joost
Modified: 2017-08-07 09:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Roman Joost 2016-10-26 04:45:19 UTC 
In case the rpm-test-trigger service is down (e.g. after crash) for a certain period of time (e.g. 60s to hours), we'll need a strategy to find advisories which changed state during the down time to scheduled tests.
Comment 1 Roman Joost 2016-10-27 01:06:36 UTC 
We need structured results implemented by the Errata team to implement this. See Bug 1342878
Comment 2 Roman Joost 2016-11-22 23:54:12 UTC 
We had a discussion about this to use durable queues. But we came to the conclusion that this might not be a reliable solution, since message queues might fail in times of down time as well.

Perhaps it can be as simple as: query ET for new items without a test result recorded.
Comment 5 Jan Hutař 2017-08-07 09:10:49 UTC 
Anyway, no matter if https://git.beaker-project.org/cgit/rpm-test-trigger/ is going to consume errata or builds, it still needs to have some stored value which would say what errata/builds were already processed or what was the last time it got any command right? (I'm just trying to figure out what is the objective here, sorry for dull questions)

In case of Koji/Brew, we might save taskID?

$ koji list-tasks --channel default
ID       Pri  Owner                State    Arch       Name
21083515 20   ellert               OPEN     noarch     build (rawhide, root-6.10.04-1.fc27.src.rpm)
21083520 19   ellert               OPEN     aarch64     +buildArch (root-6.10.04-1.fc27.src.rpm, aarch64)
21083522 19   ellert               OPEN     armhfp      +buildArch (root-6.10.04-1.fc27.src.rpm, armv7hl)
21083524 19   ellert               OPEN     i386        +buildArch (root-6.10.04-1.fc27.src.rpm, i686)
21085114 20   rjones               OPEN     noarch     build (f27-ocaml2, /rpms/ocaml:59545eed91afae7ab19d8010e3ea964372653614)
21085164 19   rjones               OPEN     aarch64     +buildArch (ocaml-4.05.0-2.fc27.src.rpm, aarch64)
[...]
Note You need to log in before you can comment on or make changes to this bug.