You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by johnmccabe <gi...@git.apache.org> on 2016/06/01 10:47:26 UTC

[GitHub] brooklyn-server pull request: BROOKLYN-259: Fix JcloudsByonLocationResolver

Github user johnmccabe commented on the pull request:

    https://github.com/apache/brooklyn-server/pull/132
  
    Hi @aledsage, sorry for the delay getting back to you, the env I had originally observed this on is still inaccessible so I had to recreate, unfortunately, still seeing an NPE when attempting to deploy to the following location (`userCredentials.getUser()` again):
    ```
    brooklyn.location.named.my-jclouds-byon=jcloudsByon:(provider="cloudstack",endpoint="https://my-cloudstack-endpoint.domain.com/client/api",region="my-region-id",networkName="my-network-id",user="root",password="supersecretrootpassword",hosts="my-existing-host-id")
    brooklyn.location.named.my-jclouds-byon.identity=MY_API_KEY
    brooklyn.location.named.my-jclouds-byon.credential=MY_SECRET_KEY
    ```
    
    ```
    2016-06-01 11:30:04,141 WARN  o.a.b.c.m.i.LocalLocationManager [brooklyn-execmanager-qQtAY4JU-1]: Failed to create location using spec LocationSpec{type=class org.apache.brooklyn.location.byon.FixedListMachineProvisioningLocation}@33a9098e (rethrowing)
    java.lang.NullPointerException: null
            at org.apache.brooklyn.location.jclouds.JcloudsLocation.createJcloudsSshMachineLocation(JcloudsLocation.java:2319) ~[brooklyn-locations-jclouds-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at org.apache.brooklyn.location.jclouds.JcloudsLocation.registerJcloudsSshMachineLocation(JcloudsLocation.java:2255) ~[brooklyn-locations-jclouds-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at org.apache.brooklyn.location.jclouds.JcloudsLocation.registerMachineLocation(JcloudsLocation.java:2106) ~[brooklyn-locations-jclouds-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at org.apache.brooklyn.location.jclouds.JcloudsLocation.registerMachine(JcloudsLocation.java:2097) ~[brooklyn-locations-jclouds-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at org.apache.brooklyn.location.jclouds.JcloudsByonLocationResolver$1.get(JcloudsByonLocationResolver.java:156) ~[brooklyn-locations-jclouds-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at org.apache.brooklyn.location.jclouds.JcloudsByonLocationResolver$1.get(JcloudsByonLocationResolver.java:147) ~[brooklyn-locations-jclouds-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at org.apache.brooklyn.location.byon.FixedListMachineProvisioningLocation.init(FixedListMachineProvisioningLocation.java:173) ~[brooklyn-core-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at org.apache.brooklyn.core.objs.proxy.InternalLocationFactory.createLocation(InternalLocationFactory.java:137) ~[brooklyn-core-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at org.apache.brooklyn.core.mgmt.internal.LocalLocationManager.createLocation(LocalLocationManager.java:94) ~[brooklyn-core-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at org.apache.brooklyn.core.objs.proxy.InternalEntityFactory$1.run(InternalEntityFactory.java:331) [brooklyn-core-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_79]
            at org.apache.brooklyn.util.core.task.BasicExecutionManager$SubmissionCallable.call(BasicExecutionManager.java:519) [brooklyn-core-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
            at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_79]
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_79]
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_79]
            at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
    ```
    I'm going to rebuild to sanity check my install (I've built clocker against the #132 brooklyn-server branch).


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---