/srv/irclogs.ubuntu.com/2020/10/30/#juju.txt

stickupkidmanadart, https://github.com/juju/juju/pull/1219610:17
Hybrid512Hi10:50
Hybrid512 I had a juju upgrade this morning (2.8.6/snap) which went well.10:51
Hybrid512I then upgraded the juju controller and as soon as I did that, it disturbed my previous deployments10:51
Hybrid512agent was unavailable (which is quite normal since controller was upgrading itself) but then, when it went up again, it looks like the model was reconfiguring itself for every charms which broke some VIPs and had quite some impacts10:51
Hybrid512agent was unavailable (which is quite normal since controller was upgrading itself) but then, when it went up again, it looks like the model was reconfiguring itself for every charms which broke some VIPs and had quite some impacts10:52
Hybrid512I didn't thought the controller would be that critical for **deployed** applications ... I could easily imagine that it would be critical to **new** deployments but not already deployed ones10:52
Hybrid512what is the best practice in such case ?10:52
stickupkidHybrid512, firstly I believe a bug at the very least would be good to track this, as it does sound like we did something wrong11:05
Hybrid512stickupkid I can create it ... just didn't know if this was a bug or if I did something wrong11:06
Hybrid512so at fisrt, would be great to know your recommended best practices towards that11:06
stickupkidI don't know enough, maybe manadart does11:07
manadartHybrid512: What version was the upgrade from?11:09
Hybrid5122.8.5 -> 2.8.611:10
Hybrid512from snap package11:10
stickupkidhml, https://github.com/juju/juju/pull/1223215:33
hmlstickupkid: ack15:33

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!