-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'make bundleRegistry' fails #243
Comments
Changing this line in the deploy/Dockerfile seems also works as a workaround for me: FROM quay.io/openshift/origin-operator-registry to FROM quay.io/openshift/origin-operator-registry:4.1.0 It was mentioned here: kubevirt/cluster-network-addons-operator#214 |
To link to the actual issue in operator-registry operator-framework/operator-registry#70 for reference. |
I have the same issue, but in my case I just need these two simple fixes: #245 |
@fromanirh I think that has a different root cause. #225 should fix. I'm not sure about this change in #245 . I do recall we had to do something similar d/s... - RUN initializer --manifests /registry --output bundles.db
+ RUN initializer --manifests /registry/kubevirt-hyperconverged --output bundles.db Would a better title for this bug be "Updating to newer Operator Registry fails"? |
make bundleRegistry' fails with:
rm ./deploy/olm-catalog/kubevirt-hyperconverged/0.0.2/kubevirt-hyperconverged-operator.v0.0.2.clusterserviceversion_merger.yaml
is a temporary workaorundThe text was updated successfully, but these errors were encountered: