Failed to discover available identity versions when contacting http://controller:5000/v3

Question

When trying to setup a controller node for openstack USSURI version. I'm asked to setup glance service as VM images management sub-service.

As of requirement : article (under ubuntu 18.04) :

1. I created a file named : admin-openrc.sh , under location : /usr/share/keystone , with content :

    export OS_USERNAME=admin 
    
    export OS_PASSWORD=ADMIN_PASS 
    
    export OS_PROJECT_NAME=admin 
    
    export OS_USER_DOMAIN_NAME=Default 
    
    export OS_PROJECT_DOMAIN_NAME=Default 
    
    export OS_AUTH_URL=http://controller:5000/v3 
    
    export OS_IDENTITY_API_VERSION=3`

where ADMIN_PASS is customized

2. Type cmd : source ./admin-openrc.sh

3. Then, create glance user with cmd : openstack user create --domain default --password-prompt glance

as output, I receive error message :

Failed to discover available identity versions when contacting http://controller:5000/v3. Attempting to parse version from URL.
Unable to establish connection to http://controller:5000/v3/auth/tokens: HTTPConnectionPool(host='controller', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fa20bba02b0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

Would anybody advise please ? I completed previously all steps : NTP install, openstack packages download, SQL install, RabbitMQ install, Memcached install, Etcd install, Keystone install (USSURI version)

It seems to be authentication issue maybe or something else ?

---

If the question helped you, up-vote it. Thanks in advance

Answer 1

Thanks for your remark. I succeeded in granting access to controller with address 10.0.0.11

I need to change NIC config accordingly (with IP : 10.0.0.11)

Answer 2

I added an entry to etc/hosts : 10.0.0.11 controller then re-execute this 2 cmds:

sudo keystone-manage bootstrap --bootstrap-password XXXXXXXX --bootstrap-admin-url http://10.0.0.11:5000/v3/ --bootstrap-internal-url http://10.0.0.11:5000/v3/ --bootstrap-public-url http://10.0.0.11:5000/v3/ --bootstrap-region-id RegionOne

sudo openstack user create --domain default --os-username XXXXXXXX --password-prompt --os-auth-url http://10.0.0.11:5000/v3 glance

But receieved, same error :

Failed to discover available identity versions when contacting http://10.0.0.11:5000/v3. Attempting to parse version from URL.

Unable to establish connection to http://10.0.0.11:5000/v3/auth/tokens: HTTPConnectionPool(host='10.0.0.11', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fe863dff290>: Failed to establish a new connection: [Errno 113] No route to host',))

Waiting for your help,

Answer 3

Also tried this :

$sudo ping controller

PING controller (10.0.0.11) 56(84) bytes of data.
From bassamvm01.internal.cloudapp.net (10.0.0.4) icmp_seq=1 Destination Host Unreachable
......
^C
--- controller ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5081ms
pipe 4

Answer 4

If this is a single control node setup (e.g. single instance of keystone) I would recommend just replacing controller with the management ip address. When going to production you tend to have a load balancer in front of these server, but you could also use a dns record resolvable on all your nodes (e.g. controller.internal).

# keystone-manage bootstrap --bootstrap-password ADMIN_PASS \
  --bootstrap-admin-url http://<your-ip>:5000/v3/ \
  --bootstrap-internal-url http://<your-ip>:5000/v3/ \
  --bootstrap-public-url http://<your-ip>:5000/v3/ \
  --bootstrap-region-id RegionOne

The disadvantage of using controller and not having a dns or load balancing solution in front (e.g. by adding it to the /etc/hosts file) is that you need to manually maintain this on all nodes, including any compute nodes you add to your setup.

Answer 5

that what just happened to me right now so i had tried to restart the network service and it work for me now. PS: i'm using openstack packstack on centos 7 the command:

> systemctl restart network