Skip to content

erase db does not erase dspace-utilities #1218

Closed

Description

@vidiecan

after deploy.yml on 5 INSTANCE, set ERASE DB, I see the main db empty but the other (dspace-utilities) not empy, verify
./.github/actions/erase-db
does it properly

2026-02-24 10:05:48,215:INFO: ========================================
2026-02-24 10:05:48,215:INFO: Reference database dspace-utilities status:
2026-02-24 10:05:48,323:INFO: 
                      license_definition:       31
         license_file_download_statistic: 44718155
                           license_label:       16
          license_label_extended_mapping:        3
                license_resource_mapping:  1978574
                            piwik_report:        1
                       user_registration:       69
                      verification_token:       14

at the moment the containers are removed

        docker stop dspacesolr$INSTANCE dspacedb$INSTANCE dspacedb-utilities$INSTANCE dspace$INSTANCE dspace-angular$INSTANCE || true
        docker rm   dspacesolr$INSTANCE dspacedb$INSTANCE dspacedb-utilities$INSTANCE dspace$INSTANCE dspace-angular$INSTANCE || true

and

docker volume rm $(docker volume ls --filter name="${NAME}_" -q)

Very likely caused by other imports

TODO:

  • after ERASE DB, check the db manually on dev-5

Activity

  1. vidiecan commented on Feb 24, 2026

    @vidiecan
    Author

    all is ok! invalid issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions