fix: Workaround for LXD sometimes failing to refresh #85
Conversation
|
|
||
| # Workaround for lxd sometimes failing to refresh | ||
| sudo snap info lxd | grep "tracking": | awk '{print $2}' | grep "5.21/stable" || sudo snap stop lxd | ||
|
|
There was a problem hiding this comment.
Should we open an issue in concierge to inform Jon that we have to go through this workaround?
There was a problem hiding this comment.
Jon is already aware, I looked through the code and implementing this workaround is not straightforward, otherwise I would have put the workaround there.
I will open an issue also on concierge to track it. At the end of the day however, the issue is with the LXD snap, and this workaround needs to be in place in whatever CI implementation we use (I think it is already included in actions-operator).
There was a problem hiding this comment.
I found a relatively clean way of implementing the workaround on concierge. Here are the issue and PR:
jnsgruk/concierge#20
jnsgruk/concierge#21
If they get merged soon, we could drop this PR. Otherwise, we can merge this to unblock CI and revert it once it is not necessary.
|
Switching to draft as this is currently being tested here: canonical/sdcore-amf-k8s-operator#463 |
|
concierge 0.9.3 will be coming out soon with that workaround integrated. Closing this PR. |
Stop LXD if it will be refreshed to workaround an issue happening often in CI where LXD fails to refresh because of a missing socket file.