Comment 2 for bug 2014226

Thanks for filing a bug and making cloud-init better and for the documentation request plug as well.
I'm adding a docs tag to the bug so it could be looked at from a documentation standpoint as well.

This bug looks conspicuously like the former bug https://bugs.launchpad.net/cloud-init/+bug/1958506 which was fixed in cloud-init version 22.2. If possible, would you be able to try reproducing this issue with a newer version of cloud-init?

You may be able to install cloud-init upstream's latest approved upstream release of 23.1 from our copr repo
https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/packages/

Once cloud-init is upgraded to 23.1 try running `sudo cloud-init clean --logs --reboot` to force cloud-init to try to reconfigure the system and network from scratch across reboot. If the KeyError still persists, then we know this is a new bug and not one formerly fixed.
I'm marking it 'incomplete' status above. Please set back to 'New' if you get a chance to confirm that latest cloud-init 23.1 still exhibits this issue.