test env:
cv:4.2.0-0.nightly-2019-08-28-004049
registory commit:8b7664d47a9bae939a19f1594139eb55ca9355a2


test result:
1.1.push the nest operator "sriov-network-operator" to quay ns "jfan" with "operator-courier"
2.create the opsrc "testkey" of the ns "jfan"
3. the registory-server pod & catalogsource are created successfully and the error about the operator will be shown in the logs of registory pod.
1) logs of registory pod

`
time="2019-08-28T08:14:00Z" level=info msg=directory dir=downloaded file=4.2 load=package
time="2019-08-28T08:14:00Z" level=warning msg="strict mode disabled" error="error loading manifests from appregistry: error loading operator manifests: [error checking provided apis in bundle : couldn't find sriovnetwork.openshift.io/v1/SriovNetwork (sriovnetworks) in bundle. found: map[], error adding operator bundle : UNIQUE constraint failed: operatorbundle.csv]" port=50051 type=appregistry
time="2019-08-28T08:14:00Z" level=info msg="serving registry" port=50051 type=appregistry
`

2) the opsrc &catalogsource & registory pod status
oc get opsrc testkey
NAME      TYPE          ENDPOINT              REGISTRY   DISPLAYNAME   PUBLISHER   STATUS      MESSAGE                                       AGE
testkey   appregistry   https://quay.io/cnr   jfan       TEST KEY      testkey     Succeeded   The object has been successfully reconciled   12m

oc get catalogsource testkey
NAME      DISPLAY    TYPE   PUBLISHER   AGE
testkey   TEST KEY   grpc   testkey     13m

oc get pods testkey-668fdd8f7b-bjk7k
NAME                       READY   STATUS    RESTARTS   AGE
testkey-668fdd8f7b-bjk7k   1/1     Running   0          13m

3)the packagemanifest from testkey
oc get packagemanifest -l opsrc-provider=testkey
NAME                      CATALOG    AGE
camel-k                   TEST KEY   14m
descheduler-test          TEST KEY   14m
mongodb-enterprise-test   TEST KEY   14m
prometheus-test           TEST KEY   14m
sriov-network-operator    TEST KEY   14m

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, 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/RHBA-2019:2922