| 2021-05-31 09:34:45 |
reemguin |
bug |
|
|
added bug |
| 2021-07-17 03:28:20 |
Launchpad Janitor |
tang (Ubuntu): status |
New |
Confirmed |
|
| 2021-07-17 03:30:21 |
Andy Sayler |
bug |
|
|
added subscriber Andy Sayler |
| 2023-04-03 06:05:53 |
Rafael Lopez |
nominated for series |
|
Ubuntu Focal |
|
| 2023-04-03 06:05:53 |
Rafael Lopez |
bug task added |
|
tang (Ubuntu Focal) |
|
| 2023-04-03 06:06:08 |
Rafael Lopez |
tang (Ubuntu Focal): status |
New |
Confirmed |
|
| 2023-04-05 03:43:26 |
Rafael Lopez |
attachment added |
|
lp1930203-focal.debdiff https://bugs.launchpad.net/ubuntu/+source/tang/+bug/1930203/+attachment/5661083/+files/lp1930203-focal.debdiff |
|
| 2023-04-05 03:44:03 |
Rafael Lopez |
tang (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2023-04-05 03:44:15 |
Rafael Lopez |
tang (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2023-04-05 03:44:29 |
Rafael Lopez |
tang (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2023-04-05 03:44:35 |
Rafael Lopez |
tang (Ubuntu Focal): assignee |
|
Rafael Lopez (rafael.lopez) |
|
| 2023-04-05 03:52:34 |
Rafael Lopez |
tags |
|
sts |
|
| 2023-04-11 02:06:46 |
Rafael Lopez |
description |
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC. |
[ Impact ]
The enabled tangd.socket service starting on boot is unreliable, due to
the start job being deleted as a result of a systemd ordering cycle.
Users relying on tangd to be started on boot have to manually
check that the service started after a reboot, or implement custom
workarounds to ensure the same.
The fix removes the opportunity for an ordering cycle to occur in the
unit by moving dependencies out of the socket unit and changing the
WantedBy to sockets.target (what it should be for a socket unit).
[ Test Plan ]
The bug is reproduced by installing 'tang' (version 7-1build1) on a machine running Focal 20.04-6 or earlier. The unit should be enabled by default.
`sudo apt install tang`
After installing the package, ensure the tang service is enabled.
`systemctl is-enabled tang`
reboot the server, and check that the tangd.socket service is running
`systemctl status tangd.socket`
The service may or may not be running depending how systemd ordered
the startup jobs for this boot. You can simply repeat rebooting the server
and eventually at some point the service will not come up after a boot.
Regardless if the service is started on boot, you can see similar messages
to these in the system log:
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on tangd-update.service/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on basic.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on sockets.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
[ Where problems could occur ]
The tang service may not start correctly. If it is made to be part of
a systemd dependency chain with other services, those services may also
be impacted/fail to start.
Since the systemd units are altered, even if the service starts it may
change the way the tang service was originally configured to run. Other
applications/clients relying on the tang service may experiences issues
if the service is not running as originally configured in prior release.
[ Other Info ]
The proposed fix is derived from an upstream fix:
https://github.com/latchset/tang/pull/42/files
There is a minor modification to the diff since the Ubuntu package source file for tangd.socket has a '.in' extension, upstream does not.
Original bug text below:
----------
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC.
---------- |
|
| 2023-04-11 02:14:32 |
Rafael Lopez |
bug |
|
|
added subscriber SE ("STS") Sponsors |
| 2023-04-11 02:28:27 |
Rafael Lopez |
description |
[ Impact ]
The enabled tangd.socket service starting on boot is unreliable, due to
the start job being deleted as a result of a systemd ordering cycle.
Users relying on tangd to be started on boot have to manually
check that the service started after a reboot, or implement custom
workarounds to ensure the same.
The fix removes the opportunity for an ordering cycle to occur in the
unit by moving dependencies out of the socket unit and changing the
WantedBy to sockets.target (what it should be for a socket unit).
[ Test Plan ]
The bug is reproduced by installing 'tang' (version 7-1build1) on a machine running Focal 20.04-6 or earlier. The unit should be enabled by default.
`sudo apt install tang`
After installing the package, ensure the tang service is enabled.
`systemctl is-enabled tang`
reboot the server, and check that the tangd.socket service is running
`systemctl status tangd.socket`
The service may or may not be running depending how systemd ordered
the startup jobs for this boot. You can simply repeat rebooting the server
and eventually at some point the service will not come up after a boot.
Regardless if the service is started on boot, you can see similar messages
to these in the system log:
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on tangd-update.service/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on basic.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on sockets.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
[ Where problems could occur ]
The tang service may not start correctly. If it is made to be part of
a systemd dependency chain with other services, those services may also
be impacted/fail to start.
Since the systemd units are altered, even if the service starts it may
change the way the tang service was originally configured to run. Other
applications/clients relying on the tang service may experiences issues
if the service is not running as originally configured in prior release.
[ Other Info ]
The proposed fix is derived from an upstream fix:
https://github.com/latchset/tang/pull/42/files
There is a minor modification to the diff since the Ubuntu package source file for tangd.socket has a '.in' extension, upstream does not.
Original bug text below:
----------
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC.
---------- |
[ Impact ]
The enabled tangd.socket service starting on boot is unreliable, due to
the start job being deleted as a result of a systemd ordering cycle.
Users relying on tangd to be started on boot have to manually
check that the service started after a reboot, or implement custom
workarounds to ensure the same.
The fix removes the opportunity for an ordering cycle to occur in the
unit by moving dependencies out of the socket unit and changing the
WantedBy to sockets.target (what it should be for a socket unit).
[ Test Plan ]
The bug is reproduced by installing 'tang' (version 7-1build1) on a machine running Focal 20.04.6 or earlier. The unit should be enabled by default.
`sudo apt install tang`
After installing the package, ensure the tang service is enabled.
`systemctl is-enabled tang`
reboot the server, and check that the tangd.socket service is running
`systemctl status tangd.socket`
The service may or may not be running depending how systemd ordered
the startup jobs for this boot. You can simply repeat rebooting the server
and eventually at some point the service will not come up after a boot.
Regardless if the service is started on boot, you can see similar messages
to these in the system log:
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on tangd-update.service/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on basic.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on sockets.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
[ Where problems could occur ]
The tang service may not start correctly. If it is made to be part of
a systemd dependency chain with other services, those services may also
be impacted/fail to start.
Since the systemd units are altered, even if the service starts it may
change the way the tang service was originally configured to run. Other
applications/clients relying on the tang service may experiences issues
if the service is not running as originally configured in prior release.
[ Other Info ]
The proposed fix is derived from an upstream fix:
https://github.com/latchset/tang/pull/42/files
There is a minor modification to the diff since the Ubuntu package source file for tangd.socket has a '.in' extension, upstream does not.
Original bug text below:
----------
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC.
---------- |
|
| 2023-04-11 10:42:48 |
Heitor Alves de Siqueira |
tags |
sts |
se-sponsor-halves sts |
|
| 2023-04-13 17:27:11 |
Heitor Alves de Siqueira |
description |
[ Impact ]
The enabled tangd.socket service starting on boot is unreliable, due to
the start job being deleted as a result of a systemd ordering cycle.
Users relying on tangd to be started on boot have to manually
check that the service started after a reboot, or implement custom
workarounds to ensure the same.
The fix removes the opportunity for an ordering cycle to occur in the
unit by moving dependencies out of the socket unit and changing the
WantedBy to sockets.target (what it should be for a socket unit).
[ Test Plan ]
The bug is reproduced by installing 'tang' (version 7-1build1) on a machine running Focal 20.04.6 or earlier. The unit should be enabled by default.
`sudo apt install tang`
After installing the package, ensure the tang service is enabled.
`systemctl is-enabled tang`
reboot the server, and check that the tangd.socket service is running
`systemctl status tangd.socket`
The service may or may not be running depending how systemd ordered
the startup jobs for this boot. You can simply repeat rebooting the server
and eventually at some point the service will not come up after a boot.
Regardless if the service is started on boot, you can see similar messages
to these in the system log:
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on tangd-update.service/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on basic.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on sockets.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
[ Where problems could occur ]
The tang service may not start correctly. If it is made to be part of
a systemd dependency chain with other services, those services may also
be impacted/fail to start.
Since the systemd units are altered, even if the service starts it may
change the way the tang service was originally configured to run. Other
applications/clients relying on the tang service may experiences issues
if the service is not running as originally configured in prior release.
[ Other Info ]
The proposed fix is derived from an upstream fix:
https://github.com/latchset/tang/pull/42/files
There is a minor modification to the diff since the Ubuntu package source file for tangd.socket has a '.in' extension, upstream does not.
Original bug text below:
----------
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC.
---------- |
[ Impact ]
The enabled tangd.socket service starting on boot is unreliable, due to
the start job being deleted as a result of a systemd ordering cycle.
Users relying on tangd to be started on boot have to manually
check that the service started after a reboot, or implement custom
workarounds to ensure the same.
The fix removes the opportunity for an ordering cycle to occur in the
unit by moving dependencies out of the socket unit and changing the
WantedBy to sockets.target (what it should be for a socket unit).
[ Test Plan ]
The bug is reproduced by installing 'tang' (version 7-1build1) on a machine running Focal 20.04.6 or earlier. The unit should be enabled by default.
`sudo apt install tang`
After installing the package, ensure the tang service is enabled.
`systemctl is-enabled tang`
reboot the server, and check that the tangd.socket service is running
`systemctl status tangd.socket`
The service may or may not be running depending how systemd ordered
the startup jobs for this boot. You can simply repeat rebooting the server
and eventually at some point the service will not come up after a boot.
Regardless if the service is started on boot, you can see similar messages
to these in the system log:
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on tangd-update.service/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on basic.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on sockets.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
[ Where problems could occur ]
The tang service may not start correctly. If it is made to be part of
a systemd dependency chain with other services, those services may also
be impacted/fail to start.
Since the systemd units are altered, even if the service starts it may
change the way the tang service was originally configured to run. Other
applications/clients relying on the tang service may experiences issues
if the service is not running as originally configured in prior release.
[ Other Info ]
The proposed fix is derived from an upstream fix:
https://github.com/latchset/tang/commit/77785125fb56
There is a minor modification to the diff since the Ubuntu package source file for tangd.socket has a '.in' extension, upstream does not.
Versions starting with v8 already contain the fix:
$ git dsc 77785125fb56
v8~9
Original bug text below:
----------
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC.
---------- |
|
| 2023-04-13 17:27:27 |
Heitor Alves de Siqueira |
description |
[ Impact ]
The enabled tangd.socket service starting on boot is unreliable, due to
the start job being deleted as a result of a systemd ordering cycle.
Users relying on tangd to be started on boot have to manually
check that the service started after a reboot, or implement custom
workarounds to ensure the same.
The fix removes the opportunity for an ordering cycle to occur in the
unit by moving dependencies out of the socket unit and changing the
WantedBy to sockets.target (what it should be for a socket unit).
[ Test Plan ]
The bug is reproduced by installing 'tang' (version 7-1build1) on a machine running Focal 20.04.6 or earlier. The unit should be enabled by default.
`sudo apt install tang`
After installing the package, ensure the tang service is enabled.
`systemctl is-enabled tang`
reboot the server, and check that the tangd.socket service is running
`systemctl status tangd.socket`
The service may or may not be running depending how systemd ordered
the startup jobs for this boot. You can simply repeat rebooting the server
and eventually at some point the service will not come up after a boot.
Regardless if the service is started on boot, you can see similar messages
to these in the system log:
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on tangd-update.service/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on basic.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on sockets.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
[ Where problems could occur ]
The tang service may not start correctly. If it is made to be part of
a systemd dependency chain with other services, those services may also
be impacted/fail to start.
Since the systemd units are altered, even if the service starts it may
change the way the tang service was originally configured to run. Other
applications/clients relying on the tang service may experiences issues
if the service is not running as originally configured in prior release.
[ Other Info ]
The proposed fix is derived from an upstream fix:
https://github.com/latchset/tang/commit/77785125fb56
There is a minor modification to the diff since the Ubuntu package source file for tangd.socket has a '.in' extension, upstream does not.
Versions starting with v8 already contain the fix:
$ git dsc 77785125fb56
v8~9
Original bug text below:
----------
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC.
---------- |
[ Impact ]
The enabled tangd.socket service starting on boot is unreliable, due to
the start job being deleted as a result of a systemd ordering cycle.
Users relying on tangd to be started on boot have to manually
check that the service started after a reboot, or implement custom
workarounds to ensure the same.
The fix removes the opportunity for an ordering cycle to occur in the
unit by moving dependencies out of the socket unit and changing the
WantedBy to sockets.target (what it should be for a socket unit).
[ Test Plan ]
The bug is reproduced by installing 'tang' (version 7-1build1) on a machine running Focal 20.04.6 or earlier. The unit should be enabled by default.
`sudo apt install tang`
After installing the package, ensure the tang service is enabled.
`systemctl is-enabled tang`
reboot the server, and check that the tangd.socket service is running
`systemctl status tangd.socket`
The service may or may not be running depending how systemd ordered
the startup jobs for this boot. You can simply repeat rebooting the server
and eventually at some point the service will not come up after a boot.
Regardless if the service is started on boot, you can see similar messages
to these in the system log:
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on tangd-update.service/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on basic.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on sockets.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
[ Where problems could occur ]
The tang service may not start correctly. If it is made to be part of
a systemd dependency chain with other services, those services may also
be impacted/fail to start.
Since the systemd units are altered, even if the service starts it may
change the way the tang service was originally configured to run. Other
applications/clients relying on the tang service may experiences issues
if the service is not running as originally configured in prior release.
[ Other Info ]
The proposed fix is derived from an upstream fix:
https://github.com/latchset/tang/commit/77785125fb56
There is a minor modification to the diff since the Ubuntu package source file for tangd.socket has a '.in' extension, upstream does not.
Versions starting with v8 already contain the fix:
$ git describe --contains 77785125fb56
v8~9
Original bug text below:
----------
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC.
---------- |
|
| 2023-04-19 23:58:20 |
Robie Basak |
tang (Ubuntu Focal): status |
In Progress |
Incomplete |
|
| 2023-04-21 03:05:39 |
Rafael Lopez |
attachment removed |
lp1930203-focal.debdiff https://bugs.launchpad.net/ubuntu/+source/tang/+bug/1930203/+attachment/5661083/+files/lp1930203-focal.debdiff |
|
|
| 2023-04-21 03:18:29 |
Rafael Lopez |
description |
[ Impact ]
The enabled tangd.socket service starting on boot is unreliable, due to
the start job being deleted as a result of a systemd ordering cycle.
Users relying on tangd to be started on boot have to manually
check that the service started after a reboot, or implement custom
workarounds to ensure the same.
The fix removes the opportunity for an ordering cycle to occur in the
unit by moving dependencies out of the socket unit and changing the
WantedBy to sockets.target (what it should be for a socket unit).
[ Test Plan ]
The bug is reproduced by installing 'tang' (version 7-1build1) on a machine running Focal 20.04.6 or earlier. The unit should be enabled by default.
`sudo apt install tang`
After installing the package, ensure the tang service is enabled.
`systemctl is-enabled tang`
reboot the server, and check that the tangd.socket service is running
`systemctl status tangd.socket`
The service may or may not be running depending how systemd ordered
the startup jobs for this boot. You can simply repeat rebooting the server
and eventually at some point the service will not come up after a boot.
Regardless if the service is started on boot, you can see similar messages
to these in the system log:
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on tangd-update.service/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on basic.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on sockets.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
[ Where problems could occur ]
The tang service may not start correctly. If it is made to be part of
a systemd dependency chain with other services, those services may also
be impacted/fail to start.
Since the systemd units are altered, even if the service starts it may
change the way the tang service was originally configured to run. Other
applications/clients relying on the tang service may experiences issues
if the service is not running as originally configured in prior release.
[ Other Info ]
The proposed fix is derived from an upstream fix:
https://github.com/latchset/tang/commit/77785125fb56
There is a minor modification to the diff since the Ubuntu package source file for tangd.socket has a '.in' extension, upstream does not.
Versions starting with v8 already contain the fix:
$ git describe --contains 77785125fb56
v8~9
Original bug text below:
----------
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC.
---------- |
[ Impact ]
The enabled tangd.socket service starting on boot is unreliable, due to
the start job being deleted as a result of a systemd ordering cycle.
Users relying on tangd to be started on boot have to manually
check that the service started after a reboot, or implement custom
workarounds to ensure the same.
The fix removes the opportunity for an ordering cycle to occur in the
unit by moving dependencies out of the socket unit and changing the
WantedBy to sockets.target (what it should be for a socket unit).
[ Test Plan ]
The bug is reproduced by installing 'tang' (version 7-1build1) on a machine running Focal 20.04.6 or earlier. The unit should be enabled by default.
`sudo apt install tang`
After installing the package, ensure the tang service is enabled.
`systemctl is-enabled tang`
reboot the server, and check that the tangd.socket service is running
`systemctl status tangd.socket`
The service may or may not be running depending how systemd ordered
the startup jobs for this boot. You can simply repeat rebooting the server
and eventually at some point the service will not come up after a boot.
Regardless if the service is started on boot, you can see similar messages
to these in the system log:
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on tangd-update.service/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on basic.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Found dependency on sockets.target/start
Apr 5 05:01:05 tangtest-vm-2 kernel: systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
The fix requires modifying the tangd.socket unit WantedBy from multi-user.target to sockets.target. This means the 'enabled' status relies on links in a different directory before and after upgrade. The upgrade ought to remove the old multi-user.target link. So assuming the unit is 'enabled', the only links existing should be:
Before upgrade:
/etc/systemd/system/multi-user.target.wants/tangd.socket
After upgrade:
/etc/systemd/system/sockets.target.wants/tangd.socket
[ Where problems could occur ]
The tang service may not start correctly. If it is made to be part of
a systemd dependency chain with other services, those services may also
be impacted/fail to start.
Since the systemd units are altered, even if the service starts it may
change the way the tang service was originally configured to run. Other
applications/clients relying on the tang service may experiences issues
if the service is not running as originally configured in prior release.
[ Other Info ]
The proposed fix is derived from an upstream fix:
https://github.com/latchset/tang/commit/77785125fb56
There is a minor modification to the diff since the Ubuntu package source file for tangd.socket has a '.in' extension, upstream does not.
Versions starting with v8 already contain the fix:
$ git describe --contains 77785125fb56
v8~9
Since we are updating the WantedBy link from multi-user to socket via a change in postinst, a downgrade using `apt install tang={version}` will not have a postinst to account for this. The best way to downgrade is to remove the package, and then install the desired version to add the correct link.
Original bug text below:
----------
I had the same issue, described here: https://bugzilla.redhat.com/show_bug.cgi?id=1792173
This issue was found, because tangd didn't provide the advertisement payload anymore, after reboot.
Ubuntu version: 20.04.2
Package version of tang: 7-1build1
The bug could be fixed by the recommended changes from Renaud Métrich 2020-01-17 08:35:08 UTC.
---------- |
|
| 2023-04-21 03:25:58 |
Rafael Lopez |
attachment added |
|
lp1930203-focal.debdiff https://bugs.launchpad.net/ubuntu/+source/tang/+bug/1930203/+attachment/5665998/+files/lp1930203-focal.debdiff |
|
| 2023-04-21 03:26:24 |
Rafael Lopez |
tang (Ubuntu Focal): status |
Incomplete |
In Progress |
|
| 2023-04-22 02:06:56 |
Brett Milford |
bug |
|
|
added subscriber Brett Milford |
| 2023-05-08 12:27:39 |
Heitor Alves de Siqueira |
attachment removed |
lp1930203-focal.debdiff https://bugs.launchpad.net/ubuntu/+source/tang/+bug/1930203/+attachment/5665998/+files/lp1930203-focal.debdiff |
|
|
| 2023-05-11 06:05:58 |
Rafael Lopez |
attachment added |
|
lp1930203-focal.debdiff https://bugs.launchpad.net/ubuntu/focal/+source/tang/+bug/1930203/+attachment/5672386/+files/lp1930203-focal.debdiff |
|
| 2023-05-20 00:29:52 |
Steve Langasek |
tang (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2023-05-20 00:29:53 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-05-20 00:29:56 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2023-05-20 00:30:03 |
Steve Langasek |
tags |
se-sponsor-halves sts |
se-sponsor-halves sts verification-needed verification-needed-focal |
|
| 2023-06-05 09:36:21 |
Heitor Alves de Siqueira |
tags |
se-sponsor-halves sts verification-needed verification-needed-focal |
se-sponsor-halves sts verification-done verification-done-focal |
|
| 2023-06-07 12:27:00 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-06-07 12:27:00 |
Launchpad Janitor |
tang (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
