fmAPI connection can not be judgef

Bug #1836283 reported by xiaodonghu on 2019-07-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Low
xiaodonghu

Bug Description

Reboot the fmManger process, and then run the test program to call the fm_set_fault function interface to report the alarm. The first time the report will fail.

xiaodonghu (xiaodonghu) wrote :

When the fmManger process restart, the fmAPI still believes that the socket connection is normal. When the first alarm is reported, it will no longer connect to the fmManger. The reported alarm will be lost.

xiaodonghu (xiaodonghu) on 2019-07-12
Changed in starlingx:
assignee: nobody → xiaodonghu (xiaodonghu)

Fix proposed to branch: master
Review: https://review.opendev.org/670759

Change abandoned by xiaodonghu (<email address hidden>) on branch: master
Review: https://review.opendev.org/670759

Ghada Khalil (gkhalil) wrote :

Low priority / not gating -- appears to be a race condition on process kill. Not likely to be seen in normal system operations.

tags: added: stx.fault
Changed in starlingx:
importance: Undecided → Low
status: New → Triaged

Change abandoned by xiaodonghu (<email address hidden>) on branch: master
Review: https://review.opendev.org/670435

Change abandoned by xiaodonghu (<email address hidden>) on branch: master
Review: https://review.opendev.org/672613

Change abandoned by xiaodonghu (<email address hidden>) on branch: master
Review: https://review.opendev.org/670765

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers