ctly due to a requirement dependency such as
Wants= or Requires=) is ordered before some other unit (via After=/Before=),
but that latter unit is also ordered before the former by some dependency
(either directly or indirectly).

Ordering cycles consist of at least two units, but might involve many
more. They generally indicate a bug in the unit definitions, as a unit
conceptually cannot be run both before and after some other unit, it must be
strictly ordered either before or after.

The ordering cycle is shown in the log message. An attempt will be made to
remove unit jobs from the transaction in order to make the transaction succeed
at least partially. Note that such cycle breaking is not going to correct the
issue, it is just an attempt to make the outcome less problematic.

The correct fix is to analyze the cycle in question and then break the cycle at
the right place by removing the right After= or Before= lines from one or more
of the involved unit files.