Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-290

Support systemd reboot inhibitor locks

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • openshift-4.12
    • None
    • None
    • Support inhibitor locks
    • True
    • Hide
      This epic was automatically marked as blocked because the resolution for a subtask has been set to Won't Do (or Won't Fix), indicating a functional team cannot support this epic. If you believe this occurred in error, please reach out to the functional team for help in getting this work into their queue.
      Show
      This epic was automatically marked as blocked because the resolution for a subtask has been set to Won't Do (or Won't Fix), indicating a functional team cannot support this epic. If you believe this occurred in error, please reach out to the functional team for help in getting this work into their queue.
    • False
    • Green
    • In Progress
    • Impediment
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      Work merged. Awaiting QE and Docs.

      Show
      Work merged. Awaiting QE and Docs.
    • 0
    • 0

      Background

      In order to support Node Graceful Shutdown properly, MCO will need to respect systemd reboot inhibitor locks.

      Scenarios

      A privileged pod on a system is flashing device firmware or reconfiguring an FPGA device can be a quick operation or a 30+ minute event. In either case, rebooting the system during the operation could be catastrophic for the device.

      Even with standard workloads, inhibiting reboot until pods have properly drained is desirable and required for Node Graceful Shutdown to be meaningful.

              rhn-engineering-skumari Sinny Kumari
              rhn-support-mrussell Mark Russell
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: