When the backup runs, it tries to backup all the collections we use in production. It does not attempt to backup collections that don't exist.
Actual behavior
It attempts to backup non-existent collections, and does not attempt to backup other collections that totally do exist!
Steps to replicate
ssh deploy@lib-solr-prod7
Look at /tmp/solr_backup.log
Note that it tries to backup the non-existent collection catalog-production1
Note that it makes no attempt to backup the collections dss-production2, pdc-discovery-production1, pdc-discovery-production2, special-collections-prod2, or figgy-edge
ls /mnt/solr_backup/solr8/production/20240605
Note that we have no backups for dss, pdc-discovery, special collections, or figgy edge.
Impact of this bug
We don't have solr backups for some production applications
Additionally, the backup log is confusing, since it says that it is trying to back up collections that don't exist
Expected behavior
When the backup runs, it tries to backup all the collections we use in production. It does not attempt to backup collections that don't exist.
Actual behavior
It attempts to backup non-existent collections, and does not attempt to backup other collections that totally do exist!
Steps to replicate
ssh deploy@lib-solr-prod7/tmp/solr_backup.logcatalog-production1dss-production2,pdc-discovery-production1,pdc-discovery-production2,special-collections-prod2, orfiggy-edgels /mnt/solr_backup/solr8/production/20240605Impact of this bug
Implementation notes, if any
We need to update collections.yml