We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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_charms.yaml
The full context is in canonical/data-platform-workflows#259, TL;DR:
When building charms, the Set up environment step from build_charms.yaml, it fails with:
Set up environment
info: Adding user `runner' to group `lxd' ... Password: Invalid password. Error: Process completed with exit code 1.
canonical/charmed-kubeflow-workflows/.github/workflows/get_charms_build_with_cache.yaml@main
CI environment of the canonical/kfp-operators#640 PR and development branch
Failing for https://github.com/canonical/kfp-operators/actions/runs/12637402786/job/35211538308?pr=640#step:9:31
The text was updated successfully, but these errors were encountered:
Thank you for reporting your feedback to us!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6714.
This message was autogenerated
Sorry, something went wrong.
ci: bump build_charm.yaml 21.0.0 -> 24.0.5
74d20fd
This will bring a fix for the runner requesting a password when adding the runner user to the LXD group. Fixes #89
3552d3e
Successfully merging a pull request may close this issue.
Bug Description
The full context is in canonical/data-platform-workflows#259, TL;DR:
When building charms, the
Set up environment
step frombuild_charms.yaml
, it fails with:To Reproduce
canonical/charmed-kubeflow-workflows/.github/workflows/get_charms_build_with_cache.yaml@main
in any CI workflowEnvironment
CI environment of the canonical/kfp-operators#640 PR and development branch
Relevant Log Output
Additional Context
Failing for https://github.com/canonical/kfp-operators/actions/runs/12637402786/job/35211538308?pr=640#step:9:31
The text was updated successfully, but these errors were encountered: