-
Notifications
You must be signed in to change notification settings - Fork 343
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
Configured plugin systemd_logs does not exist #30
Comments
I think this is a race condition with how the resources in If you do |
thanks a lot @kensimon ! it worked this time after I have deleted pod! |
I am still getting this issue : I tried the work around as described above but no joy after two attempts. Environment is :
Error is :
|
reopening, @kensimon could you please verify. |
I've seen this when I have an invalid configuration in my plugin. @jamesbuckett If you provide your plugin we can at least rule that out. |
I'm seeing this issue as well. It happens about every third time I start a test.
The error
|
Thx for reporting, I'll start investigating early this week. |
So I'll add more verbose logging to try and help diagnose, but I wonder if there was a config map mount race that exists in 1.6? |
So I'm traipsing through the control flow and nothing stands out atm. I'll have a PR to add more logging so we should get better visibility when the condition occurs, but I'm still leaning that this is a race condition on config map mounting. |
I'm going to untag this release and wait on feedback from testing. I've added more logging so if the issue occurs again we should have a better bead on whether it's a race condition or not. |
Hey Heptio Team.
When I check logs of my just deployed pod it exists with this error:
Any ideas , something is missing on the cluster itself?
The text was updated successfully, but these errors were encountered: