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 1777237 - error: lsetfilecon: (/boot/efi/EFI/fedora/fonts, system_u:object_r:boot_t:s0) Operation not supported
Summary: error: lsetfilecon: (/boot/efi/EFI/fedora/fonts, system_u:object_r:boot_t:s0)...
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: 2019-11-27 09:07 UTC by Kamil Páral
Modified: 2019-11-27 10:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 10:40:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
full dnf output (47.73 KB, text/plain)
2019-11-27 09:11 UTC, Kamil Páral
no flags Details
rpm -qa output (81.27 KB, text/plain)
2019-11-27 09:12 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2019-11-27 09:07:23 UTC
Description of problem:
When I upgraded from
grub2-1:2.02-100.fc31.noarch
to
grub2-1:2.02-102.fc31.x86_64
I saw the following errors in dnf output:

  Upgrading        : grub2-efi-ia32-1:2.02-102.fc31.x86_64                                                     35/108 
error: lsetfilecon: (/boot/efi/EFI/fedora/fonts, system_u:object_r:boot_t:s0) Operation not supported
error: lsetfilecon: (/boot/efi/EFI/fedora/grubia32.efi;5dde3bc9, system_u:object_r:boot_t:s0) Operation not supported

  Upgrading        : grub2-efi-x64-1:2.02-102.fc31.x86_64                                                      36/108 
error: lsetfilecon: (/boot/efi/EFI/fedora/grubx64.efi;5dde3bc9, system_u:object_r:boot_t:s0) Operation not supported

  Upgrading        : python2-pillow-6.1.0-4.fc31.x86_64                                                        37/108 
  Upgrading        : python3-pillow-6.1.0-4.fc31.x86_64                                                        38/108 
  Upgrading        : grub2-efi-ia32-cdboot-1:2.02-102.fc31.x86_64                                              39/108 
error: lsetfilecon: (/boot/efi/EFI/fedora/fonts, system_u:object_r:boot_t:s0) Operation not supported
error: lsetfilecon: (/boot/efi/EFI/fedora/fonts/unicode.pf2;5dde3bc9, system_u:object_r:boot_t:s0) Operation not supported
error: lsetfilecon: (/boot/efi/EFI/fedora/gcdia32.efi;5dde3bc9, system_u:object_r:boot_t:s0) Operation not supported

  Upgrading        : grub2-efi-x64-cdboot-1:2.02-102.fc31.x86_64                                               40/108 
error: lsetfilecon: (/boot/efi/EFI/fedora/gcdx64.efi;5dde3bc9, system_u:object_r:boot_t:s0) Operation not supported

  Upgrading        : grub2-tools-efi-1:2.02-102.fc31.x86_64                                                    41/108 

I'm running with selinux in permissive mode.

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

Comment 1 Kamil Páral 2019-11-27 09:11:52 UTC
Created attachment 1640037 [details]
full dnf output

Comment 2 Kamil Páral 2019-11-27 09:12:13 UTC
Created attachment 1640038 [details]
rpm -qa output

Comment 3 Javier Martinez Canillas 2019-11-27 09:18:22 UTC
Hello Kamil,

This isn't a new issue, it has already been filed as Bug #1760677.

Comment 4 Javier Martinez Canillas 2019-11-27 09:24:12 UTC
Sorry, that's a duplicate too. I meant Bug #1722766.

The root cause is that in /boot/efi the EFI System Partition is mounted, that partition contains a vfat filesystem so it's not correct to try setting labels on these files since vfat doesn't support extended attributes to store them.

Comment 5 Kamil Páral 2019-11-27 10:40:21 UTC
OK, thanks, duping.

*** 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.