Fail to connect to keystone after deploy following the guide(NFS provider)

Bug #1780915 reported by Kevin Zhao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-helm
Invalid
Undecided
Naeil Ezzoueidi

Bug Description

Fail to connect the Keystone. Follow the guide:
https://docs.openstack.org/openstack-helm/latest/install/developer/deploy-with-nfs.html
Use OpenStack image newton and pike. All failed
After deploy the keystone, try this:

linux@os-helm-x86:~$ export OS_CLOUD=openstack_helm
linux@os-helm-x86:~$ openstack endpoint list
Failed to discover available identity versions when contacting http://keystone.openstack.svc.cluster.local/v3. Attempting to parse version from URL.
Unable to establish connection to http://keystone.openstack.svc.cluster.local/v3/auth/tokens: HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f976bccb710>: Failed to establish a new connection: [Errno -2] Name or service not known',))
linux@os-helm-x86:~$

The pod:
linux@os-helm-x86:~$ kubectl get pods -n openstack
NAME READY STATUS RESTARTS AGE
ingress-7b4bc84cdd-cc6c4 1/1 Running 0 23h
ingress-error-pages-586c7f86d6-858bl 1/1 Running 0 23h
keystone-api-58474df87f-wpbg4 1/1 Running 0 23h
keystone-bootstrap-vmfk9 0/1 Completed 0 23h
keystone-credential-setup-gn7v9 0/1 Completed 0 23h
keystone-db-init-dr4g9 0/1 Completed 0 23h
keystone-db-sync-mqlxv 0/1 Completed 0 23h
keystone-domain-manage-dl2gt 0/1 Completed 0 23h
keystone-fernet-rotate-1531137600-t6947 0/1 Completed 0 19h
keystone-fernet-rotate-1531180800-4pblg 0/1 Completed 0 7h
keystone-fernet-setup-49hk5 0/1 Completed 0 23h
keystone-rabbit-init-shb7s 0/1 Completed 0 23h
mariadb-ingress-84894687fd-6mr98 1/1 Running 0 23h
mariadb-ingress-error-pages-78fb865f84-582x8 1/1 Running 0 23h
mariadb-server-0 1/1 Running 0 23h
memcached-memcached-5db74ddfd5-fhjg6 1/1 Running 0 23h
rabbitmq-rabbitmq-0 1/1 Running 0 23h
linux@os-helm-x86:~$ kubectl get svc -n openstack
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress ClusterIP 10.103.148.178 <none> 80/TCP,443/TCP 23h
ingress-error-pages ClusterIP None <none> 80/TCP 23h
ingress-exporter ClusterIP 10.99.180.72 <none> 10254/TCP 23h
keystone ClusterIP 10.99.76.74 <none> 80/TCP,443/TCP 23h
keystone-api ClusterIP 10.100.23.101 <none> 80/TCP,35357/TCP 23h
mariadb ClusterIP 10.100.221.150 <none> 3306/TCP 23h
mariadb-discovery ClusterIP None <none> 3306/TCP,4567/TCP 23h
mariadb-ingress-error-pages ClusterIP None <none> 80/TCP 23h
mariadb-server ClusterIP 10.111.66.56 <none> 3306/TCP 23h
memcached ClusterIP 10.104.61.30 <none> 11211/TCP 23h
rabbitmq ClusterIP 10.104.164.133 <none> 5672/TCP,25672/TCP,15672/TCP 23h
rabbitmq-dsv-7b1733 ClusterIP None <none> 5672/TCP,25672/TCP,15672/TCP 23h
rabbitmq-mgr-7b1733 ClusterIP 10.97.253.46 <none> 80/TCP,443/TCP 23h
linux@os-helm-x86:~$ kubectl get ing -n openstack
NAME HOSTS ADDRESS PORTS AGE
keystone keystone,keystone.openstack,keystone.openstack.svc.cluster.local 80 23h
openstack-ingress-openstack *.openstack.svc.cluster.local 80 23h
rabbitmq-mgr-7b1733 rabbitmq-mgr-7b1733,rabbitmq-mgr-7b1733.openstack,rabbitmq-mgr-7b1733.openstack.svc.cluster.local 80 23h

The ingress pod log is here:
http://paste.openstack.org/show/725390/

Revision history for this message
Kevin Zhao (kevin-zhao) wrote :

linux@os-helm-x86:~$ kubectl get ing -n openstack
NAME HOSTS ADDRESS PORTS AGE
cloudformation cloudformation,cloudformation.openstack,cloudformation.openstack.svc.cluster.local 80 3m
heat heat,heat.openstack,heat.openstack.svc.cluster.local 80 3m
keystone keystone,keystone.openstack,keystone.openstack.svc.cluster.local 80 1d
openstack-ingress-openstack *.openstack.svc.cluster.local 80 1d
rabbitmq-mgr-7b1733 rabbitmq-mgr-7b1733,rabbitmq-mgr-7b1733.openstack,rabbitmq-mgr-7b1733.openstack.svc.cluster.local 80 1d

linux@os-helm-x86:~$ ping keystone
ping: unknown host keystone
linux@os-helm-x86:~$ ping cloudformation
ping: unknown host cloudformation
linux@os-helm-x86:~$ ping heat.openstack.svc.cluster.local
ping: unknown host heat.openstack.svc.cluster.local

Revision history for this message
Kevin Zhao (kevin-zhao) wrote :
Changed in openstack-helm:
status: New → Invalid
Revision history for this message
Naeil Ezzoueidi (naeilzoueidi) wrote :

I am having the same issue.

Changed in openstack-helm:
status: Invalid → Confirmed
Revision history for this message
Naeil Ezzoueidi (naeilzoueidi) wrote :

I am working on it, will see if it is an issue from Kubernetes or from Openstack

Changed in openstack-helm:
assignee: nobody → Naeil ZOUEIDI (naeilzoueidi)
Revision history for this message
Pete Birley (portdirect) wrote :

Kevin identified that this issue was caused by not configuring nsswitch.conf appropriately.
(https://docs.openstack.org/openstack-helm/latest/install/developer/requirements-and-host-config.html#host-configuration)

Changed in openstack-helm:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.