The previous check would always fail due to multiple mistakes in the command:
not using sudo
-d ("is directory) instead of -e ("does this file/directory exist")
The use of '/' at the end of the string that is supposed to be the path of a file and not a directory
This would cause the check to always fail and rerun the TLS certification setup, which is both a waste of time and a potential cause of errors - rerunning the TLS certification setup invalidates the previous certificate, which in turn could cause unexpected SSL errors .
The previous check would always fail due to multiple mistakes in the command:
-d
("is directory) instead of-e
("does this file/directory exist")This would cause the check to always fail and rerun the TLS certification setup, which is both a waste of time and a potential cause of errors - rerunning the TLS certification setup invalidates the previous certificate, which in turn could cause unexpected SSL errors .
Here are the passing logs of the existing tests: https://privatebin.corp.redhat.com/?44159f8535cd5486#CZLJ9aHpLQ8tS8iBh6h5SZmbvDCCsgHEc8hptprTCBJk