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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081966
Title:
[SRU] Timeout for listing GPOs is not enough in some cases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2081966/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
