IBM Catalog pods fail with messages similar to "level=panic msg="open db-XXXX: permission denied""

Issue

• On a Red Hat OpenShift Container Platform cluster, certain pods from the IBM Catalog fail with CrashLoopBackOff after an upgrade of IBM Catalog pods.
• When checking the logs for these pods, the following errors and panic may be present:

$ oc logs ibm-etcd-operator-catalog-xxxx
Error: open db-XXXX: permission denied
Usage:
   [flags]

Flags:
  -d, --database string          relative path to sqlite db (default "bundles.db")
  -h, --help                     help for this command
  -p, --port string              port number to serve on (default "50051")
      --skip-migrate             do  not attempt to migrate to the latest db revision when starting
  -t, --termination-log string   path to a container termination log file (default "/dev/termination-log")

time="2024-02-17T15:33:59Z" level=panic msg="open db-XXXX: permission denied"
panic: (*logrus.Entry) 0xc000349260

goroutine 1 [running]:
github.com/sirupsen/logrus.Entry.log(0xc0000c4000, 0xc00031cde0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
        /src/vendor/github.com/sirupsen/logrus/entry.go:255 +0x325
github.com/sirupsen/logrus.(*Entry).Log(0xc0003490a0, 0xc000000000, 0xc0003bdf68, 0x1, 0x1)
        /src/vendor/github.com/sirupsen/logrus/entry.go:283 +0xf0
github.com/sirupsen/logrus.(*Logger).Log(0xc0000c4000, 0x0, 0xc0003bdf68, 0x1, 0x1)
        /src/vendor/github.com/sirupsen/logrus/logger.go:198 +0x7e
github.com/sirupsen/logrus.(*Logger).Panic(...)
        /src/vendor/github.com/sirupsen/logrus/logger.go:247
github.com/sirupsen/logrus.Panic(...)
        /src/vendor/github.com/sirupsen/logrus/exported.go:129
main.main()
        /src/vendor/github.com/operator-framework/operator-registry/cmd/registry-server/main.go:52 +0xc5

• This may include IBM operators, or theoretically operators from other vendors, but all are built using the Operator Framework SDK's Operator Registry.