#5544 Koji web server returns 403 on accessing a build log
Closed: Upstream 7 years ago Opened 7 years ago by ppisar.

This scratch build made by Koschei http://koji.fedoraproject.org/koji/taskinfo?taskID=16218669 has build logs, e.g. aarch64/build.log https://kojipkgs.fedoraproject.org//work/tasks/8670/16218670/build.log that cannot be retrieved because of permission misconfiguration. The server returns 403:

Forbidden
You don't have permission to access /work/tasks/8670/16218670/build.log on this server.


So the issue(s) here:

  • koschei logs are cleaned up after 1 day, so the build.log is already gone. There is just a broken link there to where it used to be.

  • Normally koji-gc would clean up the directory of links too and the interface would just not show any logs available, however, in this case for some reason the 'mock_output.log' still exists so the directory cannot be removed.

So, I think the best thing to do here is file a issue against koji to fix koji-gc to clean up mock_output.log as well. If we need / desire to change the koschei logs time we can do that here.
Would you be willing to file on koji, or would you prefer I do so?

On Wed, Nov 02, 2016 at 05:42:41PM +0000, Kevin Fenzi wrote:

So, I think the best thing to do here is file a issue against koji to fix
koji-gc to clean up mock_output.log as well. If we need / desire to change
the koschei logs time we can do that here. Would you be willing to file on
koji, or would you prefer I do so? ``

I don't understand koji internals, please you do the report.

I think 1 day for logs is terribly short time. Packager gets a notification
about broken build and next day the log is unavailable. Pretty useless
service.

-- Petr

Filed:

https://pagure.io/koji/issue/207
(for the koji gc bug)

and

https://pagure.io/releng/issue/130
(to increase timeout on koschi logs)

@kevin changed the status to Closed

7 years ago

Login to comment on this ticket.

Metadata