| 2023-07-12 17:59:35 |
Mitch Burton |
bug |
|
|
added bug |
| 2023-07-12 18:00:38 |
Mitch Burton |
affects |
landscape-client |
landscape-client (Ubuntu) |
|
| 2023-07-12 18:00:38 |
Mitch Burton |
landscape-client (Ubuntu): status |
New |
Fix Released |
|
| 2023-07-12 18:01:15 |
Mitch Burton |
bug task added |
|
landscape-client |
|
| 2023-07-12 18:01:21 |
Mitch Burton |
landscape-client: status |
New |
Fix Released |
|
| 2023-07-14 19:59:17 |
Andreas Hasenack |
bug |
|
|
added subscriber Andreas Hasenack |
| 2023-07-27 20:28:03 |
Lucas Kanashiro |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-07-27 20:28:03 |
Lucas Kanashiro |
bug task added |
|
landscape-client (Ubuntu Jammy) |
|
| 2023-07-27 20:28:03 |
Lucas Kanashiro |
nominated for series |
|
Ubuntu Focal |
|
| 2023-07-27 20:28:03 |
Lucas Kanashiro |
bug task added |
|
landscape-client (Ubuntu Focal) |
|
| 2023-07-27 21:00:00 |
Mitch Burton |
description |
debian/rules override_dh_installsystemd uses --no-start to prevent the landscape-client service from being started post-install until landscape-config is run. This has the side-effect of the services stopping on upgrade so that when landscape upgrades itself, it cannot report the result.
Should modify the dh_installsystemd call to avoid stopping the service on upgrade. |
[ Impact ]
debian/rules override_dh_installsystemd uses --no-start to prevent the landscape-client service from being started post-install until landscape-config is run. This has the side-effect of the services stopping on upgrade so that when landscape upgrades itself, it cannot report the result.
Patching this will allow users to upgrade Landscape Client to this version (and future versions) and transition to the new version without interruption of the service.
The patch fixes this by using the default dh_installsystemd behaviour combined with a service ExecCondition that checks the registration status of Landscape Client. If registered, the service must be running, and so should be started again after upgrade.
[ Test Plan ]
The following tests will be performed, in addition to the ones laid out in https://wiki.canonical.com/Landscape/ClientSRUTests/23.02
On jammy and focal:
test 1: install version 19.12, register with Landscape Server, service is running, upgrade to version 23
test 2: install version 19.12, register with Landscape Server, systemctl stop landscape-client, upgrade to version 23
test 3: install version 19.12, register with Landscape Server, systemctl stop landscape-client, systemctl disable landscape-client, upgrade to version 23
test 4: install version 19.23, do not register with Landscape Server, service is not running, upgrade to version 23
[ Where problems could occur ]
As this is a change to the systemd unit behaviour, problems would probably present as the service failing to start after upgrade, or failing to stop, continuing to run the previous version. |
|
| 2023-08-23 15:43:09 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Graham Inggs |
| 2023-09-02 00:54:05 |
Steve Langasek |
landscape-client (Ubuntu Jammy): status |
New |
Incomplete |
|
| 2023-09-05 16:42:46 |
Mitch Burton |
description |
[ Impact ]
debian/rules override_dh_installsystemd uses --no-start to prevent the landscape-client service from being started post-install until landscape-config is run. This has the side-effect of the services stopping on upgrade so that when landscape upgrades itself, it cannot report the result.
Patching this will allow users to upgrade Landscape Client to this version (and future versions) and transition to the new version without interruption of the service.
The patch fixes this by using the default dh_installsystemd behaviour combined with a service ExecCondition that checks the registration status of Landscape Client. If registered, the service must be running, and so should be started again after upgrade.
[ Test Plan ]
The following tests will be performed, in addition to the ones laid out in https://wiki.canonical.com/Landscape/ClientSRUTests/23.02
On jammy and focal:
test 1: install version 19.12, register with Landscape Server, service is running, upgrade to version 23
test 2: install version 19.12, register with Landscape Server, systemctl stop landscape-client, upgrade to version 23
test 3: install version 19.12, register with Landscape Server, systemctl stop landscape-client, systemctl disable landscape-client, upgrade to version 23
test 4: install version 19.23, do not register with Landscape Server, service is not running, upgrade to version 23
[ Where problems could occur ]
As this is a change to the systemd unit behaviour, problems would probably present as the service failing to start after upgrade, or failing to stop, continuing to run the previous version. |
[ Impact ]
debian/rules override_dh_installsystemd uses --no-start to prevent the landscape-client service from being started post-install until landscape-config is run. This has the side-effect of the services stopping on upgrade so that when landscape upgrades itself, it cannot report the result.
Patching this will allow users to upgrade Landscape Client to this version (and future versions) and transition to the new version without interruption of the service.
The patch fixes this by using the default dh_installsystemd behaviour combined with a service ExecCondition that checks the registration status of Landscape Client. If registered, the service must be running, and so should be started again after upgrade.
[ Test Plan ]
The following tests will be performed, in addition to the ones laid out in https://wiki.canonical.com/Landscape/ClientSRUTests/23.02
On jammy and focal:
test 1: install version 19.12, register with Landscape Server, service is running, upgrade to version 23
expected behaviour: landscape-client service restarts, running the new version (23).
test 2: install version 19.12, register with Landscape Server, systemctl stop landscape-client, upgrade to version 23
expected behaviour: landscape-client service restarts, running the new version (23).
test 3: install version 19.12, register with Landscape Server, systemctl stop landscape-client, systemctl disable landscape-client, upgrade to version 23
expected-behaviour: landscape-client service does not start (as it is disabled), but when enabled, the new version (23) is running.
test 4: install version 19.23, do not register with Landscape Server, service is not running, upgrade to version 23
expected-behaviour: landscape-client service never runs, registration has not occurred.
[ Where problems could occur ]
As this is a change to the systemd unit behaviour, problems would probably present as the service failing to start after upgrade, or failing to stop, continuing to run the previous version. |
|
| 2023-09-15 23:49:29 |
Steve Langasek |
landscape-client (Ubuntu Jammy): status |
Incomplete |
Fix Committed |
|
| 2023-09-15 23:49:31 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-09-15 23:49:34 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2023-09-15 23:49:39 |
Steve Langasek |
tags |
|
verification-needed verification-needed-jammy |
|
| 2023-09-15 23:56:57 |
Steve Langasek |
landscape-client (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2023-09-15 23:57:01 |
Steve Langasek |
tags |
verification-needed verification-needed-jammy |
verification-needed verification-needed-focal verification-needed-jammy |
|
