Description of problem: I was trying an overcloud deployment(3 ctrl, 1 compute, 1 ceph) on baremetal with network isolation and it failed with the following error message after long period: ERROR: openstack ERROR: Authentication failed. Please try again with option --include-password or export HEAT_INCLUDE_PASSWORD=1 Authentication required After further checks I discovered that connectivity for nodes on the storage network was broken. I disabled the storage network thus bringing it to the provisioning network and deployment succeeded. However the error that I got is misleading. This leads me thinking that a deployment will fail without a proper message pointing to which node(IP on certain network) timed out if one node's networking is not configured correctly. This will make troubleshooting difficult especially when you'll have large deployments. I expect poor switch port configuration or incorrect cabling to happen and we should be able to point this out when deployment fails.
this is not a regression, removing from osp10 Further, I believe we may have fixed this by having Heat reauthenticate to Keystone prior to the token expiring. Steve can you confirm if that was the root cause for this error?
This looks like a dupe for a bug fixed at about the same time as this one was raised. The fix was to raise the token expiry, but James could be right about token re-authentication happening now too. *** This bug has been marked as a duplicate of bug 1235908 ***