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

Default argocd instance does not get recreated after deletion deletion

XMLWordPrintable

    • GitOps Crimson Sprint 21

      Description of Problem

      • The default openshift-gitops instance does not come up upon deleting it
      • Initially, restart of cluster deployment seemed to be the cause but this is reproducible as it is 

      Additional Info

      • This was tested on FIPS env against v1.17 operator

      Problem Reproduction

      • Install the GitOps operator 
      • Delete the openshift-gitops instance

      Reproducibility

      • Always

      Prerequisites/Environment

      • <OpenShift, managed service (e.g., ROSA, ARO), operators, layered product, and other software versions, build details>

      Steps to Reproduce

      • See Problem Reproduction

      Expected Results

      • openshift-gitops instance should be re created 
      • Only way to disable the default instance should be by using DISALE_DEFAULT_INSTANCE env

      Actual Results

      • openshift-gitops instance does not get re created 

      Problem Analysis

      • <Completed by engineering team as part of the triage/refinement process>

      Root Cause

      • <What is the root cause of the problem? Or, why is it not a bug?>

      Workaround (If Possible)

      • <Are there any workarounds we can provide to the customers?>

      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.

              rh-ee-nakhil Nittala Akhil
              rhn-support-vab Varsha B
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: