Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2749

PVCs for datagrid and amq are not removed when KieApp is deleted

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • 7.7.1.GA
    • 7.7.0.GA
    • Cloud
    • None

    • OpenShift 4.x + Operator 7.7.0 CR1 + Authoring HA

    • CR1
    • Workaround Exists
    • Hide

      Delete Persistent Volume Claims manually.
      Go to Storage -> Persistent Volume Claims and then delete left over Datagrid and AMQ PVC

      Show
      Delete Persistent Volume Claims manually. Go to Storage -> Persistent Volume Claims and then delete left over Datagrid and AMQ PVC
    • Hide
      1. Deploy Authoring HA using Operator
      2. Wait for environment to start up
      3. delete KieApp where is defined Authoring HA scenario
      4. Check Persistent Volume Claims after KieApp is deleted and all pods are terminated

      Actual result:
      Datagrid and AMQ PVCs are still in project
      Expected result:
      Datagrid and AMQ PVCs are deleted

      Show
      Deploy Authoring HA using Operator Wait for environment to start up delete KieApp where is defined Authoring HA scenario Check Persistent Volume Claims after KieApp is deleted and all pods are terminated Actual result: Datagrid and AMQ PVCs are still in project Expected result: Datagrid and AMQ PVCs are deleted
    • 2020 Week 16-18 (from Apr 13)

      When is deleted KieApp with defined Authoring HA scenario, Persistent Volume Claims for AMQ and Datagrid are not deleted. Then for users there are allocated Persistent Volumes that are not used anymore.
      PVCs for Business Central and KIE Server are deleted when KieApp is deleted.

              rhn-support-fspolti Filippe Spolti
              jakubschwan Jakub Schwan
              Jakub Schwan Jakub Schwan
              Jakub Schwan Jakub Schwan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: