-
Notifications
You must be signed in to change notification settings - Fork 82
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.
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
Pod logs stop being pulled when container log files are rotated #446
Comments
Related: ansible/awx#11338 |
Trying to fix this here: #683 |
I seem to still get only the first chunk of logs. Running AWX receptor version 1.4.1 against OpenShift 3.11's (I know, I know) Kubernetes 1.11.0+d4cacc0. (Edit: this appears to not be a timing issue, as I initially thought.) It is worth noting that the |
Crosslinking ansible/awx#14158 I am guessing this may have the same root cause? |
and upstream has a PR for something that sounds related: kubernetes/kubernetes#118500 |
A potential fix was merged in upstream kubernetes in kubernetes/kubernetes#115702 |
I updated kubernetes to 1.29 -- this seems to fix the issues for me |
As seen in ansible/awx#11338 and ansible/receptor#446 - Force `RECEPTOR_KUBE_SUPPORT_RECONNECT` as per ansible/receptor#683 - Pump up timeouts thereof
As a followup of https://github.com/ansible/awx/issues/10366.\
Receptor is pulling logs from the pods using the kubernetes API log call
receptor/pkg/workceptor/kubernetes.go
Lines 273 to 276 in 156e6e2
However as explained in kubernetes/kubernetes#59902, if the container log files (on the node) are rotated the log stream stops. As a consequence logs are not fully sent to AWX database. In such case, the AWX jobs will be flagged as failed, even though it went to the end, because the whole logs are not available.
The text was updated successfully, but these errors were encountered: