rhel-osp-director: After rebooting the OC nodes - unable to communicate with OC keystone.
Steps to reproduce:
1. Deploy overcloud 7.3
2. Upgrade to 8.0
3. Reboot all nodes as part of testing.
4. Try to run any command against the overcloud.
[stack@instack ~]$ nova list
No handlers could be found for logger "keystoneauth.identity.generic.base"
ERROR (ConnectFailure): Unable to establish connection to https://192.168.200.180:13000/v2.0/tokens
Port 13000 isn't open on the controller(s).
No stopped pcs resources.
Should be able to run commands against the overcloud.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
I just reproduced it today, this basically means that none of the API endpoints for the overcloud work after a restart, because everything is tied into keystone. What is worse, this breaks automation in a bad way, we don't even get errors that we can parse, any python-*-client based command just hangs.
If there is no scalable workaround (manual service restart on multiple hosts isn't exactly scalable), I'd suggest the priority is set to the highest possible.
please retest and confirm if this is still an issue with OSP10
Verified with openstack-tripleo-heat-templates-5.1.0-6.el7ost.noarch
By doing :
- Upgrade 9->10.
- Reboot OC nodes.
- Check the ability to communicate with the overcloud upon reboot.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.