Re: OKD Openshift-origin Control plane pods didn't come up Centos 7.6

2019-02-11 Thread Dhanushka Parakrama
Hi Daniel

Please find the below outputs , Seems like docker  containers are running .
So is their any reason why i'm getting this error?


[root@master ~]# ping master.example.com
PING master.example.com (192.168.8.90) 56(84) bytes of data.
64 bytes from master.example.com (192.168.8.90): icmp_seq=1 ttl=64
time=0.026 ms
64 bytes from master.example.com (192.168.8.90): icmp_seq=2 ttl=64
time=0.027 ms
64 bytes from master.example.com (192.168.8.90): icmp_seq=3 ttl=64
time=0.025 ms
^C
--- master.example.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.025/0.026/0.027/0.000 ms
[root@master ~]# host master.example.com
master.example.com has address 192.168.8.90



[root@master ~]# docker ps -a
CONTAINER IDIMAGE   COMMAND
  CREATED STATUS PORTS
 NAMES
2e3388e943b086d1731999db"/bin/bash -c
'#!/..."   2 minutes ago   Exited (1) 2 minutes ago

 
k8s_api_master-api-master.example.com_kube-system_4f2be631c4c438f1a1cbb365abe8008d_572
5922f5b0e62d86d1731999db"/bin/bash -c
'#!/..."   2 minutes ago   Exited (1) 2 minutes ago

 
k8s_controllers_master-controllers-master.example.com_kube-system_17dd294c94f3b66b916fb5744aa45704_573
cb23b7948526docker.io/openshift/origin-pod:v4.0.0   "/usr/bin/pod"
 2 days ago  Up 2 days
k8s_POD_master-controllers-master.example.com_kube-system_17dd294c94f3b66b916fb5744aa45704_0
db06dd94d55bdocker.io/openshift/origin-pod:v4.0.0   "/usr/bin/pod"
 2 days ago  Up 2 days
k8s_POD_master-api-master.example.com_kube-system_4f2be631c4c438f1a1cbb365abe8008d_0
96fa1bf8ac6186d1731999db"/bin/bash -c
'#!/..."   2 days ago  Exited (1) 2 days ago

k8s_controllers_master-controllers-master.example.com_kube-system_369e6fc74dadab198ffb8a2d58b411b2_30
c5b7363ddb7986d1731999db"/bin/bash -c
'#!/..."   2 days ago  Exited (1) 2 days ago

k8s_api_master-api-master.example.com_kube-system_79d9dfdfe61e5047d4c37a55e60d4cbd_30
f1d336ff1701ff5dd2137a4f"/bin/sh -c
'#!/bi..."   2 days ago  Up 2 days

k8s_etcd_master-etcd-master.example.com_kube-system_3f15983188280070dc68ad06ce271a4d_0
6ca7b19a1c1edocker.io/openshift/origin-pod:v4.0.0   "/usr/bin/pod"
 2 days ago  Up 2 days
k8s_POD_master-controllers-master.example.com_kube-system_369e6fc74dadab198ffb8a2d58b411b2_0
9cc3b1fdf8e5docker.io/openshift/origin-pod:v4.0.0   "/usr/bin/pod"
 2 days ago  Up 2 days
k8s_POD_master-etcd-master.example.com_kube-system_3f15983188280070dc68ad06ce271a4d_0
0a99f6529885docker.io/openshift/origin-pod:v4.0.0   "/usr/bin/pod"
 2 days ago  Up 2 days
k8s_POD_master-api-master.example.com_kube-system_79d9dfdfe61e5047d4c37a55e60d4cbd_0




On Mon, 11 Feb 2019 at 15:59, Daniel Comnea  wrote:

> is master.example.com resolvable ? you could also try to jump on the
> master node and see if the pod is up and if so start from that end.
>
> On Mon, Feb 11, 2019 at 4:28 AM Dhanushka Parakrama <
> parakrama1...@gmail.com> wrote:
>
>> Hi  Team
>>
>> I'm trying to install  openshift origin 3.11 in Centos 7.6 and i got the
>> "Pods didn't came up error"  Can you guys please help me the fix the below
>> error .
>>
>>
>>
>> Error
>> =
>>
>> failed: [master.example.com] (item=controllers) => {"attempts": 60,
>> "changed": false, "item": "controllers", "msg": {"cmd": "/usr/bin/oc get
>> pod master-controllers-master.example.com -o json -n kube-system",
>> "results": [{}], "returncode": 1, "stderr": "The connection to the server
>> master.example.com:8443 was refused - did you specify the right host or
>> port?\n", "stdout": ""}}
>> ...ignoring
>>
>> TASK [openshift_control_plane : Check status in the kube-system
>> namespace]
>> 
>> fatal: [master.example.com]: FAILED! => {"changed": true, "cmd": ["oc",
>> "status", "--config=/etc/origin/master/admin.kubeconfig", "-n",
>> "kube-system"], "delta": "0:00:00.199493", "end": "2019-02-11
>> 08:52:36.021191", "msg": "non-zero return code", "rc": 1, "start":
>> "2019-02-11 08:52:35.821698", "stderr": "The connection to the server
>> master.example.com:8443 was refused - did you specify the right host or
>> port?\nThe connection to the server master.example.com:8443 was refused
>> - did you specify the right host or port?\nThe connection to the server
>> master.example.com:8443 was refused - did you specify the right host or
>> port?\nThe connection to the server master.example.com:8443 was refused
>> - did you specify the right host or port?\nThe connection to the server
>> master.example.com:8443

Re: OKD Openshift-origin Control plane pods didn't come up Centos 7.6

2019-02-11 Thread Daniel Comnea
is master.example.com resolvable ? you could also try to jump on the master
node and see if the pod is up and if so start from that end.

On Mon, Feb 11, 2019 at 4:28 AM Dhanushka Parakrama 
wrote:

> Hi  Team
>
> I'm trying to install  openshift origin 3.11 in Centos 7.6 and i got the
> "Pods didn't came up error"  Can you guys please help me the fix the below
> error .
>
>
>
> Error
> =
>
> failed: [master.example.com] (item=controllers) => {"attempts": 60,
> "changed": false, "item": "controllers", "msg": {"cmd": "/usr/bin/oc get
> pod master-controllers-master.example.com -o json -n kube-system",
> "results": [{}], "returncode": 1, "stderr": "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?\n", "stdout": ""}}
> ...ignoring
>
> TASK [openshift_control_plane : Check status in the kube-system namespace]
> 
> fatal: [master.example.com]: FAILED! => {"changed": true, "cmd": ["oc",
> "status", "--config=/etc/origin/master/admin.kubeconfig", "-n",
> "kube-system"], "delta": "0:00:00.199493", "end": "2019-02-11
> 08:52:36.021191", "msg": "non-zero return code", "rc": 1, "start":
> "2019-02-11 08:52:35.821698", "stderr": "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?\nThe connection to the server master.example.com:8443 was refused -
> did you specify the right host or port?\nThe connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?\nThe connection to the server master.example.com:8443 was refused -
> did you specify the right host or port?\nThe connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?\nThe connection to the server master.example.com:8443 was refused -
> did you specify the right host or port?\nThe connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?\nThe connection to the server master.example.com:8443 was refused -
> did you specify the right host or port?\nThe connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?\nThe connection to the server master.example.com:8443 was refused -
> did you specify the right host or port?\nThe connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?\nThe connection to the server master.example.com:8443 was refused -
> did you specify the right host or port?\nThe connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?\nThe connection to the server master.example.com:8443 was refused -
> did you specify the right host or port?\nThe connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?\nThe connection to the server master.example.com:8443 was refused -
> did you specify the right host or port?", "stderr_lines": ["The connection
> to the server master.example.com:8443 was refused - did you specify the
> right host or port?", "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?", "The connection to the server master.example.com:8443 was refused
> - did you specify the right host or port?", "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?", "The connection to the server master.example.com:8443 was refused
> - did you specify the right host or port?", "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?", "The connection to the server master.example.com:8443 was refused
> - did you specify the right host or port?", "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?", "The connection to the server master.example.com:8443 was refused
> - did you specify the right host or port?", "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?", "The connection to the server master.example.com:8443 was refused
> - did you specify the right host or port?", "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?", "The connection to the server master.example.com:8443 was refused
> - did you specify the right host or port?", "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?", "The connection to the server master.example.com:8443 was refused
> - did you specify the right host or port?", "The connection to the server
> master.example.com:8443 was refused - did you specify the right host or
> port?"], "stdout": "", "stdout_lines": []}
> .

OKD Openshift-origin Control plane pods didn't come up Centos 7.6

2019-02-10 Thread Dhanushka Parakrama
Hi  Team

I'm trying to install  openshift origin 3.11 in Centos 7.6 and i got the
"Pods didn't came up error"  Can you guys please help me the fix the below
error .



Error
=

failed: [master.example.com] (item=controllers) => {"attempts": 60,
"changed": false, "item": "controllers", "msg": {"cmd": "/usr/bin/oc get
pod master-controllers-master.example.com -o json -n kube-system",
"results": [{}], "returncode": 1, "stderr": "The connection to the server
master.example.com:8443 was refused - did you specify the right host or
port?\n", "stdout": ""}}
...ignoring

TASK [openshift_control_plane : Check status in the kube-system namespace]

fatal: [master.example.com]: FAILED! => {"changed": true, "cmd": ["oc",
"status", "--config=/etc/origin/master/admin.kubeconfig", "-n",
"kube-system"], "delta": "0:00:00.199493", "end": "2019-02-11
08:52:36.021191", "msg": "non-zero return code", "rc": 1, "start":
"2019-02-11 08:52:35.821698", "stderr": "The connection to the server
master.example.com:8443 was refused - did you specify the right host or
port?\nThe connection to the server master.example.com:8443 was refused -
did you specify the right host or port?\nThe connection to the server
master.example.com:8443 was refused - did you specify the right host or
port?\nThe connection to the server master.example.com:8443 was refused -
did you specify the right host or port?\nThe connection to the server
master.example.com:8443 was refused - did you specify the right host or
port?\nThe connection to the server master.example.com:8443 was refused -
did you specify the right host or port?\nThe connection to the server
master.example.com:8443 was refused - did you specify the right host or
port?\nThe connection to the server master.example.com:8443 was refused -
did you specify the right host or port?\nThe connection to the server
master.example.com:8443 was refused - did you specify the right host or
port?\nThe connection to the server master.example.com:8443 was refused -
did you specify the right host or port?\nThe connection to the server
master.example.com:8443 was refused - did you specify the right host or
port?\nThe connection to the server master.example.com:8443 was refused -
did you specify the right host or port?\nThe connection to the server
master.example.com:8443 was refused - did you specify the right host or
port?\nThe connection to the server master.example.com:8443 was refused -
did you specify the right host or port?\nThe connection to the server
master.example.com:8443 was refused - did you specify the right host or
port?\nThe connection to the server master.example.com:8443 was refused -
did you specify the right host or port?", "stderr_lines": ["The connection
to the server master.example.com:8443 was refused - did you specify the
right host or port?", "The connection to the server master.example.com:8443
was refused - did you specify the right host or port?", "The connection to
the server master.example.com:8443 was refused - did you specify the right
host or port?", "The connection to the server master.example.com:8443 was
refused - did you specify the right host or port?", "The connection to the
server master.example.com:8443 was refused - did you specify the right host
or port?", "The connection to the server master.example.com:8443 was
refused - did you specify the right host or port?", "The connection to the
server master.example.com:8443 was refused - did you specify the right host
or port?", "The connection to the server master.example.com:8443 was
refused - did you specify the right host or port?", "The connection to the
server master.example.com:8443 was refused - did you specify the right host
or port?", "The connection to the server master.example.com:8443 was
refused - did you specify the right host or port?", "The connection to the
server master.example.com:8443 was refused - did you specify the right host
or port?", "The connection to the server master.example.com:8443 was
refused - did you specify the right host or port?", "The connection to the
server master.example.com:8443 was refused - did you specify the right host
or port?", "The connection to the server master.example.com:8443 was
refused - did you specify the right host or port?", "The connection to the
server master.example.com:8443 was refused - did you specify the right host
or port?", "The connection to the server master.example.com:8443 was
refused - did you specify the right host or port?"], "stdout": "",
"stdout_lines": []}
...ignoring

TASK [openshift_control_plane : debug]

ok: [master.example.com] => {
"msg": []
}

TASK [openshift_control_plane : Get pods in the kube-s