cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10123) VmWork job gets deleted before the parent job had time to fetch its result
Date Fri, 17 Nov 2017 18:33:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10123:

blueorangutan commented on issue #2303: CLOUDSTACK-10123: any entity should use GMT timestamp
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run
smoke tests

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> VmWork job gets deleted before the parent job had time to fetch its result
> --------------------------------------------------------------------------
>                 Key: CLOUDSTACK-10123
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Marc-Aurèle Brothier
>            Assignee: Marc-Aurèle Brothier
> 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.

This message was sent by Atlassian JIRA

View raw message