[ 
https://issues.apache.org/jira/browse/NIFI-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019429#comment-16019429
 ] 

Fredrik Sko commented on NIFI-3616:
-----------------------------------

Just upgraded to 1.2.0, and the issue is unfortunately still present.

> Flushing and listing queues becomes unavailable when running clusters
> ---------------------------------------------------------------------
>
>                 Key: NIFI-3616
>                 URL: https://issues.apache.org/jira/browse/NIFI-3616
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 1.2.0, 1.1.1
>         Environment: OS: Ubuntu 16.04.2, 4.4.0-66-generic
> Java: 1.8.0_121 (openjdk-8-jre-headless)
> Issue confirmed on both physical and virtual platforms.
>            Reporter: Fredrik Sko
>              Labels: cluster
>         Attachments: Screen Shot 2017-03-16 at 18.13.53.png
>
>
> When setting up a new cluster with NiFi 1.1.2 (which is not available under 
> "Affect version/s"), it is not possible to flush or list queues in 
> connections.
> See attached screenshots for error message.
> Procedure for reproducing:
> 1) Set up a new cluster with i.e. 3 nodes
> 2) Grant yourself necessary policies for the root process group\[0\].
> 3) Create two funnels
> 4) Create a connection between those funnels
> 5) Right click on the connection and choose "List queue". This produces the 
> error message "Unable to perform the desired action due to insufficient 
> permissions. Contact the system administrator.". The same thing will happen 
> if you try to empty the queue (even when empty).
> In my test setup I currently have some flowfiles in one of the connections, 
> and have yet to find a workaround allowing me to empty it.
> The following error message is produced in {{nifi-app.log}} on all nodes:
> {code}2017-03-16 13:37:03,141 INFO [NiFi Web Server-509] 
> o.a.n.w.a.c.AccessDeniedExceptionMapper EMAILADDRESS=XXX, CN=XXX, C=XX does 
> not have permission to access the requested resource. Returning Forbidden 
> response.{code}
> Starting a single node instance repeating the exact steps above does not 
> produce this error.
> Please let me know if further information or files are needed.
> \[0\]: "View the component", "Modify the component", "View the data", "Modify 
> the data".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to