Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Found during TPS testing for 7.4...
Installed:
acpid.x86_64 0:2.0.19-6.el7
acpid-sysvinit.x86_64 0:2.0.19-6.el7
Complete!
New leaves:
acpid-sysvinit.x86_64
.qa.[root@x86-64-7w-v1 ~]# rpm -Uvh /mnt/redhat/brewroot/packages/acpid/2.0.19/7.el7/data/signed/fd431d51/x86_64/acpid-2.0.19-7.el7.x86_64.rpm /mnt/redhat/brewroot/packages/acpid/2.0.19/7.el7/data/signed/fd431d51/x86_64/acpid-sysvinit-2.0.19-7.el7.x86_64.rpm
Preparing... ################################# [100%]
Updating / installing...
1:acpid-2.0.19-7.el7 ################################# [ 25%]
2:acpid-sysvinit-2.0.19-7.el7 ################################# [ 50%]
Cleaning up / removing...
3:acpid-sysvinit-2.0.19-6.el7 ################################# [ 75%]
4:acpid-2.0.19-6.el7 ################################# [100%]
mv: cannot stat ‘/etc/acpi/events/*.conf’: No such file or directory
warning: %posttrans(acpid-2.0.19-7.el7.x86_64) scriptlet failed, exit status 1
.qa.[root@x86-64-7w-v1 ~]# ll /etc/acpi/events/
total 8
-rw-r--r--. 1 root root 168 Mar 21 11:41 powerconf
-rw-r--r--. 1 root root 236 Mar 21 11:41 videoconf
Version-Release number of selected component (if applicable):
acpid-2.0.19-7.el7
How reproducible:
always
Steps to Reproduce:
1. Install 2.0.19-6 then attempt to upgrade to 2.0.19-7 (via rpm, yum etc. )
2.
3.
Actual results:
mv: cannot stat ‘/etc/acpi/events/*.conf’: No such file or directory
warning: %posttrans(acpid-2.0.19-7.el7.x86_64) scriptlet failed, exit status 1
Expected results:
no %post errors, previous configuration is migrated
Additional info:
It appears the file glob in %post is incorrect. I confirmed a fresh install of 2.0.19-6 on a different system places the videoconf and powerconf in /etc/acpi/events. At some point it looks like the naming convention changed to something other than the %post script was expecting.
https://bugzilla.redhat.com/show_bug.cgi?id=1086686
may be related.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2183