Forum Discussion

Sergei Kamnev's avatar
Sergei Kamnev
Copper Contributor
Apr 28, 2017

Files in future after Cloud Service deployment

Hello,

We have a problem in Azure, and we expect that Microsoft guys can answer or advise it soon.

 

We found recently that after deploying our Cloud Service to Production, many files have date and time in future. You can see it on screen below: files are 10:04am while server time is still 8:41am.

 

 

On the same screen you can see folders of 7:23am - this is exact UTC time when deployment occured. We are located in UTC+3 timezone, so maybe this is somehow related.

We didn't observe this before. We also have another Cloud Service, and didn't realize such problem there. We will double check that.

 

The result of this is that files are reported by IIS as in future, so browser's caching fails.

Here is example of IIS response headers:

 

I also note strange ETag by IIS with leading "W/". Usually ETag doesn't have that.

When "future comes", all becomes good.

Please help,

 

Sergei.

 

 

App Services
azure

2 Replies

  • Pieter Veenstra's avatar
    Pieter Veenstra
    MVP
    Apr 28, 2017

    Hi Sergei Kamnev,

     

    In general these things happen when processes running at the wrong time create files. So it is unlikely that any of the processes on the same box as where the files are stored would be creating these files.

     

    You would probably need to look at where these files came from?

     

    e.g. If you create a file on a remote file system while the file system and your system don't run t the same time then you might get some unexpected results. Same of course if you create a Virtual Machine set the time to somewhere in the future and then create a template from that VM you will see files in the future.

     

    So finding the source of the files will probably give you the answer.

    • Sergei Kamnev's avatar
      Sergei Kamnev
      Copper Contributor
      May 03, 2017
      Pieter,

      Thank you for your input. I understand all this, so I wouldn't raise the issue if I wouldn't be sure.
      Today I did another PROD deployment, and these files get valid time in Azure. So I can tell definitely that _sometimes_ Azure Cloud Services break timestamps of files during deployment. I don't know exact case, and it is not my job to test Cloud Services. The worst thing is that this can affect behavior of our product, which is bad for our customers.

      Thanks,
      Sergei.

Resources