Closed Ziabatcha closed 3 months ago
Defined NEW_RELEASE_FORWARDING_NAME in BasicServces.js and fix returning error response with **status code "500".
Test in local VM of /v1/embed-yourself service: Before callback : POST http://172.28.127.11:3003/v1/record-service-request header :{"user":"User Name","originator":"MacAddressTableRecorder","x-correlator":"EEDA960E-8d8b-8B2C-e01e-6d3c517D32Bb","trace-indicator":1,"customer-journey":"unknown","operation-key":"Operation key not yet provided.","Content-Type":"application/json"}body :{"x-correlator":"550e8400-e29b-11d4-a716-446655440000","trace-indicator":"1.3.1","user":"User Name","originator":"Resolver","application-name":"MacAddressTableRecorder","release-number":"1.0.0","operation-name":"/v1/embed-yourself","response-code":200}response code:204 RequestBuilder.js:33 loggingErrorHandler - caught error, returning response with status code "500" and body {"code":500,"message":"response body required.","errors":[{"path":".response","message":"response body required."}]}
After Fix: callback : POST http://172.28.127.11:3003/v1/record-service-request header :{"user":"User Name","originator":"MacAddressTableRecorder","x-correlator":"De74c584-cdD1-c6eE-74fE-d8B2Dc1fbECA","trace-indicator":1,"customer-journey":"unknown","operation-key":"Operation key not yet provided.","Content-Type":"application/json"}body :{"x-correlator":"550e8400-e29b-11d4-a716-446655440000","trace-indicator":"1.3.1","user":"User Name","originator":"Resolver","application-name":"MacAddressTableRecorder","release-number":"1.0.0","operation-name":"/v1/embed-yourself","response-code":204}response code:204
Verified in 1.0.9 and issue not observed hence closing it
We noticed the MATR container(test_v1.0.5) is continuously restarting after upgrading the MWDI code to test_v1.1.3 in TestLab environment.
MATR container logs: