Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-2901

OOMKilled status is communicated poorly to the user

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. OOMKilled status display improval
      2. When pod is killed by OOM Killer, Pod status flashes as "OOMKilled" for up to 1 second and than pod restarts. It is really easy to miss this status, which can send a user on a hunt for the crash reason.
      3. Poor communication of failure reasons is a huge timesink for users.
      4. web console, unsure of any other components.

              amobrem Ali Mobrem
              mkrutov Mikhail Krutov (Inactive)
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None