You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If release_charm.yaml fails after successfully uploading the .charm files to Charmhub, it will fail during the upload .charm file step on subsequent retries, unless a new build is created.
This means that the entire workflow has to be restarted if release_charm.yaml fails after uploading the .charm files but before releasing the charm.
Workaround: restart the Build charm job that the Release job depends on
(Note: in most data platform repos, there are two Build charm jobs—one in the Tests that's cached and one for the release that's not cached—re-trigger the top-level Build charm job that's not cached)
If release_charm.yaml fails after successfully uploading the .charm files to Charmhub, it will fail during the upload .charm file step on subsequent retries, unless a new build is created.
This means that the entire workflow has to be restarted if release_charm.yaml fails after uploading the .charm files but before releasing the charm.
Example:
Workflow fails after .charm files uploaded: https://github.com/canonical/mysql-router-operator/actions/runs/4510876749/attempts/1
Re-try fails to upload .charm files: https://github.com/canonical/mysql-router-operator/actions/runs/4510876749/attempts/2
Entire workflow has to be restarted to pass: https://github.com/canonical/mysql-router-operator/actions/runs/4510876749/attempts/3
Error from logs
Solution
Parse the error; if it has already been uploaded to charmhub, catch the error
The text was updated successfully, but these errors were encountered: