Brief Openshift troubleshooting
If you have issues after an automagic openshift-on-openstack deployment:
1. Remember: every buildconfig created *before* the registry is not authorized to push the images
2. Remember: hawkular is a java application. Startup is slow. Just click there and wait for the startup
3. Ansible is your friend. To get container logs, just
ansible all -m shell -a ‘ls /var/log/containers/CONTAINER_NAME*’
ansible all -m shell -a ‘cat /var/log/containers/CONTAINER_NAME*’ > CONTAINER_NAME.log
4. If a container don’t startup during the deployment, a broken image may have been downloaded
Jun 1 23:30:36 dev-7-infra-0 atomic-openshift-node: I0601 23:30:36.234103 32913 server.go:608] Event(api.ObjectReference{Kind:”Pod”, Namespace:”default”, Name:”router-1-deploy”, UID:”033670a9-470e-11e7-878f-fa163eac2bf7″, APIVersion:”v1″, ResourceVersion:”936″, FieldPath:””}): type: ‘Warning’ reason: ‘FailedSync’ Error syncing pod, skipping: failed to “StartContainer” for “POD” with RunContainerError: “runContainer: Error response from daemon: {\”message\”:\”invalid header field value \\\”oci runtime error: container_linux.go:247: starting container process caused \\\\\\\”exec: \\\\\\\\\\\\\\\”/pod\\\\\\\\\\\\\\\”: stat /pod: no such file or directory\\\\\\\”\\\\n\\\”\”}”
Cleanup docker repo
docker ps -aq | xargs docker rm
docker rmi 90e9207f44f0 –force
5. Run oadm diagnostics on the master 😉
6. Check #oc get hostsubnet
June 01 2017 09:52 am | Politica| 1,064 views