[
https://issues.apache.org/jira/browse/CLOUDSTACK-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733176#comment-13733176
]
Prasanna Santhanam commented on CLOUDSTACK-4099:
------------------------------------------------
[~aprateek] The template is pre-seeded into devcloud. we need to reseed the new
one and create a new template. There is no mechanism to autoupdate it, but it
can be added. If you are concerned about the '4.2' affectsVersion - this fix is
not important to be done now, can be deferred to be updated later. But would be
nice if we can fix, upgrade all our toolchains to go in the same cadence as the
releases.
> update the systemvm templates in DevCloud2
> ------------------------------------------
>
> Key: CLOUDSTACK-4099
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4099
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: DevCloud
> Affects Versions: 4.2.0
> Reporter: Prasanna Santhanam
> Priority: Critical
>
> DevCloud2 is still using the old templates for systemVMs. These need to be
> updated to the latest stable templates available from jenkins. Fixes exist for
> 1. vm time sync with hypervisor
> 2. vhd-util within systemvm
> 3. latest haproxy
> 4. irqbalance fix
> etc
--
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: http://www.atlassian.com/software/jira
