Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-8225

RC 1.19.0-2 : haproxy replica remains 1 with HA upgrade

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Currently there is a known issue where upgrading the operator from versions prior to 1.17.z, the redis-ha-haproxy deployment does not automatically scale to 3 replicas after the upgrade. This occurs specifically when HA mode was enabled before upgrading to version 1.17.z.

      Workaround: Manually scale the redis-ha-haproxy deployment to match the replica count

      oc scale deployment <argocd instance>-redis-ha-haproxy -n <argocd namespace> --replicas=3
      Show
      Currently there is a known issue where upgrading the operator from versions prior to 1.17.z, the redis-ha-haproxy deployment does not automatically scale to 3 replicas after the upgrade. This occurs specifically when HA mode was enabled before upgrading to version 1.17.z. Workaround: Manually scale the redis-ha-haproxy deployment to match the replica count oc scale deployment <argocd instance>-redis-ha-haproxy -n <argocd namespace> --replicas=3
    • GitOps Crimson Sprint 25

      Description of Problem

      • Automatic upgrade from 1.16.4 to 1.19.0, haproxy pod count remains 1
      • Upon disabling and enabling HA, replica count increases to 3

      Reproducibility

      • Always

      Prerequisites/Environment

      • Regular OCP with 1.19 RC installed

      Steps to Reproduce

      • Install 1.16.4 from gitops-1.16
      • Enable HA
      • Upgrade the operator to 1.19

      Expected Results

      • haproxy deployment with 3 replicas

      Actual Results

      • haproxy deployment replicas remains 1

      Workaround (If Possible)

      • Increase the replica count manually

      Fix Approaches

      • <If we decide to fix this bug, how will we do it?>

      Acceptance Criteria

      • ...

      Definition of Done

      • Code Complete:
        • All code has been written, reviewed, and approved.
      • Tested:
        • Unit tests have been written and passed.
        • Ensure code coverage is not reduced with the changes.
        • Integration tests have been automated.
        • System tests have been conducted, and all critical bugs have been fixed.
        • Tested and merged on OpenShift either upstream or downstream on a local build.
      • Documentation:
        • User documentation or release notes have been written (if applicable).
      • Build:
        • Code has been successfully built and integrated into the main repository / project.
        • Midstream changes (if applicable) are done, reviewed, approved and merged.
      • Review:
        • Code has been peer-reviewed and meets coding standards.
        • All acceptance criteria defined in the user story have been met.
        • Tested by reviewer on OpenShift.
      • Deployment:
        • The feature has been deployed on OpenShift cluster for testing.

              rhn-support-alkumari Alka Kumari
              rhn-support-vab Varsha B
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: