But all the recent notifications greenwave sent are related to compose, not to the packages tested: https://apps.fedoraproject.org/datagrepper/raw?category=greenwave&rows_per_page=1&delta=127800
@gnaponie @lucarval any idea?
I actually see those two messages: https://apps.fedoraproject.org/datagrepper/id?id=2019-be4e6c34-3372-4fb2-9144-dfdae1e0256b&is_raw=true&size=extra-large https://apps.fedoraproject.org/datagrepper/id?id=2019-a5dfd9a1-0fc3-4b40-9da2-1d2b2679650c&is_raw=true&size=extra-large
Beside those, checking the logs for previous cases I see that the decision didn't change. Unfortunately I don't a timestamp of when the log got printed. This is a bit uncomfortable for the debugging. I'm wondering why that's not printed...
Everything seems fine. It might just be that was a bit slow to reply, I see the result has timestamp "2019-09-09T15:43:10.424750" and the greenwave message was at "2019-09-09 15:51:22 UTC", but without timestamps in the logs it is a bit hard to see what was the slow point.
Re-running my monitoring script this morning, I've noticed that rdbsync was down, so I've restarted it.
On the greenwave front, it looks like things are going fine, so I guess @gnaponie was correct and it was just slow yesterday (my script waits for 15 minutes then mark the step as failed)
Let's close this ticket as currently things are working! :)
Thanks for your help @gnaponie ! :)
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.