Comment 2 for bug 1979992

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nfv (master)

Reviewed: https://review.opendev.org/c/starlingx/nfv/+/847981
Committed: https://opendev.org/starlingx/nfv/commit/fc1aff636def785b2c18c3db0db093208523fec6
Submitter: "Zuul (22348)"
Branch: master

commit fc1aff636def785b2c18c3db0db093208523fec6
Author: Heitor Matsui <email address hidden>
Date: Tue Jun 28 11:45:04 2022 -0300

    Detect and kill hung vim process

    There is a specific scenario when vim starts where threads keep
    stalled and then after 600s the subsystems are marked as not sane.
    In this situation vim is supposed to quit, but instead it stays
    alive but in a failed state.

    This commit adds an extra step in vim monitoring ocf script to
    test if vim rpc port is open and responding, and if not, vim
    is forcefully killed.

    Test Plan
    PASS: install/bootstrap/unlock AIO-SX
    PASS: get vim to a not-sane state and observe it being killed
          and restarted in this scenario

    Closes-bug: 1979992
    Change-Id: I55777a0858507634a362e58b9da281492809a03d
    Signed-off-by: Heitor Matsui <email address hidden>