Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1937550 - Crash reporting does not work in text installer mode due to missing report-cli
Summary: Crash reporting does not work in text installer mode due to missing report-cli
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lorax
Version: 34
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Williamson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F34BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2021-03-10 23:09 UTC by Adam Williamson
Modified: 2021-03-25 00:16 UTC (History)
10 users (show)

Fixed In Version: lorax-35.0-3.fc35 lorax-35.0-3.eln110 lorax-34.9-4.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-13 17:04:48 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Adam Williamson 2021-03-10 23:09:09 UTC 
With Fedora-Everything-netinst-x86_64-34_Beta-1.1.iso , reporting an installer crash from text mode fails with "/bin/sh: line 1: report-cli: command not found". Reporting a crash from graphical install mode works fine.

Proposing as a Beta blocker as a violation of basic criterion "The installer must be able to report failures to Bugzilla, with appropriate information included." - we have test cases for both GUI and text mode flagged as relating to that criterion.

I'm filing against anaconda as I'd suggest the correct fix for this would be for one of the anaconda subpackages to require report-cli.
Comment 1 Chris Murphy 2021-03-11 01:02:43 UTC 
- Download libreport-cli-2.14.0-17.fc34.x86_64.rpm
$ rpm2cpio ./libreport-cli-2.14.0-17.fc34.x86_64.rpm | cpio -idmv
- Boot Fedora-Everything-netinst-x86_64-34_Beta-1.1.iso with inst.text inst.ssh
- In VM, switch to tty2 and:
# rsync -r chris.0.119:/home/chris/Downloads/usr/bin/report-cli .
# chown root: report-cli
# kill -USR1 `cat /var/run/anaconda.pid`

And then I get bug 1937560. So it looks like it's only because /usr/bin/report-cli is missing from the media.
Comment 2 Adam Williamson 2021-03-11 01:13:57 UTC 
"I'm filing against anaconda as I'd suggest the correct fix for this would be for one of the anaconda subpackages to require report-cli."

...or alternatively, as Chris pointed out, the fix could be for the moron who wrote https://github.com/weldr/lorax/commit/86f0e72224f2a84fa6c3e7278523777c9b6aeed1#diff-e4634444f05cab8f034f2d4ed8e083a2259af1e52ca0e06918f5830ecc096a1aR280 to fix that. I wonder who that was.

...*ahem*
Comment 3 Adam Williamson 2021-03-11 01:35:49 UTC 
https://github.com/weldr/lorax/pull/1121
Comment 4 Fedora Update System 2021-03-11 02:49:41 UTC 
FEDORA-2021-b089abe324 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 5 Fedora Update System 2021-03-11 02:55:41 UTC 
FEDORA-2021-13f5b0f568 has been pushed to the Fedora ELN stable repository.
If problem still persists, please make note of it in this bug report.
Comment 6 Adam Williamson 2021-03-11 03:12:24 UTC 
Got closed by my Rawhide build, oops.
Comment 7 Fedora Update System 2021-03-11 03:12:42 UTC 
FEDORA-2021-ea564e699b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea564e699b
Comment 8 Adam Williamson 2021-03-11 04:03:18 UTC 
openQA will build a netinst as part of testing the update. When it's done I will grab it and check that crash reporting is fixed.
Comment 9 Adam Williamson 2021-03-11 04:18:50 UTC 
+4 in https://pagure.io/fedora-qa/blocker-review/issue/297 , marking accepted.
Comment 10 Adam Williamson 2021-03-11 18:19:35 UTC 
I tested the ISO openQA built and confirmed this works in it, see bug https://bugzilla.redhat.com/show_bug.cgi?id=1937928 .
Comment 11 Fedora Update System 2021-03-11 19:51:18 UTC 
FEDORA-2021-ea564e699b has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ea564e699b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea564e699b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 12 Fedora Update System 2021-03-13 01:33:19 UTC 
FEDORA-2021-ea564e699b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea564e699b
Comment 13 Fedora Update System 2021-03-13 01:33:37 UTC 
FEDORA-2021-ea564e699b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea564e699b
Comment 14 Fedora Update System 2021-03-13 17:04:48 UTC 
FEDORA-2021-ea564e699b has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 15 Fedora Update System 2021-03-13 19:27:24 UTC 
FEDORA-2021-16525d15e0 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2021-16525d15e0 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-16525d15e0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 16 Fedora Update System 2021-03-25 00:16:34 UTC 
FEDORA-2021-16525d15e0 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.