action #17408
Updated by asmorodskyi about 7 years ago
**Observation** A test in openQA is incomplete, even if every module passes. **Steps to reproduce** * Change the ownership of e.g. /var/lib/openqa/share/factory/hdd to something so that the "_openqa-worker" user is not allowed to write to this path. * Start any test with PUBLISH_HDD_1 variable * All modules will pass but overall status will be "incomplete" and no errors in os-autoinst.log openQA web interface * Only worker log will have permissions error Observe how the test fails (shows incomplete at the end) even if the web interface shows "passed" on every module **Problem** If an openqa-worker fails to write to the hard drive, the web interface does not show any hint, why a test is incomplete. Syslog shows an entry stating "Permission denied" but this could be a problem on live instances of openQA where an testing engineer may not be able to access the logs of the openqa-worker process. **Possible solutions** A suggestion of mine would be to provide some sort of message in the web ui, stating why a test is "incomplete". It would be also nice, if the log of the worker can be somehow investigated over the web interface. This, of course, depends on how critical/secret the information is that are written to the log by openqa-worker.