All 2.3.6 binaries should now be removed from distribution. The snap
should refresh to 2.3.5 if you have the 2.3.6 binary.
Thanks,
Nicholas
On 04/23/2018 10:06 AM, Adam Israel wrote:
Hi all,
What wasn't clear to me from the email is that, with 2.3.6 pulled,
we're unable to bootstrap new
All 2.3.6 binaries should now be removed from distribution. The snap
should refresh to 2.3.5 if you have the 2.3.6 binary.
Thanks,
Nicholas
On 04/23/2018 10:06 AM, Adam Israel wrote:
Hi all,
What wasn't clear to me from the email is that, with 2.3.6 pulled,
we're unable to bootstrap new
Hi all,
What wasn't clear to me from the email is that, with 2.3.6 pulled, we're
unable to bootstrap new controllers without providing an alternate
agent-stream, i.e., --agent-stream=proposed.
In future cases like this, is it feasible to roll back the snap to the
previous version, so new
Hi all,
What wasn't clear to me from the email is that, with 2.3.6 pulled, we're
unable to bootstrap new controllers without providing an alternate
agent-stream, i.e., --agent-stream=proposed.
In future cases like this, is it feasible to roll back the snap to the
previous version, so new
Hey people,
We have field reports where a 2.3.6 upgrade interacted badly with some
charm settings causing Juju to get itself into a stuck, somewhat corrupt
state. We are still evaluating how to fix this for stuck systems.
The symptom is the 2.3.6 upgrade fails and gets stuck.
The agents are
Hey people,
We have field reports where a 2.3.6 upgrade interacted badly with some
charm settings causing Juju to get itself into a stuck, somewhat corrupt
state. We are still evaluating how to fix this for stuck systems.
The symptom is the 2.3.6 upgrade fails and gets stuck.
The agents are
