Observed with the ps-indicators-autopilot-release job for all 3 machines
(http://10.97.0.1:8080/view/autopilot/job/ps-indicators-autopilot-release-testing/183/)
Excerpt from the log (http://10.97.0.1:8080/view/autopilot/job/ps-indicators-autopilot-release-testing/183/label=autopilot-ati/console):
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/utah/run.py", line 240, in run_tests
machine.installclient()
File "/usr/lib/python2.7/dist-packages/utah/provisioning/provisioning.py", line 383, in installclient
self.uploadfiles([deb], tmppath)
File "/usr/lib/python2.7/dist-packages/utah/provisioning/ssh.py", line 161, in uploadfiles
self.activecheck()
File "/usr/lib/python2.7/dist-packages/utah/provisioning/ssh.py", line 332, in activecheck
self.provisioncheck()
File "/usr/lib/python2.7/dist-packages/utah/provisioning/provisioning.py", line 294, in provisioncheck
utah.timeout.timeout(config.installtimeout, self._provision)
File "/usr/lib/python2.7/dist-packages/utah/timeout.py", line 77, in timeout
retval = command(*args, **kw)
File "/usr/lib/python2.7/dist-packages/utah/provisioning/provisioning.py", line 426, in _provision
self._create()
File "/usr/lib/python2.7/dist-packages/utah/provisioning/baremetal/cobbler.py", line 197, in _create
self._disable_netboot)
File "/usr/lib/python2.7/dist-packages/utah/provisioning/rsyslog.py", line 85, in wait_for_install
self._wait_for_steps(steps, logfile, callbacks)
File "/usr/lib/python2.7/dist-packages/utah/provisioning/rsyslog.py", line 97, in _wait_for_steps
with open(logfile, 'w') as f:
IOError: [Errno 13] Permission denied: '/var/log/utah/dx-autopilot-ati-install.log'
Jean Baptiste change the permissions in the file and the job has been
relaunched again so the testing isn't blocked.
The file already existed with user and group utah without write permissions for
the group and that was causing the permission problem for user jenkins and
group utah.
The reason the file was created with a different user is unknown. I believe
maybe it was created when trying to reproduce a problem in the lab and was left
there.
Anyway, I believe this should be solved with configuration, that is, this log file should be
created in the jenkins job workspace.