Add postgresql service to requirements

[baierjan]

If this unit gets activated, the units listed in Requires= will be activated as well. If one of the other units fails to activate, and an ordering dependency After= on the failing unit is set, this unit will not be started. Besides, with or without specifying After=, this unit will be stopped (or restarted) if one of the other units is explicitly stopped (or restarted).

Reference: https://progress.opensuse.org/issues/122578

[kraih]

After checking the systemd docs, the combination of After and Requires looks correct to me.

[Martchus]

What about the other services needing postgresql? Shouldn't they be treated in the same way?

[kraih]

What about the other services needing postgresql? Shouldn't they be treated in the same way?

Or they have a Requires on the webui.

[perlpunk]

I retriggered CircleCI jobs, we had various problems there

[okurz]

hm, this introduces a strong requirement on PostgreSQL. But what for hosts that don't actually run the database but use a remote database that we support just as well? I am not sure if https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Wants=would also help for stopping services but one could try.

[baierjan]

Right, this will require to have the webui on the database server. Maybe we can go around by dropping a symlink into openqa-webui.service.requires directory if postgresql.service is detected; or having multiple service file for each use-case, similar to our multiple worker setup (openqa-worker-plain vs. openqa-worker-auto-restart). I am afraid that both use-cases cannot be implemented inside one service file. What about having something like openqa-webui-standalone.service?