Bug 1991228

Summary:	packagekitd should not require that /boot/efi be mounted
Product:	Red Hat Enterprise Linux 7	Reporter:	D. Hugh Redelmeier <hugh>
Component:	PackageKit	Assignee:	Richard Hughes <rhughes>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.9	CC:	klember
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-08 07:27:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description D. Hugh Redelmeier 2021-08-08 13:40:46 UTC

Description of problem:
packagekitd forces mounting of /boot/efi


Version-Release number of selected component (if applicable):
PackageKit-1.1.10-2.el7.centos.x86_64


How reproducible:
always

Steps to Reproduce:
1. add options to /etc/fstab entry for /boot/efi to have it automout:
UUID=A9B4-1C74          /boot/efi               vfat    umask=0077,shortname=winnt,x-systemd.automount,noauto 0 2

3. reboot

Actual results:
/boot/efi gets mounted.. From journal:
Aug 07 10:38:35  PackageKit[1855]: daemon start
Aug 07 10:38:35  systemd[1]: Got automount request for /boot/efi, triggered by 1855 (packagekitd)



Expected results:
/boot/efi will only be mounted when a new grub or firmware is being installed.
(After which I will reboot.  So the dirty bit will only be on while I'm attending the system.)

Additional info:
By mounting /boot/efi, the dirty bit on the ESP is set.  Essentially all the time.
When power fails, the dirty bit is left on.
My machine's firmware refuses to boot from a dirty ESP.
I have to boot from a live USB stick and do an fsck.
This is horrible for a 24/7 machine.

Comment 4 RHEL Program Management 2023-02-08 07:27:45 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.