Errors when deleting non-empty CO

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • Affects Version/s: COmanage Registry 4.0.2 (Purple Jade MR2)
    • Component/s: Registry
    • Environment:
      RHEL 7, PostgreSQL 11.15, PHP 7.4, Registry develop snapshot 2022-02-24 (commit daf36af)

      Attempt to delete non-empty CO fails.

      Test case – Created new CO from template and added single org_identity, then attempted to delete. Garbage collection job failed with this message:

      SQLSTATE[23503]: Foreign key violation: 7 ERROR: update or delete on table "cm_cos" violates foreign key constraint "cm_org_identities_co_id_fkey" on table "cm_org_identities" DETAIL: Key (id)=(14) is still referenced from table "cm_org_identities"

      Initial attempt to expunge the offending org_identity and delete the CO again failed with "CoreJob.GarbageCollector not available" as the job apparently stopped running after the failure.  After switching to CO 1 and viewing CoreJob.GarbageCollector in the web interface the job was apparently requeued. (But the job still failed.)

            Assignee:
            Benn Oshrin (internet2.edu)
            Reporter:
            Allan Kim
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: