-
Notifications
You must be signed in to change notification settings - Fork 50
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
charming-actions/upload-charm
action is uploading images incorrectly and affecting charms' functionality
#962
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5952.
|
Doing some investigation after canonical/charming-actions#139 (comment) comment where they suggest that this change took place back in November 2023, I think I 've found another place where this has bitten us (and probably there is more) Kserve-controllerLooking at repo's releases, I see the following: Revision 561
Revision 558
and taking a look at the CI runs:
they have images with different hash but they are being released with the same resource-revision. |
It looks like this issue is also affecting the PR tracks and the "stable" tracks (e.g. |
…#147) Use resource revision number returned by upload-resource command when uploading a charm with resources. This replaces the previous behaviour when the action was listing resources and was using the latest available. Closes #139 Ref canonical/bundle-kubeflow#962
Bug Description
It appears that canonical/charming-actions#139 is affecting some charms' functionality:
WaitingStatus
because oferror initializing configuration '/envoy/envoy.yaml'
envoy-operator#114ch:1.8/edge
andch:latest/edge
kubeflow-dashboard-operator#194We need to investigate how this issue is affecting us:
To Reproduce
canonical/charming-actions#139 contains all the necessary information.
Environment
CI environment.
Relevant Log Output
Additional Context
No response
The text was updated successfully, but these errors were encountered: