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

CoreOS node stuck with message "A start job is running for CoreOS Trigger Multipath"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.14.z
    • RHCOS
    • Critical
    • No
    • 3
    • 255 - Integration & Delivery
    • 1
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress
    • Customer Escalated

      Description of problem:

      CoreOS node stuck with message "A start job is running for CoreOS Trigger Multipath"

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

      4.14

      How reproducible:

      Steps to Reproduce:

      1. On 4.14 version During MCP update, a node is stuck while booting. This happened twice on different clusters.
2. The error message is similar on both occasions.
3. Can someone provide more details about the error and if it is bug in 4.14 version.

      Actual results:

      Node is stuck with error message "A start job is running for CoreOS Trigger Multipath"

      Expected results:

      Node should not stuck while booting

      Additional info:

              jlebon1@redhat.com Jonathan Lebon
              rhn-support-pkhilare Pawan Khilare
              Aashish Radhakrishnan Aashish Radhakrishnan
              Michael Nguyen, Timothée Ravier
              Votes:
              1 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: