A Team Master fails to start when using Role Filters


  • A team master is not starting / accessible and the master logs show the following exception:
2019-01-15 22:05:50.899+0000 [id=15]    WARNING o.e.jetty.server.HttpChannel#handleException: /teams-master-01/login
    at java.util.Collections$UnmodifiableCollection.addAll(Collections.java:1065)
    at nectar.plugins.rbac.groups.GroupContainerACL.hasPermission(GroupContainerACL.java:234)
    at nectar.plugins.rbac.groups.GroupContainerACL._hasPermission(GroupContainerACL.java:123)
    at nectar.plugins.rbac.groups.GroupContainerACL.hasPermission(GroupContainerACL.java:76)
    at com.cloudbees.opscenter.bluesteel.security.GlobalAdminACL.hasPermission(GlobalAdminACL.java:46)
    at hudson.security.ACL.checkPermission(ACL.java:72)
    at hudson.security.AccessControlled.checkPermission(AccessControlled.java:47)
    at jenkins.model.Jenkins.getTarget(Jenkins.java:4643)


Related Issue(s)

  • CORE-1479


This issue is caused by role filters that are defined at the Team Master item level in Operations Center. Roles filters are not supported by Team Master at the moment.


The solution is to remove the role filters and restart the Team Master.

To configure the role filters of a team master, click the black arrow next the to the team master’s name and select Roles:

Then select Filter

Deselect all roles and hit “Apply”.

Have more questions? Submit a request


Please sign in to leave a comment.