Github user aledsage commented on the issue:

    https://github.com/apache/brooklyn-server/pull/778
  
    Note the test failures are real, e.g.:
    ```
    java.lang.UnsupportedOperationException: Call to 'config[]' not permitted 
on read-only entity Application[41jsve4k]
        at 
org.apache.brooklyn.core.objs.proxy.EntityProxyImpl.invoke(EntityProxyImpl.java:198)
        at com.sun.proxy.$Proxy18.config(Unknown Source)
        at 
org.apache.brooklyn.core.mgmt.internal.LocalEntityManager.tryGetDeploymentUid(LocalEntityManager.java:899)
        at 
org.apache.brooklyn.core.mgmt.internal.LocalEntityManager.unmanage(LocalEntityManager.java:449)
        at 
org.apache.brooklyn.core.mgmt.internal.LocalEntityManager.unmanage(LocalEntityManager.java:443)
        at 
org.apache.brooklyn.core.mgmt.ha.HighAvailabilityManagerImpl.clearManagedItems(HighAvailabilityManagerImpl.java:923)
        at 
org.apache.brooklyn.core.mgmt.ha.HighAvailabilityManagerImpl.setInternalNodeState(HighAvailabilityManagerImpl.java:529)
        at 
org.apache.brooklyn.core.mgmt.ha.HighAvailabilityManagerImpl.stop(HighAvailabilityManagerImpl.java:489)
        at 
org.apache.brooklyn.core.mgmt.ha.HighAvailabilityManagerImpl.stop(HighAvailabilityManagerImpl.java:482)
        at 
org.apache.brooklyn.core.mgmt.ha.HotStandbyTest$HaMgmtNode.tearDownThisOnly(HotStandbyTest.java:116)
        at 
org.apache.brooklyn.core.mgmt.ha.HotStandbyTest$HaMgmtNode.tearDownAll(HotStandbyTest.java:122)
        at 
org.apache.brooklyn.core.mgmt.ha.HotStandbyTest.tearDown(HotStandbyTest.java:154)
    ```
    It is now trying to look up the "deploymentUid" config-key on a standby 
node, which is failing.
    
    If folk think this PR is the right direction, then I'll fix those.
    
    But if people think `&appId=...` is the simpler (and better) way to go, 
then I'll be closing this PR!


---
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.
---

Reply via email to