** Description changed:

+ [SRU]
+ 
+ [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 with no necessity.
+ process during its execution.
  
- SRU placeholder for fix: https://github.com/ubuntu/adsys/pull/1097
+ [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;
+ 
+ [Impact]
+ 
+ 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

** Description changed:

  [SRU]
  
  [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;
  
- [Impact]
+ [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

-- 
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:
  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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to