I'm still a little confused about what is happening. When I deploy the lma charms with juju 2.9.35 there is not problem, but this bug shows up when I redeploy with juju 2.9.36. In both cases the pylibjuju version is 3.0.1.
@gabrielcocenza will try to pin the pylibjuju version for the juju-lint charm to a stable version. This may still be a release blocker though as, unlike with juju 3.0, I think we should expect full backwards compatibility with 2.9.35.
@gabrielcocenza did some investigation and found a reproducer for the problem: https:/ /pastebin. canonical. com/p/C9YfB9DZT k/
I'm still a little confused about what is happening. When I deploy the lma charms with juju 2.9.35 there is not problem, but this bug shows up when I redeploy with juju 2.9.36. In both cases the pylibjuju version is 3.0.1.
Here is a crashdump from 2.9.35 (without this failure): https:/ /oil-jenkins. canonical. com/artifacts/ a619937a- e7b9-4957- bac9-6bc6940ca4 7e/generated/ generated/ lma-maas/ juju-crashdump- lma-maas- 2022-10- 26-09.34. 00.tar. gz /oil-jenkins. canonical. com/artifacts/ 7df9a1a2- cde9-48c1- 94f7-3894c01d27 bd/generated/ generated/ lma-maas/ juju-crashdump- lma-maas- 2022-10- 26-06.57. 34.tar. gz
Here is a crashdump from 2.9.36 (with this failure): https:/
@gabrielcocenza will try to pin the pylibjuju version for the juju-lint charm to a stable version. This may still be a release blocker though as, unlike with juju 3.0, I think we should expect full backwards compatibility with 2.9.35.