No, it's not "during" bootstrap, bootstrap had finished, services were added, units were being added and then it went boom. However I believe it is the implicit upgrade, my gripe is that this upgrade doesn't occur during the "block til we're done" bootstrap.
RE: Does this happen with 1.23.2?
Yes, it's with 1.23.2 client and proposed agent-stream so that 1.23.3 tools are found.
I'm almost certain that the charms in question aren't important, you will get a config-changed error because those are credentials for an OpenStack deployment that's not publicly available (and has subsequently been torn down)
RE: implicit upgrade during bootstrap?
No, it's not "during" bootstrap, bootstrap had finished, services were added, units were being added and then it went boom. However I believe it is the implicit upgrade, my gripe is that this upgrade doesn't occur during the "block til we're done" bootstrap.
RE: Does this happen with 1.23.2?
Yes, it's with 1.23.2 client and proposed agent-stream so that 1.23.3 tools are found.
I'm almost certain that the charms in question aren't important, you will get a config-changed error because those are credentials for an OpenStack deployment that's not publicly available (and has subsequently been torn down)