4.9 will require a new system vm template when we add the strongswan
support and ospf, but I don't think I have added anything yet which will
require a new system vm (yet).
Rohit started a dev@ thread about a week or so ago on this topic for us.
On Apr 28, 2016 7:38 AM, "Rajani Karuturi" wrote:
ah..makes sense. Thanks Erik. I will revert the config change.
~Rajani
On Thu, Apr 28, 2016 at 4:11 PM, Erik Weber wrote:
> AFAIK it hasn't been necessary to update the systemvm template yet, that is
> probably why it still shows as 4.6.0.
>
> --
> Erik
>
> On Thu, Apr 28, 2016 at 12:04 PM, Bha
AFAIK it hasn't been necessary to update the systemvm template yet, that is
probably why it still shows as 4.6.0.
--
Erik
On Thu, Apr 28, 2016 at 12:04 PM, Bharat Kumar
wrote:
> Hi All,
>
> looks like the systemvm templates are not getting built correctly in
> http://jenkins.buildacloud.org/jo
In the job configuration, I see the version as 4.6.0.
I am not sure if that is where it reads from. I changed it to 4.9.0
- export version=4.6.0
+ export version=4.9.0
I will keep an eye on the job. Let me know if there are any issues with
this change.
~Rajani
On Thu, Apr 28, 2016 at 3:34 PM,
Hi All,
looks like the systemvm templates are not getting built correctly in
http://jenkins.buildacloud.org/job/build-systemvm64-master.
The build version is in correctly set to 4.6, Im not sure but i think the
build version in
/etc/cloudstck-release is also getting wrongly set inside the temp
