Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1545
@wido the Trillian env failed to run the tests for your latest PR due to
following error:
2016-11-21 09:59:54,000 INFO [cloud.agent.AgentShell] (main:null) (logid:)
Agent started
2016-11-21 09:59:54,005 INFO [cloud.agent.AgentShell] (main:null) (logid:)
Implementation Version is 4.10.0.0-SNAPSHOT
2016-11-21 09:59:54,007 INFO [cloud.agent.AgentShell] (main:null) (logid:)
agent.properties found at /etc/cloudstack/agent/agent.properties
2016-11-21 09:59:54,013 INFO [cloud.agent.AgentShell] (main:null) (logid:)
Defaulting to using properties file for storage
2016-11-21 09:59:54,016 INFO [cloud.agent.AgentShell] (main:null) (logid:)
Defaulting to the constant time backoff algorithm
2016-11-21 09:59:54,035 INFO [cloud.utils.LogUtils] (main:null) (logid:)
log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2016-11-21 09:59:54,050 INFO [cloud.agent.AgentShell] (main:null) (logid:)
Using default Java settings for IPv6 preference for agent connection
2016-11-21 09:59:54,211 INFO [cloud.agent.Agent] (main:null) (logid:) id is
2016-11-21 09:59:54,251 ERROR [cloud.agent.AgentShell] (main:null) (logid:)
Unable to start agent:
java.lang.NullPointerException
at java.io.File.<init>(File.java:277)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:786)
at com.cloud.agent.Agent.<init>(Agent.java:165)
at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:397)
at
com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:367)
at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:351)
at com.cloud.agent.AgentShell.start(AgentShell.java:456)
at com.cloud.agent.AgentShell.main(AgentShell.java:491)
Please modify the code to still work where an explicit path may not be
defined, and that with your change KVM agent would run on CentOS6/7. Thanks.
/cc @jburwell
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
