Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-4939

[release-2.5] errata: memcachd setting max_item_size not populated

XMLWordPrintable

    • False
    • None
    • False
    • Optimize
    • No
    • Bug Fix

      Create an informative issue (See each section, incomplete templates/issues won't be triaged)

      Using the current documentation as a model, please complete the issue template. 

      Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

      Prerequisite: Start with what we have

      Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

       - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

       - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

      Describe the changes in the doc and link to your dev story

      Provide info for the following steps:

      1. - [X] Mandatory Add the required version to the Fix version/s field.

      2. - [X] Mandatory Choose the type of documentation change.

            - [ ] New topic in an existing section or new section
            - [X] Update to an existing topic
      https://github.com/stolostron/rhacm-docs/blob/2.5_stage/release_notes/errata.adoc

      3. - [ ] Mandatory for GA content:
                  
             - [X] Add steps and/or other important conceptual information here: 
             Fixes an observability issue that caused memory cached settings to not be propagated to the memory cached client.
                  
             - [ ] Add Required access level for the user to complete the task here:
             

             - [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)
           When users specify memcached maxItemSize setting in multiclusterobservability custom resource advanced settings (as shown below), it was not propagated to the memcached clients. This bug has been fixed. For example,

      spec:
      advanced:
      storeMemcached:
      maxItemSize: 10m

      now sets "max_item_size": "10MiB" in observability-thanos-store-shard-x deployments.

      spec:
      advanced:
      queryFrontendMemcached:
      maxItemSize: 10m

      now sets "max_item_size": "10MiB" in observability-thanos-query-frontend deployment.
           
             - [ ] Add link to dev story here: https://issues.redhat.com/browse/ACM-4683

      4. - [X] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:
      See (3) above

            rh-ee-ofischer Oliver Fischer
            smeduri1@redhat.com Subbarao Meduri
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: