[
https://issues.apache.org/jira/browse/CLOUDSTACK-7143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143270#comment-14143270
]
ASF GitHub Bot commented on CLOUDSTACK-7143:
--------------------------------------------
Github user lsimons commented on the pull request:
https://github.com/apache/cloudstack/pull/16#issuecomment-56385199
thanks for testing rohit. We've never seen this (with xen).
If you look at the error,
```
/dev/vda5: Superblock last mount time (Fri Sep 19 14:54...)
now = Mon Sep 15 20:34... is in the future
```
the fsck is unhappy with the last recorded mount being sep 19 (last friday,
which is correct, i.e. it matches with when we ran the build on jenkins)
because the date of the system as its booting is in the past, sep 15. So
somehow the system clock of the VM is wrong...?
Either during the build process the time was moved backward some time after
mounting the filesystem, or during the boot process time moved backward, or ...
?
I've checked and the date of the build slave where the image was baked is
correct and managed with ntp so very likely was always correct...so I really
don't see how the build could result in that timestamp existing anywhere.
Can you check the date of your KVM host? Or perhaps if you have an NTP
server with a wrong date?
> Refactor systemvm build scripts to be easier to test
> ----------------------------------------------------
>
> Key: CLOUDSTACK-7143
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7143
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
> Reporter: Leo Simons
> Fix For: Future
>
>
> The veewee-wrapping build code could do with some love.
> E-mail thread:
> http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201407.mbox/%3C7A6CF878-7A28-4D4A-BCD2-0C264F8C90B7%40schubergphilis.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
