CLOUDSTACK-10123: any entity should use GMT timestamp values#2303
Conversation
5a37f15 to
6f0fa89
Compare
6f0fa89 to
a2b8786
Compare
borisstoyanov
left a comment
There was a problem hiding this comment.
LGTM based on code review
|
LGTM, pending testing. |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1236 |
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1273 |
|
@blueorangutan test |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-1661)
|
Depending on the timezone you're running CS (before GMT timezones) you could experience that some jobs are marked as failed since the parent job got a null result despite its child job having successfully done the job. The child job got deleted by the
CleanupTaskahead of time, due to a missing datetime conversion to GMT timezone.Jobs are failing with this message:
Job failed with un-handled exceptionThe fix intends to correct any datetime used in the code that should be using the GMT timezone instead of the local one since all DB datetime should be stored at GMT.