Description of problem: Not able to access log files. http://slave25.cloud.gluster.org/logs/glusterfs-logs-20160816:07:48:59.tgz Getting "404 Not Found" error. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
So, I dug into this. For whatever reason, the logs weren't on the machine :( We need to do better than this for our job logs.
The logs for NetBSD is also not available. http://nbslave74.cloud.gluster.org/archives/logs/glusterfs-logs-20160812083125.tgz https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/18672/consoleFull
http://nbslave74.cloud.gluster.org/logs/glusterfs-logs-20160812083125.tgz Fixing the netbsd logs involve a long chain of dependencies. I need to get netbsd's changes incorporated into master. And then make it run the latest version of regression.sh, which has the code to generate the right URL. I've put things in motion, it'll take some time. This immediate problem on centos was a result of my mistake (see https://github.com/gluster/glusterfs-patch-acceptance-tests/commit/255cf2197287cab1ece59bf170b47e8925c46219). It's been fixed and the new code pushed to all online centos servers.