Comment # 2 on bug 1191616 from Dominique Leuenberger

(In reply to Jiri Slaby from comment #1)
> I assume this was an one-shot issue and is hopefully fixed?

I was a two-off (openQA showed the issue twice - but never again since
20211011)

so, thanks for the ping, let's close this and assume we won't ever see it again