Bug 1371922

Summary:	Can't see build log of failed build
Product:	[Internal] Red Hat Internal Copr	Reporter:	Matej Habrnal <mhabrnal>
Component:	builder	Assignee:	Pavel Raiskup <praiskup>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-18 09:03:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1306183
Bug Blocks:

Description Matej Habrnal 2016-08-31 12:38:24 UTC

Description of problem:
I wanted to see build log of failed build [1] and Chroot Details link responded to me with 404:

Not Found

The requested URL /results/abrt/rhel-7-dogfooding/rhel-7.dev-x86_64/00004720-abrt was not found on this server.

[1] https://copr.devel.redhat.com/coprs/abrt/rhel-7-dogfooding/build/4720/

Comment 1 Pavel Raiskup 2016-09-01 04:59:33 UTC

The build log was garbage-collected (iow: logs were available and disappeared
after some time), is that right?

I've disabled this by "hot-fix" but this deserves upgrade to newer copr
release because it has been fixed upstream some time ago.

Comment 2 Matej Habrnal 2016-09-01 08:01:24 UTC

> The build log was garbage-collected (iow: logs were available and disappeared
> after some time), is that right?
>
The build logs aren't available even during the build.

Comment 3 Pavel Raiskup 2016-09-01 08:25:22 UTC

Right, different issue.  Backend stopped to work for some reason, we are
up2running again.  I'll keep the "hot-fix" from comment #1 active and this
bug open till the next copr rebase.

Comment 4 Pavel Raiskup 2018-09-18 09:03:06 UTC

Fixed for quite some time.