[AAA-117] C: rpc on isolated node should not return status code 401, expected is 501 Created: 14/Feb/17 Updated: 21/Mar/19 Resolved: 07/Feb/18 |
|
| Status: | Resolved |
| Project: | aaa |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Peter Gubka | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7792 |
| Description |
|
The issue is observed in https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/585/archives/robot-plugin/log.html.gz#s1-s9 After the isolation of the leader, the rpc was run on isolated leader. 2017-02-14 04:41:16,456 | INFO | h for user karaf | command | 46 - org.apache.karaf.log.command - 3.0.8 | ROBOT MESSAGE: Starting test Rpc_On_Isolated_Node |
| Comments |
| Comment by Tomas Cere [ 14/Feb/17 ] |
|
Minor clarification, in manual testing it seems that on an isolated node sometimes any restconf request seems to return 401 for some reason. |
| Comment by Tomas Cere [ 12/Oct/17 ] |
|
I think this 401 has more to do with aaa not having the datastore available on the isolated node, hence it cannot do whatever it wants to do with the datastore and just fails the authentification. |
| Comment by Ryan Goulding [ 07/Feb/18 ] |
|
Functions as designed. Closing. |