Describe the bug

We run the SCB with nikto in our kubernetes cluster. When the nikto scan does not find an robot.txt it seems, that no file containing findings is created. Then the lurker tries to open that file, but fails. Therefore the corresponding pod fails and opens a new pod to scans the target again. The scan itself runs perfectly.

Steps To Reproduce

Run a nikto scan on a website, which has no robots.txt .

Expected behavior

When no robot.txt is found then there should be a findings file created with the content, that no robot.txt was found. Then the lurker should be able to read that file and the pod is running successful.

System (please complete the following information):

Kubernetes Version 1.22
SCB Operator 3.12.0
Nikto Scanner 3.12.0

Additional context

Logs of a failed pod. This logs are from the lurker:

2022/06/27 13:03:57 Starting lurker
2022/06/27 13:03:57 Waiting for main container 'nikto' to complete
2022/06/27 13:03:57 After scan is completed file '/home/securecodebox/nikto-results.json' will be uploaded to .... (The destination name was removed)
2022/06/27 13:03:57 Waiting for maincontainer to exit.
2022/06/27 13:04:02 Main Container exited. Lurker will end as well.
2022/06/27 13:04:02 Uploading result files.
2022/06/27 13:04:02 Uploading /home/securecodebox/nikto-results.json
2022/06/27 13:04:02 File has a size of 0 bytes
2022/06/27 13:04:02 Failed to read file
2022/06/27 13:04:02 open /home/securecodebox/nikto-results.json: no such file or directory