Skip to content

Instantly share code, notes, and snippets.

@amitkumarj441
Last active June 23, 2017 11:46
Show Gist options
  • Select an option

  • Save amitkumarj441/5fb2aa4bfd232319a424de42b98e6d5c to your computer and use it in GitHub Desktop.

Select an option

Save amitkumarj441/5fb2aa4bfd232319a424de42b98e6d5c to your computer and use it in GitHub Desktop.
OpenShift 1.5 status
[root@viaq openshift-ansible]oc status
In project logging on server https://viaq.logging.test:8443
svc/logging-es - 172.30.39.221:9200 -> restapi
dc/logging-es-7vo926zw deploys docker.io/openshift/origin-logging-elasticsearch:v1.5.1
deployment #2 deployed 18 hours ago - 1 pod
deployment #1 failed 22 hours ago: config change
svc/logging-es-cluster - 172.30.63.148:9300
dc/logging-es-7vo926zw deploys docker.io/openshift/origin-logging-elasticsearch:v1.5.1
deployment #2 deployed 18 hours ago - 1 pod
deployment #1 failed 22 hours ago: config change
https://kibana.viaq.logging.test (reencrypt) (svc/logging-kibana)
dc/logging-kibana deploys
docker.io/openshift/origin-logging-kibana:v1.5.1
deployment #2 deployed 17 hours ago - 1 pod
deployment #1 failed 22 hours ago: config change
docker.io/openshift/origin-logging-auth-proxy:v1.5.1
deployment #2 deployed 17 hours ago - 1 pod
deployment #1 failed 22 hours ago: config change
svc/logging-mux - 172.30.163.15 ports 24284->mux-forward, 23456->tcp-json
dc/logging-mux deploys docker.io/openshift/origin-logging-fluentd:v1.5.1
deployment #1 failed 17 hours ago: config change
dc/logging-curator deploys docker.io/openshift/origin-logging-curator:v1.5.1
deployment #1 deployed 22 hours ago - 1 pod
pod/logging-fluentd-024kj runs docker.io/openshift/origin-logging-fluentd:v1.5.1
Errors:
1 error and 1 warning identified, use 'oc status -v' to see details.
[root@viaq openshift-ansible]# oc status -v
In project logging on server https://viaq.logging.test:8443
svc/logging-es - 172.30.39.221:9200 -> restapi
dc/logging-es-7vo926zw deploys docker.io/openshift/origin-logging-elasticsearch:v1.5.1
deployment #2 deployed 18 hours ago - 1 pod
deployment #1 failed 22 hours ago: config change
svc/logging-es-cluster - 172.30.63.148:9300
dc/logging-es-7vo926zw deploys docker.io/openshift/origin-logging-elasticsearch:v1.5.1
deployment #2 deployed 18 hours ago - 1 pod
deployment #1 failed 22 hours ago: config change
https://kibana.viaq.logging.test (reencrypt) (svc/logging-kibana)
dc/logging-kibana deploys
docker.io/openshift/origin-logging-kibana:v1.5.1
deployment #2 deployed 17 hours ago - 1 pod
deployment #1 failed 22 hours ago: config change
docker.io/openshift/origin-logging-auth-proxy:v1.5.1
deployment #2 deployed 17 hours ago - 1 pod
deployment #1 failed 22 hours ago: config change
svc/logging-mux - 172.30.163.15 ports 24284->mux-forward, 23456->tcp-json
dc/logging-mux deploys docker.io/openshift/origin-logging-fluentd:v1.5.1
deployment #1 failed 17 hours ago: config change
dc/logging-curator deploys docker.io/openshift/origin-logging-curator:v1.5.1
deployment #1 deployed 22 hours ago - 1 pod
pod/logging-fluentd-024kj runs docker.io/openshift/origin-logging-fluentd:v1.5.1
Errors:
* route/logging-kibana is routing traffic to svc/logging-kibana, but either the administrator has not installed a router or the router is not selecting this route.
try: oc adm router -h
Warnings:
* pod/logging-curator-1-hklth has restarted 22 times
Info:
* pod/logging-es-7vo926zw-1-deploy has no liveness probe to verify pods are still running.
try: oc set probe pod/logging-es-7vo926zw-1-deploy --liveness ...
* pod/logging-fluentd-024kj has no liveness probe to verify pods are still running.
try: oc set probe pod/logging-fluentd-024kj --liveness ...
* pod/logging-kibana-1-deploy has no liveness probe to verify pods are still running.
try: oc set probe pod/logging-kibana-1-deploy --liveness ...
* pod/logging-mux-1-deploy has no liveness probe to verify pods are still running.
try: oc set probe pod/logging-mux-1-deploy --liveness ...
* dc/logging-curator has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
try: oc set probe dc/logging-curator --readiness ...
* dc/logging-curator has no liveness probe to verify pods are still running.
try: oc set probe dc/logging-curator --liveness ...
* dc/logging-es-7vo926zw has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
try: oc set probe dc/logging-es-7vo926zw --readiness ...
* dc/logging-es-7vo926zw has no liveness probe to verify pods are still running.
try: oc set probe dc/logging-es-7vo926zw --liveness ...
* dc/logging-kibana has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
try: oc set probe dc/logging-kibana --readiness ...
* dc/logging-kibana has no liveness probe to verify pods are still running.
try: oc set probe dc/logging-kibana --liveness ...
* dc/logging-mux has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
try: oc set probe dc/logging-mux --readiness ...
* dc/logging-mux has no liveness probe to verify pods are still running.
try: oc set probe dc/logging-mux --liveness ...
View details with 'oc describe <resource>/<name>' or list everything with 'oc get all'.
[root@viaq openshift-ansible]#
[root@viaq openshift-ansible]# oc get pods
NAME READY STATUS RESTARTS AGE
logging-curator-1-hklth 1/1 Running 22 21h
logging-es-7vo926zw-1-deploy 0/1 Error 0 21h
logging-es-7vo926zw-2-phjrq 1/1 Running 0 18h
logging-fluentd-024kj 1/1 Running 1 21h
logging-kibana-1-deploy 0/1 Error 0 21h
logging-kibana-2-jmt73 2/2 Running 0 17h
logging-mux-1-deploy 0/1 Error 0 16h
[root@viaq openshift-ansible]# !docker
docker images|grep logging
docker.io/openshift/origin-logging-curator v1.5.1 27a20151da17 6 weeks ago 224.9 MB
docker.io/openshift/origin-logging-auth-proxy v1.5.1 6bca7a2e8641 6 weeks ago 715.5 MB
docker.io/openshift/origin-logging-kibana v1.5.1 81f8b0aaea10 6 weeks ago 682.9 MB
docker.io/openshift/origin-logging-fluentd v1.5.1 b7012a18fd69 8 weeks ago 358.8 MB
docker.io/openshift/origin-logging-elasticsearch v1.5.1 033ed6e1c620 8 weeks ago 429.9 MB
[root@viaq openshift-ansible]# ls -la
total 3548
drwxr-xr-x. 5 root root 247 Jun 22 18:04 .
drwxr-xr-x. 4 root root 46 Jun 22 11:51 ..
-rw-r--r--. 1 root root 15 Jun 22 11:54 0001-Compatibility-updates-to-openshift_logging-role-for-.patch
-rw-r--r--. 1 root root 764 Jun 22 11:58 ansible-inventory
drwxr-xr-x. 2 root root 198 Jun 22 11:51 library
-rw-r--r--. 1 root root 1070 Jun 22 18:04 mux-ca.crt
-rw-r--r--. 1 root root 65 Jun 22 18:04 mux-shared-key
-rw-r--r--. 1 root root 3588502 Jun 22 13:06 output
drwxr-xr-x. 10 root root 141 Jun 22 11:51 playbooks
drwxr-xr-x. 74 root root 4096 Jun 22 11:51 roles
-rwxr-xr-x. 1 root root 15109 Jun 22 18:01 setup-mux.sh
-rw-r--r--. 1 root root 1235 Jun 22 11:56 vars.yaml.template
[root@viaq openshift-ansible]#
[root@viaq openshift-ansible]# hostname -f
viaq.logging.test
[root@viaq openshift-ansible]# MUX_HOST=mux.viaq.logging.test
[root@viaq openshift-ansible]# MUX_HOST=mux.viaq.logging.test ./setup-mux.sh
Fri Jun 23 11:00:07 UTC 2017 [INFO] cleanup old mux configuration, if any . . .
Fri Jun 23 11:00:09 UTC 2017 [INFO] generate mux server cert, key
Fri Jun 23 11:00:10 UTC 2017 [INFO] generate mux shared key
Fri Jun 23 11:00:10 UTC 2017 [INFO] create secret for mux
Fri Jun 23 11:00:10 UTC 2017 [INFO] add mux secret to fluentd service account
Fri Jun 23 11:00:11 UTC 2017 [INFO] using existing namespace [mux-undefined] - not recreating
Fri Jun 23 11:00:11 UTC 2017 [INFO] delete with "oc delete project mux-undefined"
Fri Jun 23 11:00:12 UTC 2017 [INFO] added mux configuration based on fluentd configuration
Fri Jun 23 11:00:12 UTC 2017 [INFO] created mux deployment configuration
Fri Jun 23 11:00:13 UTC 2017 [INFO] created mux service
Fri Jun 23 11:00:13 UTC 2017 [INFO] Success: the CA cert is in mux-ca.crt - the shared key is in mux-shared-key
-rw-r--r--. 1 root root 1070 Jun 23 11:00 mux-ca.crt
-rw-r--r--. 1 root root 65 Jun 23 11:00 mux-shared-key
[root@viaq openshift-ansible]# oc get pods
NAME READY STATUS RESTARTS AGE
logging-curator-1-hklth 1/1 Running 22 21h
logging-es-7vo926zw-1-deploy 0/1 Error 0 22h
logging-es-7vo926zw-2-phjrq 1/1 Running 0 18h
logging-fluentd-024kj 1/1 Running 1 22h
logging-kibana-1-deploy 0/1 Error 0 22h
logging-kibana-2-jmt73 2/2 Running 0 17h
logging-mux-1-deploy 1/1 Running 0 7m
logging-mux-1-wtwgd 0/1 Pending 0 7m
[root@viaq openshift-ansible]# oc logs logging-mux-1-deploy
--> Scaling logging-mux-1 to 1
--> Waiting up to 10m0s for pods in rc logging-mux-1 to become ready
error: update acceptor rejected logging-mux-1: pods for rc "logging-mux-1" took longer than 600 seconds to become ready
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment