Closed carlcsaposs-canonical closed 7 months ago
This is the original deprecation notice: https://github.com/canonical/lxd/issues/12419
I can change the NIC's specific options in lxd 5.21 as follows:
lxc config device set juju-f89d82-0 eth0 limits.priority=0
I've tested the following commands in lxc, using 5.20 from latest/stable.
Script results: https://pastebin.ubuntu.com/p/dk2MstxbbK/
This test is not doing what is expected in 5.20 either.
@phvalguima Until to last week, the test was passing successfully, thus doing what it was expected to - example successful run on main
with lxd (5.20/stable) 5.20-f3dd836
On this PR - where Carl pins LXD to 5.20
the test passes successfully with lxd (5.20/stable) 5.20-f3dd836
@Mehdi-Bendriss indeed the unit goes to lost for a period of time. Still, I think we should give a shot with lxc config device set juju-f89d82-0 eth0 limits.priority=0
before deciding to pin the version.
@phvalguima agreed. Which is exactly what this issue is about, to track and try/test the new fix you proposed, with LXD 5.21 - please make a PR with the fix, referencing this issue DPE-4055
But in order to not block other PRs, pinning LXD to the latest working version, is a sensible temporary solution.
test passed on 2024-04-11 with lxd 5.20-f3dd836 snap rev 27049 https://github.com/canonical/opensearch-operator/actions/runs/8640068334/job/23687547198 test failed on 2024-04-12 with lxd 5.21.1-43998c6 snap rev 28155 https://github.com/canonical/opensearch-operator/actions/runs/8655512868/job/23734702946#step:21:1686
https://chat.canonical.com/canonical/pl/877qxrhr37d99n3qibhgdayyra