Please perform both cases and for each

- indicate what cables/interfaces were pulled

- indicate what hosts the cables were pulled from

- indicate approximate timestamp of when the cable was pulled

- indicate approximate timestamp of when the cable was reinserted

- Run ‘collect all’ and provide me access to the collect tarball

Also, just to be sure … please confirm that you are physically pulling the cable and not just ifdowning the interface.

Eric.

From: Wang, Yi C [mailto:yi.c.wang@intel.com]
Sent: Sunday, June 30, 2019 9:45 PM
To: MacDonald, Eric
Cc: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] a question about starlingx error handling behavior
Importance: High

Hi Eric,

I am working on the LP 1815513. Based on my tests, if I unplug the cable of active controller for management network for a long time (for example, 30s), and then plug it, the whole system can recover after some reboots. But if I unplug the cable for a short time, and then plug it. The whole system can’t recover. I need to lock/unlock controllers manually to bring the system back. So my questions are:

1. Is the behavior acceptable? (recover the system by manual lock/unlock operations)

2. If the answer is no for #1, we need the system to recover automatically. I am not familiar with internal maintenance logics, could you give me some hints?

Thanks.

Yi