Unable to register a user with Deis on s390x

[rishi.in...@gmail.com]

Hello,

I was finally able to get most of the Deis core components (except deis-monitor-telegraf) built and running on s390x.  Now I am trying to create a user to start the process of app deployment.  However, I am getting the following error:

/==================================================/

# deis register http://x.xx.xxx.xxx.nip.io

Error: http://x.xx.xxx.xxx.nip.io does not appear to be a valid Deis controller.

Make sure that the Controller URI is correct, the server is running and

your deis version is correct.

/==================================================/

I can confirm that my router is running as seen below:

/==================================================/

NAMESPACE   NAME                                     READY     STATUS             RESTARTS   AGE

deis        deis-builder-925871579-njjx1             1/1       Running            1          5h

deis        deis-controller-121201537-y8u5j          1/1       Running            1          5d

deis        deis-database-2346481533-wgt1o           1/1       Running            0          5d

deis        deis-logger-1750174080-5edv2             1/1       Running            2          5d

deis        deis-logger-fluentd-0vrp5                1/1       Running            0          5h

deis        deis-logger-redis-4282343581-zpzf0       1/1       Running            0          5d

deis        deis-minio-4284334528-8ioxc              1/1       Running            0          5d

deis        deis-monitor-grafana-947410455-10toi     1/1       Running            0          5d

deis        deis-monitor-influxdb-802438432-yh8n8    1/1       Running            0          5d

deis        deis-monitor-telegraf-1qnct              0/1       CrashLoopBackOff   62         4h

deis        deis-nsqd-2528936859-qwiv8               1/1       Running            0          5d

deis        deis-registry-4098254024-md5lc           1/1       Running            1          5d

deis        deis-registry-proxy-5clyi                1/1       Running            0          5h

deis        deis-router-1833288991-u41gg             1/1       Running            0          5h

deis        deis-workflow-manager-3855316227-oew1d   1/1       Running            0          5h

deis        kube-dns-v8-vtbot                        4/4       Running            4          5d

However,

# kubectl get svc deis-router --namespace=deis

NAME          CLUSTER-IP   EXTERNAL-IP   PORT(S)                            AGE

deis-router   10.0.0.36    <pending>     80/TCP,443/TCP,2222/TCP,9090/TCP   20d

/==================================================/

EXTERNAL-IP is shown to be in "pending" state.  I am not sure if that is a cause of concern and if so how can I debug this further?

I have already used "localhost", IP, 127.0.0.1 values for controller but it did not help.

Any pointers greatly appreciated.

[Matthew Fisher]

This looks related to https://github.com/deis/workflow/issues/533. Essentially the cloud provider (I'm assuming you're running on bare metal) does not support creating a load balancer for you when the service defines it as `type: LoadBalancer` like the router.

--
You received this message because you are subscribed to the Google Groups "Deis Users List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to deis-users+unsubscribe@googlegroups.com.
To post to this group, send email to deis-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/deis-users/3ff3053f-f859-4cca-9993-a14fe05744de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[rishi.in...@gmail.com]

Thanks Matt,

That helped to some extent but it still doesn't like it.  I think I have the right format and the NodePort value.

# kubectl describe svc deis-router --namespace=deis

Name:                   deis-router

Namespace:              deis

Labels:                 heritage=deis

Selector:               app=deis-router

Type:                   NodePort

IP:                     10.0.0.191

Port:                   http    80/TCP

NodePort:               http    32359/TCP

Endpoints:              172.17.0.9:8080

Port:                   https   443/TCP

NodePort:               https   30418/TCP

Endpoints:              172.17.0.9:6443

Port:                   builder 2222/TCP

NodePort:               builder 32693/TCP

Endpoints:              172.17.0.9:2222

Port:                   healthz 9090/TCP

NodePort:               healthz 30300/TCP

Endpoints:              172.17.0.9:9090

Session Affinity:       None

No events.

# deis register http://x.xx.xxx.xx.nip.io:32359

Error: http://x.xx.xxx.xx.nip.io:32359 does not appear to be a valid Deis controller.

Make sure that the Controller URI is correct, the server is running and

your deis version is correct.

#

To unsubscribe from this group and stop receiving emails from it, send an email to deis-users+...@googlegroups.com.

[rishi.in...@gmail.com]

nvm - it worked after I corrected my URL - it was missing "deis" .. so this works in case someone runs into this issue:

# deis register http://deis.x.xx.xxx.xx.nip.io:32359

username: admin

password:

password (confirm):

[Matthew Fisher]

Try adding a new entry in /etc/hosts. Based on the output I'd assume the following would work:

10.0.0.191    deis.k8s.local deis-builder.k8s.local

Then from your client run `deis register http://deis.k8s.local:32359` and see if that works. If that doesn't work, then I'd start by checking your network connection to the host and make sure that the controller is definitely listening on port 32359 on 10.0.0.191.

To unsubscribe from this group and stop receiving emails from it, send an email to deis-users+unsubscribe@googlegroups.com.

To post to this group, send email to deis-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/deis-users/150336af-9eec-4cd7-ab90-15df29058392%40googlegroups.com.