QA » openQA Project

I looked around on openqaworker4 to see the current setup. If I understood correctly, the problem is that both openqa-worker-plain@.service and openqa-worker-auto-restart@.service are PartOf=openqa-worker.target. The easy workaround would be to mask the other (unused) service, which if I interpret the history correctly was done on that particular worker, we can document this as the solution. However I believe we can improve also by introducing Conflicts= in our unit files. According to documentation:

If a unit has a Conflicts= setting on another unit, starting the former will stop the latter and vice versa.

This should at least prevent both services to be running simultaneously. In our case, we are starting both services so the following applies.

If unit A that conflicts with unit B is scheduled to be started at the same time as B, the transaction will either fail (in case both are required parts of the transaction) or be modified to be fixed (in case one or both jobs are not a required part of the transaction). In the latter case, the job that is not required will be removed, or in case both are not required, the unit that conflicts will be started and the unit that is conflicted is stopped.

I will need to test the behavior and where to put the Conflicts= for the best result.

Setting due date based on mean cycle time of SUSE QE Tools

I did some tests, now the manual activation of openqa-worker-auto-restart@X.service will stop the conflicting openqa-worker-plain@X.service before starting and vice versa. Activating the worker target did start the missing services (via openqa-worker@X.service symlink), but did not start the conflicting one.