search

operator-framework / operator-registry

Operator Registry runs in a Kubernetes or OpenShift cluster to provide operator catalog data to Operator Lifecycle Manager.
Apache License 2.0
211 stars 242 forks source link

opm index database cannot be read using : quay.io/operator-framework/upstream-community-operators #179

Open cmoulliard opened 4 years ago

cmoulliard commented 4 years ago

Issue

The index database pushed within the following image which is currently packaged as CatalogSource from olm release 0.14.1 cannot be read quay.io/operator-framework/upstream-community-operators

The following command returns this error

 ./bin/opm index export -i quay.io/operator-framework/upstream-community-operators:latest -f tmp/packages -c docker -o prometheus
INFO[0000] export from the index                         index="quay.io/operator-framework/upstream-community-operators:latest" package=prometheus
INFO[0000] Pulling previous image quay.io/operator-framework/upstream-community-operators:latest to get metadata  index="quay.io/operator-framework/upstream-community-operators:latest" package=prometheus
INFO[0000] running docker pull                           index="quay.io/operator-framework/upstream-community-operators:latest" package=prometheus
INFO[0001] Getting label data from previous image        index="quay.io/operator-framework/upstream-community-operators:latest" package=prometheus
INFO[0001] running docker inspect                        index="quay.io/operator-framework/upstream-community-operators:latest" package=prometheus
Error: no such table: operatorbundle

because the following SQL request cannot find the operatorbundle table

https://github.com/operator-framework/operator-registry/blob/338978155aef7c488592fed6fb3f11f1f6affab2/pkg/sqlite/query.go#L564-L567

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

ecordell commented 3 years ago

That issue seems to be resolved, but in trying to replicate I found another one.

This should be fixed by: https://github.com/operator-framework/community-operators/pull/3010

J0zi commented 3 years ago

@ecordell, @cmoulliard I suppose you are trying to pull an image which is not the one you want. You are trying to pull an image which is for our pipeline purposes. This is the index image for Kubernetes upstream-community-operators, correct one: quay.io/operatorhubio/catalog:latest https://quay.io/repository/operatorhubio/catalog?tab=tags