While we cannot reproduce this bug without autopilot, David and I discussed the deeper issue where enterprises parties working with certification need to control the exact version juju selects for the state-server. Juju CI does this by adding an option to env in environments.yaml like so:
agent-version: 1.22.1
This technique is not a hack. Any party or tool can set this to ensure repeatability of a process. We may want to publicise this technique more widely. In the case of tools like OIL, autopilot, and Juju CI, this ensures unwanted upgrades are avoided.
While we cannot reproduce this bug without autopilot, David and I discussed the deeper issue where enterprises parties working with certification need to control the exact version juju selects for the state-server. Juju CI does this by adding an option to env in environments.yaml like so:
agent-version: 1.22.1
This technique is not a hack. Any party or tool can set this to ensure repeatability of a process. We may want to publicise this technique more widely. In the case of tools like OIL, autopilot, and Juju CI, this ensures unwanted upgrades are avoided.