follower reports 401 (unauthorized) and 500 (Internal Error) when leader is isolated. (CONTROLLER-1838)

[CONTROLLER-1842] don't exclude the polling cycles of WUKS in robot suites Created: 22/Jun/18  Updated: 22/Jun/18  Resolved: 22/Jun/18

Status: Resolved
Project: controller
Component/s: clustering
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Medium
Reporter: Jamo Luhrsen Assignee: Jamo Luhrsen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File log.html    

 Description   

We are using the robot flag to not show all the polling cycles of the WUKS
keyword (saves on log output), but we want to see those in this case on the
off chance that we might learn something.

 Comments   
Comment by Jamo Luhrsen [ 22/Jun/18 ]

Attached is the log.html of a job showing where each /restconf/modules fails 5 consecutive times with 5s timeouts each. There doesn't
appear to be anything special about each failure that is different than the final failure which we were only seeing by default.

this is coming from a job using tell-based.

BTW, this is easy to do with existing logs. just pull the robot output.xml file and use the 'rebot' utility (installed when you install
robot framework) to create it. example:

rebot -L TRACE output.xml
Generated at Wed Feb 07 19:56:35 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.