| 2024-01-03 21:13:21 |
CloudRoot AB |
bug |
|
|
added bug |
| 2024-01-04 00:04:28 |
Ubuntu Foundations Team Bug Bot |
affects |
ubuntu |
systemd (Ubuntu) |
|
| 2024-01-22 17:59:20 |
Apport retracing service |
tags |
amd64 apport-package need-duplicate-check noble |
amd64 apport-package noble |
|
| 2024-01-22 17:59:21 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
| 2024-04-12 02:32:38 |
Launchpad Janitor |
systemd (Ubuntu): status |
New |
Confirmed |
|
| 2024-04-26 03:33:33 |
Daniel van Vugt |
summary |
package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 |
package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] |
|
| 2024-04-26 03:35:11 |
Daniel van Vugt |
tags |
amd64 apport-package noble |
amd64 apport-package mantic noble |
|
| 2024-04-29 20:59:30 |
Nick Rosbrook |
nominated for series |
|
Ubuntu Noble |
|
| 2024-04-29 20:59:30 |
Nick Rosbrook |
bug task added |
|
systemd (Ubuntu Noble) |
|
| 2024-04-29 20:59:43 |
Nick Rosbrook |
systemd (Ubuntu Noble): status |
New |
Triaged |
|
| 2024-04-29 20:59:56 |
Nick Rosbrook |
systemd (Ubuntu Noble): importance |
Undecided |
High |
|
| 2024-04-29 20:59:59 |
Nick Rosbrook |
systemd (Ubuntu Noble): assignee |
|
Nick Rosbrook (enr0n) |
|
| 2024-04-29 21:00:36 |
Nick Rosbrook |
tags |
amd64 apport-package mantic noble |
amd64 apport-package foundations-todo mantic noble systemd-sru-next |
|
| 2024-04-30 13:35:26 |
Nick Rosbrook |
tags |
amd64 apport-package foundations-todo mantic noble systemd-sru-next |
amd64 apport-package mantic noble systemd-sru-next |
|
| 2024-05-17 08:45:25 |
Nick Rosbrook |
systemd (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2024-05-17 09:53:35 |
Nick Rosbrook |
description |
upgraded from 22.04 -> 24.04
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Jan 3 21:06:55 2024
ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-02-27 (311 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
dpkg 1.22.1ubuntu5
apt 2.7.6
SourcePackage: systemd
Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago)
mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 |
[Impact]
For users that disabled the stub-resolver, and in doing so also created a symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf (note this is not the correct way to disable the stub-resolver), upgrading from Jammy to Noble will fail with:
cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file
This logic in systemd-resolved.postinst is guarded by a version check, and is only run on upgrades from systemd versions before 251.4-2 (which in practice means only upgrades from Jammy), and on new installs.
[Test Plan]
Start a VM or container running Jammy. Disable the stub-resolver, and create the symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf:
$ mkdir -p /etc/systemd/resolved.conf.d/
$ cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF
[Resolve]
DNSStubListener=no
EOF
$ sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
$ sudo systemctl restart systemd-resolved
Then, run an upgrade to Noble:
$ do-release-upgrade --devel
NB that currently, even devel upgrades are disabled to from Jammy to Noble, so the upgrade would need to be run as:
$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/ $ tar xf noble.tar.gz
$ ./noble
Inspect the relevant output and logs to ensure that systemd-resolved was upgraded successfully during the upgrade.
[Where problems could occur]
The fix is to make such a failure non-fatal. This is safe because although manually creating this symlink is not necessary, it will not impact the operation of systemd-resolved. Hence, failing to make this cp will not impact the user. Later in the postinst, we force the new symlink anyways.
If something was wrong with the change, it would likely cause the systemd-resolved.postinst to fail a different way.
[Original Description]
upgraded from 22.04 -> 24.04
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Jan 3 21:06:55 2024
ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-02-27 (311 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
dpkg 1.22.1ubuntu5
apt 2.7.6
SourcePackage: systemd
Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago)
mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 |
|
| 2024-05-17 10:06:05 |
Nick Rosbrook |
description |
[Impact]
For users that disabled the stub-resolver, and in doing so also created a symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf (note this is not the correct way to disable the stub-resolver), upgrading from Jammy to Noble will fail with:
cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file
This logic in systemd-resolved.postinst is guarded by a version check, and is only run on upgrades from systemd versions before 251.4-2 (which in practice means only upgrades from Jammy), and on new installs.
[Test Plan]
Start a VM or container running Jammy. Disable the stub-resolver, and create the symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf:
$ mkdir -p /etc/systemd/resolved.conf.d/
$ cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF
[Resolve]
DNSStubListener=no
EOF
$ sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
$ sudo systemctl restart systemd-resolved
Then, run an upgrade to Noble:
$ do-release-upgrade --devel
NB that currently, even devel upgrades are disabled to from Jammy to Noble, so the upgrade would need to be run as:
$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/ $ tar xf noble.tar.gz
$ ./noble
Inspect the relevant output and logs to ensure that systemd-resolved was upgraded successfully during the upgrade.
[Where problems could occur]
The fix is to make such a failure non-fatal. This is safe because although manually creating this symlink is not necessary, it will not impact the operation of systemd-resolved. Hence, failing to make this cp will not impact the user. Later in the postinst, we force the new symlink anyways.
If something was wrong with the change, it would likely cause the systemd-resolved.postinst to fail a different way.
[Original Description]
upgraded from 22.04 -> 24.04
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Jan 3 21:06:55 2024
ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-02-27 (311 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
dpkg 1.22.1ubuntu5
apt 2.7.6
SourcePackage: systemd
Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago)
mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 |
[Impact]
For users that disabled the stub-resolver, and in doing so also created a symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf (note this is not the correct way to disable the stub-resolver), upgrading from Jammy to Noble will fail with:
cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file
This logic in systemd-resolved.postinst is guarded by a version check, and is only run on upgrades from systemd versions before 251.4-2 (which in practice means only upgrades from Jammy), and on new installs.
[Test Plan]
Start a VM or container running Jammy. Disable the stub-resolver, and create the symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf:
$ mkdir -p /etc/systemd/resolved.conf.d/
$ cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF
[Resolve]
DNSStubListener=no
EOF
$ ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
$ systemctl restart systemd-resolved
Then, run an upgrade to Noble:
$ do-release-upgrade --devel
NB that currently, even devel upgrades are disabled to from Jammy to Noble, so the upgrade would need to be run as:
$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/
$ tar xf noble.tar.gz
$ ./noble
Inspect the relevant output and logs to ensure that systemd-resolved was upgraded successfully during the upgrade.
[Where problems could occur]
The fix is to make such a failure non-fatal. This is safe because although manually creating this symlink is not necessary, it will not impact the operation of systemd-resolved. Hence, failing to make this cp will not impact the user. Later in the postinst, we force the new symlink anyways.
If something was wrong with the change, it would likely cause the systemd-resolved.postinst to fail a different way.
[Original Description]
upgraded from 22.04 -> 24.04
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Jan 3 21:06:55 2024
ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-02-27 (311 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
dpkg 1.22.1ubuntu5
apt 2.7.6
SourcePackage: systemd
Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago)
mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 |
|
| 2024-05-17 10:06:51 |
Nick Rosbrook |
description |
[Impact]
For users that disabled the stub-resolver, and in doing so also created a symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf (note this is not the correct way to disable the stub-resolver), upgrading from Jammy to Noble will fail with:
cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file
This logic in systemd-resolved.postinst is guarded by a version check, and is only run on upgrades from systemd versions before 251.4-2 (which in practice means only upgrades from Jammy), and on new installs.
[Test Plan]
Start a VM or container running Jammy. Disable the stub-resolver, and create the symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf:
$ mkdir -p /etc/systemd/resolved.conf.d/
$ cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF
[Resolve]
DNSStubListener=no
EOF
$ ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
$ systemctl restart systemd-resolved
Then, run an upgrade to Noble:
$ do-release-upgrade --devel
NB that currently, even devel upgrades are disabled to from Jammy to Noble, so the upgrade would need to be run as:
$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/
$ tar xf noble.tar.gz
$ ./noble
Inspect the relevant output and logs to ensure that systemd-resolved was upgraded successfully during the upgrade.
[Where problems could occur]
The fix is to make such a failure non-fatal. This is safe because although manually creating this symlink is not necessary, it will not impact the operation of systemd-resolved. Hence, failing to make this cp will not impact the user. Later in the postinst, we force the new symlink anyways.
If something was wrong with the change, it would likely cause the systemd-resolved.postinst to fail a different way.
[Original Description]
upgraded from 22.04 -> 24.04
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Jan 3 21:06:55 2024
ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-02-27 (311 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
dpkg 1.22.1ubuntu5
apt 2.7.6
SourcePackage: systemd
Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago)
mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 |
[Impact]
For users that disabled the stub-resolver, and in doing so also created a symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf (note this is not the correct way to disable the stub-resolver), upgrading from Jammy to Noble will fail with:
cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file
This logic in systemd-resolved.postinst is guarded by a version check, and is only run on upgrades from systemd versions before 251.4-2 (which in practice means only upgrades from Jammy), and on new installs.
[Test Plan]
Start a VM or container running Jammy. Disable the stub-resolver, and create the symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf:
$ mkdir -p /etc/systemd/resolved.conf.d/
$ cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF
[Resolve]
DNSStubListener=no
EOF
$ ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
$ systemctl restart systemd-resolved
Then, run an upgrade to Noble:
$ do-release-upgrade --devel
NB that currently, even devel upgrades are disabled to from Jammy to Noble, so the upgrade would need to be run as:
$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
$ tar xf noble.tar.gz
$ ./noble
Inspect the relevant output and logs to ensure that systemd-resolved was upgraded successfully during the upgrade.
[Where problems could occur]
The fix is to make such a failure non-fatal. This is safe because although manually creating this symlink is not necessary, it will not impact the operation of systemd-resolved. Hence, failing to make this cp will not impact the user. Later in the postinst, we force the new symlink anyways.
If something was wrong with the change, it would likely cause the systemd-resolved.postinst to fail a different way.
[Original Description]
upgraded from 22.04 -> 24.04
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Jan 3 21:06:55 2024
ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-02-27 (311 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
dpkg 1.22.1ubuntu5
apt 2.7.6
SourcePackage: systemd
Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago)
mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 |
|
| 2024-05-17 14:31:40 |
Nick Rosbrook |
systemd (Ubuntu Noble): status |
Triaged |
In Progress |
|
| 2024-05-20 17:55:15 |
Marco Trevisan (Treviño) |
bug |
|
|
added subscriber Marco Trevisan (Treviño) |
| 2024-05-20 18:23:11 |
CloudRoot AB |
removed subscriber CloudRoot AB |
|
|
|
| 2024-05-22 09:45:28 |
Łukasz Zemczak |
systemd (Ubuntu Noble): status |
In Progress |
Fix Committed |
|
| 2024-05-22 09:45:30 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-05-22 09:45:32 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2024-05-22 09:45:37 |
Łukasz Zemczak |
tags |
amd64 apport-package mantic noble systemd-sru-next |
amd64 apport-package mantic noble systemd-sru-next verification-needed verification-needed-noble |
|
| 2024-05-22 15:37:31 |
Nick Rosbrook |
tags |
amd64 apport-package mantic noble systemd-sru-next verification-needed verification-needed-noble |
amd64 apport-package mantic noble systemd-sru-next verification-done-noble verification-needed |
|
| 2024-06-04 19:47:26 |
Launchpad Janitor |
systemd (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
| 2024-06-04 19:47:37 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
