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 1823000 - attempting to set SELinux context on EFI FAT filesystems
Summary: attempting to set SELinux context on EFI FAT filesystems
Keywords:
Status: CLOSED DUPLICATE of bug 1722766
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-10 21:33 UTC by Subhendu Ghosh
Modified: 2020-04-14 09:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-14 09:54:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Subhendu Ghosh 2020-04-10 21:33:49 UTC 
Description of problem:

During grub2 upgrade, the package is trying to set SELinuc file context on vfat filesystem.

Version-Release number of selected component (if applicable):
grub2-efi-x64-1:2.02-107.fc31.x86_64 

How reproducible:
always

Steps to Reproduce:
1. dnf update grub2
2.
3.

Actual results:

  Upgrading        : grub2-efi-x64-1:2.02-107.fc31.x86_64                                                                                                                        68/219 
error: lsetfilecon: (/boot/efi/EFI/fedora/fonts, system_u:object_r:boot_t:s0) Operation not supported
error: lsetfilecon: (/boot/efi/EFI/fedora/grubx64.efi;5e90e3ed, system_u:object_r:boot_t:s0) Operation not supported

Expected results:

lsetfilecon should not be used on VFAT filesystems


Additional info:
Comment 1 Javier Martinez Canillas 2020-04-14 09:54:10 UTC 

*** This bug has been marked as a duplicate of bug 1722766 ***
Note You need to log in before you can comment on or make changes to this bug.