This is due to secure permissions on /etc/keystone , presumably something that has been done as a security fix. Running keystone-manage via sudo solves that issue.
This is due to secure permissions on /etc/keystone , presumably something that has been done as a security fix. Running keystone-manage via sudo solves that issue.