VirtualServer that references a WAF policy which uses a bundle does not recover if the bundle is missing on startup #5530
Labels
bug
An issue reporting a potential bug
ready for refinement
An issue that was triaged and it is ready to be refined
Describe the bug
When deploying a VirtualServer with a WAF policy which uses the
apBundle
setting, the VirtualServer will remain go into aWarning
state if the expected.tgz
bundle file is not present. The VirtualServer will subsequently stay in thisWarning
state even after the.tgz
bundle file is put into the expected directory afterwords.Example warning message:
To Reproduce
Steps to reproduce the behavior:
Policy
of kindwaf
, with theapBundle
option as shown in the Policy Resource docsExpected behavior
The VirtualServer will go from a
Warning
state to aValid
state after the bundle file has been placed in the expected directory.Your environment
The text was updated successfully, but these errors were encountered: