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

Enabling invalid or missing plugin causes console to crash loop

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If you edit the console operator config and enable a random plugin name (or the name of a real plugin that doesn't have a ConsolePlugin resource for whatever reason), the console will crash loop. This seems to be a regression introduced by the new internal pluginsOrder argument to the console backend. The console operator will skip plugins without ConsolePlugin resource, but still adds the plugin to pluginsOrder.

      For example, this error:

      E0820 18:14:49.393104 1 sync_v400.go:726] failed to get "pipelines-console-plugin" plugin: consoleplugin.console.openshift.io "pipelines-console-plugin" not found

      Results in the following console-config config map values:

      {{
      plugins: []
      pluginsOrder:

      • pipelines-console-plugin
        }}

      And the following error from the console pod:

      F0820 17:40:43.219455 1 validate.go:76] invalid flag: plugins-order, error: list must only contain currently enabled plugins

              jhadvig@redhat.com Jakub Hadvig
              spadgett@redhat.com Samuel Padgett
              None
              None
              YaDan Pei YaDan Pei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: