Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-12736

microshift-etcd doesn't handle any signals - becomes defunct requiring microshift restart

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 4.14.0
    • 4.13, 4.14
    • MicroShift
    • None
    • Moderate
    • No
    • uShift Sprint 236, uShift Sprint 237
    • 2
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      killing microshift-etcd with a normally non-fatal signal like SIGHUP or SIGINT the process becomes defunct requiring a microshift restart.   Normally systemd managed processes automatically restart on signals like this.

      Version-Release number of selected component (if applicable):

      4.13

      How reproducible:

      Always

      Steps to Reproduce:

      1. Get the pid of microshift-etcd and kill -1 on it
      
      

      Actual results:

      1. ps -ef on microshift-etcd shows it as defunct and still parented by microshift
      2. Nobody home on port 2379 and the cluster is unresponsive until microshift is restarted.

      Expected results:

      Cleanly handle signals and restart

      Additional info:

       

              ggiguash@redhat.com Gregory Giguashvili
              mifiedle@redhat.com Mike Fiedler
              Mike Fiedler Mike Fiedler
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: