Catalog update [dxoperator] [v4.13,v4.14,v4.15,v4.16,v4.17,v4.18,v4.19] #7539
Conversation
rh-operator-bundle-bot
added
operator-hosted-pipeline/started
approved
rh-operator-bundle-bot
changed the title
Static test results
|
rh-operator-bundle-bot
added
operator-hosted-pipeline/failed
and removed
operator-hosted-pipeline/started
labels
|
There were some errors while publishing your Operator Bundle. You can use this support case to contact the Red Hat certification team for review. |
Pipeline SummaryPipeline: operator-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/07187a6df5e14546a112153dc993b77e TroubleshootingPlease refer to the troubleshooting guide. Run |
|
@Allda I started a new pull request because I had some issues with my old one, but still having the same issues. You asked about OMP, and I am running: I've been following the instructions here: https://redhat-openshift-ecosystem.github.io/operator-pipelines/users/fbc_onboarding/#file-based-catalog-onboarding I've also been using the makefile provided by the above link. The makefile looks like it pulls its own version of OPM and uses that, version 1.46.0. I had previously used this same process for the community operator repo, where it worked fine. |
|
Hmm.. the opm version seems to be right. Let me try to reproduce it locally. I'll get back to you later today. |
|
@cdemadura I rendered a catalog in my environment with a fresh Makefile and clered /bin folder, and the format of the catalogs for >=4.17 has changed. I submitted changes to #7551. The PR got merged automatically, and the changes are applied. I hope it is fine with you. Otherwise, we can still revert it. |
|
@Allda, thank you so much! Do you have any tips on how I can troubleshoot why my setup isn't generating the correct files? I'll be submitting another operator in the next month or so, and would want to avoid running into this again. |
|
@cdemadura The Makefile generates a catalog in a different format for versions >=4.17. The generation is handled by The script itself is available here: https://github.com/redhat-openshift-ecosystem/operator-pipelines/blob/main/fbc/render_catalogs.sh I would maybe start debugging it by adding a verbose output and executing the script manually without the Makefile. You can share the output here with me and I'll review it. |
|
@Allda I ran the render_catalogs.sh script, and it was able to generate the proper catalog files when running it without the makefile. I went into the container while running, and the opm version is Version: version.Version{OpmVersion:"v1.46.0", GitCommit:"ced4d17d", BuildDate:"2024-08-16T12:44:43Z", GoOs:"linux", GoArch:"amd64"}. Something seems to be happening inside of the container that is generated when the makefile runs. Here is what happens outside of the container, if that helps at all. Ultimately, I would like to change my operator to be all versions of openshift 4.13 and greater. I was told that FBC would be the best way to do this. Is there a guide to changing the versioning of this, once I get the FBC issue figured out? make fbc-onboarding |
3 participants
No description provided.