Re: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)

[Mike Tutkowski]

At several of the companies where I've worked before, we would hold "bug
court" a couple times per week as the release marched on.

Representatives from different areas (product marketing, sales, support,
engineering, etc.) would attend and we'd go through all issues opened since
the previous bug court and prioritize them. Depending on how close we were
to GA for a release, less critical defects (unless trivial to fix) would be
postponed until a subsequent release.

This allowed us to control more closely what went into a release the closer
we got to GA, but it's probably not practical for CloudStack as it requires
a fair amount of discussion for each new issue.

On Tue, Sep 1, 2015 at 2:11 AM, Daan Hoogland 
wrote:

> There is something like this on the page by Remi on the new release
> procedure. It is one of the lesser things about it. I think we should only
> look at stability. The discussion on what is minor or major is not
> something we want to need to have.
>
> On Tue, Sep 1, 2015 at 3:48 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com
> > wrote:
>
> > What do we think, though, about tickets listed as Minor going in at this
> > point in 4.6 development?
> >
> > If they entail a trivial change in only a file or two, it's probably OK,
> > but where should we draw the line?
> >
> > At some point as the release goes on, we should stop accepting PRs that
> are
> > tied to Minor tickets and only allow churn in that branch for more major
> > issues. Those PRs tied to Minor tickets can then be for the next release.
> >
> > Thoughts?
> >
> > On Mon, Aug 31, 2015 at 12:03 PM, Daan Hoogland  >
> > wrote:
> >
> > > As David says; Though I think it is very polite of you to wait and ask
> > > around, you have this right if you can show master doesn't work.
> > >
> > > On Mon, Aug 31, 2015 at 6:06 PM, David Nalley  wrote:
> > >
> > > > On Mon, Aug 31, 2015 at 12:57 AM, Koushik Das <
> koushik@citrix.com>
> > > > wrote:
> > > > > I am no longer able to start MS after this. I did a clean build
> > > followed
> > > > by starting MS. Did travis pass for it? Should we revert?
> > > > >
> > > >
> > > > Yes, and in general, when things break you should feel empowered to
> > > > revert (still send a note to the list, but as a committer, you have a
> > > > binding veto at your disposal - feel free to make use of it to keep
> > > > quality high.)
> > > >
> > > > --David
> > > >
> > >
> > >
> > >
> > > --
> > > 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
>



-- 
*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: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)

[Daan Hoogland]

There is something like this on the page by Remi on the new release
procedure. It is one of the lesser things about it. I think we should only
look at stability. The discussion on what is minor or major is not
something we want to need to have.

On Tue, Sep 1, 2015 at 3:48 AM, Mike Tutkowski  wrote:

> What do we think, though, about tickets listed as Minor going in at this
> point in 4.6 development?
>
> If they entail a trivial change in only a file or two, it's probably OK,
> but where should we draw the line?
>
> At some point as the release goes on, we should stop accepting PRs that are
> tied to Minor tickets and only allow churn in that branch for more major
> issues. Those PRs tied to Minor tickets can then be for the next release.
>
> Thoughts?
>
> On Mon, Aug 31, 2015 at 12:03 PM, Daan Hoogland 
> wrote:
>
> > As David says; Though I think it is very polite of you to wait and ask
> > around, you have this right if you can show master doesn't work.
> >
> > On Mon, Aug 31, 2015 at 6:06 PM, David Nalley  wrote:
> >
> > > On Mon, Aug 31, 2015 at 12:57 AM, Koushik Das 
> > > wrote:
> > > > I am no longer able to start MS after this. I did a clean build
> > followed
> > > by starting MS. Did travis pass for it? Should we revert?
> > > >
> > >
> > > Yes, and in general, when things break you should feel empowered to
> > > revert (still send a note to the list, but as a committer, you have a
> > > binding veto at your disposal - feel free to make use of it to keep
> > > quality high.)
> > >
> > > --David
> > >
> >
> >
> >
> > --
> > 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

Re: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)

[David Nalley]

On Mon, Aug 31, 2015 at 12:57 AM, Koushik Das  wrote:
> I am no longer able to start MS after this. I did a clean build followed by 
> starting MS. Did travis pass for it? Should we revert?
>

Yes, and in general, when things break you should feel empowered to
revert (still send a note to the list, but as a committer, you have a
binding veto at your disposal - feel free to make use of it to keep
quality high.)

--David

Re: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)

[Daan Hoogland]

As David says; Though I think it is very polite of you to wait and ask
around, you have this right if you can show master doesn't work.

On Mon, Aug 31, 2015 at 6:06 PM, David Nalley  wrote:

> On Mon, Aug 31, 2015 at 12:57 AM, Koushik Das 
> wrote:
> > I am no longer able to start MS after this. I did a clean build followed
> by starting MS. Did travis pass for it? Should we revert?
> >
>
> Yes, and in general, when things break you should feel empowered to
> revert (still send a note to the list, but as a committer, you have a
> binding veto at your disposal - feel free to make use of it to keep
> quality high.)
>
> --David
>



-- 
Daan

Re: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)

[Mike Tutkowski]

What do we think, though, about tickets listed as Minor going in at this
point in 4.6 development?

If they entail a trivial change in only a file or two, it's probably OK,
but where should we draw the line?

At some point as the release goes on, we should stop accepting PRs that are
tied to Minor tickets and only allow churn in that branch for more major
issues. Those PRs tied to Minor tickets can then be for the next release.

Thoughts?

On Mon, Aug 31, 2015 at 12:03 PM, Daan Hoogland 
wrote:

> As David says; Though I think it is very polite of you to wait and ask
> around, you have this right if you can show master doesn't work.
>
> On Mon, Aug 31, 2015 at 6:06 PM, David Nalley  wrote:
>
> > On Mon, Aug 31, 2015 at 12:57 AM, Koushik Das 
> > wrote:
> > > I am no longer able to start MS after this. I did a clean build
> followed
> > by starting MS. Did travis pass for it? Should we revert?
> > >
> >
> > Yes, and in general, when things break you should feel empowered to
> > revert (still send a note to the list, but as a committer, you have a
> > binding veto at your disposal - feel free to make use of it to keep
> > quality high.)
> >
> > --David
> >
>
>
>
> --
> 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: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)

[Mike Tutkowski]

I would say, yeah, revert it. Daan and I did a visual walk through of the
code, but I don't think either of us did a build and tried to run it. I
thought the tests said they were good on Travis, though.

On Sun, Aug 30, 2015 at 10:57 PM, Koushik Das koushik@citrix.com
wrote:

 I am no longer able to start MS after this. I did a clean build followed
 by starting MS. Did travis pass for it? Should we revert?

  mvn clean install -Dsimulator -DskipTests
  mvn -pl client jetty:run -Dsimulator

 Getting the following error. No qualifying bean of type
 [com.cloud.network.element.HAProxyLBRule] found for dependency: expected at
 least 1 bean which qualifies as autowire candidate for this dependency.

 2015-08-31 09:51:29.195:WARN::Nested in
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'accountManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: private com.cloud.storage.dao.VMTemplateDao
 com.cloud.user.AccountManagerImpl._templateDao; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'VMTemplateDaoImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: org.apache.cloudstack.storage.datastore.db.TemplateDataStoreDao
 com.cloud.storage.dao.VMTemplateDaoImpl._templateDataStoreDao; nested
 exception is org.springframework.beans.factory.BeanCreationException: Error
 creating bean with name 'templateDataStoreDaoImpl': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: private
 org.apache.cloudstack.engine.subsystem.api.storage.DataStoreManager
 org.apache.cloudstack.storage.image.db.TemplateDataStoreDaoImpl._storeMgr;
 nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'dataStoreProviderManager': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field:
 org.apache.cloudstack.storage.datastore.PrimaryDataStoreProviderManager
 org.apache.cloudstack.storage.datastore.provider.DataStoreProviderManagerImpl.primaryDataStoreProviderMgr;
 nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'primaryDataStoreProviderMgr': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: com.cloud.storage.StorageManager
 org.apache.cloudstack.storage.datastore.manager.PrimaryDataStoreProviderManagerImpl.storageMgr;
 nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'storageManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: protected com.cloud.agent.AgentManager
 com.cloud.storage.StorageManagerImpl._agentMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'clusteredAgentManagerImpl': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: protected com.cloud.ha.HighAvailabilityManager
 com.cloud.agent.manager.AgentManagerImpl._haMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'highAvailabilityManagerExtImpl': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: com.cloud.alert.AlertManager
 com.cloud.ha.HighAvailabilityManagerImpl._alertMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'alertManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: protected com.cloud.capacity.CapacityManager
 com.cloud.alert.AlertManagerImpl._capacityMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'capacityManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: com.cloud.resource.ResourceManager
 com.cloud.capacity.CapacityManagerImpl._resourceMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'resourceManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: 

Re: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)

[Mike Tutkowski]

In fact, the JIRA ticket is listed as Minor. At this point in 4.6, I
don't think we want to merge in code for tickets listed as Minor.

Perhaps Remi can confirm or deny that.

On Sun, Aug 30, 2015 at 11:03 PM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 I would say, yeah, revert it. Daan and I did a visual walk through of the
 code, but I don't think either of us did a build and tried to run it. I
 thought the tests said they were good on Travis, though.

 On Sun, Aug 30, 2015 at 10:57 PM, Koushik Das koushik@citrix.com
 wrote:

 I am no longer able to start MS after this. I did a clean build followed
 by starting MS. Did travis pass for it? Should we revert?

  mvn clean install -Dsimulator -DskipTests
  mvn -pl client jetty:run -Dsimulator

 Getting the following error. No qualifying bean of type
 [com.cloud.network.element.HAProxyLBRule] found for dependency: expected at
 least 1 bean which qualifies as autowire candidate for this dependency.

 2015-08-31 09:51:29.195:WARN::Nested in
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'accountManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: private com.cloud.storage.dao.VMTemplateDao
 com.cloud.user.AccountManagerImpl._templateDao; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'VMTemplateDaoImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: org.apache.cloudstack.storage.datastore.db.TemplateDataStoreDao
 com.cloud.storage.dao.VMTemplateDaoImpl._templateDataStoreDao; nested
 exception is org.springframework.beans.factory.BeanCreationException: Error
 creating bean with name 'templateDataStoreDaoImpl': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: private
 org.apache.cloudstack.engine.subsystem.api.storage.DataStoreManager
 org.apache.cloudstack.storage.image.db.TemplateDataStoreDaoImpl._storeMgr;
 nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'dataStoreProviderManager': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field:
 org.apache.cloudstack.storage.datastore.PrimaryDataStoreProviderManager
 org.apache.cloudstack.storage.datastore.provider.DataStoreProviderManagerImpl.primaryDataStoreProviderMgr;
 nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'primaryDataStoreProviderMgr': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: com.cloud.storage.StorageManager
 org.apache.cloudstack.storage.datastore.manager.PrimaryDataStoreProviderManagerImpl.storageMgr;
 nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'storageManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: protected com.cloud.agent.AgentManager
 com.cloud.storage.StorageManagerImpl._agentMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'clusteredAgentManagerImpl': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: protected com.cloud.ha.HighAvailabilityManager
 com.cloud.agent.manager.AgentManagerImpl._haMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'highAvailabilityManagerExtImpl': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: com.cloud.alert.AlertManager
 com.cloud.ha.HighAvailabilityManagerImpl._alertMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'alertManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: protected com.cloud.capacity.CapacityManager
 com.cloud.alert.AlertManagerImpl._capacityMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'capacityManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: com.cloud.resource.ResourceManager
 com.cloud.capacity.CapacityManagerImpl._resourceMgr; nested exception 

Re: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)

[Remi Bergsma]

I say we revert so the 4.6 testing can continue and then work on fixing why 
this broke the build. No hard feelings, we simply need master to build. 

If someone can revert, please do. I can do it in about two hours. 

Sent from my iPhone

 On 31 Aug 2015, at 06:58, Koushik Das koushik@citrix.com wrote:
 
 I am no longer able to start MS after this. I did a clean build followed by 
 starting MS. Did travis pass for it? Should we revert? 
 
 mvn clean install -Dsimulator -DskipTests
 mvn -pl client jetty:run -Dsimulator
 
 Getting the following error. No qualifying bean of type 
 [com.cloud.network.element.HAProxyLBRule] found for dependency: expected at 
 least 1 bean which qualifies as autowire candidate for this dependency.
 
 2015-08-31 09:51:29.195:WARN::Nested in 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'accountManagerImpl': Injection of autowired dependencies failed; 
 nested exception is org.springframework.beans.factory.BeanCreationException: 
 Could not autowire field: private com.cloud.storage.dao.VMTemplateDao 
 com.cloud.user.AccountManagerImpl._templateDao; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'VMTemplateDaoImpl': Injection of autowired dependencies failed; 
 nested exception is org.springframework.beans.factory.BeanCreationException: 
 Could not autowire field: 
 org.apache.cloudstack.storage.datastore.db.TemplateDataStoreDao 
 com.cloud.storage.dao.VMTemplateDaoImpl._templateDataStoreDao; nested 
 exception is org.springframework.beans.factory.BeanCreationException: Error 
 creating bean with name 'templateDataStoreDaoImpl': Injection of autowired 
 dependencies failed; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Could not autowire 
 field: private 
 org.apache.cloudstack.engine.subsystem.api.storage.DataStoreManager 
 org.apache.cloudstack.storage.image.db.TemplateDataStoreDaoImpl._storeMgr; 
 nested exception is org.springframework.beans.factory.BeanCreationException: 
 Error creating bean with name 'dataStoreProviderManager': Injection of 
 autowired dependencies failed; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Could not autowire 
 field: 
 org.apache.cloudstack.storage.datastore.PrimaryDataStoreProviderManager 
 org.apache.cloudstack.storage.datastore.provider.DataStoreProviderManagerImpl.primaryDataStoreProviderMgr;
  nested exception is org.springframework.beans.factory.BeanCreationException: 
 Error creating bean with name 'primaryDataStoreProviderMgr': Injection of 
 autowired dependencies failed; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Could not autowire 
 field: com.cloud.storage.StorageManager 
 org.apache.cloudstack.storage.datastore.manager.PrimaryDataStoreProviderManagerImpl.storageMgr;
  nested exception is org.springframework.beans.factory.BeanCreationException: 
 Error creating bean with name 'storageManagerImpl': Injection of autowired 
 dependencies failed; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Could not autowire 
 field: protected com.cloud.agent.AgentManager 
 com.cloud.storage.StorageManagerImpl._agentMgr; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'clusteredAgentManagerImpl': Injection of autowired dependencies 
 failed; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Could not autowire 
 field: protected com.cloud.ha.HighAvailabilityManager 
 com.cloud.agent.manager.AgentManagerImpl._haMgr; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'highAvailabilityManagerExtImpl': Injection of autowired 
 dependencies failed; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Could not autowire 
 field: com.cloud.alert.AlertManager 
 com.cloud.ha.HighAvailabilityManagerImpl._alertMgr; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'alertManagerImpl': Injection of autowired dependencies failed; 
 nested exception is org.springframework.beans.factory.BeanCreationException: 
 Could not autowire field: protected com.cloud.capacity.CapacityManager 
 com.cloud.alert.AlertManagerImpl._capacityMgr; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'capacityManagerImpl': Injection of autowired dependencies failed; 
 nested exception is org.springframework.beans.factory.BeanCreationException: 
 Could not autowire field: com.cloud.resource.ResourceManager 
 com.cloud.capacity.CapacityManagerImpl._resourceMgr; nested exception is 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'resourceManagerImpl': Injection of autowired dependencies failed; 
 nested exception 

Re: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)

[Rajani Karuturi]

I am doing a build with revert locally. Will revert once done.

~Rajani

On Mon, Aug 31, 2015 at 11:11 AM, Remi Bergsma rberg...@schubergphilis.com
wrote:

 I say we revert so the 4.6 testing can continue and then work on fixing
 why this broke the build. No hard feelings, we simply need master to build.

 If someone can revert, please do. I can do it in about two hours.

 Sent from my iPhone

  On 31 Aug 2015, at 06:58, Koushik Das koushik@citrix.com wrote:
 
  I am no longer able to start MS after this. I did a clean build followed
 by starting MS. Did travis pass for it? Should we revert?
 
  mvn clean install -Dsimulator -DskipTests
  mvn -pl client jetty:run -Dsimulator
 
  Getting the following error. No qualifying bean of type
 [com.cloud.network.element.HAProxyLBRule] found for dependency: expected at
 least 1 bean which qualifies as autowire candidate for this dependency.
 
  2015-08-31 09:51:29.195:WARN::Nested in
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'accountManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: private com.cloud.storage.dao.VMTemplateDao
 com.cloud.user.AccountManagerImpl._templateDao; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'VMTemplateDaoImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: org.apache.cloudstack.storage.datastore.db.TemplateDataStoreDao
 com.cloud.storage.dao.VMTemplateDaoImpl._templateDataStoreDao; nested
 exception is org.springframework.beans.factory.BeanCreationException: Error
 creating bean with name 'templateDataStoreDaoImpl': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: private
 org.apache.cloudstack.engine.subsystem.api.storage.DataStoreManager
 org.apache.cloudstack.storage.image.db.TemplateDataStoreDaoImpl._storeMgr;
 nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'dataStoreProviderManager': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field:
 org.apache.cloudstack.storage.datastore.PrimaryDataStoreProviderManager
 org.apache.cloudstack.storage.datastore.provider.DataStoreProviderManagerImpl.primaryDataStoreProviderMgr;
 nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'primaryDataStoreProviderMgr': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: com.cloud.storage.StorageManager
 org.apache.cloudstack.storage.datastore.manager.PrimaryDataStoreProviderManagerImpl.storageMgr;
 nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'storageManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: protected com.cloud.agent.AgentManager
 com.cloud.storage.StorageManagerImpl._agentMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'clusteredAgentManagerImpl': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: protected com.cloud.ha.HighAvailabilityManager
 com.cloud.agent.manager.AgentManagerImpl._haMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'highAvailabilityManagerExtImpl': Injection of autowired
 dependencies failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: com.cloud.alert.AlertManager
 com.cloud.ha.HighAvailabilityManagerImpl._alertMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'alertManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: protected com.cloud.capacity.CapacityManager
 com.cloud.alert.AlertManagerImpl._capacityMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'capacityManagerImpl': Injection of autowired dependencies
 failed; nested exception is
 org.springframework.beans.factory.BeanCreationException: Could not autowire
 field: com.cloud.resource.ResourceManager
 com.cloud.capacity.CapacityManagerImpl._resourceMgr; nested exception is
 org.springframework.beans.factory.BeanCreationException: Error