The ActivationPolicy= parameter was backported in bug 1664844, but when this is set to down (or always-down or manual) without also specifying RequiredForOnline=no, then there is a hang at boot waiting for the network to finish coming online.
[test case]
With the latest systemd, which includes support for ActivationPolicy=, configure an interface with ActivationPolicy=down and reboot. The boot will be delayed waiting for that interface.
[regression potential]
any regression would likely cause the system to encounter delay at boot, or to boot before configured interface(s) are fully online at boot, or to fail to correctly/fully configure interface(s).
[scope]
this is needed for all releases
[other info]
this is only needed for convenience, as any configuration using ActivationPolicy=down can also easily add RequiredForOnline=no
[impact]
The ActivationPolicy= parameter was backported in bug 1664844, but when this is set to down (or always-down or manual) without also specifying RequiredForOnli ne=no, then there is a hang at boot waiting for the network to finish coming online.
[test case]
With the latest systemd, which includes support for ActivationPolicy=, configure an interface with ActivationPolic y=down and reboot. The boot will be delayed waiting for that interface.
[regression potential]
any regression would likely cause the system to encounter delay at boot, or to boot before configured interface(s) are fully online at boot, or to fail to correctly/fully configure interface(s).
[scope]
this is needed for all releases
[other info]
this is only needed for convenience, as any configuration using ActivationPolic y=down can also easily add RequiredForOnli ne=no