Re: Fedora 33 blocker status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2020-09-18 at 16:10 -0400, Ben Cotton wrote:
> 4. abrt  https://bugzilla.redhat.com/show_bug.cgi?id=1878317 —; NEW
> Can't report a crash (even with local processing) due to "Could not
> resolve host: retrace.fedoraproject.org"
> 
> Since the retrace server is still offline, abrt should fall back to
> local processing. It does not.

This is not quite an accurate description. If you get to the actual
backtrace generation action, fallback from the remote server to local
processing *does* work. The problem is that report_uReport tries to run
*before you ever reach that stage*, and report_uReport can only work if
retrace.fedoraproject.org is up and accepting reports. There's no
fallback for report_uReport.

Arguably, it failing should be non-fatal, but it seems like it's fatal.

>  As an unprivileged user, skipping the
> report_uReport step results in chmod errors and behavior like BZ
> 1873029. As root, it core dumps.

For me, anyway. Would be good if others could confirm.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux