#2760 Consider bug #2032085 (systemd-resolved not being used as expected) as a FESCo blocker
Closed: Accepted 2 years ago by ngompa. Opened 2 years ago by adamwill.

At last week's blocker review meeting, we reviewed https://bugzilla.redhat.com/show_bug.cgi?id=2032085 , and concluded it was not really a blocker under the release criteria, but it seemed there would be a strong case for FESCo to declare it a blocker given that it constitutes a substantial unintended variance between editions and away from how things are intended to work. So, filing this ticket to bring it to FESCo's attention for consideration. Thanks.


You have my sword, ehm... +1.

Metadata Update from @churchyard:
- Issue set to the milestone: Fedora Linux 36

2 years ago

Additional context is the approved system-wide change to use resolved by default in Fedora 33.

This is one of those nasty hydra bugs which are still alive after a dozen fixes in various places.

+1 to making it a hill to die on.

I'll add that migrating users from the incorrect configuration to the correct configuration is difficult or impossible to do without causing unexpected breakage for users who intentionally configure their systems differently than our defaults. So even a single messed up release is quite problematic. Sounds like we've now had several. :/

Metadata Update from @churchyard:
- Issue tagged with: pending announcement

2 years ago

Metadata Update from @ngompa:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Attachments 1
Attached 2 years ago View Comment