Re: failed 430-440 upgrade: Unable to start instance due to Unable to get answer that is of class com.cloud.agent.api.StartAnswer

[Wido den Hollander]

On 10/21/2014 12:36 AM, Nux! wrote:
> Wido,
> 
> Alas DEBUG is on without telling me anything I can understand. Here's some 
> more:
> 
> http://pastebin.com/raw.php?i=cYf8g5tg
> 

So this is the issue:

2014-10-20 23:24:27,323 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-1:null) Seq 1-1609755391808241885:  { Ans: ,
MgmtId: 270567360573239, via: 1, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.Answer":{"result":false,"details":"No enum
constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"Stopped
by previous failure","wait":0}}] }

That should be fixed in 4.4.1

By this commit:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=eeac81838fcc3c53d2115074c8141c9411d3ef4c

Just upgrading the agent to 4.4.1 is enough, the mgmt server can still
run 4.4.0

Wido

> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Wido den Hollander" 
>> To: dev@cloudstack.apache.org
>> Sent: Monday, 20 October, 2014 23:29:04
>> Subject: Re: failed 430-440 upgrade: Unable to start instance due to Unable 
>> to get answer that is of class
>> com.cloud.agent.api.StartAnswer
> 
>> On 10/21/2014 12:25 AM, Nux! wrote:
>>> Hi guys,
>>>
>>> I've followed the 4.3.x to 4.4.0 upgrade instruction to the letter and it 
>>> has
>>> worked, except the last step which failed to restart my system VMs. Now I'm 
>>> on
>>> 4.4.0 without any system VMs; they are stuck in a creation loop which never
>>> succeeds. Relevant management log:
>>>
>>> Job failed due to exception Resource [Host:1] is unreachable: Host 1: 
>>> Unable to
>>> start instance due to Unable to get answer that is of class
>>> com.cloud.agent.api.StartAnswer
>>> http://pastebin.com/raw.php?i=k6WksLcU
>>>
>>> And on the agent:
>>>
>>> 2014-10-20 23:10:57,369 DEBUG [cloud.agent.Agent] 
>>> (agentRequest-Handler-5:null)
>>> Processing command: com.cloud.agent.api.StopCommand
>>> 2014-10-20 23:10:57,371 DEBUG [kvm.resource.LibvirtConnection]
>>> (agentRequest-Handler-5:null) can't find connection: KVM, for vm: v-439-VM,
>>> continue
>>> 2014-10-20 23:10:57,372 DEBUG [kvm.resource.LibvirtConnection]
>>> (agentRequest-Handler-5:null) can't find connection: LXC, for vm: v-439-VM,
>>> continue
>>> 2014-10-20 23:10:57,372 DEBUG [kvm.resource.LibvirtConnection]
>>> (agentRequest-Handler-5:null) can't find which hypervisor the vm used , then
>>> use the default hypervisor
>>> 2014-10-20 23:10:57,374 DEBUG [kvm.resource.LibvirtComputingResource]
>>> (agentRequest-Handler-5:null) Failed to get dom xml:
>>> org.libvirt.LibvirtException: Domain not found: no domain with matching name
>>> 'v-439-VM'
>>> 2014-10-20 23:10:57,375 DEBUG [kvm.resource.LibvirtComputingResource]
>>> (agentRequest-Handler-5:null) Failed to get dom xml:
>>> org.libvirt.LibvirtException: Domain not found: no domain with matching name
>>> 'v-439-VM'
>>> 2014-10-20 23:10:57,377 DEBUG [kvm.resource.LibvirtComputingResource]
>>> (agentRequest-Handler-5:null) Failed to get dom xml:
>>> org.libvirt.LibvirtException: Domain not found: no domain with matching name
>>> 'v-439-VM'
>>>
>>> And this goes on and on.
>>>
>>> Any ideas?
>>>
>>
>> Is all the logging on DEBUG on the Agent? there has to be more
>> information in the logfile telling you what is going on exactly.
>>
>> Wido
>>
>>> Lucian
>>>
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro

commits on 4.5

[Daan Hoogland]

David,

I keep seeing commits passing to the 4.5 branch. As you are the RM I am not
reverting them. Should I? Not one of them has come from a hotfix branch for
weeks.

-- 
Daan

Re: [PROPOSAL] Move to github PR only during moratorium on commit

[sebgoa]

On Oct 21, 2014, at 6:32 AM, Mike Tutkowski  
wrote:

> Code reviews are great.
> 
> However, we will need to change our behavior quite a bit if code is to make
> it in within a reasonable amount of time as code reviews today often don't
> get done in a timely fashion.


Just look at it as an incremental step forward. Reviews could just be a "ship 
it", like we see many times on RB.

The point is really to track the commits better and have the RMs (whatever many 
we have), to do the commits and construct the release branches.

This would be much better than the free for all we have right now and would 
redirect development to feature branches and bugfix branches until merged.

And fwiw, I do believe that RM is a full time job.


> 
> In a volunteer community, it's hard to "assign" work (including code
> reviews) to people (let alone expect it done on your schedule).
> 
> This is, of course, different at most of our day jobs where managers are in
> a position to make sure the community is responsive.
> 
> On Monday, October 20, 2014, Rajani Karuturi  wrote:
> 
>> I like the way Stephen split it.
>> Here is my vote.
>> +1 on using github pull requests.
>> +1 on compulsory code reviews and PRs even for committers and CI build pass
>> before merging.
>> +1 on merges from 4.5 to master and no individual commits(or cherry-picks)
>> to the branches
>> +0 on RM for master and commits gated by him. I agree with Stephen that
>> code reviewer should be doing the push. But, I am ok with RM doing
>> it(assuming we have a volunteer ;) ).
>> 
>> +1 on any changes independently.
>> 
>> 
>> ~Rajani
>> 
>> On Mon, Oct 20, 2014 at 5:21 PM, Stephen Turner > >
>> wrote:
>> 
>>> As I just said in the other thread -- but to repeat it here in the
>>> PROPOSAL thread --
>>> 
>>> I am +1 on using github pull requests.
>>> 
>>> I am +1 on all code changes being reviewed by a committer other than the
>>> author, as well as undergoing some automated CI testing, before the pull
>>> request is merged.
>>> 
>>> I am +0 on only the master RM merging the pull request. I don't want the
>>> author to push the code, but I think the code reviewer could do this; in
>>> practice the RM will not be able to review everything again so is likely
>> to
>>> rubber-stamp the results of the code review / automated testing. But I
>>> could live with the master RM doing it.
>>> 
>>> I am +1 on moving ahead with any of these parts individually, rather than
>>> waiting for everything to be in place before doing anything.
>>> 
>>> --
>>> Stephen Turner
>>> 
>>> 
>>> -Original Message-
>>> From: sebgoa [mailto:run...@gmail.com ]
>>> Sent: 18 October 2014 10:00
>>> To: dev@cloudstack.apache.org 
>>> Subject: [PROPOSAL] Move to github PR only during moratorium on commit
>>> 
>>> After [1] I would like to officially bring up the following proposal.
>>> 
>>> [Proposal]
>>> 
>>> All commits come through github PR, *even* for committers. We declare a
>>> moratorium period (agreed suspension of activity) during which direct
>>> commit to master is forbidden.
>>> Only the master RM is allowed to merge PR in master (we define a master
>>> RM). If direct commit to master is done, master RM reverts without
>> warning.
>>> Same for 4.5 and 4.4. branches.
>>> 
>>> 
>>> This is drastic and I am sure some folks will not like it, but here is my
>>> justification for such a measure:
>>> 
>>> [Reasons]:
>>> 
>>> Our commit and release processes have so far been based on the idea that
>>> development happens on master and that a release branch is cut from
>> master
>>> (unstable development branch). Then a different set of community members
>>> harden the release branch, QA and bring it to GA level. During that time
>>> development keeps on going in master.
>>> 
>>> This is an OK process if we have the luxury of having a QA team and can
>>> cope with split personality of being developers and release managers.
>>> 
>>> My point of view is that as a community we cannot afford such a split
>>> brain organization and our experience overt the last year proves my point
>>> (delayed release date, broken builds, features merged without warning...)
>>> 
>>> We can avoid this by cutting a release branch from a stable one (from the
>>> start), then as you (Daan) have mentioned several times, fix bugs in the
>>> release branch and merge them back in the stable source of the release
>> (be
>>> it master).
>>> 
>>> Feature development need to be done outside master, period. Not only for
>>> non-committers but also for committers. And merge request need to be
>>> called. This will help review and avoid surprises.
>>> 
>>> New git workflow were proposed and shutdown, mostly calling for better CI
>>> to solve quality issues. CI will not solve our quality issues alone. We
>>> need to better police ourselves.
>>> 
>>> To avoid long discussions, I propose this simple but drastic measure. We
>>> move all our commits to github PR until 4.5 is out, this stands for
>>> committers 

Re: [PROPOSAL] Move to github PR only during moratorium on commit

[Daan Hoogland]

Ok, no one says it so let me be the bad guy.


Nothing will work unless the citrix department in california agrees. They
have their in-house legacy proces to change and will not unless they can
sell it easily upstream. So whether we make a grand uninfied proposal or
take small steps doesn't matter, it must fit their internal political
situation.
This is very unhealthy. I am not saying that the objections coming from
that group are unreasonable every time. Sometimes they were more then other
times. I am even sure that they are working on improving as well but this
is invisible to the rest of us. A mail every once in a while does not make
this visible. The proces of improving the way we work is impaired by it.
They to need to make small steps so we can see what is happening and where
we are going. Even a grand proposal by Citrix California won't be accepted,
because the change will be to big!



I made some small steps in improving during the 4.4.1 release process.
These were largely ignored or reverted in the current branch. unless the
current state of 4.5 happens to be very good we are in for a repeat of
recent history.


You know where to find me,
Daan

On Tue, Oct 21, 2014 at 6:32 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Code reviews are great.
>
> However, we will need to change our behavior quite a bit if code is to make
> it in within a reasonable amount of time as code reviews today often don't
> get done in a timely fashion.
>
> In a volunteer community, it's hard to "assign" work (including code
> reviews) to people (let alone expect it done on your schedule).
>
> This is, of course, different at most of our day jobs where managers are in
> a position to make sure the community is responsive.
>
> On Monday, October 20, 2014, Rajani Karuturi  wrote:
>
> > I like the way Stephen split it.
> > Here is my vote.
> > +1 on using github pull requests.
> > +1 on compulsory code reviews and PRs even for committers and CI build
> pass
> > before merging.
> > +1 on merges from 4.5 to master and no individual commits(or
> cherry-picks)
> > to the branches
> > +0 on RM for master and commits gated by him. I agree with Stephen that
> > code reviewer should be doing the push. But, I am ok with RM doing
> > it(assuming we have a volunteer ;) ).
> >
> > +1 on any changes independently.
> >
> >
> > ~Rajani
> >
> > On Mon, Oct 20, 2014 at 5:21 PM, Stephen Turner <
> stephen.tur...@citrix.com
> > >
> > wrote:
> >
> > > As I just said in the other thread -- but to repeat it here in the
> > > PROPOSAL thread --
> > >
> > > I am +1 on using github pull requests.
> > >
> > > I am +1 on all code changes being reviewed by a committer other than
> the
> > > author, as well as undergoing some automated CI testing, before the
> pull
> > > request is merged.
> > >
> > > I am +0 on only the master RM merging the pull request. I don't want
> the
> > > author to push the code, but I think the code reviewer could do this;
> in
> > > practice the RM will not be able to review everything again so is
> likely
> > to
> > > rubber-stamp the results of the code review / automated testing. But I
> > > could live with the master RM doing it.
> > >
> > > I am +1 on moving ahead with any of these parts individually, rather
> than
> > > waiting for everything to be in place before doing anything.
> > >
> > > --
> > > Stephen Turner
> > >
> > >
> > > -Original Message-
> > > From: sebgoa [mailto:run...@gmail.com ]
> > > Sent: 18 October 2014 10:00
> > > To: dev@cloudstack.apache.org 
> > > Subject: [PROPOSAL] Move to github PR only during moratorium on commit
> > >
> > > After [1] I would like to officially bring up the following proposal.
> > >
> > > [Proposal]
> > > 
> > > All commits come through github PR, *even* for committers. We declare a
> > > moratorium period (agreed suspension of activity) during which direct
> > > commit to master is forbidden.
> > > Only the master RM is allowed to merge PR in master (we define a master
> > > RM). If direct commit to master is done, master RM reverts without
> > warning.
> > > Same for 4.5 and 4.4. branches.
> > > 
> > >
> > > This is drastic and I am sure some folks will not like it, but here is
> my
> > > justification for such a measure:
> > >
> > > [Reasons]:
> > > 
> > > Our commit and release processes have so far been based on the idea
> that
> > > development happens on master and that a release branch is cut from
> > master
> > > (unstable development branch). Then a different set of community
> members
> > > harden the release branch, QA and bring it to GA level. During that
> time
> > > development keeps on going in master.
> > >
> > > This is an OK process if we have the luxury of having a QA team and can
> > > cope with split personality of being developers and release managers.
> > >
> > > My point of view is that as a community we cannot afford such a split
> > > brain organization and our experience overt the last year proves my
> point
> > >

Re: [PROPOSAL] Move to github PR only during moratorium on commit

[sebgoa]

On Oct 21, 2014, at 9:36 AM, Daan Hoogland  wrote:

> Ok, no one says it so let me be the bad guy.
> 
> 
> Nothing will work unless the citrix department in california agrees. They
> have their in-house legacy proces to change and will not unless they can
> sell it easily upstream. So whether we make a grand uninfied proposal or
> take small steps doesn't matter, it must fit their internal political
> situation.
> This is very unhealthy. I am not saying that the objections coming from
> that group are unreasonable every time. Sometimes they were more then other
> times. I am even sure that they are working on improving as well but this
> is invisible to the rest of us. A mail every once in a while does not make
> this visible. The proces of improving the way we work is impaired by it.
> They to need to make small steps so we can see what is happening and where
> we are going. Even a grand proposal by Citrix California won't be accepted,
> because the change will be to big!
> 
> 
> 
> I made some small steps in improving during the 4.4.1 release process.
> These were largely ignored or reverted in the current branch. unless the
> current state of 4.5 happens to be very good we are in for a repeat of
> recent history.
> 
> 
> You know where to find me,
> Daan

I will mostly +1 this 

-sebastien

> 
> On Tue, Oct 21, 2014 at 6:32 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
> 
>> Code reviews are great.
>> 
>> However, we will need to change our behavior quite a bit if code is to make
>> it in within a reasonable amount of time as code reviews today often don't
>> get done in a timely fashion.
>> 
>> In a volunteer community, it's hard to "assign" work (including code
>> reviews) to people (let alone expect it done on your schedule).
>> 
>> This is, of course, different at most of our day jobs where managers are in
>> a position to make sure the community is responsive.
>> 
>> On Monday, October 20, 2014, Rajani Karuturi  wrote:
>> 
>>> I like the way Stephen split it.
>>> Here is my vote.
>>> +1 on using github pull requests.
>>> +1 on compulsory code reviews and PRs even for committers and CI build
>> pass
>>> before merging.
>>> +1 on merges from 4.5 to master and no individual commits(or
>> cherry-picks)
>>> to the branches
>>> +0 on RM for master and commits gated by him. I agree with Stephen that
>>> code reviewer should be doing the push. But, I am ok with RM doing
>>> it(assuming we have a volunteer ;) ).
>>> 
>>> +1 on any changes independently.
>>> 
>>> 
>>> ~Rajani
>>> 
>>> On Mon, Oct 20, 2014 at 5:21 PM, Stephen Turner <
>> stephen.tur...@citrix.com
>>> >
>>> wrote:
>>> 
 As I just said in the other thread -- but to repeat it here in the
 PROPOSAL thread --
 
 I am +1 on using github pull requests.
 
 I am +1 on all code changes being reviewed by a committer other than
>> the
 author, as well as undergoing some automated CI testing, before the
>> pull
 request is merged.
 
 I am +0 on only the master RM merging the pull request. I don't want
>> the
 author to push the code, but I think the code reviewer could do this;
>> in
 practice the RM will not be able to review everything again so is
>> likely
>>> to
 rubber-stamp the results of the code review / automated testing. But I
 could live with the master RM doing it.
 
 I am +1 on moving ahead with any of these parts individually, rather
>> than
 waiting for everything to be in place before doing anything.
 
 --
 Stephen Turner
 
 
 -Original Message-
 From: sebgoa [mailto:run...@gmail.com ]
 Sent: 18 October 2014 10:00
 To: dev@cloudstack.apache.org 
 Subject: [PROPOSAL] Move to github PR only during moratorium on commit
 
 After [1] I would like to officially bring up the following proposal.
 
 [Proposal]
 
 All commits come through github PR, *even* for committers. We declare a
 moratorium period (agreed suspension of activity) during which direct
 commit to master is forbidden.
 Only the master RM is allowed to merge PR in master (we define a master
 RM). If direct commit to master is done, master RM reverts without
>>> warning.
 Same for 4.5 and 4.4. branches.
 
 
 This is drastic and I am sure some folks will not like it, but here is
>> my
 justification for such a measure:
 
 [Reasons]:
 
 Our commit and release processes have so far been based on the idea
>> that
 development happens on master and that a release branch is cut from
>>> master
 (unstable development branch). Then a different set of community
>> members
 harden the release branch, QA and bring it to GA level. During that
>> time
 development keeps on going in master.
 
 This is an OK process if we have the luxury of having a QA team and can
 cope with split personality of being developers and release managers.
 
 My point o

pre-announcement of release 4.4.1

[Daan Hoogland]

H devs, as the finalisation of the release announcement is taking some
time, here is the sneak preview:

= = =

[APACHE CLOUDSTACK LOGO]

Announcing Apache™ CloudStack™ v4.4.1

Mature, easy-to-deploy Open Source Cloud computing software platform
boasts improved efficiency and performance.

[DATELINE] —NN MONTH 2014— The Apache CloudStack project today
announced the immediate availability of Apache CloudStack v4.4.1, the
latest version of the turnkey Open Source cloud computing software
platform used for creating private-, public-, and hybrid cloud
environments.

Apache CloudStack clouds enable billions of dollars' worth of business
transactions annually across their clouds, and its maturity and
stability has led it to has become the Open Source platform for many
service providers to set up on-demand, elastic public cloud computing
services, as well as enterprises and others to set up a private or
hybrid cloud for use by their own employees.

[@@ "QUOTE," said Hugo Trippaers, Vice President of Apache CloudStack.
"MORE FROM HUGO."]

Lauded by Gartner Group, CloudStack includes an intuitive user
interface and rich APIs for managing the compute, networking,
software, and storage infrastructure resources.

CloudStack v4.4.1 reflects dozens of new features and improvements, including:
-Improved Storage Management
-Virtual Private Cloud tiers can now span guest networks across
availability zones
-Support for VMware Distributed Resource Scheduler
-Improved Support for Hyper-V Zones, VPC and Storage Migration

A complete overview of all new enhancements can be found in the
project release notes at
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/

CloudStack has been used by thousands of organizations worldwide and
is in use/production at Alcatel-Lucent, Autodesk, BT Cloud, China
Telecom, DATACAENTER Services, DataPipe, Edmunds.com, Exoscale,
GreenQloud, Hokkaido University, IDC Frontier, Ikoula, KDDI, KT/Korea
Telecom, LeaseWeb, NTT, Orange, PCextreme, Schuberg Philis, Shopzilla,
Slovak Telekom, SunGard AS, Taiwan Mobile, Tata, Trader Media Group,
TomTom, University of Melbourne, University of Sao Paolo, Verizon,
WebMD and Zynga, among others.

CloudStack originated at Cloud.com, which was acquired by Citrix in
2011. CloudStack was submitted to the Apache Incubator in April 2012
and graduated as an Apache Software Foundation Top-level Project in
March 2013.

Availability
CloudStack v4.4.1 is available immediately as a free download from
http://cloudstack.apache.org/downloads.html. Apache CloudStack
software is released under the Apache License v2.0.

Governance and Oversight
Apache CloudStack is overseen by a self-selected team of active
contributors to the project. A Project Management Committee (PMC)
guides the Project's day-to-day operations, including community
development and product
releases.

Get Involved!
Apache CloudStack welcomes contribution and community participation
through mailing lists as well as attending face-to-face MeetUps,
developer trainings, and user events. Catch CloudStack in action at
the CloudStack Collaboration Conference, the official user/developer
conference of the Apache CloudStack community, 19-21 November 2014 in
Budapest, Hungary @CCCEU14
http://events.linuxfoundation.org/events/cloudstack-collaboration-conference-europe

About Apache CloudStack
Apache CloudStack is a mature, turnkey integrated
Infrastructure-as-a-Service (IaaS) Open Source software platform that
allows users to build feature-rich public and private cloud
environments. Hailed by Gartner Group as "a solid product", CloudStack
includes an intuitive user interface and rich APIs for managing the
compute, networking, software, and storage infrastructure resources.
CloudStack entered the Apache Incubator in April 2012 and became an
Apache Top-level Project in March 2013. For downloads, documentation,
and ways to become involved with Apache CloudStack, visit
http://cloudstack.apache.org/ and https://twitter.com/CloudStack

# # #

© The Apache Software Foundation. "Apache", "CloudStack", "Apache
CloudStack", the Apache CloudStack logo, and the Apache CloudStack
Cloud Monkey logo are registered trademarks or trademarks of The
Apache Software Foundation. All other brands and trademarks are the
property of their respective owners.

Contacts
Apache CloudStack
[FULL NAME]
[telephone number with country code]
market...@cloudstack.apache.org

-- 
Daan

Re: failed 430-440 upgrade: Unable to start instance due to Unable to get answer that is of class com.cloud.agent.api.StartAnswer

[Nux!]

Thanks Wido, I'll attempt another upgrade tonight. Cheers!

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Wido den Hollander" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 21 October, 2014 08:12:23
> Subject: Re: failed 430-440 upgrade: Unable to start instance due to Unable 
> to get answer that is of class
> com.cloud.agent.api.StartAnswer

> On 10/21/2014 12:36 AM, Nux! wrote:
>> Wido,
>> 
>> Alas DEBUG is on without telling me anything I can understand. Here's some 
>> more:
>> 
>> http://pastebin.com/raw.php?i=cYf8g5tg
>> 
> 
> So this is the issue:
> 
> 2014-10-20 23:24:27,323 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-1:null) Seq 1-1609755391808241885:  { Ans: ,
> MgmtId: 270567360573239, via: 1, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"No enum
> constant
> com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"Stopped
> by previous failure","wait":0}}] }
> 
> That should be fixed in 4.4.1
> 
> By this commit:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=eeac81838fcc3c53d2115074c8141c9411d3ef4c
> 
> Just upgrading the agent to 4.4.1 is enough, the mgmt server can still
> run 4.4.0
> 
> Wido
> 
>> --
>> Sent from the Delta quadrant using Borg technology!
>> 
>> Nux!
>> www.nux.ro
>> 
>> - Original Message -
>>> From: "Wido den Hollander" 
>>> To: dev@cloudstack.apache.org
>>> Sent: Monday, 20 October, 2014 23:29:04
>>> Subject: Re: failed 430-440 upgrade: Unable to start instance due to Unable 
>>> to
>>> get answer that is of class
>>> com.cloud.agent.api.StartAnswer
>> 
>>> On 10/21/2014 12:25 AM, Nux! wrote:
 Hi guys,

 I've followed the 4.3.x to 4.4.0 upgrade instruction to the letter and it 
 has
 worked, except the last step which failed to restart my system VMs. Now 
 I'm on
 4.4.0 without any system VMs; they are stuck in a creation loop which never
 succeeds. Relevant management log:

 Job failed due to exception Resource [Host:1] is unreachable: Host 1: 
 Unable to
 start instance due to Unable to get answer that is of class
 com.cloud.agent.api.StartAnswer
 http://pastebin.com/raw.php?i=k6WksLcU

 And on the agent:

 2014-10-20 23:10:57,369 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-5:null)
 Processing command: com.cloud.agent.api.StopCommand
 2014-10-20 23:10:57,371 DEBUG [kvm.resource.LibvirtConnection]
 (agentRequest-Handler-5:null) can't find connection: KVM, for vm: v-439-VM,
 continue
 2014-10-20 23:10:57,372 DEBUG [kvm.resource.LibvirtConnection]
 (agentRequest-Handler-5:null) can't find connection: LXC, for vm: v-439-VM,
 continue
 2014-10-20 23:10:57,372 DEBUG [kvm.resource.LibvirtConnection]
 (agentRequest-Handler-5:null) can't find which hypervisor the vm used , 
 then
 use the default hypervisor
 2014-10-20 23:10:57,374 DEBUG [kvm.resource.LibvirtComputingResource]
 (agentRequest-Handler-5:null) Failed to get dom xml:
 org.libvirt.LibvirtException: Domain not found: no domain with matching 
 name
 'v-439-VM'
 2014-10-20 23:10:57,375 DEBUG [kvm.resource.LibvirtComputingResource]
 (agentRequest-Handler-5:null) Failed to get dom xml:
 org.libvirt.LibvirtException: Domain not found: no domain with matching 
 name
 'v-439-VM'
 2014-10-20 23:10:57,377 DEBUG [kvm.resource.LibvirtComputingResource]
 (agentRequest-Handler-5:null) Failed to get dom xml:
 org.libvirt.LibvirtException: Domain not found: no domain with matching 
 name
 'v-439-VM'

 And this goes on and on.

 Any ideas?

>>>
>>> Is all the logging on DEBUG on the Agent? there has to be more
>>> information in the logfile telling you what is going on exactly.
>>>
>>> Wido
>>>
 Lucian


 --
 Sent from the Delta quadrant using Borg technology!

 Nux!
> >>> www.nux.ro

Review Request 26969: During VM deployment and while choosing CUSTOM disk offering for data disk, the size of the data disk is not considered for checking resource limit of primary storage.

[bharat kumar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/26969/
---

Review request for cloudstack and Kishan Kavala.


Bugs: CLOUDSTACK-7760
https://issues.apache.org/jira/browse/CLOUDSTACK-7760


Repository: cloudstack-git


Description
---

https://issues.apache.org/jira/browse/CLOUDSTACK-7760
During VM deployment and while choosing CUSTOM disk offering for data disk, the 
size of the data disk is not considered for checking resource limit of primary 
storage.


Diffs
-

  server/src/com/cloud/vm/UserVmManagerImpl.java 
2636096d03d7cfa097605ac066b8bd66b24972b7 

Diff: https://reviews.apache.org/r/26969/diff/


Testing
---

tested on 4.5


Thanks,

bharat kumar

Re: Review Request 26361: CLOUDSTACK-7660: Enhance system vm template to support baremetal

[Harikrishna Patnala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/26361/
---

(Updated Oct. 21, 2014, 1:02 p.m.)


Review request for cloudstack, Frank Zhang and Sateesh Chodapuneedi.


Bugs: CLOUDSTACK-7660
https://issues.apache.org/jira/browse/CLOUDSTACK-7660


Repository: cloudstack-git


Description
---

CLOUDSTACK-7660: Enhance system vm template to support baremetal
Installed Package flask and merged the disk partition


Please review the merging part of disk partitions.


Diffs (updated)
-

  systemvm/patches/debian/buildsystemvm.sh 7f6188a 
  tools/appliance/definitions/systemvmtemplate/preseed.cfg 0d2f70b 

Diff: https://reviews.apache.org/r/26361/diff/


Testing
---


Thanks,

Harikrishna Patnala

Re: [PROPOSAL] Remove SNAPSHOT from versioning and keep tags on the release branch

[Pierre-Luc Dion]

Rohit, I would much prefer something like Nate suggestions, at least when
working with cloudstack build from git source is easy to know using the
cloudstack version api call and rpm packages name.

Rohit, just be sure, what you are suggesting is ,as example, for branch 4.5
 until 4.5.0 is GA, the version show would be 4.5.0 in the 4.5 branch, once
4.5.0 is GA, then code build from 4.5 branch would have 4.5.1.
Compare to current where version is 4.5.0-SNAPSHOT until GA (GA commit
would have 4.5.0), post GA: 4.5.1-SNAPSHOT.
Correct?

I thought  the version label was define at one place , in a pom.xml ,
nowhere else. it's not the case in the code?  I know it's not for the
APIdoc which need to be manually defined.  I guest it wouldn't be too
complicated to have the version define at only one place and avoid to have
a -snapshot inside the debian/changelog file.

Nate, your help is very welcome, I'm not the proper person for how builds
are currently setups, might have to look with Hugo for that.


On Mon, Oct 20, 2014 at 1:29 PM, Erik Weber  wrote:

> On Mon, Oct 20, 2014 at 12:33 PM, Rohit Yadav 
> wrote:
>
> > Hi,
> >
> > Background:
> >
> > Whenever we start on a new release and cut its release branch, for
> example
> > 4.5 branch, we add the -SNAPSHOT string to the version string in
> pom.xmls,
> > debian/changelog and elsewhere. Just this mere action adds a divergence
> > between release and master branches and between two minor releases as
> well.
> > Also, we have seen build issue that come up just because someone forgot
> to
> > add or remove -SNAPSHOT or .snapshot in debian/ or packaging. The other
> > issue is historically we keep release tags on the release branches, by
> > doing this it makes it easy to find commits and follow the git history.
> By
> > doing a separate RC branch and then tagging on it is alright, you can
> still
> > do a git fetch and git checkout  but it break the historic
> convention.
> >
> >
> > So, please share your views on the follow proposal that try to add simple
> > changes:
> >
> > 1. Remove -SNAPSHOT suffix (and its lower/other case variants) from the
> > source code, just change to next version and keep working on it; we don’
> > have to fix build systems often.
> >
> > 2. In future keep release tags on major release branch (for example,
> > 4.3.0, 4.3.1 both on 4.3 branch)
> >
> >
> >
> Is it possible somehow (git foo or something?) to find out if a
> tarball/branch is an official release?
> I mean besides relying on the version number in POMs etc.
>
> As others I agree that having some sort of indication in the package wether
> or not your install is an official release or not is important.
> But it's only important to have some metadata about it, ie. the package
> name or similar.
>
> So if we could improve the packaging to figure out a way to check if the
> release is official or not, that would be sufficient for my use case.
>
> --
> Erik Weber
>

Re: [PROPOSAL] Remove SNAPSHOT from versioning and keep tags on the release branch

[Nate Gordon]

Unfortunately maven's concept of multi-module projects requires that the
sub projects define the version of the parent that they want. So it is
scattered throughout all the pom files, but there is a handy maven plugin
that can update them all for you. I think the bigger problem is around the
os packages and manual intervention. Which I think is solvable, but I've
never attempted to use the scripts that have been mentioned. So I might
need a little guidance as to the expected behavior, and what doesn't work
now. Otherwise it seems like a solvable problem.

On Tue, Oct 21, 2014 at 8:42 AM, Pierre-Luc Dion 
wrote:

> Rohit, I would much prefer something like Nate suggestions, at least when
> working with cloudstack build from git source is easy to know using the
> cloudstack version api call and rpm packages name.
>
> Rohit, just be sure, what you are suggesting is ,as example, for branch 4.5
>  until 4.5.0 is GA, the version show would be 4.5.0 in the 4.5 branch, once
> 4.5.0 is GA, then code build from 4.5 branch would have 4.5.1.
> Compare to current where version is 4.5.0-SNAPSHOT until GA (GA commit
> would have 4.5.0), post GA: 4.5.1-SNAPSHOT.
> Correct?
>
> I thought  the version label was define at one place , in a pom.xml ,
> nowhere else. it's not the case in the code?  I know it's not for the
> APIdoc which need to be manually defined.  I guest it wouldn't be too
> complicated to have the version define at only one place and avoid to have
> a -snapshot inside the debian/changelog file.
>
> Nate, your help is very welcome, I'm not the proper person for how builds
> are currently setups, might have to look with Hugo for that.
>
>
> On Mon, Oct 20, 2014 at 1:29 PM, Erik Weber  wrote:
>
> > On Mon, Oct 20, 2014 at 12:33 PM, Rohit Yadav  >
> > wrote:
> >
> > > Hi,
> > >
> > > Background:
> > >
> > > Whenever we start on a new release and cut its release branch, for
> > example
> > > 4.5 branch, we add the -SNAPSHOT string to the version string in
> > pom.xmls,
> > > debian/changelog and elsewhere. Just this mere action adds a divergence
> > > between release and master branches and between two minor releases as
> > well.
> > > Also, we have seen build issue that come up just because someone forgot
> > to
> > > add or remove -SNAPSHOT or .snapshot in debian/ or packaging. The other
> > > issue is historically we keep release tags on the release branches, by
> > > doing this it makes it easy to find commits and follow the git history.
> > By
> > > doing a separate RC branch and then tagging on it is alright, you can
> > still
> > > do a git fetch and git checkout  but it break the historic
> > convention.
> > >
> > >
> > > So, please share your views on the follow proposal that try to add
> simple
> > > changes:
> > >
> > > 1. Remove -SNAPSHOT suffix (and its lower/other case variants) from the
> > > source code, just change to next version and keep working on it; we
> don’
> > > have to fix build systems often.
> > >
> > > 2. In future keep release tags on major release branch (for example,
> > > 4.3.0, 4.3.1 both on 4.3 branch)
> > >
> > >
> > >
> > Is it possible somehow (git foo or something?) to find out if a
> > tarball/branch is an official release?
> > I mean besides relying on the version number in POMs etc.
> >
> > As others I agree that having some sort of indication in the package
> wether
> > or not your install is an official release or not is important.
> > But it's only important to have some metadata about it, ie. the package
> > name or similar.
> >
> > So if we could improve the packaging to figure out a way to check if the
> > release is official or not, that would be sufficient for my use case.
> >
> > --
> > Erik Weber
> >
>



-- 


*Nate Gordon*Director of Technology | Appcore - the business of cloud
computing®

Office +1.800.735.7104  |  Direct +1.515.612.7787
nate.gor...@appcore.com  |  www.appcore.com

--

The information in this message is intended for the named recipients only.
It may contain information that is privileged, confidential or otherwise
protected from disclosure. If you are not the intended recipient, you are
hereby notified that any disclosure, copying, distribution, or the taking
of any action in reliance on the contents of this message is strictly
prohibited. If you have received this e-mail in error, do not print it or
disseminate it or its contents. In such event, please notify the sender by
return e-mail and delete the e-mail file immediately thereafter. Thank you.

Re: [PROPOSAL] Remove SNAPSHOT from versioning and keep tags on the release branch

[Rohit Yadav]

Hi,

> On 21-Oct-2014, at 9:40 pm, Nate Gordon  wrote:
>
> Unfortunately maven's concept of multi-module projects requires that the
> sub projects define the version of the parent that they want. So it is
> scattered throughout all the pom files, but there is a handy maven plugin
> that can update them all for you. I think the bigger problem is around the
> os packages and manual intervention. Which I think is solvable, but I've
> never attempted to use the scripts that have been mentioned. So I might
> need a little guidance as to the expected behavior, and what doesn't work
> now. Otherwise it seems like a solvable problem.

I guess, we can write a script that adds custom prefixes to builds in pom.xml; 
other than this the only places that may need tinkering are packages/ and 
debian/changelog (also in upgrade paths, but we remove any -SNAPSHOT stuff in 
them).

For for master or 4.5.0, we keep the versions 4.6.0 and 4.5.0 respectively; 
people who want custom suffixes can use a script (that recursively goes to all 
packages/submodules and fixes pom.xml). People may want to tag built rpms/debs 
which they can do either by adding suffixes to those packages. We may also 
reintroduce having  a plain text file that holds git commit SHA out of which a 
build was built and put it in some package like cloudstack-common (we had one 
of those before).

>
> On Tue, Oct 21, 2014 at 8:42 AM, Pierre-Luc Dion 
> wrote:
>
>> Rohit, I would much prefer something like Nate suggestions, at least when
>> working with cloudstack build from git source is easy to know using the
>> cloudstack version api call and rpm packages name.
>>
>> Rohit, just be sure, what you are suggesting is ,as example, for branch 4.5
>> until 4.5.0 is GA, the version show would be 4.5.0 in the 4.5 branch, once
>> 4.5.0 is GA, then code build from 4.5 branch would have 4.5.1.
>> Compare to current where version is 4.5.0-SNAPSHOT until GA (GA commit
>> would have 4.5.0), post GA: 4.5.1-SNAPSHOT.
>> Correct?
>>
>> I thought  the version label was define at one place , in a pom.xml ,
>> nowhere else. it's not the case in the code?  I know it's not for the
>> APIdoc which need to be manually defined.  I guest it wouldn't be too
>> complicated to have the version define at only one place and avoid to have
>> a -snapshot inside the debian/changelog file.
>>
>> Nate, your help is very welcome, I'm not the proper person for how builds
>> are currently setups, might have to look with Hugo for that.
>>
>>
>> On Mon, Oct 20, 2014 at 1:29 PM, Erik Weber  wrote:
>>
>>> On Mon, Oct 20, 2014 at 12:33 PM, Rohit Yadav >>
>>> wrote:
>>>
 Hi,

 Background:

 Whenever we start on a new release and cut its release branch, for
>>> example
 4.5 branch, we add the -SNAPSHOT string to the version string in
>>> pom.xmls,
 debian/changelog and elsewhere. Just this mere action adds a divergence
 between release and master branches and between two minor releases as
>>> well.
 Also, we have seen build issue that come up just because someone forgot
>>> to
 add or remove -SNAPSHOT or .snapshot in debian/ or packaging. The other
 issue is historically we keep release tags on the release branches, by
 doing this it makes it easy to find commits and follow the git history.
>>> By
 doing a separate RC branch and then tagging on it is alright, you can
>>> still
 do a git fetch and git checkout  but it break the historic
>>> convention.


 So, please share your views on the follow proposal that try to add
>> simple
 changes:

 1. Remove -SNAPSHOT suffix (and its lower/other case variants) from the
 source code, just change to next version and keep working on it; we
>> don’
 have to fix build systems often.

 2. In future keep release tags on major release branch (for example,
 4.3.0, 4.3.1 both on 4.3 branch)



>>> Is it possible somehow (git foo or something?) to find out if a
>>> tarball/branch is an official release?
>>> I mean besides relying on the version number in POMs etc.
>>>
>>> As others I agree that having some sort of indication in the package
>> wether
>>> or not your install is an official release or not is important.
>>> But it's only important to have some metadata about it, ie. the package
>>> name or similar.
>>>
>>> So if we could improve the packaging to figure out a way to check if the
>>> release is official or not, that would be sufficient for my use case.
>>>
>>> --
>>> Erik Weber
>>>
>>
>
>
>
> --
>
>
> *Nate Gordon*Director of Technology | Appcore - the business of cloud
> computing®
>
> Office +1.800.735.7104  |  Direct +1.515.612.7787
> nate.gor...@appcore.com  |  www.appcore.com
>
> --
>
> The information in this message is intended for the named recipients only.
> It may contain information that is privileged, confidential or otherwise
> protected from disclosure. If you are not

Re: commits on 4.5

[Mike Tutkowski]

Hi Daan,

Do you know if the check-in protocol for 4.5 (or rather for any branched
release) is formally documented on the Wiki somewhere?

If it's not, it's probably harder to "enforce" it.

Thanks!
Mike

On Tue, Oct 21, 2014 at 1:21 AM, Daan Hoogland 
wrote:

> David,
>
> I keep seeing commits passing to the 4.5 branch. As you are the RM I am not
> reverting them. Should I? Not one of them has come from a hotfix branch for
> weeks.
>
> --
> Daan
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

Re: Review Request 26871: CLOUDSTACK-7748: Cloudstack version number is missing in system vm template.

[Nitin Mehta]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/26871/#review57604
---



tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh


Hari - I am not too familiar with the code so do educate me if I am wrong 
but as I have been asking repeated times why can we not make version mandatory 
rather than change this every release like you are doing right now ?


- Nitin Mehta


On Oct. 21, 2014, 6:09 a.m., Harikrishna Patnala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/26871/
> ---
> 
> (Updated Oct. 21, 2014, 6:09 a.m.)
> 
> 
> Review request for cloudstack, Kishan Kavala and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-7748
> https://issues.apache.org/jira/browse/CLOUDSTACK-7748
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-7748: Cloudstack version number is missing in system vm template.
> /etc/cloudstack-release in system vm does not have version number which 
> leads in vm deployment failure while checking router version
> 
> 
> During the system vm build, arguments can be passed to build.sh script 
> where 'version' argument is one of the optional arguments. The bug is even if 
> version argument is not passed defalut value(CLOUDSTACK_RELEASE=4.4.0) is 
> overridden by the null value (since argument is not passed).
> 
> 
> Diffs
> -
> 
>   tools/appliance/build.sh 8bf78b1 
>   tools/appliance/definitions/systemvmtemplate/configure_systemvm_services.sh 
> c076bb5 
> 
> Diff: https://reviews.apache.org/r/26871/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Harikrishna Patnala
> 
>

Re: commits on 4.5

[David Nalley]

We are well past feature freeze - but I haven't started a hard code
freeze; though it is imminent.

--David

On Tue, Oct 21, 2014 at 12:46 PM, Mike Tutkowski
 wrote:
> Hi Daan,
>
> Do you know if the check-in protocol for 4.5 (or rather for any branched
> release) is formally documented on the Wiki somewhere?
>
> If it's not, it's probably harder to "enforce" it.
>
> Thanks!
> Mike
>
> On Tue, Oct 21, 2014 at 1:21 AM, Daan Hoogland 
> wrote:
>>
>> David,
>>
>> I keep seeing commits passing to the 4.5 branch. As you are the RM I am
>> not
>> reverting them. Should I? Not one of them has come from a hotfix branch
>> for
>> weeks.
>>
>> --
>> Daan
>
>
>
>
> --
> Mike Tutkowski
> Senior CloudStack Developer, SolidFire Inc.
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud™

RE: commits on 4.5

[Edison Su]

Sorry, I am not aware of the 4.5 release policy, I'll revert my commits on 4.5.

> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Tuesday, October 21, 2014 12:22 AM
> To: dev; David Nalley
> Subject: commits on 4.5
> 
> David,
> 
> I keep seeing commits passing to the 4.5 branch. As you are the RM I am not
> reverting them. Should I? Not one of them has come from a hotfix branch for
> weeks.
> 
> --
> Daan

Re: commits on 4.5

[Mike Tutkowski]

So, in the past, feature freeze has been when we branch from master (in
this case, 4.5) and then people check directly into 4.5 until the RM has
called code freeze (at which point, we started using that -forward concept).

Where did we land on that? Once code freeze has passed, do people need to
create hotfix branches or are we still using -forward for 4.5?

On Tue, Oct 21, 2014 at 10:50 AM, David Nalley  wrote:

> We are well past feature freeze - but I haven't started a hard code
> freeze; though it is imminent.
>
> --David
>
> On Tue, Oct 21, 2014 at 12:46 PM, Mike Tutkowski
>  wrote:
> > Hi Daan,
> >
> > Do you know if the check-in protocol for 4.5 (or rather for any branched
> > release) is formally documented on the Wiki somewhere?
> >
> > If it's not, it's probably harder to "enforce" it.
> >
> > Thanks!
> > Mike
> >
> > On Tue, Oct 21, 2014 at 1:21 AM, Daan Hoogland 
> > wrote:
> >>
> >> David,
> >>
> >> I keep seeing commits passing to the 4.5 branch. As you are the RM I am
> >> not
> >> reverting them. Should I? Not one of them has come from a hotfix branch
> >> for
> >> weeks.
> >>
> >> --
> >> Daan
> >
> >
> >
> >
> > --
> > Mike Tutkowski
> > Senior CloudStack Developer, SolidFire Inc.
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud™
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

Re: commits on 4.5

[Mike Tutkowski]

I would hold off on that, Edison.

We need to make sure the policy is clear (and probably documented) first.

On Tue, Oct 21, 2014 at 10:57 AM, Edison Su  wrote:

> Sorry, I am not aware of the 4.5 release policy, I'll revert my commits on
> 4.5.
>
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > Sent: Tuesday, October 21, 2014 12:22 AM
> > To: dev; David Nalley
> > Subject: commits on 4.5
> >
> > David,
> >
> > I keep seeing commits passing to the 4.5 branch. As you are the RM I am
> not
> > reverting them. Should I? Not one of them has come from a hotfix branch
> for
> > weeks.
> >
> > --
> > Daan
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

RE: Help in Adding XenServer to CS Management Server

[Ritu Sabharwal]

Hi Rajani,

The SSVM is up and I can see it green in XenCenter.  

The systemvm.iso is available in the XenServer host. Below is the snapshot of 
it.

[root@DCM-Xen-69 ~]# ls -al /opt/xensource/packages/iso/
total 160684
drwxr-xr-x 2 root root 4096 Oct 15 10:49 .
drwxr-xr-x 5 root root 4096 May 20  2011 ..
-rw-r--r-- 1 root root 51802112 Oct 20 09:20 systemvm.iso
-rw-r--r-- 1 root root 45643776 May  5  2011 XenCenter.iso
-rw-r--r-- 1 root root 66908160 May 10  2011 xs-tools-5.6.100.iso

The current value of secstorage.allowed.internal.sites is 0.0.0.0/0. The CentOS 
template is not seeded offline i.e. from internal n/w. In that case also, do I 
need to change the value of secstorage.allowed.internal.sites?

Thanks & Regards,
Ritu S.
-Original Message-
From: Rajani Karuturi [mailto:raj...@apache.org] 
Sent: Monday, October 20, 2014 9:30 PM
To: dev@cloudstack.apache.org
Subject: Re: Help in Adding XenServer to CS Management Server

Is the SSVM Agent UP? (check 9 and 10 in the wiki) Did you check 
secstorage.allowed.internal.sites config value? (point 6 in the wiki)

~Rajani

On Tue, Oct 21, 2014 at 1:20 AM, Ritu Sabharwal 
wrote:

> Hi,
>
> I have been trying hard to get this up and running but have no luck so far.
>
> I have refereed to this troubleshooting guide for system vms:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates
> ,+Secondary+storage+troubleshooting
>
> The SSVM and CPVM are running but I don't see any health check script 
> there and also I can't ssh from XenServer host to the SSVM. I get no 
> route to host error.
>
> Please provide help in resolving these errors.
>
> Thanks & Regards,
> Ritu S.
>
> -Original Message-
> From: Ritu Sabharwal [mailto:rsabh...@brocade.com]
> Sent: Friday, October 17, 2014 3:02 PM
> To: dev@cloudstack.apache.org
> Subject: RE: Help in Adding XenServer to CS Management Server
>
> Hi,
>
> I could move ahead with the issues and see the SSVM and CPVM coming up .
> But when I  try to create a user VM I still don't see the default template.
>
> What could be the problem here? Any suggestions?
>
> Thanks & Regards,
> Ritu S.
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pdion...@apache.org]
> Sent: Wednesday, October 15, 2014 7:52 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Help in Adding XenServer to CS Management Server
>
> Ritu,
>  You have to wait a little when creating a zone until you have the 
> SSVM and CPVM ready. then it will automatically download a centos 5.6  
> which confirm your initial zone is working. if  this is not happening, 
> there might be a config issue related to primary, secondary storage or 
> network label.
>
> hope this help,
>
> PL
>
>
> On Wed, Oct 15, 2014 at 9:08 PM, Yitao Jiang  wrote:
>
> > 1.Check zone status, make sure enabled.
> > 2.change mgmt server debug level, watch ing the log file in 
> > /var/log/cloud/ On Oct 16, 2014 7:13 AM, "Ritu Sabharwal" <
> rsabh...@brocade.com> wrote:
> >
> > > Hi,
> > >
> > > I am trying to add XenServer to the CS Management Server.
> > >
> > > I could add the hosts and I see Host status as up on the GUI. But 
> > > I don't see any System VMs coming up and Virtual Router coming up 
> > > in the
> > dashboard.
> > > When I try to create a User VM there is no template available to
> select.
> > >
> > > I am blocked at this point.
> > >
> > > I did seed Secondary Storage by importing system VM templat from
> > > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemv
> > > m6 4/ for Xen (systemvm64template-4.4-2014-09-30-xen.vhd.bz2<
> > >
> > http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm6
> > 4/
> > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template
> > -4
> > .4-2014-09-30-xen.vhd.bz2
> > > >)
> > >
> > > Any help on this is appreciated.
> > >
> > > Thanks & Regards,
> > > Ritu S.
> > >
> >
>

Build failed in Jenkins: build-4.5 #35

[jenkins]

See 

Changes:

[sudison] Revert "fix kvm issue, for windows sever 2008, it will crash without 
hyperv enlightment featre enabled"

[sudison] Revert "There are few cases that mgt server won't reponse agent's 
pingcommand timely, or in KVM's case, libvirt won't repsonse in few mintues, 
which will cause agent reconnect to mgt server, then all the on going tasks on 
host will fail"

--
[...truncated 1828 lines...]
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.481 sec
Running org.apache.cloudstack.region.RegionManagerTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.144 sec
Running org.apache.cloudstack.service.ServiceOfferingVOTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.19 sec
Running org.apache.cloudstack.affinity.AffinityApiUnitTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.282 sec
Running org.apache.cloudstack.privategw.AclOnPrivateGwTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.71 sec
Running org.apache.cloudstack.network.lb.CertServiceTest
Tests run: 15, Failures: 5, Errors: 3, Skipped: 0, Time elapsed: 3.29 sec <<< 
FAILURE!
Running org.apache.cloudstack.network.lb.ApplicationLoadBalancerTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.952 sec
Running org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 30.597 sec
Running com.cloud.template.TemplateManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.096 sec
Running com.cloud.keystore.KeystoreTest
org.apache.cloudstack.api.response.UserVmResponse/null/{"id":"3","securitygroup":[],"nic":[],"tags":[],"affinitygroup":[]}
org.apache.cloudstack.api.response.AlertResponse/null/{"id":"100","description":"Hello"}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.87 sec
Running com.cloud.server.ConfigurationServerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.074 sec
Running com.cloud.event.EventControlsUnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.37 sec
Running com.cloud.resourcelimit.ResourceLimitManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec
Running com.cloud.api.dispatch.ParamGenericValidationWorkerTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.149 sec
Running com.cloud.api.dispatch.ParamProcessWorkerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.106 sec
Running com.cloud.api.dispatch.CommandCreationWorkerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 sec
Running com.cloud.api.dispatch.DispatchChainFactoryTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec
Running com.cloud.api.dispatch.SpecificCmdValidationWorkerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec
Running com.cloud.api.ApiServletTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.55 sec
Running com.cloud.api.ApiResponseHelperTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.144 sec
Running com.cloud.alert.AlertControlsUnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.095 sec
Running com.cloud.ha.KVMFencerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.488 sec
Running com.cloud.ha.HighAvailabilityManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.639 sec
Running com.cloud.capacity.CapacityManagerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.221 sec
Running com.cloud.vm.snapshot.VMSnapshotManagerTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.978 sec
Running com.cloud.vm.FirstFitPlannerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.242 sec
Running com.cloud.vm.UserVmManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.335 sec
Running com.cloud.vm.DeploymentPlanningManagerImplTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.07 sec
Running com.cloud.servlet.ConsoleProxyServletTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec
Running com.cloud.servlet.StaticResourceServletTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.532 sec
Running com.cloud.network.ExternalLoadBalancerDeviceManagerImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.121 sec
Running com.cloud.network.NetworkModelTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.149 sec
Running com.cloud.network.security.SecurityGroupManagerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.571 sec
Running com.cloud.network.security.SecurityGroupQueueTest
Total jobs dequeued = 10, num queued=1000 queue current size

Re: Unreleased 4.4.1 packages on cloudstack.apt-get.eu, why?

[Nux!]

well, cheers for that, looks like I am going to use them tonight. :)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Daan Hoogland" 
> To: "dev" 
> Sent: Monday, 20 October, 2014 22:05:05
> Subject: Re: Unreleased 4.4.1 packages on cloudstack.apt-get.eu, why?

> me on a device with keyboard; I put them back after rebuilding them with
> the tag for the approved commit. I was holding of on the announce to let
> the mirrors sync and to make a good announcement together with Sally and
> Pierre-Luc.
> 
> kind regards,
> 
> On Mon, Oct 20, 2014 at 10:51 PM, Daan Hoogland 
> wrote:
> 
>> I did. This time they should be there. For convenience,that is.
>> Op 20 okt. 2014 22:49 schreef "Erik Weber" :
>>
>> On Mon, Oct 20, 2014 at 10:43 PM, Nux!  wrote:
>>>
>>> > Guys.. for crying out loud.. who put the 4.4.1 rpms back and regenerated
>>> > the repodata?
>>> > I wouldn't normally care, but this repo is advertised in many places,
>>> > people have it installed, it will get used ... with unreleased, buggy
>>> > software ...
>>> >
>>> > Please make another directory or something.
>>> >
>>> > :(
>>> >
>>> >
>>> 4.4.1 is officially voted for now, right? I'm not familiar with bylaws and
>>> such, but is there something that prohibits us from distributing before an
>>> announcement has been made?
>>>
>>> --
>>> Erik
>>>
>>> > --
>>> > Sent from the Delta quadrant using Borg technology!
>>> >
>>> > Nux!
>>> > www.nux.ro
>>> >
>>> > - Original Message -
>>> > > From: "Daan Hoogland" 
>>> > > To: "dev" 
>>> > > Sent: Friday, 10 October, 2014 08:46:05
>>> > > Subject: Re: Unreleased 4.4.1 packages on cloudstack.apt-get.eu, why?
>>> >
>>> > > I was thinking about that. I shouldn't have done this upload but had a
>>> > > reason to. I want to make these available for testers. maybe i can
>>> upload
>>> > > them without adding them to the rpm index...?
>>> > >
>>> > > On Thu, Oct 9, 2014 at 7:47 PM, Nux!  wrote:
>>> > >
>>> > >> Perhaps we need a testing repo for non-final packages?
>>> > >>
>>> > >> --
>>> > >> Sent from the Delta quadrant using Borg technology!
>>> > >>
>>> > >> Nux!
>>> > >> www.nux.ro
>>> > >>
>>> > >> - Original Message -
>>> > >> > From: "Daan Hoogland" 
>>> > >> > To: "dev" 
>>> > >> > Sent: Thursday, 9 October, 2014 17:42:50
>>> > >> > Subject: Re: Unreleased 4.4.1 packages on cloudstack.apt-get.eu,
>>> why?
>>> > >>
>>> > >> > i did
>>> > >> >
>>> > >> > On Thu, Oct 9, 2014 at 3:07 PM, Ian Duffy  wrote:
>>> > >> >
>>> > >> >> Wildo,
>>> > >> >>
>>> > >> >> Do we have no kind of audit on uploads?
>>> > >> >>
>>> > >> >> On 9 October 2014 12:25, Wido den Hollander 
>>> wrote:
>>> > >> >>
>>> > >> >> >
>>> > >> >> >
>>> > >> >> > On 10/09/2014 01:21 PM, Nux! wrote:
>>> > >> >> > > Hello,
>>> > >> >> > >
>>> > >> >> > > I've noticed there are 4.4.1 packages on
>>> > >> >> > http://cloudstack.apt-get.eu/rhel/4.4/.
>>> > >> >> > > Since 4.4.0 is latest release, how come? This is bad, people
>>> will
>>> > >> >> > install broken stuff.
>>> > >> >> > > Can anyone fix this?
>>> > >> >> > >
>>> > >> >> >
>>> > >> >> > I removed the packages, but I'm not sure who uploaded them.
>>> > >> >> >
>>> > >> >> > They were uploaded on September 30th at 11:12 CET.
>>> > >> >> >
>>> > >> >> > Wido
>>> > >> >> >
>>> > >> >> > > Lucian
>>> > >> >> > >
>>> > >> >> > > --
>>> > >> >> > > Sent from the Delta quadrant using Borg technology!
>>> > >> >> > >
>>> > >> >> > > Nux!
>>> > >> >> > > www.nux.ro
>>> > >> >> > >
>>> > >> >> >
>>> > >> >>
>>> > >> >
>>> > >> >
>>> > >> >
>>> > >> > --
>>> > >> > Daan
>>> > >>
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > Daan
>>> >
>>>
>>
> 
> 
> --
> Daan

Re: pre-announcement of release 4.4.1

[Mike Tutkowski]

This look really good!

On Tue, Oct 21, 2014 at 3:14 AM, Daan Hoogland 
wrote:

> H devs, as the finalisation of the release announcement is taking some
> time, here is the sneak preview:
>
> = = =
>
> [APACHE CLOUDSTACK LOGO]
>
> Announcing Apache™ CloudStack™ v4.4.1
>
> Mature, easy-to-deploy Open Source Cloud computing software platform
> boasts improved efficiency and performance.
>
> [DATELINE] —NN MONTH 2014— The Apache CloudStack project today
> announced the immediate availability of Apache CloudStack v4.4.1, the
> latest version of the turnkey Open Source cloud computing software
> platform used for creating private-, public-, and hybrid cloud
> environments.
>
> Apache CloudStack clouds enable billions of dollars' worth of business
> transactions annually across their clouds, and its maturity and
> stability has led it to has become the Open Source platform for many
> service providers to set up on-demand, elastic public cloud computing
> services, as well as enterprises and others to set up a private or
> hybrid cloud for use by their own employees.
>
> [@@ "QUOTE," said Hugo Trippaers, Vice President of Apache CloudStack.
> "MORE FROM HUGO."]
>
> Lauded by Gartner Group, CloudStack includes an intuitive user
> interface and rich APIs for managing the compute, networking,
> software, and storage infrastructure resources.
>
> CloudStack v4.4.1 reflects dozens of new features and improvements,
> including:
> -Improved Storage Management
> -Virtual Private Cloud tiers can now span guest networks across
> availability zones
> -Support for VMware Distributed Resource Scheduler
> -Improved Support for Hyper-V Zones, VPC and Storage Migration
>
> A complete overview of all new enhancements can be found in the
> project release notes at
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/
>
> CloudStack has been used by thousands of organizations worldwide and
> is in use/production at Alcatel-Lucent, Autodesk, BT Cloud, China
> Telecom, DATACAENTER Services, DataPipe, Edmunds.com, Exoscale,
> GreenQloud, Hokkaido University, IDC Frontier, Ikoula, KDDI, KT/Korea
> Telecom, LeaseWeb, NTT, Orange, PCextreme, Schuberg Philis, Shopzilla,
> Slovak Telekom, SunGard AS, Taiwan Mobile, Tata, Trader Media Group,
> TomTom, University of Melbourne, University of Sao Paolo, Verizon,
> WebMD and Zynga, among others.
>
> CloudStack originated at Cloud.com, which was acquired by Citrix in
> 2011. CloudStack was submitted to the Apache Incubator in April 2012
> and graduated as an Apache Software Foundation Top-level Project in
> March 2013.
>
> Availability
> CloudStack v4.4.1 is available immediately as a free download from
> http://cloudstack.apache.org/downloads.html. Apache CloudStack
> software is released under the Apache License v2.0.
>
> Governance and Oversight
> Apache CloudStack is overseen by a self-selected team of active
> contributors to the project. A Project Management Committee (PMC)
> guides the Project's day-to-day operations, including community
> development and product
> releases.
>
> Get Involved!
> Apache CloudStack welcomes contribution and community participation
> through mailing lists as well as attending face-to-face MeetUps,
> developer trainings, and user events. Catch CloudStack in action at
> the CloudStack Collaboration Conference, the official user/developer
> conference of the Apache CloudStack community, 19-21 November 2014 in
> Budapest, Hungary @CCCEU14
>
> http://events.linuxfoundation.org/events/cloudstack-collaboration-conference-europe
>
> About Apache CloudStack
> Apache CloudStack is a mature, turnkey integrated
> Infrastructure-as-a-Service (IaaS) Open Source software platform that
> allows users to build feature-rich public and private cloud
> environments. Hailed by Gartner Group as "a solid product", CloudStack
> includes an intuitive user interface and rich APIs for managing the
> compute, networking, software, and storage infrastructure resources.
> CloudStack entered the Apache Incubator in April 2012 and became an
> Apache Top-level Project in March 2013. For downloads, documentation,
> and ways to become involved with Apache CloudStack, visit
> http://cloudstack.apache.org/ and https://twitter.com/CloudStack
>
> # # #
>
> © The Apache Software Foundation. "Apache", "CloudStack", "Apache
> CloudStack", the Apache CloudStack logo, and the Apache CloudStack
> Cloud Monkey logo are registered trademarks or trademarks of The
> Apache Software Foundation. All other brands and trademarks are the
> property of their respective owners.
>
> Contacts
> Apache CloudStack
> [FULL NAME]
> [telephone number with country code]
> market...@cloudstack.apache.org
>
> --
> Daan
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

Re: Help in Adding XenServer to CS Management Server

[Nitin Mehta]

Make sure you are using the right systemvm.iso, for this version and for
this hypervisor. You won't find scripts if scripts in sytemvm.iso havent
been injected onto ssvm
You can also login from Xencenter into ssvm and check logs as well.

On 21/10/14 10:03 AM, "Ritu Sabharwal"  wrote:

>Hi Rajani,
>
>The SSVM is up and I can see it green in XenCenter.
>
>The systemvm.iso is available in the XenServer host. Below is the
>snapshot of it.
>
>[root@DCM-Xen-69 ~]# ls -al /opt/xensource/packages/iso/
>total 160684
>drwxr-xr-x 2 root root 4096 Oct 15 10:49 .
>drwxr-xr-x 5 root root 4096 May 20  2011 ..
>-rw-r--r-- 1 root root 51802112 Oct 20 09:20 systemvm.iso
>-rw-r--r-- 1 root root 45643776 May  5  2011 XenCenter.iso
>-rw-r--r-- 1 root root 66908160 May 10  2011 xs-tools-5.6.100.iso
>
>The current value of secstorage.allowed.internal.sites is 0.0.0.0/0. The
>CentOS template is not seeded offline i.e. from internal n/w. In that
>case also, do I need to change the value of
>secstorage.allowed.internal.sites?
>
>Thanks & Regards,
>Ritu S.
>-Original Message-
>From: Rajani Karuturi [mailto:raj...@apache.org]
>Sent: Monday, October 20, 2014 9:30 PM
>To: dev@cloudstack.apache.org
>Subject: Re: Help in Adding XenServer to CS Management Server
>
>Is the SSVM Agent UP? (check 9 and 10 in the wiki) Did you check
>secstorage.allowed.internal.sites config value? (point 6 in the wiki)
>
>~Rajani
>
>On Tue, Oct 21, 2014 at 1:20 AM, Ritu Sabharwal 
>wrote:
>
>> Hi,
>>
>> I have been trying hard to get this up and running but have no luck so
>>far.
>>
>> I have refereed to this troubleshooting guide for system vms:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates
>> ,+Secondary+storage+troubleshooting
>>
>> The SSVM and CPVM are running but I don't see any health check script
>> there and also I can't ssh from XenServer host to the SSVM. I get no
>> route to host error.
>>
>> Please provide help in resolving these errors.
>>
>> Thanks & Regards,
>> Ritu S.
>>
>> -Original Message-
>> From: Ritu Sabharwal [mailto:rsabh...@brocade.com]
>> Sent: Friday, October 17, 2014 3:02 PM
>> To: dev@cloudstack.apache.org
>> Subject: RE: Help in Adding XenServer to CS Management Server
>>
>> Hi,
>>
>> I could move ahead with the issues and see the SSVM and CPVM coming up .
>> But when I  try to create a user VM I still don't see the default
>>template.
>>
>> What could be the problem here? Any suggestions?
>>
>> Thanks & Regards,
>> Ritu S.
>>
>> -Original Message-
>> From: Pierre-Luc Dion [mailto:pdion...@apache.org]
>> Sent: Wednesday, October 15, 2014 7:52 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: Help in Adding XenServer to CS Management Server
>>
>> Ritu,
>>  You have to wait a little when creating a zone until you have the
>> SSVM and CPVM ready. then it will automatically download a centos 5.6
>> which confirm your initial zone is working. if  this is not happening,
>> there might be a config issue related to primary, secondary storage or
>> network label.
>>
>> hope this help,
>>
>> PL
>>
>>
>> On Wed, Oct 15, 2014 at 9:08 PM, Yitao Jiang 
>>wrote:
>>
>> > 1.Check zone status, make sure enabled.
>> > 2.change mgmt server debug level, watch ing the log file in
>> > /var/log/cloud/ On Oct 16, 2014 7:13 AM, "Ritu Sabharwal" <
>> rsabh...@brocade.com> wrote:
>> >
>> > > Hi,
>> > >
>> > > I am trying to add XenServer to the CS Management Server.
>> > >
>> > > I could add the hosts and I see Host status as up on the GUI. But
>> > > I don't see any System VMs coming up and Virtual Router coming up
>> > > in the
>> > dashboard.
>> > > When I try to create a User VM there is no template available to
>> select.
>> > >
>> > > I am blocked at this point.
>> > >
>> > > I did seed Secondary Storage by importing system VM templat from
>> > > 
>>http://secure-web.cisco.com/1gUYzrTMP4_zt6B7yu1eZm6uBqfffITqyVeBGbnHBI-0W
>>51IPO478b_yzMFXjTTcV15QCBCQnmZjqkRmiKzqbu3N90krlwtq1PCEBOg_XGxtGFpbQZsZdC
>>c8XLiDDwFq4Ov4RD1naqhDxLv0HXM7LqyMU7JnQlVx1xaiwb8z_m-E/http%3A%2F%2Fjenki
>>ns.buildacloud.org%2Fview%2F4.4%2Fjob%2Fcloudstack-4.4-systemv
>> > > m6 4/ for Xen (systemvm64template-4.4-2014-09-30-xen.vhd.bz2<
>> > >
>> > 
>>http://secure-web.cisco.com/16OFpcrv9LcUzeznlMuXnFxkgvkcDd81s4oz4P5Vo3i8_
>>GA3m_OvSDO5KgPom5CEcuPM3FEKi0oqEWqfu70dU4Mp-CL_WYUvuU66MqRZVqGt6mNT7KhmWU
>>WkvDAGQl31uLHdXUKD-zonVFZjKRIe5zsuqz7KqnAYqgf9BmfMKj2Q/http%3A%2F%2Fjenki
>>ns.buildacloud.org%2Fview%2F4.4%2Fjob%2Fcloudstack-4.4-systemvm6
>> > 4/
>> > lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template
>> > -4
>> > .4-2014-09-30-xen.vhd.bz2
>> > > >)
>> > >
>> > > Any help on this is appreciated.
>> > >
>> > > Thanks & Regards,
>> > > Ritu S.
>> > >
>> >
>>

Re: commits on 4.5

[Daan Hoogland]

I wouldn't do that either Edison, that's up to David. I think the
practice of making hotfix branches is good in any case.

The thing that worries me most is that commits are being entered
seperately on both 45 and master instead of merging back.

On Tue, Oct 21, 2014 at 7:01 PM, Mike Tutkowski
 wrote:
> I would hold off on that, Edison.
>
> We need to make sure the policy is clear (and probably documented) first.
>
> On Tue, Oct 21, 2014 at 10:57 AM, Edison Su  wrote:
>
>> Sorry, I am not aware of the 4.5 release policy, I'll revert my commits on
>> 4.5.
>>
>> > -Original Message-
>> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> > Sent: Tuesday, October 21, 2014 12:22 AM
>> > To: dev; David Nalley
>> > Subject: commits on 4.5
>> >
>> > David,
>> >
>> > I keep seeing commits passing to the 4.5 branch. As you are the RM I am
>> not
>> > reverting them. Should I? Not one of them has come from a hotfix branch
>> for
>> > weeks.
>> >
>> > --
>> > Daan
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*



-- 
Daan

Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

Hi,

I want to upgrade a 4.3.1 installation to 4.4.1. 
Am I still required to add the 4.4.0-6 template before in order for this thing 
to succeed or has that been solved?

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Daan Hoogland]

yes, i am afraid you are.

On Tue, Oct 21, 2014 at 9:15 PM, Nux!  wrote:
> Hi,
>
> I want to upgrade a 4.3.1 installation to 4.4.1.
> Am I still required to add the 4.4.0-6 template before in order for this 
> thing to succeed or has that been solved?
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro



-- 
Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

So, to clarify:
- I need to add "systemvm-kvm-4.4" from 
http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-kvm.qcow2.bz2
- And then add the same "systemvm-kvm-4.4" (same name? won't cause problems?) 
from 
http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.1-7-xen.vhd.bz2

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Daan Hoogland" 
> To: "dev" 
> Sent: Tuesday, 21 October, 2014 20:18:01
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

> yes, i am afraid you are.
> 
> On Tue, Oct 21, 2014 at 9:15 PM, Nux!  wrote:
>> Hi,
>>
>> I want to upgrade a 4.3.1 installation to 4.4.1.
>> Am I still required to add the 4.4.0-6 template before in order for this 
>> thing
>> to succeed or has that been solved?
>>
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
> 
> 
> 
> --
> Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Daan Hoogland]

you will add the seond one after the db upgrade. the first one is
needed during the db upgrade. flakey, i admit.

On Tue, Oct 21, 2014 at 9:24 PM, Nux!  wrote:
> So, to clarify:
> - I need to add "systemvm-kvm-4.4" from 
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-kvm.qcow2.bz2
> - And then add the same "systemvm-kvm-4.4" (same name? won't cause problems?) 
> from 
> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.1-7-xen.vhd.bz2
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
>> From: "Daan Hoogland" 
>> To: "dev" 
>> Sent: Tuesday, 21 October, 2014 20:18:01
>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?
>
>> yes, i am afraid you are.
>>
>> On Tue, Oct 21, 2014 at 9:15 PM, Nux!  wrote:
>>> Hi,
>>>
>>> I want to upgrade a 4.3.1 installation to 4.4.1.
>>> Am I still required to add the 4.4.0-6 template before in order for this 
>>> thing
>>> to succeed or has that been solved?
>>>
>>> Lucian
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>
>>
>>
>> --
>> Daan



-- 
Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

Roger that, flakey is ok, as long as we know the exact steps to take. :)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Daan Hoogland" 
> To: "dev" 
> Sent: Tuesday, 21 October, 2014 20:26:09
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

> you will add the seond one after the db upgrade. the first one is
> needed during the db upgrade. flakey, i admit.
> 
> On Tue, Oct 21, 2014 at 9:24 PM, Nux!  wrote:
>> So, to clarify:
>> - I need to add "systemvm-kvm-4.4" from
>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-kvm.qcow2.bz2
>> - And then add the same "systemvm-kvm-4.4" (same name? won't cause problems?)
>> from
>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.1-7-xen.vhd.bz2
>>
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> - Original Message -
>>> From: "Daan Hoogland" 
>>> To: "dev" 
>>> Sent: Tuesday, 21 October, 2014 20:18:01
>>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 
>>> 4.4.1?
>>
>>> yes, i am afraid you are.
>>>
>>> On Tue, Oct 21, 2014 at 9:15 PM, Nux!  wrote:
 Hi,

 I want to upgrade a 4.3.1 installation to 4.4.1.
 Am I still required to add the 4.4.0-6 template before in order for this 
 thing
 to succeed or has that been solved?

 Lucian

 --
 Sent from the Delta quadrant using Borg technology!

 Nux!
 www.nux.ro
>>>
>>>
>>>
>>> --
>>> Daan
> 
> 
> 
> --
> Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

Since we're at it, can anyone confirm the "manual systemvm hotfix" is no longer 
needed with 4.4.1?

https://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.0/upgrade/upgrade-4.3.html#manual-hofix

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nux!" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 21 October, 2014 20:27:29
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

> Roger that, flakey is ok, as long as we know the exact steps to take. :)
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Daan Hoogland" 
>> To: "dev" 
>> Sent: Tuesday, 21 October, 2014 20:26:09
>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?
> 
>> you will add the seond one after the db upgrade. the first one is
>> needed during the db upgrade. flakey, i admit.
>> 
>> On Tue, Oct 21, 2014 at 9:24 PM, Nux!  wrote:
>>> So, to clarify:
>>> - I need to add "systemvm-kvm-4.4" from
>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-kvm.qcow2.bz2
>>> - And then add the same "systemvm-kvm-4.4" (same name? won't cause 
>>> problems?)
>>> from
>>> http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.1-7-xen.vhd.bz2
>>>
>>> Lucian
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>> - Original Message -
 From: "Daan Hoogland" 
 To: "dev" 
 Sent: Tuesday, 21 October, 2014 20:18:01
 Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 
 4.4.1?
>>>
 yes, i am afraid you are.

 On Tue, Oct 21, 2014 at 9:15 PM, Nux!  wrote:
> Hi,
>
> I want to upgrade a 4.3.1 installation to 4.4.1.
> Am I still required to add the 4.4.0-6 template before in order for this 
> thing
> to succeed or has that been solved?
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro



 --
 Daan
>> 
>> 
>> 
>> --
> > Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Daan Hoogland]

On Tue, Oct 21, 2014 at 9:32 PM, Nux!  wrote:
> ual sys


that would be once you install the 4.4.1 templates, yes. remind me
often we need to upgrade the systemvm upgrade mechs

-- 
Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Daan Hoogland]

I read wrong. didn't think this was needed this way for the 4.4.0
templates, only for the 4.4.1 templates.

On Tue, Oct 21, 2014 at 9:35 PM, Daan Hoogland  wrote:
> On Tue, Oct 21, 2014 at 9:32 PM, Nux!  wrote:
>> ual sys
>
>
> that would be once you install the 4.4.1 templates, yes. remind me
> often we need to upgrade the systemvm upgrade mechs
>
> --
> Daan



-- 
Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

Right, so the steps would be:

- install 4.4.0-6 systemvm
- upgrade management/db
- install 4.4.1 systemvm
- do the manual db hotfix thing
- finally restart the systemvms so they use the 4.4.1 template

Does that cover it?

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Daan Hoogland" 
> To: "dev" 
> Sent: Tuesday, 21 October, 2014 20:35:51
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

> On Tue, Oct 21, 2014 at 9:32 PM, Nux!  wrote:
>> ual sys
> 
> 
> that would be once you install the 4.4.1 templates, yes. remind me
> often we need to upgrade the systemvm upgrade mechs
> 
> --
> Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Daan Hoogland]

it most certainly does

On Tue, Oct 21, 2014 at 9:38 PM, Nux!  wrote:
> Right, so the steps would be:
>
> - install 4.4.0-6 systemvm
> - upgrade management/db
> - install 4.4.1 systemvm
> - do the manual db hotfix thing
> - finally restart the systemvms so they use the 4.4.1 template
>
> Does that cover it?
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
>> From: "Daan Hoogland" 
>> To: "dev" 
>> Sent: Tuesday, 21 October, 2014 20:35:51
>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?
>
>> On Tue, Oct 21, 2014 at 9:32 PM, Nux!  wrote:
>>> ual sys
>>
>>
>> that would be once you install the 4.4.1 templates, yes. remind me
>> often we need to upgrade the systemvm upgrade mechs
>>
>> --
>> Daan



-- 
Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

Ok, cheers. I'll start shortly, fingers crossed. :)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Daan Hoogland" 
> To: "dev" 
> Sent: Tuesday, 21 October, 2014 20:39:50
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

> it most certainly does
> 
> On Tue, Oct 21, 2014 at 9:38 PM, Nux!  wrote:
>> Right, so the steps would be:
>>
>> - install 4.4.0-6 systemvm
>> - upgrade management/db
>> - install 4.4.1 systemvm
>> - do the manual db hotfix thing
>> - finally restart the systemvms so they use the 4.4.1 template
>>
>> Does that cover it?
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> - Original Message -
>>> From: "Daan Hoogland" 
>>> To: "dev" 
>>> Sent: Tuesday, 21 October, 2014 20:35:51
>>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 
>>> 4.4.1?
>>
>>> On Tue, Oct 21, 2014 at 9:32 PM, Nux!  wrote:
 ual sys
>>>
>>>
>>> that would be once you install the 4.4.1 templates, yes. remind me
>>> often we need to upgrade the systemvm upgrade mechs
>>>
>>> --
>>> Daan
> 
> 
> 
> --
> Daan

Certificate expired

[Mike Tutkowski]

Hi,

I just started getting this test-run error message on two of my CloudStack
dev boxes today (below).

I don't recall sign-signing a certificate, but perhaps I just forgot.

Can someone give me the context around this error?

Thanks!

Results :


---

Test set: org.apache.cloudstack.network.lb.CertServiceTest

---

Tests run: 15, Failures: 2, Errors: 2, Skipped: 4, Time elapsed: 0.538 sec
<<< FAILURE!

runUploadSslCertBadkeyAlgo(org.apache.cloudstack.network.lb.CertServiceTest)
 Time elapsed: 0.128 sec  <<< FAILURE!

java.lang.AssertionError

at org.junit.Assert.fail(Assert.java:86)

at org.junit.Assert.assertTrue(Assert.java:41)

at org.junit.Assert.assertTrue(Assert.java:52)

at
org.apache.cloudstack.network.lb.CertServiceTest.runUploadSslCertBadkeyAlgo(CertServiceTest.java:539)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)

at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)

at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)

at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)

at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)

at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)

at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)

at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)

at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)

at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)

at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)

at org.junit.runners.ParentRunner.run(ParentRunner.java:309)

at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)

at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)

at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)

at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)

at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)

at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)

at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)

runUploadSslCertBadkeyPair(org.apache.cloudstack.network.lb.CertServiceTest)
 Time elapsed: 0.01 sec  <<< FAILURE!

java.lang.AssertionError

at org.junit.Assert.fail(Assert.java:86)

at org.junit.Assert.assertTrue(Assert.java:41)

at org.junit.Assert.assertTrue(Assert.java:52)

at
org.apache.cloudstack.network.lb.CertServiceTest.runUploadSslCertBadkeyPair(CertServiceTest.java:495)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)

at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)

at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)

at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)

at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)

at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)

at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)

at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)

at org.junit.runners.ParentRunner.runChildr

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

Well, hit a small issue:
- added 4.4.0 systemvm - OK
- upgraded management/db - OK
- add 4.4.1 systemvm - FAIL - "Cannot use reserved names for templates"

So the names from the 4.4.0 and 4.4.1 systemvm names are identical and 
conflict. I added the 4.4.1 systemvm as systemvm-kvm-4.4.1. Would this work?

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nux!" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 21 October, 2014 20:43:41
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

> Ok, cheers. I'll start shortly, fingers crossed. :)
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Daan Hoogland" 
>> To: "dev" 
>> Sent: Tuesday, 21 October, 2014 20:39:50
>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?
> 
>> it most certainly does
>> 
>> On Tue, Oct 21, 2014 at 9:38 PM, Nux!  wrote:
>>> Right, so the steps would be:
>>>
>>> - install 4.4.0-6 systemvm
>>> - upgrade management/db
>>> - install 4.4.1 systemvm
>>> - do the manual db hotfix thing
>>> - finally restart the systemvms so they use the 4.4.1 template
>>>
>>> Does that cover it?
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>> - Original Message -
 From: "Daan Hoogland" 
 To: "dev" 
 Sent: Tuesday, 21 October, 2014 20:35:51
 Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 
 4.4.1?
>>>
 On Tue, Oct 21, 2014 at 9:32 PM, Nux!  wrote:
> ual sys


 that would be once you install the 4.4.1 templates, yes. remind me
 often we need to upgrade the systemvm upgrade mechs

 --
 Daan
>> 
>> 
>> 
>> --
> > Daan

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

So what I see has happened is as a result of the DB upgrade from 4.3.1 to 4.4.1 
 the systemvm-kvm-4.4 (4.4.0-6) has been marked of type System, it's not 
deletable now. 
Also its ID in the DB is now present as the template to use for ConsoleProxy, 
SSVM and VR.
It's as if the hotfix was performed, although I have most certainly not.

Can I just go ahead and perform the hotfix manually, but for systemvm-kvm-4.4.1 
instead of systemvm-kvm-4.4?
I imagine it should just work, but would not rather take my chances at pulling 
another long night. :)

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nux!" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 21 October, 2014 21:12:28
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

> Well, hit a small issue:
> - added 4.4.0 systemvm - OK
> - upgraded management/db - OK
> - add 4.4.1 systemvm - FAIL - "Cannot use reserved names for templates"
> 
> So the names from the 4.4.0 and 4.4.1 systemvm names are identical and 
> conflict.
> I added the 4.4.1 systemvm as systemvm-kvm-4.4.1. Would this work?
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Nux!" 
>> To: dev@cloudstack.apache.org
>> Sent: Tuesday, 21 October, 2014 20:43:41
>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?
> 
>> Ok, cheers. I'll start shortly, fingers crossed. :)
>> 
>> --
>> Sent from the Delta quadrant using Borg technology!
>> 
>> Nux!
>> www.nux.ro
>> 
>> - Original Message -
>>> From: "Daan Hoogland" 
>>> To: "dev" 
>>> Sent: Tuesday, 21 October, 2014 20:39:50
>>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 
>>> 4.4.1?
>> 
>>> it most certainly does
>>> 
>>> On Tue, Oct 21, 2014 at 9:38 PM, Nux!  wrote:
 Right, so the steps would be:

 - install 4.4.0-6 systemvm
 - upgrade management/db
 - install 4.4.1 systemvm
 - do the manual db hotfix thing
 - finally restart the systemvms so they use the 4.4.1 template

 Does that cover it?

 --
 Sent from the Delta quadrant using Borg technology!

 Nux!
 www.nux.ro

 - Original Message -
> From: "Daan Hoogland" 
> To: "dev" 
> Sent: Tuesday, 21 October, 2014 20:35:51
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 
> 4.4.1?

> On Tue, Oct 21, 2014 at 9:32 PM, Nux!  wrote:
>> ual sys
>
>
> that would be once you install the 4.4.1 templates, yes. remind me
> often we need to upgrade the systemvm upgrade mechs
>
> --
> Daan
>>> 
>>> 
>>> 
>>> --
> > > Daan

RE: Help in Adding XenServer to CS Management Server

[Ritu Sabharwal]

Hi  Nitin,

I have picked the system vm template from 
http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/lastStableBuild/
 . This Build #132. 

My XenServer is 5.6 SP2 and CS Mgmt Server is built from master.

Please verify is this is the right combination.

Thanks & Regards,
Ritu S.


-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com] 
Sent: Tuesday, October 21, 2014 11:34 AM
To: dev@cloudstack.apache.org
Subject: Re: Help in Adding XenServer to CS Management Server

Make sure you are using the right systemvm.iso, for this version and for this 
hypervisor. You won't find scripts if scripts in sytemvm.iso havent been 
injected onto ssvm You can also login from Xencenter into ssvm and check logs 
as well.

On 21/10/14 10:03 AM, "Ritu Sabharwal"  wrote:

>Hi Rajani,
>
>The SSVM is up and I can see it green in XenCenter.
>
>The systemvm.iso is available in the XenServer host. Below is the 
>snapshot of it.
>
>[root@DCM-Xen-69 ~]# ls -al /opt/xensource/packages/iso/ total 160684
>drwxr-xr-x 2 root root 4096 Oct 15 10:49 .
>drwxr-xr-x 5 root root 4096 May 20  2011 ..
>-rw-r--r-- 1 root root 51802112 Oct 20 09:20 systemvm.iso
>-rw-r--r-- 1 root root 45643776 May  5  2011 XenCenter.iso
>-rw-r--r-- 1 root root 66908160 May 10  2011 xs-tools-5.6.100.iso
>
>The current value of secstorage.allowed.internal.sites is 0.0.0.0/0. 
>The CentOS template is not seeded offline i.e. from internal n/w. In 
>that case also, do I need to change the value of 
>secstorage.allowed.internal.sites?
>
>Thanks & Regards,
>Ritu S.
>-Original Message-
>From: Rajani Karuturi [mailto:raj...@apache.org]
>Sent: Monday, October 20, 2014 9:30 PM
>To: dev@cloudstack.apache.org
>Subject: Re: Help in Adding XenServer to CS Management Server
>
>Is the SSVM Agent UP? (check 9 and 10 in the wiki) Did you check 
>secstorage.allowed.internal.sites config value? (point 6 in the wiki)
>
>~Rajani
>
>On Tue, Oct 21, 2014 at 1:20 AM, Ritu Sabharwal 
>wrote:
>
>> Hi,
>>
>> I have been trying hard to get this up and running but have no luck 
>>so far.
>>
>> I have refereed to this troubleshooting guide for system vms:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+template
>> s
>> ,+Secondary+storage+troubleshooting
>>
>> The SSVM and CPVM are running but I don't see any health check script 
>> there and also I can't ssh from XenServer host to the SSVM. I get no 
>> route to host error.
>>
>> Please provide help in resolving these errors.
>>
>> Thanks & Regards,
>> Ritu S.
>>
>> -Original Message-
>> From: Ritu Sabharwal [mailto:rsabh...@brocade.com]
>> Sent: Friday, October 17, 2014 3:02 PM
>> To: dev@cloudstack.apache.org
>> Subject: RE: Help in Adding XenServer to CS Management Server
>>
>> Hi,
>>
>> I could move ahead with the issues and see the SSVM and CPVM coming up .
>> But when I  try to create a user VM I still don't see the default 
>>template.
>>
>> What could be the problem here? Any suggestions?
>>
>> Thanks & Regards,
>> Ritu S.
>>
>> -Original Message-
>> From: Pierre-Luc Dion [mailto:pdion...@apache.org]
>> Sent: Wednesday, October 15, 2014 7:52 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: Help in Adding XenServer to CS Management Server
>>
>> Ritu,
>>  You have to wait a little when creating a zone until you have the 
>> SSVM and CPVM ready. then it will automatically download a centos 5.6 
>> which confirm your initial zone is working. if  this is not 
>> happening, there might be a config issue related to primary, 
>> secondary storage or network label.
>>
>> hope this help,
>>
>> PL
>>
>>
>> On Wed, Oct 15, 2014 at 9:08 PM, Yitao Jiang 
>>wrote:
>>
>> > 1.Check zone status, make sure enabled.
>> > 2.change mgmt server debug level, watch ing the log file in 
>> > /var/log/cloud/ On Oct 16, 2014 7:13 AM, "Ritu Sabharwal" <
>> rsabh...@brocade.com> wrote:
>> >
>> > > Hi,
>> > >
>> > > I am trying to add XenServer to the CS Management Server.
>> > >
>> > > I could add the hosts and I see Host status as up on the GUI. But 
>> > > I don't see any System VMs coming up and Virtual Router coming up 
>> > > in the
>> > dashboard.
>> > > When I try to create a User VM there is no template available to
>> select.
>> > >
>> > > I am blocked at this point.
>> > >
>> > > I did seed Secondary Storage by importing system VM templat from
>> > > 
>>http://secure-web.cisco.com/1gUYzrTMP4_zt6B7yu1eZm6uBqfffITqyVeBGbnHBI
>>-0W 
>>51IPO478b_yzMFXjTTcV15QCBCQnmZjqkRmiKzqbu3N90krlwtq1PCEBOg_XGxtGFpbQZs
>>ZdC 
>>c8XLiDDwFq4Ov4RD1naqhDxLv0HXM7LqyMU7JnQlVx1xaiwb8z_m-E/http%3A%2F%2Fje
>>nki ns.buildacloud.org%2Fview%2F4.4%2Fjob%2Fcloudstack-4.4-systemv
>> > > m6 4/ for Xen (systemvm64template-4.4-2014-09-30-xen.vhd.bz2<
>> > >
>> > 
>>http://secure-web.cisco.com/16OFpcrv9LcUzeznlMuXnFxkgvkcDd81s4oz4P5Vo3
>>i8_ 
>>GA3m_OvSDO5KgPom5CEcuPM3FEKi0oqEWqfu70dU4Mp-CL_WYUvuU66MqRZVqGt6mNT7Kh
>>mWU 
>>WkvDAGQl31uLHdXUKD-zonVFZjKRIe5zsuqz7KqnAYqgf9BmfMKj2Q/http%3A%2F%2Fje
>>nk

Re: Help in Adding XenServer to CS Management Server

[Nitin Mehta]

I am talking about systemvm.iso and not the systemvm template
Systemvm.iso contains all our systemvm (ssvm, cpvm, routervm)  agent
code(java + some scripts) that gets patched onto the systemvms once they
are deployed.


Did you build your systemvm.iso recently [1] (mvn clean install -P
developer,systemvm)? I highly doubt that it is stale copy.
Once you build it make sure to propagate to XS using [2]



[1] - 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudSt
ack



On 21/10/14 1:37 PM, "Ritu Sabharwal"  wrote:

>Hi  Nitin,
>
>I have picked the system vm template from
>http://secure-web.cisco.com/1p_apfJrUd4xtpNMybTlJT2rF1GVAA_ArTgZgpoLLM7iz_
>v_dk65i2eNK12F0Hue3YL5mlJVoVAHNjbKmY_1TPUYUClbuqglIw-MV8Tb-TmketxXTmakYdFc
>SJYL5ba6JS-m9QkG81DIklmXeMCyvSrZlWcQQiHeCsQDZKs-wE70/http%3A%2F%2Fjenkins.
>buildacloud.org%2Fview%2F4.4%2Fjob%2Fcloudstack-4.4-systemvm64%2FlastStabl
>eBuild%2F . This Build #132.
>
>My XenServer is 5.6 SP2 and CS Mgmt Server is built from master.
>
>Please verify is this is the right combination.
>
>Thanks & Regards,
>Ritu S.
>
>
>-Original Message-
>From: Nitin Mehta [mailto:nitin.me...@citrix.com]
>Sent: Tuesday, October 21, 2014 11:34 AM
>To: dev@cloudstack.apache.org
>Subject: Re: Help in Adding XenServer to CS Management Server
>
>Make sure you are using the right systemvm.iso, for this version and for
>this hypervisor. You won't find scripts if scripts in sytemvm.iso havent
>been injected onto ssvm You can also login from Xencenter into ssvm and
>check logs as well.
>
>On 21/10/14 10:03 AM, "Ritu Sabharwal"  wrote:
>
>>Hi Rajani,
>>
>>The SSVM is up and I can see it green in XenCenter.
>>
>>The systemvm.iso is available in the XenServer host. Below is the
>>snapshot of it.
>>
>>[root@DCM-Xen-69 ~]# ls -al /opt/xensource/packages/iso/ total 160684
>>drwxr-xr-x 2 root root 4096 Oct 15 10:49 .
>>drwxr-xr-x 5 root root 4096 May 20  2011 ..
>>-rw-r--r-- 1 root root 51802112 Oct 20 09:20 systemvm.iso
>>-rw-r--r-- 1 root root 45643776 May  5  2011 XenCenter.iso
>>-rw-r--r-- 1 root root 66908160 May 10  2011 xs-tools-5.6.100.iso
>>
>>The current value of secstorage.allowed.internal.sites is 0.0.0.0/0.
>>The CentOS template is not seeded offline i.e. from internal n/w. In
>>that case also, do I need to change the value of
>>secstorage.allowed.internal.sites?
>>
>>Thanks & Regards,
>>Ritu S.
>>-Original Message-
>>From: Rajani Karuturi [mailto:raj...@apache.org]
>>Sent: Monday, October 20, 2014 9:30 PM
>>To: dev@cloudstack.apache.org
>>Subject: Re: Help in Adding XenServer to CS Management Server
>>
>>Is the SSVM Agent UP? (check 9 and 10 in the wiki) Did you check
>>secstorage.allowed.internal.sites config value? (point 6 in the wiki)
>>
>>~Rajani
>>
>>On Tue, Oct 21, 2014 at 1:20 AM, Ritu Sabharwal 
>>wrote:
>>
>>> Hi,
>>>
>>> I have been trying hard to get this up and running but have no luck
>>>so far.
>>>
>>> I have refereed to this troubleshooting guide for system vms:
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+template
>>> s
>>> ,+Secondary+storage+troubleshooting
>>>
>>> The SSVM and CPVM are running but I don't see any health check script
>>> there and also I can't ssh from XenServer host to the SSVM. I get no
>>> route to host error.
>>>
>>> Please provide help in resolving these errors.
>>>
>>> Thanks & Regards,
>>> Ritu S.
>>>
>>> -Original Message-
>>> From: Ritu Sabharwal [mailto:rsabh...@brocade.com]
>>> Sent: Friday, October 17, 2014 3:02 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: RE: Help in Adding XenServer to CS Management Server
>>>
>>> Hi,
>>>
>>> I could move ahead with the issues and see the SSVM and CPVM coming up
>>>.
>>> But when I  try to create a user VM I still don't see the default
>>>template.
>>>
>>> What could be the problem here? Any suggestions?
>>>
>>> Thanks & Regards,
>>> Ritu S.
>>>
>>> -Original Message-
>>> From: Pierre-Luc Dion [mailto:pdion...@apache.org]
>>> Sent: Wednesday, October 15, 2014 7:52 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: Re: Help in Adding XenServer to CS Management Server
>>>
>>> Ritu,
>>>  You have to wait a little when creating a zone until you have the
>>> SSVM and CPVM ready. then it will automatically download a centos 5.6
>>> which confirm your initial zone is working. if  this is not
>>> happening, there might be a config issue related to primary,
>>> secondary storage or network label.
>>>
>>> hope this help,
>>>
>>> PL
>>>
>>>
>>> On Wed, Oct 15, 2014 at 9:08 PM, Yitao Jiang 
>>>wrote:
>>>
>>> > 1.Check zone status, make sure enabled.
>>> > 2.change mgmt server debug level, watch ing the log file in
>>> > /var/log/cloud/ On Oct 16, 2014 7:13 AM, "Ritu Sabharwal" <
>>> rsabh...@brocade.com> wrote:
>>> >
>>> > > Hi,
>>> > >
>>> > > I am trying to add XenServer to the CS Management Server.
>>> > >
>>> > > I could add the hosts and I see Host status as up on the GUI. But
>>> > > I don't see any System VMs coming up and Virtual R

Re: Help in Adding XenServer to CS Management Server

[Nitin Mehta]

Sorry got sent accidentally

[2] - https://cwiki.apache.org/confluence/display/CLOUDSTACK/SystemVm.iso

On 21/10/14 1:45 PM, "Nitin Mehta"  wrote:

>I am talking about systemvm.iso and not the systemvm template
>Systemvm.iso contains all our systemvm (ssvm, cpvm, routervm)  agent
>code(java + some scripts) that gets patched onto the systemvms once they
>are deployed.
>
>
>Did you build your systemvm.iso recently [1] (mvn clean install -P
>developer,systemvm)? I highly doubt that it is stale copy.
>Once you build it make sure to propagate systemvm.iso to XS using [2]
>
>
>
>[1] - 
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudS
>t
>ack
>
>
>
>On 21/10/14 1:37 PM, "Ritu Sabharwal"  wrote:
>
>>Hi  Nitin,
>>
>>I have picked the system vm template from
>>http://secure-web.cisco.com/1p_apfJrUd4xtpNMybTlJT2rF1GVAA_ArTgZgpoLLM7iz
>>_
>>v_dk65i2eNK12F0Hue3YL5mlJVoVAHNjbKmY_1TPUYUClbuqglIw-MV8Tb-TmketxXTmakYdF
>>c
>>SJYL5ba6JS-m9QkG81DIklmXeMCyvSrZlWcQQiHeCsQDZKs-wE70/http%3A%2F%2Fjenkins
>>.
>>buildacloud.org%2Fview%2F4.4%2Fjob%2Fcloudstack-4.4-systemvm64%2FlastStab
>>l
>>eBuild%2F . This Build #132.
>>
>>My XenServer is 5.6 SP2 and CS Mgmt Server is built from master.
>>
>>Please verify is this is the right combination.
>>
>>Thanks & Regards,
>>Ritu S.
>>
>>
>>-Original Message-
>>From: Nitin Mehta [mailto:nitin.me...@citrix.com]
>>Sent: Tuesday, October 21, 2014 11:34 AM
>>To: dev@cloudstack.apache.org
>>Subject: Re: Help in Adding XenServer to CS Management Server
>>
>>Make sure you are using the right systemvm.iso, for this version and for
>>this hypervisor. You won't find scripts if scripts in sytemvm.iso havent
>>been injected onto ssvm You can also login from Xencenter into ssvm and
>>check logs as well.
>>
>>On 21/10/14 10:03 AM, "Ritu Sabharwal"  wrote:
>>
>>>Hi Rajani,
>>>
>>>The SSVM is up and I can see it green in XenCenter.
>>>
>>>The systemvm.iso is available in the XenServer host. Below is the
>>>snapshot of it.
>>>
>>>[root@DCM-Xen-69 ~]# ls -al /opt/xensource/packages/iso/ total 160684
>>>drwxr-xr-x 2 root root 4096 Oct 15 10:49 .
>>>drwxr-xr-x 5 root root 4096 May 20  2011 ..
>>>-rw-r--r-- 1 root root 51802112 Oct 20 09:20 systemvm.iso
>>>-rw-r--r-- 1 root root 45643776 May  5  2011 XenCenter.iso
>>>-rw-r--r-- 1 root root 66908160 May 10  2011 xs-tools-5.6.100.iso
>>>
>>>The current value of secstorage.allowed.internal.sites is 0.0.0.0/0.
>>>The CentOS template is not seeded offline i.e. from internal n/w. In
>>>that case also, do I need to change the value of
>>>secstorage.allowed.internal.sites?
>>>
>>>Thanks & Regards,
>>>Ritu S.
>>>-Original Message-
>>>From: Rajani Karuturi [mailto:raj...@apache.org]
>>>Sent: Monday, October 20, 2014 9:30 PM
>>>To: dev@cloudstack.apache.org
>>>Subject: Re: Help in Adding XenServer to CS Management Server
>>>
>>>Is the SSVM Agent UP? (check 9 and 10 in the wiki) Did you check
>>>secstorage.allowed.internal.sites config value? (point 6 in the wiki)
>>>
>>>~Rajani
>>>
>>>On Tue, Oct 21, 2014 at 1:20 AM, Ritu Sabharwal 
>>>wrote:
>>>
 Hi,

 I have been trying hard to get this up and running but have no luck
so far.

 I have refereed to this troubleshooting guide for system vms:
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+template
 s
 ,+Secondary+storage+troubleshooting

 The SSVM and CPVM are running but I don't see any health check script
 there and also I can't ssh from XenServer host to the SSVM. I get no
 route to host error.

 Please provide help in resolving these errors.

 Thanks & Regards,
 Ritu S.

 -Original Message-
 From: Ritu Sabharwal [mailto:rsabh...@brocade.com]
 Sent: Friday, October 17, 2014 3:02 PM
 To: dev@cloudstack.apache.org
 Subject: RE: Help in Adding XenServer to CS Management Server

 Hi,

 I could move ahead with the issues and see the SSVM and CPVM coming up
.
 But when I  try to create a user VM I still don't see the default
template.

 What could be the problem here? Any suggestions?

 Thanks & Regards,
 Ritu S.

 -Original Message-
 From: Pierre-Luc Dion [mailto:pdion...@apache.org]
 Sent: Wednesday, October 15, 2014 7:52 PM
 To: dev@cloudstack.apache.org
 Subject: Re: Help in Adding XenServer to CS Management Server

 Ritu,
  You have to wait a little when creating a zone until you have the
 SSVM and CPVM ready. then it will automatically download a centos 5.6
 which confirm your initial zone is working. if  this is not
 happening, there might be a config issue related to primary,
 secondary storage or network label.

 hope this help,

 PL


 On Wed, Oct 15, 2014 at 9:08 PM, Yitao Jiang 
wrote:

 > 1.Check zone status, make sure enabled.
 > 2.change mgmt server debug level, watch ing the log file in
 > /var

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

Well, that didn't go so well. Trying to "hotfix" the 4.4.1 systemvm resulted in 
successfull SSVM and CP VMs to be restarted, however the VR upgrade went bad: 
http://pastebin.com/raw.php?i=SB3tYHZc

I'll try to downgrade to the 4.4.0 Sys VM and see if that will work.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nux!" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 21 October, 2014 21:25:41
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

> So what I see has happened is as a result of the DB upgrade from 4.3.1 to 
> 4.4.1
> the systemvm-kvm-4.4 (4.4.0-6) has been marked of type System, it's not
> deletable now.
> Also its ID in the DB is now present as the template to use for ConsoleProxy,
> SSVM and VR.
> It's as if the hotfix was performed, although I have most certainly not.
> 
> Can I just go ahead and perform the hotfix manually, but for 
> systemvm-kvm-4.4.1
> instead of systemvm-kvm-4.4?
> I imagine it should just work, but would not rather take my chances at pulling
> another long night. :)
> 
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Nux!" 
>> To: dev@cloudstack.apache.org
>> Sent: Tuesday, 21 October, 2014 21:12:28
>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?
> 
>> Well, hit a small issue:
>> - added 4.4.0 systemvm - OK
>> - upgraded management/db - OK
>> - add 4.4.1 systemvm - FAIL - "Cannot use reserved names for templates"
>> 
>> So the names from the 4.4.0 and 4.4.1 systemvm names are identical and 
>> conflict.
>> I added the 4.4.1 systemvm as systemvm-kvm-4.4.1. Would this work?
>> 
>> --
>> Sent from the Delta quadrant using Borg technology!
>> 
>> Nux!
>> www.nux.ro
>> 
>> - Original Message -
>>> From: "Nux!" 
>>> To: dev@cloudstack.apache.org
>>> Sent: Tuesday, 21 October, 2014 20:43:41
>>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 
>>> 4.4.1?
>> 
>>> Ok, cheers. I'll start shortly, fingers crossed. :)
>>> 
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>> 
>>> Nux!
>>> www.nux.ro
>>> 
>>> - Original Message -
 From: "Daan Hoogland" 
 To: "dev" 
 Sent: Tuesday, 21 October, 2014 20:39:50
 Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 
 4.4.1?
>>> 
 it most certainly does
 
 On Tue, Oct 21, 2014 at 9:38 PM, Nux!  wrote:
> Right, so the steps would be:
>
> - install 4.4.0-6 systemvm
> - upgrade management/db
> - install 4.4.1 systemvm
> - do the manual db hotfix thing
> - finally restart the systemvms so they use the 4.4.1 template
>
> Does that cover it?
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
>> From: "Daan Hoogland" 
>> To: "dev" 
>> Sent: Tuesday, 21 October, 2014 20:35:51
>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 
>> 4.4.1?
>
>> On Tue, Oct 21, 2014 at 9:32 PM, Nux!  wrote:
>>> ual sys
>>
>>
>> that would be once you install the 4.4.1 templates, yes. remind me
>> often we need to upgrade the systemvm upgrade mechs
>>
>> --
>> Daan
 
 
 
 --
> > > > Daan

RE: Certificate expired

[Frank Zhang]

I met the error too.
It's caused by file ./server/test/resources/certs/rsa_self_signed.crt which is 
expired today.
I thought we need to replace it with a new one

commit 0076307863e9155273d9e4c14282de429388c9e9
Author: Syed 
Date:   Wed Nov 6 15:08:42 2013 -0500

Squashed merge of Ssl Termination feature

Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-4821
FS: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSL+Termination+Support

This patch implements the SSL offload feature for loadbalancers
and includes the implementaion for this to work with Netscaler.

The following are the new API's that this patch adds

uploadSslCert
deleteSslCert
listSslCert
assignCertToLoadBalancer
removeCertFromLoadBalancer

Unit tests are also included in the patch.

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Tuesday, October 21, 2014 1:09 PM
> To: dev@cloudstack.apache.org
> Subject: Certificate expired
> 
> Hi,
> 
> I just started getting this test-run error message on two of my CloudStack dev
> boxes today (below).
> 
> I don't recall sign-signing a certificate, but perhaps I just forgot.
> 
> Can someone give me the context around this error?
> 
> Thanks!
> 
> Results :
> 
> 
> ---
> 
> Test set: org.apache.cloudstack.network.lb.CertServiceTest
> 
> ---
> 
> Tests run: 15, Failures: 2, Errors: 2, Skipped: 4, Time elapsed: 0.538 sec <<<
> FAILURE!
> 
> runUploadSslCertBadkeyAlgo(org.apache.cloudstack.network.lb.CertServiceTest)
>  Time elapsed: 0.128 sec  <<< FAILURE!
> 
> java.lang.AssertionError
> 
> at org.junit.Assert.fail(Assert.java:86)
> 
> at org.junit.Assert.assertTrue(Assert.java:41)
> 
> at org.junit.Assert.assertTrue(Assert.java:52)
> 
> at
> org.apache.cloudstack.network.lb.CertServiceTest.runUploadSslCertBadkeyAlgo
> (CertServiceTest.java:539)
> 
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 57)
> 
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> mpl.java:43)
> 
> at java.lang.reflect.Method.invoke(Method.java:606)
> 
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMe
> thod.java:47)
> 
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:
> 12)
> 
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMeth
> od.java:44)
> 
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.jav
> a:17)
> 
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> 
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> 
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> 
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java
> :70)
> 
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java
> :50)
> 
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> 
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> 
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> 
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> 
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> 
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> 
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:2
> 36)
> 
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider
> .java:134)
> 
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:11
> 3)
> 
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 57)
> 
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> mpl.java:43)
> 
> at java.lang.reflect.Method.invoke(Method.java:606)
> 
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(Reflecti
> onUtils.java:189)
> 
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(Provi
> derFactory.java:165)
> 
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFact
> ory.java:85)
> 
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBoot
> er.java:103)
> 
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> 
> runUploadSslCertBadkeyPair(org.apache.cloudstack.network.lb.CertServiceTest)
>  Time elapsed: 0.01 sec  <<< FAILURE!
> 
> java.lang.AssertionError
> 
> at org.junit.Assert.fail(Assert.java:86)
> 
> at org.junit.Assert.assertTrue(Assert.java:41)
> 
> at org.junit.Assert.

Re: Certificate expired

[Mike Tutkowski]

Interesting...I just updated master and tried to re-build, but that test
failed again.

On Tue, Oct 21, 2014 at 4:12 PM, Frank Zhang  wrote:

> I met the error too.
> It's caused by file ./server/test/resources/certs/rsa_self_signed.crt
> which is expired today.
> I thought we need to replace it with a new one
>
> commit 0076307863e9155273d9e4c14282de429388c9e9
> Author: Syed 
> Date:   Wed Nov 6 15:08:42 2013 -0500
>
> Squashed merge of Ssl Termination feature
>
> Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-4821
> FS:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSL+Termination+Support
>
> This patch implements the SSL offload feature for loadbalancers
> and includes the implementaion for this to work with Netscaler.
>
> The following are the new API's that this patch adds
>
> uploadSslCert
> deleteSslCert
> listSslCert
> assignCertToLoadBalancer
> removeCertFromLoadBalancer
>
> Unit tests are also included in the patch.
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Tuesday, October 21, 2014 1:09 PM
> > To: dev@cloudstack.apache.org
> > Subject: Certificate expired
> >
> > Hi,
> >
> > I just started getting this test-run error message on two of my
> CloudStack dev
> > boxes today (below).
> >
> > I don't recall sign-signing a certificate, but perhaps I just forgot.
> >
> > Can someone give me the context around this error?
> >
> > Thanks!
> >
> > Results :
> >
> >
> >
> ---
> >
> > Test set: org.apache.cloudstack.network.lb.CertServiceTest
> >
> >
> ---
> >
> > Tests run: 15, Failures: 2, Errors: 2, Skipped: 4, Time elapsed: 0.538
> sec <<<
> > FAILURE!
> >
> >
> runUploadSslCertBadkeyAlgo(org.apache.cloudstack.network.lb.CertServiceTest)
> >  Time elapsed: 0.128 sec  <<< FAILURE!
> >
> > java.lang.AssertionError
> >
> > at org.junit.Assert.fail(Assert.java:86)
> >
> > at org.junit.Assert.assertTrue(Assert.java:41)
> >
> > at org.junit.Assert.assertTrue(Assert.java:52)
> >
> > at
> >
> org.apache.cloudstack.network.lb.CertServiceTest.runUploadSslCertBadkeyAlgo
> > (CertServiceTest.java:539)
> >
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > 57)
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> > mpl.java:43)
> >
> > at java.lang.reflect.Method.invoke(Method.java:606)
> >
> > at
> > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMe
> > thod.java:47)
> >
> > at
> >
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:
> > 12)
> >
> > at
> > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMeth
> > od.java:44)
> >
> > at
> >
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.jav
> > a:17)
> >
> > at
> >
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> >
> > at
> >
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> >
> > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> >
> > at
> >
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java
> > :70)
> >
> > at
> >
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java
> > :50)
> >
> > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> >
> > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> >
> > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> >
> > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> >
> > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> >
> > at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> >
> > at
> >
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:2
> > 36)
> >
> > at
> >
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider
> > .java:134)
> >
> > at
> >
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:11
> > 3)
> >
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > 57)
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> > mpl.java:43)
> >
> > at java.lang.reflect.Method.invoke(Method.java:606)
> >
> > at
> >
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(Reflecti
> > onUtils.java:189)
> >
> > at
> >
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(Provi
> > derFactory.java:165)
> >
> > at
> >
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFact
> > ory.java:85)
> >
> > at
> >
> org.apac

RE: Certificate expired

[Frank Zhang]

What did you update? You replace the file with you manually built certificate?

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Tuesday, October 21, 2014 3:16 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Certificate expired
> 
> Interesting...I just updated master and tried to re-build, but that test 
> failed
> again.
> 
> On Tue, Oct 21, 2014 at 4:12 PM, Frank Zhang 
> wrote:
> 
> > I met the error too.
> > It's caused by file ./server/test/resources/certs/rsa_self_signed.crt
> > which is expired today.
> > I thought we need to replace it with a new one
> >
> > commit 0076307863e9155273d9e4c14282de429388c9e9
> > Author: Syed 
> > Date:   Wed Nov 6 15:08:42 2013 -0500
> >
> > Squashed merge of Ssl Termination feature
> >
> > Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-4821
> > FS:
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSL+Termination
> > +Support
> >
> > This patch implements the SSL offload feature for loadbalancers
> > and includes the implementaion for this to work with Netscaler.
> >
> > The following are the new API's that this patch adds
> >
> > uploadSslCert
> > deleteSslCert
> > listSslCert
> > assignCertToLoadBalancer
> > removeCertFromLoadBalancer
> >
> > Unit tests are also included in the patch.
> >
> > > -Original Message-
> > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > Sent: Tuesday, October 21, 2014 1:09 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Certificate expired
> > >
> > > Hi,
> > >
> > > I just started getting this test-run error message on two of my
> > CloudStack dev
> > > boxes today (below).
> > >
> > > I don't recall sign-signing a certificate, but perhaps I just forgot.
> > >
> > > Can someone give me the context around this error?
> > >
> > > Thanks!
> > >
> > > Results :
> > >
> > >
> > >
> > --
> > -
> > >
> > > Test set: org.apache.cloudstack.network.lb.CertServiceTest
> > >
> > >
> > --
> > -
> > >
> > > Tests run: 15, Failures: 2, Errors: 2, Skipped: 4, Time elapsed:
> > > 0.538
> > sec <<<
> > > FAILURE!
> > >
> > >
> > runUploadSslCertBadkeyAlgo(org.apache.cloudstack.network.lb.CertServic
> > eTest)
> > >  Time elapsed: 0.128 sec  <<< FAILURE!
> > >
> > > java.lang.AssertionError
> > >
> > > at org.junit.Assert.fail(Assert.java:86)
> > >
> > > at org.junit.Assert.assertTrue(Assert.java:41)
> > >
> > > at org.junit.Assert.assertTrue(Assert.java:52)
> > >
> > > at
> > >
> > org.apache.cloudstack.network.lb.CertServiceTest.runUploadSslCertBadke
> > yAlgo
> > > (CertServiceTest.java:539)
> > >
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >
> > > at
> > >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > > 57)
> > >
> > > at
> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce
> > > ssorI
> > > mpl.java:43)
> > >
> > > at java.lang.reflect.Method.invoke(Method.java:606)
> > >
> > > at
> > > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(Framewor
> > > kMe
> > > thod.java:47)
> > >
> > > at
> > >
> >
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:
> > > 12)
> > >
> > > at
> > > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkM
> > > eth
> > > od.java:44)
> > >
> > > at
> > >
> > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMeth
> > od.jav
> > > a:17)
> > >
> > > at
> > >
> > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.j
> > ava:26)
> > >
> > > at
> > >
> > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.jav
> > a:27)
> > >
> > > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> > >
> > > at
> > >
> > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunn
> > er.java
> > > :70)
> > >
> > > at
> > >
> > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunn
> > er.java
> > > :50)
> > >
> > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> > >
> > > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> > >
> > > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> > >
> > > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> > >
> > > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> > >
> > > at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> > >
> > > at
> > >
> > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider
> > .java:2
> > > 36)
> > >
> > > at
> > >
> > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4P
> > rovider
> > > .java:134)
> > >
> > > at
> > >
> > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.
> > java:11
> > > 3)
> > >

Re: Certificate expired

[Mike Tutkowski]

No, sorry...I didn't clarify. I thought you were saying this was all fixed
in code, so I updated and tried to re-build the codebase:

mvn -P developer,systemvm clean install

But it failed on the same test.

On Tue, Oct 21, 2014 at 4:17 PM, Frank Zhang  wrote:

> What did you update? You replace the file with you manually built
> certificate?
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Tuesday, October 21, 2014 3:16 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: Certificate expired
> >
> > Interesting...I just updated master and tried to re-build, but that test
> failed
> > again.
> >
> > On Tue, Oct 21, 2014 at 4:12 PM, Frank Zhang 
> > wrote:
> >
> > > I met the error too.
> > > It's caused by file ./server/test/resources/certs/rsa_self_signed.crt
> > > which is expired today.
> > > I thought we need to replace it with a new one
> > >
> > > commit 0076307863e9155273d9e4c14282de429388c9e9
> > > Author: Syed 
> > > Date:   Wed Nov 6 15:08:42 2013 -0500
> > >
> > > Squashed merge of Ssl Termination feature
> > >
> > > Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-4821
> > > FS:
> > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSL+Termination
> > > +Support
> > >
> > > This patch implements the SSL offload feature for loadbalancers
> > > and includes the implementaion for this to work with Netscaler.
> > >
> > > The following are the new API's that this patch adds
> > >
> > > uploadSslCert
> > > deleteSslCert
> > > listSslCert
> > > assignCertToLoadBalancer
> > > removeCertFromLoadBalancer
> > >
> > > Unit tests are also included in the patch.
> > >
> > > > -Original Message-
> > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > Sent: Tuesday, October 21, 2014 1:09 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: Certificate expired
> > > >
> > > > Hi,
> > > >
> > > > I just started getting this test-run error message on two of my
> > > CloudStack dev
> > > > boxes today (below).
> > > >
> > > > I don't recall sign-signing a certificate, but perhaps I just forgot.
> > > >
> > > > Can someone give me the context around this error?
> > > >
> > > > Thanks!
> > > >
> > > > Results :
> > > >
> > > >
> > > >
> > > --
> > > -
> > > >
> > > > Test set: org.apache.cloudstack.network.lb.CertServiceTest
> > > >
> > > >
> > > --
> > > -
> > > >
> > > > Tests run: 15, Failures: 2, Errors: 2, Skipped: 4, Time elapsed:
> > > > 0.538
> > > sec <<<
> > > > FAILURE!
> > > >
> > > >
> > > runUploadSslCertBadkeyAlgo(org.apache.cloudstack.network.lb.CertServic
> > > eTest)
> > > >  Time elapsed: 0.128 sec  <<< FAILURE!
> > > >
> > > > java.lang.AssertionError
> > > >
> > > > at org.junit.Assert.fail(Assert.java:86)
> > > >
> > > > at org.junit.Assert.assertTrue(Assert.java:41)
> > > >
> > > > at org.junit.Assert.assertTrue(Assert.java:52)
> > > >
> > > > at
> > > >
> > > org.apache.cloudstack.network.lb.CertServiceTest.runUploadSslCertBadke
> > > yAlgo
> > > > (CertServiceTest.java:539)
> > > >
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > >
> > > > at
> > > >
> > >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > > > 57)
> > > >
> > > > at
> > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce
> > > > ssorI
> > > > mpl.java:43)
> > > >
> > > > at java.lang.reflect.Method.invoke(Method.java:606)
> > > >
> > > > at
> > > > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(Framewor
> > > > kMe
> > > > thod.java:47)
> > > >
> > > > at
> > > >
> > >
> >
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:
> > > > 12)
> > > >
> > > > at
> > > > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkM
> > > > eth
> > > > od.java:44)
> > > >
> > > > at
> > > >
> > > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMeth
> > > od.jav
> > > > a:17)
> > > >
> > > > at
> > > >
> > > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.j
> > > ava:26)
> > > >
> > > > at
> > > >
> > > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.jav
> > > a:27)
> > > >
> > > > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> > > >
> > > > at
> > > >
> > > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunn
> > > er.java
> > > > :70)
> > > >
> > > > at
> > > >
> > > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunn
> > > er.java
> > > > :50)
> > > >
> > > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> > > >
> > > > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> > > >
> > > > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> > > 

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Pierre-Luc Dion]

Hi. Sorry to see this thread late. Upgrading from 4.3.1 to 4.4.1 only
require one systemvm template. (The one with -7).

Refer to 4.4.1 release notes , it should point to proper urls for sysvm
too.


Le mardi 21 octobre 2014, Nux!  a écrit :

> Well, that didn't go so well. Trying to "hotfix" the 4.4.1 systemvm
> resulted in successfull SSVM and CP VMs to be restarted, however the VR
> upgrade went bad: http://pastebin.com/raw.php?i=SB3tYHZc
>
> I'll try to downgrade to the 4.4.0 Sys VM and see if that will work.
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Nux!" >
> > To: dev@cloudstack.apache.org 
> > Sent: Tuesday, 21 October, 2014 21:25:41
> > Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x -
> 4.4.1?
>
> > So what I see has happened is as a result of the DB upgrade from 4.3.1
> to 4.4.1
> > the systemvm-kvm-4.4 (4.4.0-6) has been marked of type System, it's not
> > deletable now.
> > Also its ID in the DB is now present as the template to use for
> ConsoleProxy,
> > SSVM and VR.
> > It's as if the hotfix was performed, although I have most certainly not.
> >
> > Can I just go ahead and perform the hotfix manually, but for
> systemvm-kvm-4.4.1
> > instead of systemvm-kvm-4.4?
> > I imagine it should just work, but would not rather take my chances at
> pulling
> > another long night. :)
> >
> > Lucian
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> >> From: "Nux!" >
> >> To: dev@cloudstack.apache.org 
> >> Sent: Tuesday, 21 October, 2014 21:12:28
> >> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x -
> 4.4.1?
> >
> >> Well, hit a small issue:
> >> - added 4.4.0 systemvm - OK
> >> - upgraded management/db - OK
> >> - add 4.4.1 systemvm - FAIL - "Cannot use reserved names for templates"
> >>
> >> So the names from the 4.4.0 and 4.4.1 systemvm names are identical and
> conflict.
> >> I added the 4.4.1 systemvm as systemvm-kvm-4.4.1. Would this work?
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> - Original Message -
> >>> From: "Nux!" >
> >>> To: dev@cloudstack.apache.org 
> >>> Sent: Tuesday, 21 October, 2014 20:43:41
> >>> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x -
> 4.4.1?
> >>
> >>> Ok, cheers. I'll start shortly, fingers crossed. :)
> >>>
> >>> --
> >>> Sent from the Delta quadrant using Borg technology!
> >>>
> >>> Nux!
> >>> www.nux.ro
> >>>
> >>> - Original Message -
>  From: "Daan Hoogland" >
>  To: "dev" >
>  Sent: Tuesday, 21 October, 2014 20:39:50
>  Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x
> - 4.4.1?
> >>>
>  it most certainly does
> 
>  On Tue, Oct 21, 2014 at 9:38 PM, Nux! >
> wrote:
> > Right, so the steps would be:
> >
> > - install 4.4.0-6 systemvm
> > - upgrade management/db
> > - install 4.4.1 systemvm
> > - do the manual db hotfix thing
> > - finally restart the systemvms so they use the 4.4.1 template
> >
> > Does that cover it?
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> >> From: "Daan Hoogland" >
> >> To: "dev" >
> >> Sent: Tuesday, 21 October, 2014 20:35:51
> >> Subject: Re: Is the 4.4.0 template still necessary for upgrade
> 4.3.x - 4.4.1?
> >
> >> On Tue, Oct 21, 2014 at 9:32 PM, Nux! >
> wrote:
> >>> ual sys
> >>
> >>
> >> that would be once you install the 4.4.1 templates, yes. remind me
> >> often we need to upgrade the systemvm upgrade mechs
> >>
> >> --
> >> Daan
> 
> 
> 
>  --
> > > > > Daan
>


-- 

*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

*CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

Review Request 27000: CLOUDSTACK-7762 -[Automation] - Fix test failure for test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py

[sangeetha hariharan]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27000/
---

Review request for cloudstack, anthony xu and Chandan Purushothama.


Bugs: CLOUDSTACK-7762
https://issues.apache.org/jira/browse/CLOUDSTACK-7762


Repository: cloudstack-git


Description
---

test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py fails in BVT runs 
with the following exception:

2014-10-20 16:41:00,497 INFO [o.a.c.f.j.i.AsyncJobMonitor] 
(API-Job-Executor-120:ctx-83b738d9 job-459) Add job-459 into job monitoring
2014-10-20 16:41:00,497 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-120:ctx-83b738d9 job-459) Executing AsyncJobVO {id:459, 
userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd: 
org.apache.cloudstack.api.command.admin.vmsnapshot.RevertToVMSnapshotCmdByAdmin,
 cmdInfo: {"response":"json","ctxDetails":"
{\"com.cloud.vm.snapshot.VMSnapshot\":\"12280973-a1e4-43e3-80b3-3afacd607909\"}

","cmdEventType":"VMSNAPSHOT.REVERTTO","ctxUserId":"2","httpmethod":"GET","vmsnapshotid":"12280973-a1e4-43e3-80b3-3afacd607909","ctxAccountId":"2","ctxStartEventId":"1406","apiKey":"aJwkScf5ziRwz8gKQ9HB0Ce6hSsTJTUtmUDUQ_U2teV3vVmuLQRLad8xqAgr7CrFOEQbywdVpKSt2yC_ORXLYg","signature":"cYBxgg8eBfktovmCaHYox2xoTE8\u003d"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 11489258594360, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2014-10-20 16:41:00,529 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-120:ctx-83b738d9 job-459) Unexpected exception while 
executing 
org.apache.cloudstack.api.command.admin.vmsnapshot.RevertToVMSnapshotCmdByAdmin
com.cloud.exception.InvalidParameterValueException: VM Snapshot revert not 
allowed. This will result in VM state change. You can revert running VM to disk 
and memory type snapshot and stopped VM to disk type snapshot
at 
com.cloud.vm.snapshot.VMSnapshotManagerImpl.revertToSnapshot(VMSnapshotManagerImpl.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)

Root Cause :
reverting Snapshots is allowed only when there is no vm state change associated 
with it.
Following are the 2 scenarios allowed: 
1.Revert a "Running" VM to a "Disk and Memory" Snapshot ( with and without 
"quiesce" option).
2.Revert a "Stopped" VM to a "Disk " Snapshot ( with and without "quiesce" 
option).

In this test case , we are testing reverting to a Disk " Snapshot. Introduced a 
Vm stop before performing the revert operation.


Diffs
-

  test/integration/smoke/test_vm_snapshots.py 131da99 

Diff: https://reviews.apache.org/r/27000/diff/


Testing
---

Tested with advanced zone set up with Xenserver hosts:

Test to create VM snapshots ... === TestName: test_01_create_vm_snapshots | 
Status : SUCCESS ===
ok
Test to revert VM snapshots ... === TestName: test_02_revert_vm_snapshots | 
Status : SUCCESS ===
ok
Test to delete vm snapshots ... === TestName: test_03_delete_vm_snapshots | 
Status : SUCCESS ===
ok

--
Ran 3 tests in 795.005s

OK


Thanks,

sangeetha hariharan

RE: Certificate expired

[Frank Zhang]

I made a new certificate, but there are lots of unit cases using different CAs; 
some of them use correct file; some of them use incorrect file.
It takes time to understand what files need to be updated.

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Tuesday, October 21, 2014 3:20 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Certificate expired
> 
> No, sorry...I didn't clarify. I thought you were saying this was all fixed in 
> code,
> so I updated and tried to re-build the codebase:
> 
> mvn -P developer,systemvm clean install
> 
> But it failed on the same test.
> 
> On Tue, Oct 21, 2014 at 4:17 PM, Frank Zhang 
> wrote:
> 
> > What did you update? You replace the file with you manually built
> > certificate?
> >
> > > -Original Message-
> > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > Sent: Tuesday, October 21, 2014 3:16 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: Certificate expired
> > >
> > > Interesting...I just updated master and tried to re-build, but that
> > > test
> > failed
> > > again.
> > >
> > > On Tue, Oct 21, 2014 at 4:12 PM, Frank Zhang
> > > 
> > > wrote:
> > >
> > > > I met the error too.
> > > > It's caused by file
> > > > ./server/test/resources/certs/rsa_self_signed.crt
> > > > which is expired today.
> > > > I thought we need to replace it with a new one
> > > >
> > > > commit 0076307863e9155273d9e4c14282de429388c9e9
> > > > Author: Syed 
> > > > Date:   Wed Nov 6 15:08:42 2013 -0500
> > > >
> > > > Squashed merge of Ssl Termination feature
> > > >
> > > > Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-4821
> > > > FS:
> > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSL+Termina
> > > > tion
> > > > +Support
> > > >
> > > > This patch implements the SSL offload feature for loadbalancers
> > > > and includes the implementaion for this to work with Netscaler.
> > > >
> > > > The following are the new API's that this patch adds
> > > >
> > > > uploadSslCert
> > > > deleteSslCert
> > > > listSslCert
> > > > assignCertToLoadBalancer
> > > > removeCertFromLoadBalancer
> > > >
> > > > Unit tests are also included in the patch.
> > > >
> > > > > -Original Message-
> > > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > > Sent: Tuesday, October 21, 2014 1:09 PM
> > > > > To: dev@cloudstack.apache.org
> > > > > Subject: Certificate expired
> > > > >
> > > > > Hi,
> > > > >
> > > > > I just started getting this test-run error message on two of my
> > > > CloudStack dev
> > > > > boxes today (below).
> > > > >
> > > > > I don't recall sign-signing a certificate, but perhaps I just forgot.
> > > > >
> > > > > Can someone give me the context around this error?
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Results :
> > > > >
> > > > >
> > > > >
> > > > --
> > > > 
> > > > -
> > > > >
> > > > > Test set: org.apache.cloudstack.network.lb.CertServiceTest
> > > > >
> > > > >
> > > > --
> > > > 
> > > > -
> > > > >
> > > > > Tests run: 15, Failures: 2, Errors: 2, Skipped: 4, Time elapsed:
> > > > > 0.538
> > > > sec <<<
> > > > > FAILURE!
> > > > >
> > > > >
> > > > runUploadSslCertBadkeyAlgo(org.apache.cloudstack.network.lb.CertSe
> > > > rvic
> > > > eTest)
> > > > >  Time elapsed: 0.128 sec  <<< FAILURE!
> > > > >
> > > > > java.lang.AssertionError
> > > > >
> > > > > at org.junit.Assert.fail(Assert.java:86)
> > > > >
> > > > > at org.junit.Assert.assertTrue(Assert.java:41)
> > > > >
> > > > > at org.junit.Assert.assertTrue(Assert.java:52)
> > > > >
> > > > > at
> > > > >
> > > > org.apache.cloudstack.network.lb.CertServiceTest.runUploadSslCertB
> > > > adke
> > > > yAlgo
> > > > > (CertServiceTest.java:539)
> > > > >
> > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > >
> > > > > at
> > > > >
> > > >
> > >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > > > > 57)
> > > > >
> > > > > at
> > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
> > > > > Acce
> > > > > ssorI
> > > > > mpl.java:43)
> > > > >
> > > > > at java.lang.reflect.Method.invoke(Method.java:606)
> > > > >
> > > > > at
> > > > > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(Fram
> > > > > ewor
> > > > > kMe
> > > > > thod.java:47)
> > > > >
> > > > > at
> > > > >
> > > >
> > >
> >
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:
> > > > > 12)
> > > > >
> > > > > at
> > > > > org.junit.runners.model.FrameworkMethod.invokeExplosively(Framew
> > > > > orkM
> > > > > eth
> > > > > od.java:44)
> > > > >
> > > > > at
> > > > >
> > > > org.junit.internal.runners.statements.InvokeMethod.evaluate(Invoke
> > > > Meth
> > > > od.jav
> > > > > a:17)
> > > > >
> >

Re: Certificate expired

[Mike Tutkowski]

I see - thanks.

On Tue, Oct 21, 2014 at 4:36 PM, Frank Zhang  wrote:

> I made a new certificate, but there are lots of unit cases using different
> CAs; some of them use correct file; some of them use incorrect file.
> It takes time to understand what files need to be updated.
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Tuesday, October 21, 2014 3:20 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: Certificate expired
> >
> > No, sorry...I didn't clarify. I thought you were saying this was all
> fixed in code,
> > so I updated and tried to re-build the codebase:
> >
> > mvn -P developer,systemvm clean install
> >
> > But it failed on the same test.
> >
> > On Tue, Oct 21, 2014 at 4:17 PM, Frank Zhang 
> > wrote:
> >
> > > What did you update? You replace the file with you manually built
> > > certificate?
> > >
> > > > -Original Message-
> > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > Sent: Tuesday, October 21, 2014 3:16 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: Re: Certificate expired
> > > >
> > > > Interesting...I just updated master and tried to re-build, but that
> > > > test
> > > failed
> > > > again.
> > > >
> > > > On Tue, Oct 21, 2014 at 4:12 PM, Frank Zhang
> > > > 
> > > > wrote:
> > > >
> > > > > I met the error too.
> > > > > It's caused by file
> > > > > ./server/test/resources/certs/rsa_self_signed.crt
> > > > > which is expired today.
> > > > > I thought we need to replace it with a new one
> > > > >
> > > > > commit 0076307863e9155273d9e4c14282de429388c9e9
> > > > > Author: Syed 
> > > > > Date:   Wed Nov 6 15:08:42 2013 -0500
> > > > >
> > > > > Squashed merge of Ssl Termination feature
> > > > >
> > > > > Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-4821
> > > > > FS:
> > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSL+Termina
> > > > > tion
> > > > > +Support
> > > > >
> > > > > This patch implements the SSL offload feature for loadbalancers
> > > > > and includes the implementaion for this to work with Netscaler.
> > > > >
> > > > > The following are the new API's that this patch adds
> > > > >
> > > > > uploadSslCert
> > > > > deleteSslCert
> > > > > listSslCert
> > > > > assignCertToLoadBalancer
> > > > > removeCertFromLoadBalancer
> > > > >
> > > > > Unit tests are also included in the patch.
> > > > >
> > > > > > -Original Message-
> > > > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > > > Sent: Tuesday, October 21, 2014 1:09 PM
> > > > > > To: dev@cloudstack.apache.org
> > > > > > Subject: Certificate expired
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I just started getting this test-run error message on two of my
> > > > > CloudStack dev
> > > > > > boxes today (below).
> > > > > >
> > > > > > I don't recall sign-signing a certificate, but perhaps I just
> forgot.
> > > > > >
> > > > > > Can someone give me the context around this error?
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > Results :
> > > > > >
> > > > > >
> > > > > >
> > > > > --
> > > > > 
> > > > > -
> > > > > >
> > > > > > Test set: org.apache.cloudstack.network.lb.CertServiceTest
> > > > > >
> > > > > >
> > > > > --
> > > > > 
> > > > > -
> > > > > >
> > > > > > Tests run: 15, Failures: 2, Errors: 2, Skipped: 4, Time elapsed:
> > > > > > 0.538
> > > > > sec <<<
> > > > > > FAILURE!
> > > > > >
> > > > > >
> > > > > runUploadSslCertBadkeyAlgo(org.apache.cloudstack.network.lb.CertSe
> > > > > rvic
> > > > > eTest)
> > > > > >  Time elapsed: 0.128 sec  <<< FAILURE!
> > > > > >
> > > > > > java.lang.AssertionError
> > > > > >
> > > > > > at org.junit.Assert.fail(Assert.java:86)
> > > > > >
> > > > > > at org.junit.Assert.assertTrue(Assert.java:41)
> > > > > >
> > > > > > at org.junit.Assert.assertTrue(Assert.java:52)
> > > > > >
> > > > > > at
> > > > > >
> > > > > org.apache.cloudstack.network.lb.CertServiceTest.runUploadSslCertB
> > > > > adke
> > > > > yAlgo
> > > > > > (CertServiceTest.java:539)
> > > > > >
> > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > > >
> > > > > > at
> > > > > >
> > > > >
> > > >
> > >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > > > > > 57)
> > > > > >
> > > > > > at
> > > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
> > > > > > Acce
> > > > > > ssorI
> > > > > > mpl.java:43)
> > > > > >
> > > > > > at java.lang.reflect.Method.invoke(Method.java:606)
> > > > > >
> > > > > > at
> > > > > > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(Fram
> > > > > > ewor
> > > > > > kMe
> > > > > > thod.java:47)
> > > > > >
> > > > > > at
> > > > > >
> > > > >
> > > >
> > >
> >
> org.junit.internal.runne

Re: Review Request 27000: CLOUDSTACK-7762 -[Automation] - Fix test failure for test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py

[Chandan Purushothama]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27000/#review57694
---

Ship it!


Ship It!

- Chandan Purushothama


On Oct. 21, 2014, 10:34 p.m., sangeetha hariharan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27000/
> ---
> 
> (Updated Oct. 21, 2014, 10:34 p.m.)
> 
> 
> Review request for cloudstack, anthony xu and Chandan Purushothama.
> 
> 
> Bugs: CLOUDSTACK-7762
> https://issues.apache.org/jira/browse/CLOUDSTACK-7762
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py fails in BVT runs 
> with the following exception:
> 
> 2014-10-20 16:41:00,497 INFO [o.a.c.f.j.i.AsyncJobMonitor] 
> (API-Job-Executor-120:ctx-83b738d9 job-459) Add job-459 into job monitoring
> 2014-10-20 16:41:00,497 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
> (API-Job-Executor-120:ctx-83b738d9 job-459) Executing AsyncJobVO {id:459, 
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd: 
> org.apache.cloudstack.api.command.admin.vmsnapshot.RevertToVMSnapshotCmdByAdmin,
>  cmdInfo: {"response":"json","ctxDetails":"
> {\"com.cloud.vm.snapshot.VMSnapshot\":\"12280973-a1e4-43e3-80b3-3afacd607909\"}
> 
> ","cmdEventType":"VMSNAPSHOT.REVERTTO","ctxUserId":"2","httpmethod":"GET","vmsnapshotid":"12280973-a1e4-43e3-80b3-3afacd607909","ctxAccountId":"2","ctxStartEventId":"1406","apiKey":"aJwkScf5ziRwz8gKQ9HB0Ce6hSsTJTUtmUDUQ_U2teV3vVmuLQRLad8xqAgr7CrFOEQbywdVpKSt2yC_ORXLYg","signature":"cYBxgg8eBfktovmCaHYox2xoTE8\u003d"},
>  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
> null, initMsid: 11489258594360, completeMsid: null, lastUpdated: null, 
> lastPolled: null, created: null}
> 2014-10-20 16:41:00,529 ERROR [c.c.a.ApiAsyncJobDispatcher] 
> (API-Job-Executor-120:ctx-83b738d9 job-459) Unexpected exception while 
> executing 
> org.apache.cloudstack.api.command.admin.vmsnapshot.RevertToVMSnapshotCmdByAdmin
> com.cloud.exception.InvalidParameterValueException: VM Snapshot revert not 
> allowed. This will result in VM state change. You can revert running VM to 
> disk and memory type snapshot and stopped VM to disk type snapshot
> at 
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.revertToSnapshot(VMSnapshotManagerImpl.java:581)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> 
> Root Cause :
> reverting Snapshots is allowed only when there is no vm state change 
> associated with it.
> Following are the 2 scenarios allowed: 
> 1.Revert a "Running" VM to a "Disk and Memory" Snapshot ( with and without 
> "quiesce" option).
> 2.Revert a "Stopped" VM to a "Disk " Snapshot ( with and without "quiesce" 
> option).
> 
> In this test case , we are testing reverting to a Disk " Snapshot. Introduced 
> a Vm stop before performing the revert operation.
> 
> 
> Diffs
> -
> 
>   test/integration/smoke/test_vm_snapshots.py 131da99 
> 
> Diff: https://reviews.apache.org/r/27000/diff/
> 
> 
> Testing
> ---
> 
> Tested with advanced zone set up with Xenserver hosts:
> 
> Test to create VM snapshots ... === TestName: test_01_create_vm_snapshots | 
> Status : SUCCESS ===
> ok
> Test to revert VM snapshots ... === TestName: test_02_revert_vm_snapshots | 
> Status : SUCCESS ===
> ok
> Test to delete vm snapshots ... === TestName: test_03_delete_vm_snapshots | 
> Status : SUCCESS ===
> ok
> 
> --
> Ran 3 tests in 795.005s
> 
> OK
> 
> 
> Thanks,
> 
> sangeetha hariharan
> 
>

UUID versus GUID in cluster table

[Mike Tutkowski]

Hi,

Just curious...why do we have both a UUID and a GUID field in the cluster
table?

Thanks,
Mike

-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

RE: Certificate expired

[Frank Zhang]

I updated three certificated and disabled 4 cases that I cannot figure out the 
test logic.
The patch has been pushed to master; the build is working now.
I will send a mail to original author for those 4 disabled cases.

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Tuesday, October 21, 2014 3:39 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Certificate expired
> 
> I see - thanks.
> 
> On Tue, Oct 21, 2014 at 4:36 PM, Frank Zhang 
> wrote:
> 
> > I made a new certificate, but there are lots of unit cases using
> > different CAs; some of them use correct file; some of them use incorrect 
> > file.
> > It takes time to understand what files need to be updated.
> >
> > > -Original Message-
> > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > Sent: Tuesday, October 21, 2014 3:20 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: Certificate expired
> > >
> > > No, sorry...I didn't clarify. I thought you were saying this was all
> > fixed in code,
> > > so I updated and tried to re-build the codebase:
> > >
> > > mvn -P developer,systemvm clean install
> > >
> > > But it failed on the same test.
> > >
> > > On Tue, Oct 21, 2014 at 4:17 PM, Frank Zhang
> > > 
> > > wrote:
> > >
> > > > What did you update? You replace the file with you manually built
> > > > certificate?
> > > >
> > > > > -Original Message-
> > > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > > Sent: Tuesday, October 21, 2014 3:16 PM
> > > > > To: dev@cloudstack.apache.org
> > > > > Subject: Re: Certificate expired
> > > > >
> > > > > Interesting...I just updated master and tried to re-build, but
> > > > > that test
> > > > failed
> > > > > again.
> > > > >
> > > > > On Tue, Oct 21, 2014 at 4:12 PM, Frank Zhang
> > > > > 
> > > > > wrote:
> > > > >
> > > > > > I met the error too.
> > > > > > It's caused by file
> > > > > > ./server/test/resources/certs/rsa_self_signed.crt
> > > > > > which is expired today.
> > > > > > I thought we need to replace it with a new one
> > > > > >
> > > > > > commit 0076307863e9155273d9e4c14282de429388c9e9
> > > > > > Author: Syed 
> > > > > > Date:   Wed Nov 6 15:08:42 2013 -0500
> > > > > >
> > > > > > Squashed merge of Ssl Termination feature
> > > > > >
> > > > > > Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-4821
> > > > > > FS:
> > > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSL+Ter
> > > > > > mina
> > > > > > tion
> > > > > > +Support
> > > > > >
> > > > > > This patch implements the SSL offload feature for loadbalancers
> > > > > > and includes the implementaion for this to work with Netscaler.
> > > > > >
> > > > > > The following are the new API's that this patch adds
> > > > > >
> > > > > > uploadSslCert
> > > > > > deleteSslCert
> > > > > > listSslCert
> > > > > > assignCertToLoadBalancer
> > > > > > removeCertFromLoadBalancer
> > > > > >
> > > > > > Unit tests are also included in the patch.
> > > > > >
> > > > > > > -Original Message-
> > > > > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > > > > Sent: Tuesday, October 21, 2014 1:09 PM
> > > > > > > To: dev@cloudstack.apache.org
> > > > > > > Subject: Certificate expired
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I just started getting this test-run error message on two of
> > > > > > > my
> > > > > > CloudStack dev
> > > > > > > boxes today (below).
> > > > > > >
> > > > > > > I don't recall sign-signing a certificate, but perhaps I
> > > > > > > just
> > forgot.
> > > > > > >
> > > > > > > Can someone give me the context around this error?
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > Results :
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > --
> > > > > > 
> > > > > > 
> > > > > > -
> > > > > > >
> > > > > > > Test set: org.apache.cloudstack.network.lb.CertServiceTest
> > > > > > >
> > > > > > >
> > > > > > --
> > > > > > 
> > > > > > 
> > > > > > -
> > > > > > >
> > > > > > > Tests run: 15, Failures: 2, Errors: 2, Skipped: 4, Time elapsed:
> > > > > > > 0.538
> > > > > > sec <<<
> > > > > > > FAILURE!
> > > > > > >
> > > > > > >
> > > > > > runUploadSslCertBadkeyAlgo(org.apache.cloudstack.network.lb.Ce
> > > > > > rtSe
> > > > > > rvic
> > > > > > eTest)
> > > > > > >  Time elapsed: 0.128 sec  <<< FAILURE!
> > > > > > >
> > > > > > > java.lang.AssertionError
> > > > > > >
> > > > > > > at org.junit.Assert.fail(Assert.java:86)
> > > > > > >
> > > > > > > at org.junit.Assert.assertTrue(Assert.java:41)
> > > > > > >
> > > > > > > at org.junit.Assert.assertTrue(Assert.java:52)
> > > > > > >
> > > > > > > at
> > > > > > >
> > > > > > org.apache.cloudstack.network.lb.CertServiceTest.runUploadSslC
> > > > > > ertB
> > > > > > adke
> > > 

Re: [PROPOSAL] Move to github PR only during moratorium on commit

[David Nalley]

Hi Sebastien:

So I like the idea of:

1. Us putting up all inbound code for review.
2. Gating that code on a testing pass
3. Having someone else look at it before committing.

I don't think that should mean that all code that works gets an
immediate pass. I also don't think that we should have n RMs for
branches. It doesn't scale, and it moves us from consensus to
authoritarian. I am all for reverting things that break, but think
that should be a community wide responsibility, not one or two
policemen.

I also think this is a huge shift in process. Right now we have 145
open patches on ReviewBoard. We average scores of commits per day; so
understand that this is a huge, gigantic shift in how we work. This
requires a high level of commitment from everyone, and frankly it's
likely to bury TravisCI.

I also worry about the effect of this on our ability to timely ship
4.5. We have 14 Critical and blocker bugs for 4.5, and part of me
worries that this is a distraction for 4.5 release efforts.

Please don't take this as discounting your proposal or your concerns.
I don't think that many folks disagrees in principle with the first 3
points above. But timing, and implementation details may be an issue.

--David

On Sat, Oct 18, 2014 at 5:00 AM, sebgoa  wrote:
> After [1] I would like to officially bring up the following proposal.
>
> [Proposal]
> 
> All commits come through github PR, *even* for committers. We declare a 
> moratorium period (agreed suspension of activity) during which direct commit 
> to master is forbidden.
> Only the master RM is allowed to merge PR in master (we define a master RM). 
> If direct commit to master is done, master RM reverts without warning. Same 
> for 4.5 and 4.4. branches.
> 
>
> This is drastic and I am sure some folks will not like it, but here is my 
> justification for such a measure:
>
> [Reasons]:
> 
> Our commit and release processes have so far been based on the idea that 
> development happens on master and that a release branch is cut from master 
> (unstable development branch). Then a different set of community members 
> harden the release branch, QA and bring it to GA level. During that time 
> development keeps on going in master.
>
> This is an OK process if we have the luxury of having a QA team and can cope 
> with split personality of being developers and release managers.
>
> My point of view is that as a community we cannot afford such a split brain 
> organization and our experience overt the last year proves my point (delayed 
> release date, broken builds, features merged without warning…)
>
> We can avoid this by cutting a release branch from a stable one (from the 
> start), then as you (Daan) have mentioned several times, fix bugs in the 
> release branch and merge them back in the stable source of the release (be it 
> master).
>
> Feature development need to be done outside master, period. Not only for 
> non-committers but also for committers. And merge request need to be called. 
> This will help review and avoid surprises.
>
> New git workflow were proposed and shutdown, mostly calling for better CI to 
> solve quality issues. CI will not solve our quality issues alone. We need to 
> better police ourselves.
>
> To avoid long discussions, I propose this simple but drastic measure. We move 
> all our commits to github PR until 4.5 is out, this stands for committers and 
> non-committers, direct commits (especially to master) would be reverted 
> immediately.
> 
>
> Our development and release process is broken, we cannot continue like this, 
> let's fix it.
>
> [1] http://markmail.org/thread/xeliefp3oleq3g54
>
> -sebastien

Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

[Nux!]

Thanks for that. I went back to 431, but I'll try one more time to upgrade to 
4.4.1 without the 4.4.0 sysvm step.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Pierre-Luc Dion" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 21 October, 2014 23:26:49
> Subject: Re: Is the 4.4.0 template still necessary for upgrade 4.3.x - 4.4.1?

> Hi. Sorry to see this thread late. Upgrading from 4.3.1 to 4.4.1 only
> require one systemvm template. (The one with -7).
> 
> Refer to 4.4.1 release notes , it should point to proper urls for sysvm
> too.

Re: Certificate expired

[Mike Tutkowski]

Thanks, Frank!

On Tue, Oct 21, 2014 at 5:20 PM, Frank Zhang  wrote:

> I updated three certificated and disabled 4 cases that I cannot figure out
> the test logic.
> The patch has been pushed to master; the build is working now.
> I will send a mail to original author for those 4 disabled cases.
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Tuesday, October 21, 2014 3:39 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: Certificate expired
> >
> > I see - thanks.
> >
> > On Tue, Oct 21, 2014 at 4:36 PM, Frank Zhang 
> > wrote:
> >
> > > I made a new certificate, but there are lots of unit cases using
> > > different CAs; some of them use correct file; some of them use
> incorrect file.
> > > It takes time to understand what files need to be updated.
> > >
> > > > -Original Message-
> > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > Sent: Tuesday, October 21, 2014 3:20 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: Re: Certificate expired
> > > >
> > > > No, sorry...I didn't clarify. I thought you were saying this was all
> > > fixed in code,
> > > > so I updated and tried to re-build the codebase:
> > > >
> > > > mvn -P developer,systemvm clean install
> > > >
> > > > But it failed on the same test.
> > > >
> > > > On Tue, Oct 21, 2014 at 4:17 PM, Frank Zhang
> > > > 
> > > > wrote:
> > > >
> > > > > What did you update? You replace the file with you manually built
> > > > > certificate?
> > > > >
> > > > > > -Original Message-
> > > > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > > > Sent: Tuesday, October 21, 2014 3:16 PM
> > > > > > To: dev@cloudstack.apache.org
> > > > > > Subject: Re: Certificate expired
> > > > > >
> > > > > > Interesting...I just updated master and tried to re-build, but
> > > > > > that test
> > > > > failed
> > > > > > again.
> > > > > >
> > > > > > On Tue, Oct 21, 2014 at 4:12 PM, Frank Zhang
> > > > > > 
> > > > > > wrote:
> > > > > >
> > > > > > > I met the error too.
> > > > > > > It's caused by file
> > > > > > > ./server/test/resources/certs/rsa_self_signed.crt
> > > > > > > which is expired today.
> > > > > > > I thought we need to replace it with a new one
> > > > > > >
> > > > > > > commit 0076307863e9155273d9e4c14282de429388c9e9
> > > > > > > Author: Syed 
> > > > > > > Date:   Wed Nov 6 15:08:42 2013 -0500
> > > > > > >
> > > > > > > Squashed merge of Ssl Termination feature
> > > > > > >
> > > > > > > Bug: https://issues.apache.org/jira/browse/CLOUDSTACK-4821
> > > > > > > FS:
> > > > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSL+Ter
> > > > > > > mina
> > > > > > > tion
> > > > > > > +Support
> > > > > > >
> > > > > > > This patch implements the SSL offload feature for
> loadbalancers
> > > > > > > and includes the implementaion for this to work with
> Netscaler.
> > > > > > >
> > > > > > > The following are the new API's that this patch adds
> > > > > > >
> > > > > > > uploadSslCert
> > > > > > > deleteSslCert
> > > > > > > listSslCert
> > > > > > > assignCertToLoadBalancer
> > > > > > > removeCertFromLoadBalancer
> > > > > > >
> > > > > > > Unit tests are also included in the patch.
> > > > > > >
> > > > > > > > -Original Message-
> > > > > > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > > > > > > > Sent: Tuesday, October 21, 2014 1:09 PM
> > > > > > > > To: dev@cloudstack.apache.org
> > > > > > > > Subject: Certificate expired
> > > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I just started getting this test-run error message on two of
> > > > > > > > my
> > > > > > > CloudStack dev
> > > > > > > > boxes today (below).
> > > > > > > >
> > > > > > > > I don't recall sign-signing a certificate, but perhaps I
> > > > > > > > just
> > > forgot.
> > > > > > > >
> > > > > > > > Can someone give me the context around this error?
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > >
> > > > > > > > Results :
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > --
> > > > > > > 
> > > > > > > 
> > > > > > > -
> > > > > > > >
> > > > > > > > Test set: org.apache.cloudstack.network.lb.CertServiceTest
> > > > > > > >
> > > > > > > >
> > > > > > > --
> > > > > > > 
> > > > > > > 
> > > > > > > -
> > > > > > > >
> > > > > > > > Tests run: 15, Failures: 2, Errors: 2, Skipped: 4, Time
> elapsed:
> > > > > > > > 0.538
> > > > > > > sec <<<
> > > > > > > > FAILURE!
> > > > > > > >
> > > > > > > >
> > > > > > > runUploadSslCertBadkeyAlgo(org.apache.cloudstack.network.lb.Ce
> > > > > > > rtSe
> > > > > > > rvic
> > > > > > > eTest)
> > > > > > > >  Time elapsed: 0.128 sec  <<< FAILURE!
> > > > > > > >
> > > > > > > > java.lang.AssertionError
> > > > > > > >
> > > > > > > > a

Re: Review Request 27000: CLOUDSTACK-7762 -[Automation] - Fix test failure for test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py

[anthony xu]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27000/#review57716
---

Ship it!


Ship It!

- anthony xu


On Oct. 21, 2014, 10:34 p.m., sangeetha hariharan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27000/
> ---
> 
> (Updated Oct. 21, 2014, 10:34 p.m.)
> 
> 
> Review request for cloudstack, anthony xu and Chandan Purushothama.
> 
> 
> Bugs: CLOUDSTACK-7762
> https://issues.apache.org/jira/browse/CLOUDSTACK-7762
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py fails in BVT runs 
> with the following exception:
> 
> 2014-10-20 16:41:00,497 INFO [o.a.c.f.j.i.AsyncJobMonitor] 
> (API-Job-Executor-120:ctx-83b738d9 job-459) Add job-459 into job monitoring
> 2014-10-20 16:41:00,497 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
> (API-Job-Executor-120:ctx-83b738d9 job-459) Executing AsyncJobVO {id:459, 
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd: 
> org.apache.cloudstack.api.command.admin.vmsnapshot.RevertToVMSnapshotCmdByAdmin,
>  cmdInfo: {"response":"json","ctxDetails":"
> {\"com.cloud.vm.snapshot.VMSnapshot\":\"12280973-a1e4-43e3-80b3-3afacd607909\"}
> 
> ","cmdEventType":"VMSNAPSHOT.REVERTTO","ctxUserId":"2","httpmethod":"GET","vmsnapshotid":"12280973-a1e4-43e3-80b3-3afacd607909","ctxAccountId":"2","ctxStartEventId":"1406","apiKey":"aJwkScf5ziRwz8gKQ9HB0Ce6hSsTJTUtmUDUQ_U2teV3vVmuLQRLad8xqAgr7CrFOEQbywdVpKSt2yC_ORXLYg","signature":"cYBxgg8eBfktovmCaHYox2xoTE8\u003d"},
>  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
> null, initMsid: 11489258594360, completeMsid: null, lastUpdated: null, 
> lastPolled: null, created: null}
> 2014-10-20 16:41:00,529 ERROR [c.c.a.ApiAsyncJobDispatcher] 
> (API-Job-Executor-120:ctx-83b738d9 job-459) Unexpected exception while 
> executing 
> org.apache.cloudstack.api.command.admin.vmsnapshot.RevertToVMSnapshotCmdByAdmin
> com.cloud.exception.InvalidParameterValueException: VM Snapshot revert not 
> allowed. This will result in VM state change. You can revert running VM to 
> disk and memory type snapshot and stopped VM to disk type snapshot
> at 
> com.cloud.vm.snapshot.VMSnapshotManagerImpl.revertToSnapshot(VMSnapshotManagerImpl.java:581)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> 
> Root Cause :
> reverting Snapshots is allowed only when there is no vm state change 
> associated with it.
> Following are the 2 scenarios allowed: 
> 1.Revert a "Running" VM to a "Disk and Memory" Snapshot ( with and without 
> "quiesce" option).
> 2.Revert a "Stopped" VM to a "Disk " Snapshot ( with and without "quiesce" 
> option).
> 
> In this test case , we are testing reverting to a Disk " Snapshot. Introduced 
> a Vm stop before performing the revert operation.
> 
> 
> Diffs
> -
> 
>   test/integration/smoke/test_vm_snapshots.py 131da99 
> 
> Diff: https://reviews.apache.org/r/27000/diff/
> 
> 
> Testing
> ---
> 
> Tested with advanced zone set up with Xenserver hosts:
> 
> Test to create VM snapshots ... === TestName: test_01_create_vm_snapshots | 
> Status : SUCCESS ===
> ok
> Test to revert VM snapshots ... === TestName: test_02_revert_vm_snapshots | 
> Status : SUCCESS ===
> ok
> Test to delete vm snapshots ... === TestName: test_03_delete_vm_snapshots | 
> Status : SUCCESS ===
> ok
> 
> --
> Ran 3 tests in 795.005s
> 
> OK
> 
> 
> Thanks,
> 
> sangeetha hariharan
> 
>

431 to 441, VR upgrade fails with VR config: execution failed: "/opt/cloud/bin/createipAlias.sh"

[Nux!]

Hi,

I almost upgraded from 4.3.1 to 4.4.1, everything went smoothly except the VR 
upgrade (the other sysvms are fine). It will not upgrade, even if I delete it 
and create another, same story:

On the agent I see:

2014-10-22 01:17:17,857 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) Executing: 
/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vr_cfg.sh 
169.254.1.228 -c /var/cache/cloud/VR-5109f323-dc37-4af2-b75d-41dd65acbf93.cfg 
2014-10-22 01:17:17,934 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) Exit value is 1
2014-10-22 01:17:17,934 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) VR config: execution failed: 
"/opt/cloud/bin/createipAlias.sh 
289:10.13.208.78:255.255.255.248-224:10.187.71.194:255.255.255.192-", check 
/var/log/cloud.log in VR for details 

But the VR is being destroyed and I cannot investigate the /var/log/cloud.log 
...


On the management log:

Unable to start instance due to Unable to start VM[DomainRouter|r-443-VM] due 
to error in finalizeStart, not retrying
more here http://pastebin.com/raw.php?i=fY7v8Sak

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Build failed in Jenkins: build-4.5 #36

[jenkins]

See 

Changes:

[anthony.xu] CLOUDSTACK-7761:

--
[...truncated 1828 lines...]
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.295 sec
Running org.apache.cloudstack.region.RegionManagerTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.159 sec
Running org.apache.cloudstack.service.ServiceOfferingVOTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.144 sec
Running org.apache.cloudstack.affinity.AffinityApiUnitTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.554 sec
Running org.apache.cloudstack.privategw.AclOnPrivateGwTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.972 sec
Running org.apache.cloudstack.network.lb.CertServiceTest
Tests run: 15, Failures: 5, Errors: 3, Skipped: 0, Time elapsed: 2.723 sec <<< 
FAILURE!
Running org.apache.cloudstack.network.lb.ApplicationLoadBalancerTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.067 sec
Running org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.663 sec
Running com.cloud.template.TemplateManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.064 sec
Running com.cloud.keystore.KeystoreTest
org.apache.cloudstack.api.response.UserVmResponse/null/{"id":"3","securitygroup":[],"nic":[],"tags":[],"affinitygroup":[]}
org.apache.cloudstack.api.response.AlertResponse/null/{"id":"100","description":"Hello"}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.51 sec
Running com.cloud.server.ConfigurationServerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 sec
Running com.cloud.event.EventControlsUnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.201 sec
Running com.cloud.resourcelimit.ResourceLimitManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
Running com.cloud.api.dispatch.ParamGenericValidationWorkerTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.107 sec
Running com.cloud.api.dispatch.ParamProcessWorkerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running com.cloud.api.dispatch.CommandCreationWorkerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.105 sec
Running com.cloud.api.dispatch.DispatchChainFactoryTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
Running com.cloud.api.dispatch.SpecificCmdValidationWorkerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec
Running com.cloud.api.ApiServletTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.582 sec
Running com.cloud.api.ApiResponseHelperTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.094 sec
Running com.cloud.alert.AlertControlsUnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec
Running com.cloud.ha.KVMFencerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.351 sec
Running com.cloud.ha.HighAvailabilityManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.58 sec
Running com.cloud.capacity.CapacityManagerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.145 sec
Running com.cloud.vm.snapshot.VMSnapshotManagerTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.014 sec
Running com.cloud.vm.FirstFitPlannerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.106 sec
Running com.cloud.vm.UserVmManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.134 sec
Running com.cloud.vm.DeploymentPlanningManagerImplTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.489 sec
Running com.cloud.servlet.ConsoleProxyServletTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
Running com.cloud.servlet.StaticResourceServletTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.354 sec
Running com.cloud.network.ExternalLoadBalancerDeviceManagerImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.959 sec
Running com.cloud.network.NetworkModelTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.119 sec
Running com.cloud.network.security.SecurityGroupManagerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.245 sec
Running com.cloud.network.security.SecurityGroupQueueTest
Total jobs dequeued = 10, num queued=1000 queue current size=990
Num Vms= 50 Queue size = 50
Num Vms= 2 Queue size = 2 time=11761 ms
Num Vms= 5000 Queue size = 5000 time=6512 ms
Num Vms= 1 Queue size = 1 time=14 ms
Num Vms= 100 Queue size = 100 time=6496 ms
Num Vms= 1 Queue size = 1 time=3064 ms
Total jobs dequeued = 10, num queued=1010 queue current size=1000
Total jobs deq

Re: 431 to 441, VR upgrade fails with VR config: execution failed: "/opt/cloud/bin/createipAlias.sh"

[Jayapal Reddy Uradi]

Hi Nux,

There is spelling mistake 'i' instead of 'I' in the file name 'createipAlias.sh'

Work around is in VR change createIpAlias.sh -> createipAlias.sh
Observe the MS log once the VR entered into Running state stop the MS so that 
VR won't be destroyed.
Now go to VR and change the file name.

This issue got fixed in 4.5 CLOUDSTACK-7246

Thanks,
Jayapal
On 22-Oct-2014, at 6:03 AM, Nux!  wrote:

> Hi,
> 
> I almost upgraded from 4.3.1 to 4.4.1, everything went smoothly except the VR 
> upgrade (the other sysvms are fine). It will not upgrade, even if I delete it 
> and create another, same story:
> 
> On the agent I see:
> 
> 2014-10-22 01:17:17,857 DEBUG [kvm.resource.LibvirtComputingResource] 
> (agentRequest-Handler-5:null) Executing: 
> /usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vr_cfg.sh 
> 169.254.1.228 -c /var/cache/cloud/VR-5109f323-dc37-4af2-b75d-41dd65acbf93.cfg 
> 2014-10-22 01:17:17,934 DEBUG [kvm.resource.LibvirtComputingResource] 
> (agentRequest-Handler-5:null) Exit value is 1
> 2014-10-22 01:17:17,934 DEBUG [kvm.resource.LibvirtComputingResource] 
> (agentRequest-Handler-5:null) VR config: execution failed: 
> "/opt/cloud/bin/createipAlias.sh 
> 289:10.13.208.78:255.255.255.248-224:10.187.71.194:255.255.255.192-", check 
> /var/log/cloud.log in VR for details 
> 
> But the VR is being destroyed and I cannot investigate the /var/log/cloud.log 
> ...
> 
> 
> On the management log:
> 
> Unable to start instance due to Unable to start VM[DomainRouter|r-443-VM] due 
> to error in finalizeStart, not retrying
> more here http://pastebin.com/raw.php?i=fY7v8Sak
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> http://secure-web.cisco.com/1QTvqoF2kC8J2AVldxqw_eHOGu2lEYYQPIXQRv2AfAxFtBJkyYcGU9BExyL8RBhIRG7P2ubiMb3y4pE3uGE1bqL5YsDZRudJJY4-06h0_ISiM0scnTIC5qgQLx3NI9chTB64l33iEIMZFcsu49mvxV7PadSYmEtNCre8_xzMds-I/http%3A%2F%2Fwww.nux.ro
> 

Review Request 27017: CLOUDSTACK-6282: Added newly automated tests and also modified some existing tests to remove dependency

[Vinay Varma]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27017/
---

Review request for cloudstack and Santhosh Edukulla.


Bugs: CLOUDSTACK-6282
https://issues.apache.org/jira/browse/CLOUDSTACK-6282


Repository: cloudstack-git


Description
---

CLOUDSTACK-6282: Added newly automated tests and also modified some existing 
tests to remove dependency


Diffs
-

  test/integration/component/test_escalations_instances.py 1aaa688 
  test/integration/component/test_escalations_snapshots.py 4b6b7f5 
  test/integration/component/test_escalations_templates.py 78028bc 
  test/integration/component/test_escalations_volumes.py 7290325 
  test/integration/component/test_escalations_vpncustomergateways.py b09930a 
  tools/marvin/marvin/cloudstackTestClient.py ce7ffc9 
  tools/marvin/marvin/lib/base.py 77faeeb 

Diff: https://reviews.apache.org/r/27017/diff/


Testing
---

Attached are the results files for each of the file modified and the results 
shows everything is fine


File Attachments


Instancesresults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/22/6ea95260-f31e-4fdd-a9f3-f30bac872df5__Instancesresults.txt
Snapshotsresults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/22/a91e862c-dc2e-403e-85e4-6479eefcd9d1__Snapshotsresults.txt
Templatesresults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/22/545fd06e-4975-4330-8390-3723d944ec2b__Templatesresults.txt
Voumesresults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/22/9932b16c-684f-41ce-b6f9-192fe887c2b8__Voumesresults.txt
VPNCustomerGatewaysresults.txt
  
https://reviews.apache.org/media/uploaded/files/2014/10/22/58c5f08e-cac7-4873-a922-8c874a9a8e3a__VPNCustomerGatewaysresults.txt


Thanks,

Vinay Varma

Review Request 27021: Reservations for VMware VMs remain after dynamic scaling

[bharat kumar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27021/
---

Review request for cloudstack and Kishan Kavala.


Bugs: CLOUDSTACK-7763
https://issues.apache.org/jira/browse/CLOUDSTACK-7763


Repository: cloudstack-git


Description
---

Reservations for VMware VMs remain after dynamic scaling
https://issues.apache.org/jira/browse/CLOUDSTACK-7763


Diffs
-

  
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
 085b6bbed4918be3155fd44c8bed785983526e11 

Diff: https://reviews.apache.org/r/27021/diff/


Testing
---


Thanks,

bharat kumar