On May 14, 2013, at 7:37 PM, Chip Childers wrote:
> On Tuesday, May 14, 2013, John Burwell wrote:
>
>> Chip,
>>
>> After some further discussion about this issue on IRC, Alex and I
>> determined that system VM clock drift issue not only breaks S3, but has
>> other significant impacts that meri
On Tuesday, May 14, 2013, John Burwell wrote:
> Chip,
>
> After some further discussion about this issue on IRC, Alex and I
> determined that system VM clock drift issue not only breaks S3, but has
> other significant impacts that merit it being a blocker for 4.1 (e.g.
> timestamps of files writte
Chip,
After some further discussion about this issue on IRC, Alex and I determined
that system VM clock drift issue not only breaks S3, but has other significant
impacts that merit it being a blocker for 4.1 (e.g. timestamps of files written
by the SSVM being incorrect, log file correlation dif
Chip,
The source of the problem appears to be clock drift between the SSVM and S3 per
following stack trace:
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-
Chip,
I am looking into the issue now. There is a failure when the S3 upload
template command is issued. I working to determine whether or not the cause is
environmental or code.
Thanks,
-John
On May 14, 2013, at 4:56 PM, Chip Childers wrote:
> Hi all,
>
> We have a clear bug list (blocke
Hi all,
We have a clear bug list (blockers and critical) for 4.1.0. I'm going
to cut a new release candidate tonight.
If there are *any* outstanding issues known, now's the time to raise
them.
(I'm specifically looking for an ACK from jburwell here, since he
mentioned a possible S3 feature issu
