Loading...
Loading...
There is an inconsistency in how ASM-config derives the current policy revision, and in how it determines what is the 'latest' revision number for a policy. When upgrading machine the system attempts to restore the 'last active version' of each policy. The system determines the latest version by the highest revision number, which is now wrong. So an older version of the policy is restored.
The policy revision numbers start again, so the GUI appears to be displaying incorrect information, which can cause confusion.
Inactivate policy and activate again.
None.
The system now ensures the correct revision sequence in Policy History, so this issue no longer occurs.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.