Description of problem: This use case was reported by Petr Horacek. Use case details: I reconfigured the host by running [A], so the interface that was originally carrying VIPs is attached to an OVS bridge. While the keepalived-monitor observed the change and rendered new config, keepalived container failed with 'permanent error CONFIG' and not being restarted by Kubelet. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Stop/ kill the keepalives process inside keepalived container (use sudo crictl) 2. Using *sudo crictl ps* and the keepalived logs, verify the container was restarted properly by kubelet. Actual results: Keepalived container stopped working (error CONFIG) and kubelet doesn't restart the container. Expected results: keepalived-monitor should render a new keepalived config file. Keepalived should be restarted, and apply the new config. [A] https://access.redhat.com/articles/4934131
Please add Reproduction steps as [A] link is unavailable.
You can stop/kill the keepalived process inside the Kepelaived container and verify that the container is restarted properly by Kubelet.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409
*** Bug 1851447 has been marked as a duplicate of this bug. ***