See also bug 2078555
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2078852
Title:
systemd-resolved was re-enabled during upgrade from 22.04 to 24.04
Status in systemd package in Ubuntu:
New
Bug description:
systemd-resolved was disabled on my servers because i use a different
DNS setup.
During upgrade from 22.04 to 24.04, systemd-resolved was re-enabled by
the upgrade process. This would have lead to downtime of some services
as well other problems, because local DNS lookups failed to use the
correct server. Re-enabling systemd-resolved also overwrote
/etc/resolv.conf, which had to be restored from backups.
This has now been a so long standing problem (going back many LTS
releases) that i have a script for that called the "systemd-
castrator".
It basically does:
systemctl disable systemd-resolved
systemctl stop systemd-resolved
and then restores the correct resolv.conf from my source code management.
It would be nice if this problem could be solved by the Ubuntu team.
E.g. "if a systemd service is manually disabled before the upgrade, it
*stays* disabled after the upgrade".
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 255.4-1ubuntu8.4
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Sep 3 20:00:16 2024
SourcePackage: systemd
UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago)
mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078852/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
