Bug 1804075
| Summary: | unable to report bug during installation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||||||
| Component: | libreport | Assignee: | ekulik | ||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 32 | CC: | abrt-devel-list, ekulik, jakub, jmilan, lnie, mhabrnal, michal.toman, mkutlak, mmarusak, robatino | ||||||||
| 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: | 2020-02-18 10:30:29 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: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1705303 | ||||||||||
| Attachments: |
|
||||||||||
The message in the screenshot is cut off… Created attachment 1663663 [details]
anaconda.log
Proposed as a Blocker for 32-beta by Fedora user lnie using the blocker tracking app because: This affects: The installer must be able to report failures to Bugzilla, with appropriate information included. Is there anything related in the log file? I can’t see anything. And how are you reproducing the issue? Ah,I thought there might be some useful message in the log.Just noted the bug is reported successfully,but only anaconda-tb is uploaded,https://bugzilla.redhat.com/show_bug.cgi?id=1804066 I tried to create a crash with kill -USR1 `cat /var/run/anaconda.pid` three times( I thought it can be simply reproduced by kill ... ,turns out this reproducer is trickey),and the last time,I reproduced the bug successfully, it seems that you need kill it during anaconda do the storage partition. The reproducer is: try to create an software raid partition,and the bug happens during installation process #1804080 Created attachment 1663709 [details]
screenshot
Able to reproduce, but the reporter seems to work (although it could be because it was detected as duplicate and therefore a new bug was not created). Creating a new bug also worked: https://bugzilla.redhat.com/show_bug.cgi?id=1804150 Both of your screenshots obscure the potentially-useful information (text not being wrapped in the first one and log not being expanded in the second one), so I’m going to treat this as an issue on your end. Feel free to reopen if you have something actionable. |
Created attachment 1663661 [details] screenshot Description of problem: Try to report a crash bug during installation,by clicking "report bug" button, the report process will end up with an error as shown in the attached screenshot. Version-Release number of selected component (if applicable): abrt-2.14.0-2.fc32.x86_64.rpm Fedora-Server-dvd-x86_64-32-20200217.n.0.iso workstation is also affected How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: