Closed orfeas-k closed 2 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5656.
This message was autogenerated
Although this failed for 4 consecutive times, reran this now and it succeeded https://github.com/canonical/kfp-operators/actions/runs/9019490085/job/24814815779?pr=456.
We see this in different charms as well e.g. istio-pilot
Moving this issue to canonical/bundle-kubeflow
as it is happening for more than one charm.
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6081.
This message was autogenerated
pip install --no-binary=:all: --requirement=requirements.txt
for istio-pilot in a fresh LXC container with python 3.8.10, pip 24.1 is completing without errors, after installing charm bin dependencies with apt-get install rustc cargo libffi-dev libssl-dev pkg-config
Opened some PRs to play around with setuptools
installation in charm-python-packages, in case there was an incompatibility between the versions installed for the charm. The rationale there was that:
However, even when it installed a newer version of setuptools, that didn't change much
Building the charm in a fresh LXC container using charmcraft from latest/edge
is successful. Same with charmcraft from latest/candidate
In the CI though, switching charmcraft from latest/edge
(runs) to latest/candidate
(runs) seems to fix the issue and the charm is being built. Thus, I sent this PR https://github.com/canonical/istio-operators/pull/512 to use charmcraft from latest/candidate. Let the charmcraft team in Matrix know about this and asked for pointers
That being said, integration
test case test_enable_ingress_auth
fails https://github.com/canonical/istio-operators/actions/runs/10388478915/job/28764213343?pr=512#step:8:21 (both on Microk8s 1.25 and 1.26)
There are some indicators that istio-pilot could be misbehaving (although having been built successfully)
istio-pilot/0* maintenance executing 10.1.138.74 (stop) stopping charm software
...
istio-pilot/0* unknown lost 10.1.138.74 agent lost, see 'juju show-status-log istio-pilot/0'
Downloading the logs artifact the only "error" there is
`unit-istio-pilot-0: 14:24:02 INFO unit.istio-pilot/0.juju-log ingress:6: Removing gateway due to errors in processing the ingress-auth relation.`
The issue was worked around in #531 by using charmcraft from latest/candidate
in integration tests and backporting changes that free disk space in runner #519 and updating cert_handler library to v1 #517.
Doing a little more debugging, it looks like the issue could be caused because we are building two charms at the same time, since:
charmcraft pack
for both charms sequentially (and skip tests) and both builds succeed (but take around 1h to complete)In the future, we could hit this again when charmcraft from latest/edge
is promoted. If this happens, we should allocate time to work on a larger effort to refactor our CI as described e.g. in #766 or https://github.com/canonical/istio-operators/pull/412, which would probably eliminate this issue as well.
Bug Description
As of yesterday, bundle tests v2 fail to build the charms with the error shown in logs below. This has been observed in multiple runs (example) with the same exact logs. Note that:
kfp-ui
) locally withcharmcraft pack
worksTo Reproduce
Run the CI from
main
.Environment
Juju 3.5 Microk8s v1.25.16 charmcraft 2.6.0
Relevant Log Output
logs from running August 2024
Additional Context
No response