Closed tmzullinger closed 1 year ago
Or now that I think about it, possibly a transient error due to the planned outage of various Fedora services. Though in that case, it would still be good to report this in some way other than tossing a traceback into bugzilla. ;)
The traceback is generated every time we don't know what exactly happened. If the error is something we can recover from it's gracefully handled. Before the traceback was attached to bugzilla issue, it was hard to troubleshoot the issues.
I will look if this occured multiple times.
It seems that this was just a rare occurence, I don't see any other failing scratch build in the logs with the same error. Not sure what happened in this case, but if this was really a bug, it would happen on every scratch build.
Closing this.
In rhbz#2208089, the-new-hotness raised this error while trying to run a scratch build:
Perhaps this is due to a recent RHEL upgrade or something?