runlogwatch fails and stops if LOG_DIR does not exist

[elfosardo]

When running a deployment if the LOG_DIR set in runlogwatch.sh does not exist, the script exits and does not run again making it impossible to recover ramdisk logs.

For example:

[2025-02-04 11:46:35,252 pyinotify DEBUG] Start monitoring ['/shared/log/ironic/deploy'], (press c^c to halt pyinotify)
[2025-02-04 11:46:35,252 pyinotify ERROR] add_watch: cannot watch /shared/log/ironic/deploy WD=-1, Errno=No such file or directory (ENOENT)

[metal3-io-bot]

This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.