ViPR Controller: Associating a project to a vNAS server results in a Service Unavailable (6503) error


   Article Number:     523854                                   Article Version: 3     Article Type:    Break Fix 




ViPR Controller,ViPR Controller Controller 3.6 SP1





When a new project is associated to a vNAS server that already has a number of associated projects, the process is successful.   
    However, when the vNAS server drop-down is clicked to show the vNAS information a "Service Unavailable (6503)" error is displayed.   
    This may prevent further projects from being associated to the vNAS server via the ViPR UI.   







This is a ViPR UI rendering issue.   
    When the vNAS server page is opened the ViPR UI loads the vNAS server information from the ViPR DB into vNAS data table and renders the page.   
    While loading vNAS server information the vNAS server ID is concatenated with the projects names which are associated to the vNAS server.   
    With a large number of projects assigned, whose names when concatenated form a large string, this can exceed the HTTP payload limit of 4096 bytes.   
    This large payload results in the UI not being able to process the request.







      The "viprcli vnasserver assign" command can be used to associate a project to the vNAS server.     
      The "Service Unavailable (6503)" error will remain in the UI but this does not affect provisioning/exporting File Systems.     
      ViPR Engineering is currently addressing this problem, but has not provided a fix in a released patch. This solution will be updated with the patch when it has been released.   







From the ViPR portalsvc logs the following error may be seen:   

      vipr1 xxx-xxx-vpr001 portalsvc 2018-07-06 09:09:50,027 [New I/O server worker #2-3] ERROR (line 604) org.jboss.netty.handler.codec.frame.TooLongFrameException: An HTTP line is larger than 4096 bytes. at org.jboss.netty.handler.codec.http.HttpMessageDecoder.readLine(