I confirm that the last failing run is running my charm and that it contains my fix, since I can see these new traces [0] in debug_log.txt.
Note that in the log I can see that there is one unit (keystone/1) that has never been considered ready and also that keystone has never advertised the application as ready. This is also reflected in juju_status.yaml:
keystone:
charm: cs:~aurelien-lourot/keystone-1
series: bionic
os: ubuntu
charm-origin: jujucharms
charm-name: keystone
charm-rev: 1
charm-version: 07de96c
exposed: false
application-status:
current: waiting
message: Some units are not ready
since: 13 Jul 2020 16:42:12Z
So indeed I would now start looking at keystone's consumers as potential culprits.
I confirm that the last failing run is running my charm and that it contains my fix, since I can see these new traces [0] in debug_log.txt.
Note that in the log I can see that there is one unit (keystone/1) that has never been considered ready and also that keystone has never advertised the application as ready. This is also reflected in juju_status.yaml:
keystone: lourot/ keystone- 1 -status:
charm: cs:~aurelien-
series: bionic
os: ubuntu
charm-origin: jujucharms
charm-name: keystone
charm-rev: 1
charm-version: 07de96c
exposed: false
application
current: waiting
message: Some units are not ready
since: 13 Jul 2020 16:42:12Z
So indeed I would now start looking at keystone's consumers as potential culprits.
0: https:/ /github. com/juju/ charm-helpers/ pull/476/ files#diff- 935a00f40074c3c 59d617c88f71e42 efR2246