Pavel Raiskup

1. we take first machine 2. the machine fails too early (the build doesn't start), so the ticket stays in `starting` 3. no message to BUS is sent either (automation...

This seems to rarely happen, therefore we give this "2years" category. Please report if this happens frequently.

This is the remaining architecture we do not have powerful builders for.

@team, has this filtering ever been working?

Triage time: @praiskup: is this actually ever used for filtering? What tool we can take a look at for inspiration how it should be implemented? // @xsuchy suggests asking @msrb...

We are using https://github.com/fedora-copr/copr/blob/74c63e9f3bc33e0301f1c023f1e16920dd18a26b/backend/run/copr-repo#L147-L149 So `createrepo_c` definitely knows about the comps file... I'm also tagging it as a PULP-related issue (once moved to PULP, we might or might not have...

This should be relatively easy to implement as the `copr-rpmbuild` plugin. We already have e.g. one for [Fedora Review](https://github.com/fedora-copr/copr/blob/main/rpmbuild/copr_rpmbuild/automation/fedora_review.py). Integrated [here](https://github.com/fedora-copr/copr/blob/18fb9556abe71ce7230b489c24451b3625e38ab5/rpmbuild/copr_rpmbuild/automation/__init__.py#L16).

As I understood it from @TomasTomecek report, we need to obtain a logs from previously succeeding log. results. That could be done via something like: ``` $ copr list-packages @copr/copr-dev...

Thank you for the report, we'll take a look in the future.

- the pulp_installer way is outdated, but fixed for now in ansible.git - ipv6 fixed -> nagios happy - re-started on RHEL9 - blog post