Bug 1878652 - removing swap device from LVM but not fstab renders the system unbootable
Summary: removing swap device from LVM but not fstab renders the system unbootable
Keywords:
Status: CLOSED DUPLICATE of bug 1096910
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-14 09:47 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2021-05-18 17:30 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-18 17:30:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dominik 'Rathann' Mierzejewski 2020-09-14 09:47:38 UTC
Description of problem:
Removing swap device from grub kernel command line and LVM, but not from /etc/fstab renders the system unbootable.

Version-Release number of selected component (if applicable):
systemd-245.7-1.fc32.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. On a standard F32 installation, remove swap entries from /boot/grub2/grubenv
2. Remove swap volume from LVM
3. Leave the entry for /dev/mapper/fedora-swap in /etc/fstab
3. Reboot

Actual results:
Boot hangs indefinitely at
[***  ] A start job is running for /dev/mapper/fedora-swap (3min 55s / no limit)

Expected results:
Boot should proceed without swap if swap device cannot be found.

Comment 1 Fedora Program Management 2021-04-29 16:56:58 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Zbigniew Jędrzejewski-Szmek 2021-05-18 17:30:46 UTC
Yeah, the story with failing things in early boot is pretty bad. It certainly needs
a revamp, but so far there have always been more pressing issues. Hopefully one day.

*** This bug has been marked as a duplicate of bug 1096910 ***


Note You need to log in before you can comment on or make changes to this bug.