Description of problem: I have installed openstack-mitaka manually .Installation went well but when I am trying to run some command not working show error below: *********************************************************************** openstack service list Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. Unable to establish connection to http://controller:35357/v3/auth/tokens: HTTPConnectionPool(host='controller', port=35357): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x3e0a090>: Failed to establish a new connection: [Errno 111] Connection refused',)) ************************************************************************ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Tried to install openstack-mitaka on RHEL OS. 2.Install services one by one on controller and compute as need. 3.Once you are done with installation just try to login on dashboard Actual results: Once I am trying to login it showing error m unable to match keystone endpoint. so command "openstack service list" is not working. Expected results: command "openstack service list" should be work on controller node and also user should be able to login to Dashboard. Additional info:
Are you using the Mitaka release of RDO, or is this RHEL OSP? I would like to make sure this bug is filed appropriately. It sounds like you have performed a manual installation instead of using TripleO (or OSP Director if you are using RHEL OSP). It is hard to say exactly what is wrong without knowing how you performed your installation.
Mitaka release of RDO . I have followed below document. https://docs.openstack.org/mitaka/install-guide-rdo/horizon-install.html
Moving this to be filed against RDO instead of RHEL OSP. The error message you proivided is a basic connection error. Have you verified that keystone is up and running and listening on port 35357 (check with 'netstat -an | grep 35357')? This could also be a hostname resolution issue, as you are using a short hostname of 'controller' instead of a FQDN. I recommend you test that Keystone is responding using curl with the following URLs (replace the IP placeholder with your controller IP address): curl -v http://<ip address>:35357 curl -v http://controller:35357
As Nathan Pointed out some basic checks needs to be done to troubleshoot this issue further, since this bug is old and Mitaka is EOL closing this bug, feel free to open against maintained RDO release(queens+) if you see similar issue there so it can be fixed.