I don't like it, but I don't feel like either of the cited criteria[0][1] apply. Systemd is in general capable of starting and stopping services, and I don't really think this is "basic functionality". Following the link to the CoreOS issue it seems like this can be worked around by different methods if all else fails.

BetaBlocker -1
BetaFE +1

I think we're trying to stretch the service manipulation criterion too far here. Yes, systemd fails to start/stop/enable/disable a correctly-defined service. But only in this rather particular instance, and it is generally able to handle other services perfectly fine.

That said, it's certainly an unfortunate bug.

BetaBlocker -1

BetaBlocker -1

I even have not noticed that something like this is happening on any of my F36s, so

BetaBlocker -1

Yeah, I'm overall:

BetaBlocker -1

on this. the systemd criterion gets closer than the original cited one, but I still think it's probably not a blocker issue.

AGREED RejectedBetaBlocker

The following votes have been closed:

• Rejected BetaBlocker (+0, 0, -5)
  • -1 by nielsenb, catanzaro, frantisekz, lruzicka, adamwill

I even have not noticed that something like this is happening on any of my F36s, so

Note to hit this you need to provide kernel arguments that manipulate networking. nameserver= ip= rd.neednet=1 etc..

AGREED AcceptedBetaFE

Discussed during the 2022-03-14 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedFreezeException (Beta)" was made as it is a noticeable issue that cannot be fixed with an update.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-14/f36-blocker-review.2022-03-14-16.01.txt

The following votes have been closed:

• Accepted BetaFreezeException (+1, 0, -0)
  • +1 by nielsenb

Release F36 is no longer tracked by BlockerBugs, closing this ticket.