-
Notifications
You must be signed in to change notification settings - Fork 268
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
Unable to parsed scheduled event start time #147
Comments
I've reproduced the issue. It looks like we made a bad assumption when parsing the date and assumed the day would be padded to always be two digits. I will put a PR up to fix this bug today, sorry for the inconvenience! |
PR is merged, we'll be making a release soon to fix this. |
Thanks for the quick resolution! |
Using version
|
We'll investigate and post back, thanks for bringing this up |
Is this error from an actual scheduled maintenance event or testing through ec2-metadata-mock? I've run a small test with ec2-metadata-mock below and it seems to work correctly. Can you provide some more details on your configuration? The IMDS raw output would also be helpful, but I guess we don't log raw output on a parse error currently :(
STDOUT:
|
I was about to query the aws metadata server (AMS) |
no worries, I'll dig and see if one of the scheduled maintenance events does not provide an end time. |
this bug has been fixed in the v1.6.0 release. |
Hello,
I recently deployed aws-node-termination-handler in my cluster and now I have my first scheduled termination. The node hasn't drain nor cordoned and the application logs show the following message repeatedly every 2-3 seconds:
What might the problem be?
Thanks,
Yosi
The text was updated successfully, but these errors were encountered: