Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1599098 - Wrong output from 'grubby --default-kernel' when btrfs volume is mounted
Summary: Wrong output from 'grubby --default-kernel' when btrfs volume is mounted
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: grubby
Version: 28
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-07-08 21:03 UTC by Olle Liljenzin
Modified: 2018-07-08 21:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Olle Liljenzin 2018-07-08 21:03:37 UTC
Description of problem:
The path separator is removed between '/boot' and 'vmlinuz-'.

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

How reproducible:

Steps to Reproduce:
1. Run the command 'grubby --default-kernel'

Actual results:

Expected results:

Additional info:
Root file system is ext3 and /boot is ext4. The problem reproduces when an unrelated btrfs volume is mounted:

# grep btrfs /etc/fstab
/dev/vg1/ludenben /var/share/ludenben btrfs noatime,compress=lzo 1 0
# grep btrfs /proc/mounts 
/dev/mapper/vg1-ludenben /var/share/ludenben btrfs rw,seclabel,noatime,compress=lzo,space_cache,subvolid=5,subvol=/ 0 0

grubby works as expected if the btrfs volume is unmounted.

The problem is that subvolPrefix() returns 1 when it finds the unrelated btrfs volume in /proc/mounts, while the root and boot partitions are not btrfs.

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