[
https://issues.apache.org/jira/browse/CLOUDSTACK-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Yadav resolved CLOUDSTACK-1003.
-------------------------------------
Resolution: Invalid
Why not fix it the right way? We've moved on from waf, for 4.1 you should not
depend on waf and the old way of packaging is highly discouraged.
If you want you should fix the rpm build on master for 4.1, this issue is
invalid as the description and summary don't suggest the issue is with
packaging, only comment suggest that the issue is with packaging on one's
personal tree and not on master.
> Failed to start management server with master build
> ---------------------------------------------------
>
> Key: CLOUDSTACK-1003
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1003
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Install and Setup
> Affects Versions: 4.1.0
> Environment: Centos 6.0.3
> Reporter: Rayees Namathponnan
> Assignee: Pradeep Soundararajan
> Priority: Blocker
> Attachments: catalina.out
>
>
> Observed below error in MS log
> INFO [cloud.server.ConfigurationServerImpl] (main:) Processing
> updateSSLKeyStore
> INFO [cloud.server.ConfigurationServerImpl] (main:) SSL keystore located at
> /etc/cloud/management/cloud.keystore
> INFO [cloud.server.ConfigurationServerImpl] (main:) Processing updateKeyPairs
> INFO [cloud.server.ConfigurationServerImpl] (main:) Systemvm keypairs not
> found in database. Need to store them in the database
> INFO [cloud.server.ConfigurationServerImpl] (main:) Going to update systemvm
> iso with generated keypairs if needed
> INFO [utils.component.ComponentLocator] (main:) Config file found at
> /etc/cloud/management/components.xml. Configuring management-server
> INFO [utils.component.ComponentLocator] (main:) Found component:
> com.cloud.configuration.dao.ConfigurationDao in
> com.cloud.configuration.dao.ConfigurationDaoImpl - Configuration
> configuration server
> ERROR [utils.component.ComponentLocator] (main:) Unable to load configuration
> for management-server from components.xml
> com.cloud.utils.exception.CloudRuntimeException: Unable to find class:
> org.apache.cloudstack.acl.StaticRoleBasedAPIAccessChecker
> at
> com.cloud.utils.component.ComponentLocator$XmlHandler.fillInfo(ComponentLocator.java:1028)
> at
> com.cloud.utils.component.ComponentLocator$XmlHandler.startElement(ComponentLocator.java:1089)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
> Source)
> at
> org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
