Dashboard 2.2.1.20201105 - Internal server error when accessing User Settings

[jonny-mac]

I have a clean install of 2.2.1 running on Ubuntu 16.04.7 with a default Dashboard configuration, when browsing to the Administration > Users > User Settings page I get an error "Internal server error" printed on a red bar at the top. Downloading the log files and looking in nm-user-service.log shows the following relevant entries:

2020-12-14T16:50:52.716+0000  INFO 20900 --- [http-nio-127.0.0.1-8082-exec-6] c.c.s.n.t.u.m.s.i.m.AbstractUserModel    : Getting session setting for tenant:aio
2020-12-14T16:50:52.742+0000  INFO 20900 --- [http-nio-127.0.0.1-8082-exec-14] c.c.s.n.t.u.m.s.i.c.LocalAuthController  : Querying local auth, ctx: NmExternalRequestContext(correlationId=21fe0a15-52bf-4c3e-a3fc-8268ca3f0009, tenantId=aio, username=admin, userRole=ADMIN, selectedOrgId=null, selectedOrgIds=null, licensePunishment=NORMAL)
2020-12-14T16:50:52.772+0000  INFO 20900 --- [http-nio-127.0.0.1-8082-exec-10] s.n.t.u.m.s.i.c.MicrosoftOAuthController : Querying AD OAuth, ctx: NmExternalRequestContext(correlationId=4ebe3b3a-667b-4b50-95ef-f1223495fa5f, tenantId=aio, username=admin, userRole=ADMIN, selectedOrgId=null, selectedOrgIds=null, licensePunishment=NORMAL)
2020-12-14T16:50:52.794+0000 ERROR 20900 --- [http-nio-127.0.0.1-8082-exec-10] c.c.s.n.t.u.m.s.i.s.PlatformService      : failed to call platform service to get backup data, <500,HttpJsonResult(success=false, errorCode=operations.on.platform.settings.are.not.applicable, errorMessage=null, data=null, errorData=null),[Content-Type:"application/json;charset=UTF-8", Transfer-Encoding:"chunked", Date:"Mon, 14 Dec 2020 16:50:52 GMT", Connection:"close"]>
2020-12-14T16:50:52.795+0000 ERROR 20900 --- [http-nio-127.0.0.1-8082-exec-10] .u.m.s.i.c.NmUserServiceControllerAdvice : NmRuntimeException for /u/auth/microsoft
com.cisco.smb.nm.common.error.NmInternalServerErrorException: 500; internal-server-error; null; null
    at com.cisco.smb.nm.tenant.user.manager.service.impl.service.PlatformService.getPlatformSetting(PlatformService.java:38)
    at com.cisco.smb.nm.tenant.user.manager.service.impl.controller.MicrosoftOAuthController.doGetHostAndPort(MicrosoftOAuthController.java:210)
    at com.cisco.smb.nm.tenant.user.manager.service.impl.controller.MicrosoftOAuthController._dto(MicrosoftOAuthController.java:229)
    at com.cisco.smb.nm.tenant.user.manager.service.impl.controller.MicrosoftOAuthController.query(MicrosoftOAuthController.java:105)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190)
    at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138)
    at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105)
    at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:892)
    at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:797)
    at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006)
    at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
    at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)

I haven't configured any Azure AD authentication (though I would like to, which is why I am here). 

[David Harper]

Is this using a Cisco VM image, or is CBD installed on a generic Ubuntu install?

Cheers,

Dave.

[jonny-mac]

Hi Dave,

This is running on the Ubuntu 16.04 image on Azure - https://azuremarketplace.microsoft.com/en-us/marketplace/apps/Canonical.UbuntuServer

[David Harper]

Ok, thanks.  The engineering team have reproduced this in the lab and are looking into the root cause.  As soon as we get to the bottom of this, I'll let you know.  I believe you have a TAC case open as well, right?  We will keep that side updated as well.

Cheers,

Dave.

[jonny-mac]

Yes, that's my TAC case. I'm happy to close that case as there's not really anything that support can do - I'll keep an eye on the release notes and update this post when I've had a chance to deploy a fixed release.

[David Harper]

In general, a TAC case is the best way to get support.  The support communities here are really best effort.  We do try very hard to stay on top of what comes in and be responsive, but it is dependent on the efforts of the individuals.  The TAC is the formal support channel and they have guarenteed response times and automatic escalation processes when a problem is not resolved in a timely fashion.  So if you have an issue that is in any way urgent, you should always log a case.

In  this particular instance, we'll continue to update this thread so that anyone else who runs across it can see the history and the resolution, but there is no problem with keeping the case open.  And keeping it open means that the TAC engineer won't allow us to drop the ball on getting a fix to you.

Cheers,

Dave.

[jonny-mac · Accepted solution]

2.2.2 was released on 11th Jan and has fixed this issue.

[David Harper]

You beat me to it.   But yes, you are correct, the 2.2.2 build does indeed fix this problem.

Cheers,

Dave.