- Notifications
You must be signed in to change notification settings - Fork279
Termination event times match current time?#606
-
Termination events seem to always have a time matching the current time. Am I misconfigured? 2022/03/21 18:18:40 INF Adding new event to the event store event={"AutoScalingGroupName":"eks-spot-20220320215137259900000017","Description":"Spot Interruption event received. Instance i-043d45e1968bebec7 will be interrupted at 2022-03-21 18:18:38 +0000 UTC \n","EndTime":"0001-01-01T00:00:00Z","EventID":"spot-itn-event-38623039373536612d303063362d633862322d333566362d626538613263363639653330","InProgress":false,"InstanceID":"i-043d45e1968bebec7","IsManaged":true,"Kind":"SQS_TERMINATE","NodeLabels":null,"NodeName":"ip-10-89-12-166.ec2.internal","NodeProcessed":false,"Pods":null,"StartTime":"2022-03-21T18:18:38Z","State":""} |
BetaWas this translation helpful?Give feedback.
All reactions
Hello@jcam, we are returning the EventBridge event start time, in our case when instance received spot interruption. Current time is returned when we cannot parse the time in the specific format and we get a warning message thatUnable to parse time as RFC3339 from event, using current time instead., we cannot hardcode the time for spot interruption as it might take 2 or minutes to terminate the instance. But, yes the message needs to be modified to make it more clear, instead of mentioning aswill be interrupted.
Replies: 1 comment
-
Hello@jcam, we are returning the EventBridge event start time, in our case when instance received spot interruption. Current time is returned when we cannot parse the time in the specific format and we get a warning message that |
BetaWas this translation helpful?Give feedback.