Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3716

Logging-view-plugin pod can not be started on 5.7.0

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • NEW
    • Log Collection - Sprint 232, Log Collection - Sprint 233

    Description

      logging-view-plugin pod can not be started

      Version:
      openshift-logging/cluster-logging-rhel8-operator/images/v5.7.0-52

      Description:
      logging-view-plugin-787679c675-7p4d2 0/1 CreateContainerError 0 43s
      msg="runc create failed: unable to start container process: exec: \"./plugin-backend\": stat ./plugin-backend: no such file or directory"

      Events:
      Type Reason Age From Message
      ---- ------ ---- ---- -------
      Normal Scheduled 27s default-scheduler Successfully assigned openshift-logging/logging-view-plugin-787679c675-7p4d2 to ip-10-0-170-216.us-east-2.compute.internal
      Normal AddedInterface 27s multus Add eth0 [10.129.2.96/23] from ovn-kubernetes
      Normal Pulling 26s kubelet Pulling image "registry.redhat.io/openshift-logging/logging-view-plugin-rhel8@sha256:7f74432532f8348d92b5b1fc53da69c34d85caa461175644ebf58d4fe2e43a3d"
      Normal Pulled 21s kubelet Successfully pulled image "registry.redhat.io/openshift-logging/logging-view-plugin-rhel8@sha256:7f74432532f8348d92b5b1fc53da69c34d85caa461175644ebf58d4fe2e43a3d" in 5.021725044s
      Warning Failed 21s (x2 over 21s) kubelet Error: container create failed: time="2023-02-28T13:58:07Z" level=error msg="runc create failed: unable to start container process: exec: \"./plugin-backend\": stat ./plugin-backend: no such file or directory"
      Normal Pulled 6s (x2 over 21s) kubelet Container image "registry.redhat.io/openshift-logging/logging-view-plugin-rhel8@sha256:7f74432532f8348d92b5b1fc53da69c34d85caa461175644ebf58d4fe2e43a3d" already present on machine
      Warning Failed 6s kubelet Error: container create failed: time="2023-02-28T13:58:22Z" level=error msg="runc create failed: unable to start container process: exec: \"./plugin-backend\": stat ./plugin-backend: no such file or directory"

      Step to reproduce:
      1) Deploy cluster-logging 5.7.0 and forward logs to lokistack.
      2) check the pod status
      $ oc get pods
      NAME READY STATUS RESTARTS AGE
      cluster-logging-operator-7fd48d8cbb-djjlg 1/1 Running 0 15m
      collector-wj9kf 2/2 Running 0 7m35s
      logging-view-plugin-787679c675-7p4d2 0/1 CreateContainerError 0 7m39s

      Additional Info:
      One fix in LOG-3447 is not cherry-pick to master

      Attachments

        Activity

          People

            vparfono Vitalii Parfonov
            rhn-support-anli Anping Li
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: