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

Build Bundles Failure #5242

Closed
jvpasinatto opened this issue Nov 4, 2024 · 3 comments
Closed

Build Bundles Failure #5242

jvpasinatto opened this issue Nov 4, 2024 · 3 comments

Comments

@jvpasinatto
Copy link
Contributor

Hi,

Both of these actions:
https://github.com/k8s-operatorhub/community-operators/actions/runs/11660462075/job/32465164000
https://github.com/k8s-operatorhub/community-operators/actions/runs/11660142590/job/32462378032
failed in build bundles action with the same error:
TASK [build_operator_version_bundle : Fail if directory doesn't exists] ******** fatal: [localhost]: FAILED! => changed=false msg: 'Directory ''/tmp/operator-test/operators/opentelemetry-operator/0.16.0/tests/scorecard/'' specified in ''operators.operatorframework.io.test.config.v1'' doesn''t exists !!! '
As result, release process was not completed and bundles are not appearing in operatorhub.io.

Can you help?
Thanks.

@iamjoemccormick
Copy link
Contributor

I encountered the same workflow error and it seems all commits to the main branch since November 1st are also encountering the same error. Perhaps some requirements changed around the bundle format? Though I would have expected the CI wouldn't have allowed my PR to be merged if that was the case.

@tomasbakk
Copy link
Collaborator

tomasbakk commented Nov 5, 2024

Hello. We are aware of this issue and currently it is under investigation. I will update you once we have more information. We are going to open a PR to debug it further. Thank you.

@tomasbakk
Copy link
Collaborator

@jvpasinatto @iamjoemccormick Hi guys. The issue was resolved. Latest manual release fixed the broken operator. Now we will proceed with syncing the operators that were affected during the window.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants