-
Bug
-
Resolution: Done
-
Medium
-
Frankfurt Release
-
None
-
CLAMP-R6 Sprint 5
Legacy operational policy submitted to Policy Engine successfully. When refreshing the status of policy later, getting op deployment status returns 200, but getting policy status returned with 500, as shown in the log attached.
Note after investigation with Jorge: The problem comes from the legacy policy API that does not support properly semantic versioning like 1.0.0
It must be an integer like 1 or 2, etc ...
So the problem happens during the get status / delete of the legacy policy (Camel flow must be adapted)