search

openBackhaul / MicroWaveDeviceInventory

Physical and logical inventory of the MW SDN Domain
Apache License 2.0
5 stars 1 forks source link

Observing 500 internal server error for API /v1/regard-device-alarm #849

Closed Ziabatcha closed 6 months ago

Ziabatcha commented 7 months ago

[Test_v1.1.2] Observing 500 internal server error for API /v1/regard-device-alarm

{ "code": 500, "message": "Internal Server Error" }


curl -X POST "http://XXX:XX/v1/regard-device-alarm" -H "accept: application/json" -H "user: User Name" -H "originator: Resolver" -H "x-correlator: 550e8400-e29b-11d4-a716-446655440000" -H "trace-indicator: 1.3.1" -H "customer-journey: Unknown value" -H "operation-key: Operation key not yet provided." -H "Content-Type: application/json" -d "{\"notification-proxy-1-0:alarm-event-notification\":{\"alarm-event-sequence-number\":915,\"timestamp\":\"2024-02-08T07:46:02+00:00\",\"resource\":\"/core-model-1-4:network-control-domain=live/control-construct=CO17694/core-model-1-4:control-construct/equipment=HUAWEI-EQUIPMENT-1\",\"alarm-type-id\":\"alarms-1-0:ALARM_TYPE_ID_TYPE_NE_OBJ\",\"alarm-type-qualifier\":\"DCNSIZE_OVER/13110-20/FFFFFFFFFF\",\"problem-severity\":\"cleared\"}}"
nardecchia-siae commented 7 months ago

The resource attribute received from notification proxy is not correct. MWDI uses this attribute to trigger a request to it's api to manage the update of the alarm status in cache. Please notify this issue to NP developers to fix this issue

Ziabatcha commented 6 months ago

Verified this issue in test-v1.1.4, issue not observed. Hence closing this issue