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

Elasticsearch rollout not happening during storage update in clusterlogging/instance

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Critical Critical
    • None
    • Logging 5.8.1
    • Log Storage
    • False
    • None
    • False
    • NEW
    • NEW
    • Release Note Not Required
    • Log Storage - Sprint 247
    • Critical
    • Customer Escalated

      Description of problem:

      Elasticsearch rollout not happening during storage update in clusterlogging/instance.

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

      • logging 5.6.14, 5.8.1

      How Reproducible: 100%

      Steps to Reproduce:

       - Updating storage section in clusterlogging/instance , elasticsearch pods are not automatically reconciling with the latest configuration.

       

        Warning  FailedScheduling  75s   default-scheduler  0/16 nodes are available: 16 persistentvolumeclaim "elasticsearch-elasticsearch-cdm-u1oorzvb-1" not found. preemption: 0/16 nodes are available: 16 Preemption is not helpful for scheduling.
        Warning  FailedScheduling  27s   default-scheduler  0/16 nodes are available: 16 persistentvolumeclaim "elasticsearch-elasticsearch-cdm-u1oorzvb-1" not found. preemption: 0/16 nodes are available: 16 Preemption is not helpful for scheduling. 
      • Elasticsearch deployment is not getting updated with new values on its own.

       

      Workaround:

      • Need to delete the elasticsearch deployment every-time any change in made in storage section of clusterlogging/instance.

            cahartma@redhat.com Casey Hartman
            rhn-support-amanverm Aman Dev Verma
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: