-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instance upgraded from focal to noble is missing systemd-resolved #7464
Comments
|
Thanks, I extracted the raw package lists (
Looking up all the individual packages now. |
[skipping all the other lib* packages because they're dependencies]
On mon specifically, we have: -media-types
+mime-support media-types replaced mime-support, but we missed the transitional package, so we'll have to do it manually. Not sure what dependency is pulled it in though and why app wouldn't have it. |
In focal, the systemd-resolved component was included in the main
This meant there was no way to uninstall it, so we only stopped it. In noble, it was split out into a separate package. But nothing explicitly depends on it, so we don't install it during upgrade, and lose it. Knowing that, my preference would be to have the I can put a PR in for this after figuring out the systemd-hwe-hwdb thing and nftables. On the QA side, I think we should add a step like, "After an in-place upgrade, all the |
On my upgraded mon server, I see mime-support being removed, so it's weird that yours still has it. |
Currently systemd-hwe-hwdb contains exactly one udev rule:
I think it's easiest just to install it the same way we're going to do with systemd-resolved. |
These two packages are installed on fresh systems, but not on upgrades because they were split out of the systemd package. Set the dependency ourselves to make sure it's always pulled in. In the future once all SecureDrops are on noble, we can uninstall systemd-resolved entirely instead of merely stopping it. Fixes #7464.
These two packages are installed on fresh systems, but not on upgrades because they were split out of the systemd package. Set the dependency ourselves to make sure it's always pulled in. In the future once all SecureDrops are on noble, we can uninstall systemd-resolved entirely instead of merely stopping it. Fixes #7464.
These two packages are installed on fresh systems, but not on upgrades because they were split out of the systemd package. Set the dependency ourselves to make sure it's always pulled in. In the future once all SecureDrops are on noble, we can uninstall systemd-resolved entirely instead of merely stopping it. Fixes #7464.
We don't use systemd-resolved and during the focal -> noble migration, it gets dropped since it was split out to a separate package. Now that we can remove it entirely, let's have noble installs absent the package instead of merely stopping the systemd unit. Fixes #7464.
We don't use systemd-resolved and during the focal -> noble migration, it gets dropped since it was split out to a separate package. Now that we can remove it entirely, let's have noble installs absent the package instead of merely stopping the systemd unit. Fixes #7464.
Description
Doing an in-place upgrade to noble results in the system missing systemd-resolved. A fresh noble install will still have it.
Steps to Reproduce
systemctl status systemd-resolved
- it'll error./securedrop-admin install
- it will error on the step about stopping systemd-resolved.Expected Behavior
Either:
And,
./securedrop-admin install
should work post-upgrade.Next steps
dpkg -l
from both a fresh noble install and an upgrade and see if anything else is missing (ideally check both app and mon)The text was updated successfully, but these errors were encountered: