Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

More detailed logging during a provision #122

Closed
rthallisey opened this issue May 22, 2017 · 2 comments
Closed

More detailed logging during a provision #122

rthallisey opened this issue May 22, 2017 · 2 comments

Comments

@rthallisey
Copy link
Contributor

When you run a provision, we output the number of retries left and the return of oc logs -f. Once the patch for the Kubernetes client merges, we can do a lot more. We can parse the pod status, see if the image is pulling, make a note what node the pod is on, ect...

[2017-05-22T17:07:33.705-04:00] [INFO] Container not up yet, retrying 1 of 150 on pod aa-ee5b096d-d46b-46ff-bcef-f2b89dab8606
[2017-05-22T17:07:33.929-04:00] [DEBUG] oc log output:
Error from server: container "aa-ee5b096d-d46b-46ff-bcef-f2b89dab8606" in pod "aa-ee5b096d-d46b-46ff-bcef-f2b89dab8606" is waiting to start: ContainerCreating
[2017-05-22T17:07:33.929-04:00] [DEBUG] status: still waiting to start
[2017-05-22T17:07:39.929-04:00] [INFO] Container not up yet, retrying 2 of 150 on pod aa-ee5b096d-d46b-46ff-bcef-f2b89dab8606
@rthallisey rthallisey changed the title Better logging during a provision More detailed logging during a provision May 22, 2017
@rthallisey
Copy link
Contributor Author

This would change with #124

@rthallisey
Copy link
Contributor Author

I think this has improved enough to close this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rthallisey