Policy installation failure due to expired time objects

[kamilazat]

Hello all!

In R81.10 JHF Take 150, the policy package that gets installed on a cluster fails with the error message below.

"Some Access rules have time objects that are expited at least 2 days ago and were not loaded to the GW. See sk155253 for more details."

Policy debug script did not give us anything other than the same message. sk155253 suggests cleaning the relevant rules, understandably.

After several installation trials the policy gets installed. Until the successful installation, no changes are being made other than repeatedly trying to install policy.

I tried replicating the issue on a lab with the same version and hotfix, but I can install policy with expired rules successfully every single time. So I have 2 questions at this point.

1. Is policy installation failure when there are expired rules an expected behavior, or should I look deeper into the system for other issues that may have caused the failure?

2. We plan to delete the time objects and disable the relevant rules temporarily, do expired time objects render a rule as if it is disabled, or are there nuances to it?

Cheers!