21.10 release notes don't mention upgrade ordering requirement for Keystone

[James Troup]

The charm upgrade guide¹ says:

  There is no special order in which to upgrade the charms.

For the 21.10 release, this is incorrect. If you don't upgrade keystone first, other charms (e.g. nova-cloud-controller) will fail to upgrade and go into an error state. Either there should be mention of this in the release notes or the upgrade guide wording should be adjusted.

¹ https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/upgrade-charms.html

-----------------------------------
Release: 0.0.1.dev494 on 2021-10-28 17:40:12
SHA: 82f75159a2c0dc11d3f13f8e6a3106379c16d50b
Source: https://opendev.org/openstack/charm-guide/src/doc/source/release-notes/2110.rst
URL: https://docs.openstack.org/charm-guide/latest/release-notes/2110.html

[Felipe Reyes (freyes)]

this issue could have been produced by this commit:
https://opendev.org/openstack/charm-keystone/commit/9b8b81a0bc8406f03b2de884eeec91b8e8f2d442

I need to verify what the hook error are about though.

[Billy Olsen (billy-olsen)]

Actually, I believe it was this commit to charmhelpers - https://github.com/juju/charm-helpers/commit/8b30083f5f5c7fea597fc92472325bba3aefdc5c

I believe this causes the charms to go into a waiting state, not an error state iirc. Essentially blocked waiting for internal endpoints to be provided.

[Felipe Reyes (freyes)]

On Mon, 2022-01-31 at 16:56 +0000, Billy Olsen wrote:
> Actually, I believe it was this commit to charmhelpers -
> https://github.com/juju/charm-
> helpers/commit/8b30083f5f5c7fea597fc92472325bba3aefdc5c
>
> I believe this causes the charms to go into a waiting state, not an
> error state iirc. Essentially blocked waiting for internal endpoints
> to
> be provided.

Thanks for pointing this out. I will explore deploying an environment
with the charm's version prior this patch landed.