The test plan was executed for Noble (24.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.3~24.04
Candidate: 0.14.3~24.04
Version table:
*** 0.14.3~24.04 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
The following steps were executed:
1) Create a fresh VM with Ubuntu 24.04;
2) Join an active directory domain (created for test purposes);
3) Install adsys;
4) Instead of following the original plan of adding a lot of GPOs, it's better
to decrease the GPO list timeout and force a failure: this can be done by
setting gpo_list_timeout to 0 in /etc/adsys.yaml;
5) Try to update the GPOs applied to the client. It fails due to not having
enough time to fetch the required assets;
6) Increase the gpo_list_timeout in /etc/adsys.yaml (the default value for the
key is 10);
7) Try to update the GPOs applied to the client. If the configured timeout is
enough, adsys successfully fetches the required assets;
After step 7, adsys successfully fetched the required GPOs and its
assets and applied to the client.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2081966
Title:
[SRU] Timeout for listing GPOs is not enough in some cases
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Jammy:
Fix Committed
Status in adsys source package in Noble:
Fix Committed
Bug description:
[Impact]
Adsys has a fixed timeout for listing the GPOs. This can cause issues
on slower machines or in cases with many policies to be listed. Adding
a configurable timeout prevents the daemon from timing out the listing
process during its execution.
[Test Plan]
1. Configure A LOT (this can vary depending on the VM setup) of GPOs
in the AD controller;
2. Install adsys on the client, without changing the default settings;
3. Run `adsysctl policy update --all`;
4. With the default timeout, the command should timeout due to not
being able to fetch all policies in time;
5. Update adsys configuration file (/etc/adsys.yaml) and increase the
gpo_list_timeout;
6. Repeat step 3;
7. With an increased timeout, the command should fetch all policies
with no issues;
[Where Problems Could Occur]
If misconfigured by the user, the timeout could be insufficient and AD
users would not be allowed to authenticate.
Upstream PR: https://github.com/ubuntu/adsys/pull/1097
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2081966/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
