Skip to content
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

Closed
tiraboschi opened this issue Aug 23, 2019 · 5 comments
Closed

'make bundleRegistry' fails #243

tiraboschi opened this issue Aug 23, 2019 · 5 comments
Assignees

Comments

@tiraboschi
Copy link
Member

tiraboschi commented Aug 23, 2019

make bundleRegistry' fails with:

time="2019-08-23T16:21:19Z" level=fatal msg="two csvs found in one bundle"
The command '/bin/sh -c initializer --manifests /registry --output bundles.db' returned a non-zero code: 1

rm ./deploy/olm-catalog/kubevirt-hyperconverged/0.0.2/kubevirt-hyperconverged-operator.v0.0.2.clusterserviceversion_merger.yaml is a temporary workaorund

@rwsu
Copy link
Contributor

rwsu commented Aug 23, 2019

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

@djzager
Copy link
Contributor

djzager commented Aug 23, 2019

To link to the actual issue in operator-registry operator-framework/operator-registry#70 for reference.

@ffromani
Copy link
Contributor

I have the same issue, but in my case I just need these two simple fixes: #245

@rthallisey
Copy link

@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"?

@djzager
Copy link
Contributor

djzager commented Aug 28, 2019

#245

@djzager djzager closed this as completed Aug 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants