cloudstack/engine
Marc-Aurèle Brothier 421f1072d5 CLOUDSTACK-10123: Entity should use GMT TZ for timestamp values (#2303)
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 CleanupTask ahead of time, due to a missing datetime conversion to GMT timezone.

Jobs are failing with this message: Job failed with un-handled exception

The 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.
2017-11-18 09:14:57 +05:30
..
api CLOUDSTACK-10012: Migrate to Embedded Jetty 2017-11-03 23:57:25 +05:30
components-api CLOUDSTACK-9450: Network Offering for VPC based on DB flag 2017-11-03 12:39:23 +01:00
network Updating pom.xml version numbers for release 4.11.0.0-SNAPSHOT 2017-07-12 12:09:38 +05:30
orchestration CLOUDSTACK-10123: Entity should use GMT TZ for timestamp values (#2303) 2017-11-18 09:14:57 +05:30
schema Merge pull request #2005 from nuagenetworks/feature/nw_offering_for_vpc 2017-11-16 17:33:07 +01:00
service CLOUDSTACK-10012: Migrate to Embedded Jetty 2017-11-03 23:57:25 +05:30
storage Remove annotation not needed at cloud-engine-storage-image (#2324) 2017-11-16 23:11:15 +05:30
pom.xml Updating pom.xml version numbers for release 4.11.0.0-SNAPSHOT 2017-07-12 12:09:38 +05:30