Not able to assign privileges after upgrading 3.38.x to 3.41.x

Hi Team,
We have upgraded nexus from 3.38.x to 3.41.0. After upgrading, we are not able to assign privileges to roles. We are getting an error as shown in the attachment.
Kindly help us resolve the issue.

Can you look for a stack trace in your nexus.log? It’s hard to know just from the error message exactly what is causing the problem.

Hi , please find the stack trace from the nexus.log,

2022-10-10 16:52:49,314+0000 DEBUG [qtp1518096320-89] admin org.sonatype.nexus.extdirect.internal.ExtDirectDispatcher - Invoking action method: rapture_State.rapture_State_get, java-method: org.sonatype.nexus.rapture.internal.state.StateComponent.getState
2022-10-10 16:52:49,316+0000 DEBUG [qtp1518096320-89] admin org.sonatype.nexus.orient.entity.EntityHook - Unregistering OLiveQueryHook
2022-10-10 16:52:49,316+0000 DEBUG [qtp1518096320-89] admin org.sonatype.nexus.internal.orient.DatabaseManagerImpl - Opened database: component → com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx@340c2273
2022-10-10 16:52:51,633+0000 DEBUG [qtp1518096320-94] admin org.sonatype.nexus.siesta.SiestaServlet - Processing: PUT /service/rest/v1/security/roles/gh-admin?_dc=1665420772043
2022-10-10 16:52:51,636+0000 DEBUG [qtp1518096320-94] admin org.sonatype.nexus.security.role.rest.RoleApiResourceV1 - Privilege All Repositories - (read) in role gh-admin not found
2022-10-10 16:52:52,182+0000 DEBUG [qtp1518096320-89] admin org.sonatype.nexus.extdirect.internal.ExtDirectDispatcher - Creating instance of action class ‘org.sonatype.nexus.rapture.internal.state.StateComponent’ mapped to 'rapture_State
2022-10-10 16:52:52,182+0000 DEBUG [qtp1518096320-89] admin org.sonatype.nexus.extdirect.internal.ExtDirectDispatcher - Invoking action method: rapture_State.rapture_State_get, java-method: org.sonatype.nexus.rapture.internal.state.StateComponent.getState
2022-10-10 16:52:52,184+0000 DEBUG [qtp1518096320-89] admin org.sonatype.nexus.orient.entity.EntityHook - Unregistering OLiveQueryHook
2022-10-10 16:52:52,184+0000 DEBUG [qtp1518096320-89] admin org.sonatype.nexus.internal.orient.DatabaseManagerImpl - Opened database: component → com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx@2ae69462
2022-10-10 16:52:52,598+0000 DEBUG [nexus-httpclient-eviction-thread] *SYSTEM org.sonatype.nexus.internal.httpclient.SharedHttpClientConnectionManager - Closing expired connections
2022-10-10 16:52:52,598+0000 DEBUG [nexus-httpclient-eviction-thread] *SYSTEM org.sonatype.nexus.internal.httpclient.SharedHttpClientConnectionManager - Closing connections idle longer than 30000 MILLISECONDS
2022-10-10 16:52:52,662+0000 DEBUG [qtp1518096320-94] admin org.sonatype.nexus.extdirect.internal.ExtDirectDispatcher - Creating instance of action class ‘org.sonatype.nexus.rapture.internal.state.StateComponent’ mapped to 'rapture_State
2022-10-10 16:52:52,663+0000 DEBUG [qtp1518096320-94] admin org.sonatype.nexus.extdirect.internal.ExtDirectDispatcher - Invoking action method: rapture_State.rapture_State_get, java-method: org.sonatype.nexus.rapture.internal.state.StateComponent.getState
2022-10-10 16:52:52,665+0000 DEBUG [qtp1518096320-94] admin org.sonatype.nexus.orient.entity.EntityHook - Unregistering OLiveQueryHook
2022-10-10 16:52:52,665+0000 DEBUG [qtp1518096320-94] admin org.sonatype.nexus.internal.orient.DatabaseManagerImpl - Opened database: component → com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx@4bfa42c0

I’m not able to duplicate the issue. Unfortunately I don’t see any logging you could turn on to diagnose your problem further either. Digging through the code, that exception should have occurred only if we were unable to identify the privilege, but that doesn’t seem right considering it must have been one of the options in the list.

Hi @mmartz , we found that we are able to assign few privileges like nx-admin etc, however, we are not able to assign privileges starting with “All”, such as “All Repositories(read)”, “All Nuget repositories(write)” etc.
Kindly let us know what to be done to solve this issue.

Hi Himaja,
Can you file your bug report including reproduction steps in our issue tracker, please? Right after you reproduce the bug again on your Nexus Repository, please generate a Support ZIP and include it to your report, so we can see what’s happening on your instance. This way we will be able to prioritise the work, and you will be able to track its progress. Thank you in advance.

Hi @dsawa , we have created jira ticket (URL: Log in - Sonatype JIRA) and added the support zip on ticket.

1 Like

Hi @dsawa , kindly let me know if there is any solution for the issue we are facing (jira ticket number: Log in - Sonatype JIRA)