cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Burwell (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-2492) System VMs Clock Drift
Date Tue, 14 May 2013 22:51:17 GMT
John Burwell created CLOUDSTACK-2492:

             Summary: System VMs Clock Drift
                 Key: CLOUDSTACK-2492
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: ISO
    Affects Versions: 4.1.0
         Environment: devcloud/Xen
            Reporter: John Burwell
            Priority: Blocker

Testing of S3-backed Secondary Storage has revealed that the SSVM (and likely all other system
VMs) have no provision for clock synchronization (e.g. NTP to dom0 for Xen, vmware-tools for
VMWare, etc).  In particular, the S3 protocol is sensitive to drift between clients and S3.
 As an example, the following is the stack trace caused by clock drift S3:

2013-05-14 06:51:55,400 DEBUG [cloud.utils.S3Utils] (agentRequest-Handler-3:) Putting directory
/mnt/SecStorage/93fd0cb0-033b-3248-bcd0-ef6d460635ef/template/tmpl/1/5 in S3 bucket jsb-cloudstack-templates.
2013-05-14 06:51:55,401 DEBUG [cloud.utils.S3Utils] (agentRequest-Handler-3:) Creating S3
client with configuration: [protocol: https, connectionTimeOut: 50000, maxErrorRetry: 3, socketTimeout:
2013-05-14 06:51:55,403 DEBUG [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-3:)
Determining key using account id 1 and template id 5
2013-05-14 06:51:55,403 DEBUG [cloud.utils.S3Utils] (agentRequest-Handler-3:) Putting file
into bucket jsb-cloudstack-templates with key template/tmpl/1/5/
2013-05-14 06:51:55,578 ERROR [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-3:)
Failed to upload template id 5
Status Code: 403, AWS Service: Amazon S3, AWS Request ID: 970A274E132A9ACB, AWS Error Code:
RequestTimeTooSkewed, AWS Error Message: The difference between the request time and the current
time is too large., S3 Extended Request ID: 9w8a6YBxTn+WlBg96s9stxWuuP8oQ7ksZtg6++wVRHJfE2qmucrilhoEJVetJui4
        at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(
        at com.amazonaws.http.AmazonHttpClient.executeHelper(
        at com.amazonaws.http.AmazonHttpClient.execute(
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(

In addition to impacting S3, this clock drift also makes log correlation between the management
server and system VMs very difficult, if not, impossible.  Finally, there are suspicions that
the clock drift could also impact operation of console proxy and virtual router VMs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message