-
Bug
-
Resolution: Done
-
Medium
-
Amsterdam Release
-
None
-
Rackspace
-
Policy Sprint RC0 - 9/29-10/11
Upload BRMS Param Template
- couldn't open file "ClosedLoopControlName.drl"
Create BRMSParam Operational Policies
Create BRMSParamvFirewall Policy
> PUT /pdp/api/createPolicy HTTP/1.1
PE300 - Data Issue: Invalid Template. The template name, ClosedLoopControlName was not found in the dictionary.Create BRMSParamvDNS Policy
> PUT /pdp/api/createPolicy HTTP/1.1
PE300 - Data Issue: Invalid Template. The template name, ClosedLoopControlName was not found in the dictionary.Create BRMSParamvCPE Policy
> PUT /pdp/api/createPolicy HTTP/1.1
PE300 - Data Issue: Invalid Template. The template name, ClosedLoopControlName was not found in the dictionary.Create MicroService Config Policies
Pushing BRMSParam Operational policies
pushPolicy : PUT : com.BRMSParamvFirewall
< HTTP/1.1 400 Bad Request
PE300 - Data Issue: response code of the URL is 404. This indicates a problem with getting the version from the PAP or the policy does not exist.pushPolicy : PUT : com.BRMSParamvDNS
> PUT /pdp/api/pushPolicy HTTP/1.1
< HTTP/1.1 400 Bad Request
PE300 - Data Issue: response code of the URL is 404. This indicates a problem with getting the version from the PAP or the policy does not exist.pushPolicy : PUT : com.BRMSParamVOLTE
> PUT /pdp/api/pushPolicy HTTP/1.1
< HTTP/1.1 400 Bad Request
PE300 - Data Issue: response code of the URL is 404. This indicates a problem with getting the version from the PAP or the policy does not exist.pushPolicy : PUT : com.BRMSParamvCPE
> PUT /pdp/api/pushPolicy HTTP/1.1
< HTTP/1.1 400 Bad Request
PE300 - Data Issue: response code of the URL is 404. This indicates a problem with getting the version from the PAP or the policy does not exist.Pushing MicroService Config policies
pushPolicy : PUT : com.MicroServicevFirewall
- relates to
-
POLICY-276 brmsgw: not generating amsterdam rules jar
- Closed