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 1936781 - Kdump service restarting causes /bin/bash being lost
Summary: Kdump service restarting causes /bin/bash being lost
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedBlocker AcceptedFreezeException
Depends On:
Blocks: F34FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2021-03-09 06:48 UTC by Baoquan He
Modified: 2021-04-23 21:30 UTC (History)
9 users (show)

Fixed In Version: dracut-053-4.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-23 21:03:48 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Baoquan He 2021-03-09 06:48:36 UTC 
Description of problem:
In the current rawhide, when trying to restart kdump service, the initramfs generating will fail. After investigating, it's because /bin/bash is lost when calling dracut to re-generate initramfs of kdump. Then the following any bash operation will fail.


Version-Release number of selected component (if applicable):


How reproducible:
Touch /etc/kdump.conf, then execute 'systemctl restart kdump.service' to trigger  re-generating initramfs of kdump. The failure can be always seen.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Baoquan He 2021-03-09 06:50:46 UTC 
This issue failed all kdump-sysrq-c test cases of CKI on upstream kernel.
Comment 2 Fedora Blocker Bugs Application 2021-04-08 12:29:23 UTC 
Proposed as a Blocker for 34-final by Fedora user cheeselee using the blocker tracking app because:

 Critical files like `/usr/bin/bash` will disappear when the issue triggers. System will fail to boot then. Inexperienced users will hard to fix.
Comment 3 Ben Cotton 2021-04-08 16:20:32 UTC 
Is this behavior observed on F34? It's nominated as an F34 blocker, but the bug only mentions Rawhide.

If so, is this a condition that novice users will hit?
Comment 4 Robin Lee 2021-04-08 16:26:05 UTC 
(In reply to Ben Cotton from comment #3)
> Is this behavior observed on F34? It's nominated as an F34 blocker, but the
> bug only mentions Rawhide.
I met the issue also on F34.

> 
> If so, is this a condition that novice users will hit?

People who don't enable kdump will not be affected. But it is critical for people that enabled kdump. If this issue is not fixed, we have to tell people just don't enable kdump on F34.
Comment 5 Adam Williamson 2021-04-09 18:47:47 UTC 
-3 (blocker) +3 (FE) in https://pagure.io/fedora-qa/blocker-review/issue/340 . Marking as rejected blocker but accepted FE.
Comment 6 Kairui Song 2021-04-13 14:58:12 UTC 
This is reproducible on Fedora 34

This is caused by dracut change here:
https://github.com/dracutdevs/dracut/commit/41cfdfc4d37b3075fef02b1775e903ebe5a15283#diff-99bfb8fe311d6a59318f685a5e3401b59293b577968aa08cc4ff7320a163bb28L2062

It can be fixed by partially revert 41cfdfc4d37b3075fef02b1775e903ebe5a15283 (delete that new `find` based code and use the old `for` based code).

In latest dracut, the whole squash module related code have been refactored by https://github.com/dracutdevs/dracut/pull/1088
Maybe we should apply a Fedora only patch to partially revert that commit in Fedora 34? The new refactor requires systemd 248, and systemd 248 seems not included in Fedora 34.
Comment 7 Fedora Update System 2021-04-19 16:12:47 UTC 
FEDORA-2021-a0ae59d4d6 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a0ae59d4d6
Comment 8 Fedora Update System 2021-04-20 22:25:03 UTC 
FEDORA-2021-a0ae59d4d6 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-a0ae59d4d6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a0ae59d4d6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 9 Fedora Update System 2021-04-22 18:24:09 UTC 
FEDORA-2021-e716aa3f08 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-e716aa3f08`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e716aa3f08

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 10 Fedora Update System 2021-04-23 19:49:59 UTC 
FEDORA-2021-9dd2ebc2a8 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-9dd2ebc2a8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-9dd2ebc2a8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 11 Fedora Update System 2021-04-23 20:43:41 UTC 
FEDORA-2021-e716aa3f08 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e716aa3f08
Comment 12 Fedora Update System 2021-04-23 21:03:48 UTC 
FEDORA-2021-e716aa3f08 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 13 Fedora Update System 2021-04-23 21:30:08 UTC 
FEDORA-2021-9dd2ebc2a8 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-9dd2ebc2a8
Note You need to log in before you can comment on or make changes to this bug.