Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-1399 Testing of GitOps 1.3: Upgrade
  3. GITOPS-1131

Test case 2.3: Upgrade 1.2.1 -> 1.3: Upgrade with app

    XMLWordPrintable

Details

    • Sub-task
    • Status: Closed (View Workflow)
    • Undefined
    • Resolution: Done
    • None
    • 1.3
    • None
    • GITOPS Sprint 207, GITOPS Sprint 208
    • False

    Description

      Test plan: https://docs.google.com/spreadsheets/d/1QffApOul9-4NUEoB38eHui75pWLJceZZMid9BPxlpIk/edit#gid=1751686148

      Test case (may be outdated, please refer to test plan for up-to-date information):

      This test case validates upgrading from OCP 1.2.1 with existing argocd applications

      Previous State environment

      1. Install GitOps Operator 1.2.1
      2. Deploy an application in openshift-gitops (by default argocd instance)
      3. Create 2 argocd instances in namespace foo and bar
      4. Each argocd instances deploy applications in the namespaces they deployed in.
      5. Create target namespaces target1 and target2 they are managed by argocd instances in namespace foo and bar, respectively.
      6. Each argocd instances in namespace foo and boar deploy applications in target1 and target2 namespaces, respectively.

      Upgrade State environment

      1. Upgrade Gitops Operator to 1.3
      2. Verify all existing applications are deployed and sync and healthy.
      3. Verify the app is in the same state as it was in the previous installation
      4. Unstall the operator
      5. Unstallation should be clean

      Attachments

        Activity

          People

            rjeczkow Roman Jeczkowiak
            jfischer@redhat.com Jann Fischer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: