-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
operator-sdk does not copy the configs from the given index image #6505
Comments
A workaround for now would be to create another I think the bug lies somewhere in here: operator-sdk/internal/olm/operator/bundle/install.go Lines 186 to 226 in 888ea7f
It looks like we are only returning the "extra" FBC contents instead of returning the "extra" + index FBC content |
Thanks @everettraven for pointing this out. I tried to fix it and it did work well in my testing. I will raise a PR. |
copy the FBC of index-image as well if --index-image is passed to the operator-sdk run bundle command Fixes operator-framework#6505 Signed-off-by: Nitin Goyal <nigoyal@redhat.com>
copy the FBC of index-image as well if --index-image is passed to the operator-sdk run bundle command Fixes operator-framework#6505 Signed-off-by: Nitin Goyal <nigoyal@redhat.com>
) copy the FBC of index-image as well if --index-image is passed to the operator-sdk run bundle command Fixes #6505 Signed-off-by: Nitin Goyal <nigoyal@redhat.com>
Bug Report
What did you do?
I am using operator-sdk to install the operator with the below command and expect the new catalog to have the dependent operators as I am passing the index image which has the dependent operators inside it under the
configs
directory.operator-sdk run bundle quay.io/nigoyal/odf-operator-bundle:latest --timeout=10m --security-context-config restricted -n openshift-storage --index-image quay.io/nigoyal/odf-operator-catalog:odf-deps
What did you expect to see?
I am expecting my operator to get installed with the dependencies but it is stuck as it can not resolve the deps. Because the new catalog does not copy the configs directory into the
odf-operator-catalog-configs
What did you see instead? Under which circumstances?
Environment
Operator type:
Kubernetes cluster type:
$ operator-sdk version
$ go version
(if language is Go)$ kubectl version
Possible Solution
Possible solution would be to create the new directory which operator-sdk creates under the
configs
itself and serve fromconfigs
or copy theconfigs
data inside new directory.Additional context
slact thread: https://redhat-internal.slack.com/archives/C3VS0LV41/p1689838697181879
The text was updated successfully, but these errors were encountered: