I can reproduce this issue by using the old opm: [root@preserve-olm-env data]# opm version Version: version.Version{OpmVersion:"v1.14.3-5-gf6e5d92", GitCommit:"f6e5d92", BuildDate:"2020-10-14T03:19:10Z", GoOs:"linux", GoArch:"amd64"} [root@preserve-olm-env data]# opm index add --generate --bundles registry-proxy.engineering.redhat.com/rh-osbs/openshift4-windows-machine-config-operator-bundle@sha256:6f18bc811bd720900ae7e450763da778d7c7ef7607092787e80d0bb27a83f677 --binary-image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry@sha256:75df14ae994f4426943a39ac6e66b243412a18cf07688fa487380dc38cdb971c --from-index registry-proxy.engineering.redhat.com/rh-osbs/iib-pub-pending:v4.6 --overwrite-latest ... ERRO[0016] permissive mode disabled bundles="[registry-proxy.engineering.redhat.com/rh-osbs/openshift4-windows-machine-config-operator-bundle@sha256:6f18bc811bd720900ae7e450763da778d7c7ef7607092787e80d0bb27a83f677]" error="database is locked" When using the latest opm, it works well. LGTM, verify it. [root@preserve-olm-env operator-registry]# opm version Version: version.Version{OpmVersion:"v1.14.3-49-gbfe56a7", GitCommit:"bfe56a7", BuildDate:"2020-11-05T01:16:40Z", GoOs:"linux", GoArch:"amd64"} [root@preserve-olm-env operator-registry]# opm index add --generate --bundles registry-proxy.engineering.redhat.com/rh-osbs/openshift4-windows-machine-config-operator-bundle@sha256:6f18bc811bd720900ae7e450763da778d7c7ef7607092787e80d0bb27a83f677 --binary-image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry@sha256:75df14ae994f4426943a39ac6e66b243412a18cf07688fa487380dc38cdb971c --from-index registry-proxy.engineering.redhat.com/rh-osbs/iib-pub-pending:v4.6 --overwrite-latest INFO[0000] building the index bundles="[registry-proxy.engineering.redhat.com/rh-osbs/openshift4-windows-machine-config-operator-bundle@sha256:6f18bc811bd720900ae7e450763da778d7c7ef7607092787e80d0bb27a83f677]" ... INFO[0013] Generating dockerfile bundles="[registry-proxy.engineering.redhat.com/rh-osbs/openshift4-windows-machine-config-operator-bundle@sha256:6f18bc811bd720900ae7e450763da778d7c7ef7607092787e80d0bb27a83f677]" INFO[0013] writing dockerfile: index.Dockerfile bundles="[registry-proxy.engineering.redhat.com/rh-osbs/openshift4-windows-machine-config-operator-bundle@sha256:6f18bc811bd720900ae7e450763da778d7c7ef7607092787e80d0bb27a83f677]"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633