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

Logging 5.0 - Elasticsearch-operator can not start due to resource limitation (edit)

    XMLWordPrintable

Details

    • False
    • False
    • NEW
    • NEW
    • Undefined
    • Hide
      * Previously, an update in the cluster service version (CSV) accidentally introduced resources and limits for the OpenShift Elasticsearch operator container. Under specific conditions, this caused an out-of-memory condition that terminated the Elasticsearch operator pod. The current release fixes this issue by removing the CSV resources and limits for the operator container. Now, the operator gets scheduled without issues. (link:https://issues.redhat.com/browse/LOG-1254[*LOG-1254*])
      Show
      * Previously, an update in the cluster service version (CSV) accidentally introduced resources and limits for the OpenShift Elasticsearch operator container. Under specific conditions, this caused an out-of-memory condition that terminated the Elasticsearch operator pod. The current release fixes this issue by removing the CSV resources and limits for the operator container. Now, the operator gets scheduled without issues. (link: https://issues.redhat.com/browse/LOG-1254 [* LOG-1254 *])

    Description

      Attachments

        Issue Links

          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. LOG-1255 Logging 5.1 - Elasticsearch-operator can not start due to resource limitation

          • Undefined - Priority not specified.
          • Closed

          Activity

            People

              ewolinet@redhat.com Eric Wolinetz (Inactive)
              anli@redhat.com Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: