You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2018. It is now read-only.
We have been using the EBS Snapshot Scheduler for quite some time and, at some point, the date format returned by datetime.timedelta has apparently changed as we have started seeing errors in our lambda execution:
time data '2017-07-26 08:03:21' does not match format '%Y-%m-%d %H:%M:%S.%f'
these errors appear to be stopping the code execution at that point in purge_history, rather than handling the error and moving on to other snapshots in that region - as a result, no snapshots are purged.
I think a try/except would help address this issue?
try:
check_time=parse_date("2017-07-26 08:03:21")
except:
print"\n\nparse_date: invalid date found in database, skipping\n\n"
or equivalent?
Meanwhile I have to go back and massage entries in my history table data... interestingly, I found only 1 that matched.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have been using the EBS Snapshot Scheduler for quite some time and, at some point, the date format returned by datetime.timedelta has apparently changed as we have started seeing errors in our lambda execution:
these errors appear to be stopping the code execution at that point in purge_history, rather than handling the error and moving on to other snapshots in that region - as a result, no snapshots are purged.
I think a try/except would help address this issue?
or equivalent?
Meanwhile I have to go back and massage entries in my history table data... interestingly, I found only 1 that matched.
The text was updated successfully, but these errors were encountered: