Hide Forgot
+++ This bug was initially created as a clone of Bug #921430 +++ Description of problem: udisksd fills up the system log with messages: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD740ADFD_00NLR5_WD_WMANS2044958: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0) While the disk is being perfectly recognized by smartd. === START OF INFORMATION SECTION === Model Family: Western Digital Raptor Device Model: WDC WD740ADFD-00NLR4 Serial Number: WD-WMANS1564963 Firmware Version: 21.07QR4 User Capacity: 74,355,769,344 bytes [74.3 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA/ATAPI-7 published, ANSI INCITS 397-2005 Local Time is: Thu Mar 14 09:11:07 2013 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled Version-Release number of selected component (if applicable): libatasmart-0.19-3.fc18.x86_64 How reproducible: All the time. Steps to Reproduce: 1. 2. 3. Actual results: udisks-error-quark Expected results: No error, no messages. Additional info: --- Additional comment from Eddie Lania on 2013-03-15 04:51:15 EDT --- Sorry, wrong line copied from messages log, this should be the right one: Mar 15 09:37:42 atena udisksd[960]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD740ADFD_00NLR5_WD_WMANS2044958: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0) --- Additional comment from boing891 on 2013-06-26 00:50:07 EDT --- On Fedora 19 (libatasmart-0.19-4.fc19.x86_64.rpm) I had the same problem, I resolved by applying this patch https://bugs.freedesktop.org/show_bug.cgi?id=61998#c1 giu 26 06:08:15 user.linux udisksd[1474]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD1500ADFD_00NLR5_WD_WMAP41777367: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0) hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: WDC WD1500ADFD-00NLR5 Serial Number: WD-WMAP41777367 Firmware Revision: 21.07QR5 Standards: Used: ATA/ATAPI-7 published, ANSI INCITS 397-2005 Supported: 7 6 5 4 & some of 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 293046768 Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 143089 MBytes device size with M = 1000*1000: 150039 MBytes (150 GB) cache/buffer size = 16384 KBytes (type=DualPortCache) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension * Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * Gen1 signaling speed (1.5Gb/s) * Native Command Queueing (NCQ) * Phy event counters * DMA Setup Auto-Activate optimization * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Read/Write Long (AC1), obsolete * SCT Write Same (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count not supported: enhanced erase Checksum: correct udisksctl info --drive WDC_WD1500ADFD_00NLR5_WD_WMAP41777367 /org/freedesktop/UDisks2/drives/WDC_WD1500ADFD_00NLR5_WD_WMAP41777367: org.freedesktop.UDisks2.Drive: CanPowerOff: false Configuration: {} ConnectionBus: Ejectable: false Id: WDC-WD1500ADFD-00NLR5-WD-WMAP41777367 Media: MediaAvailable: true MediaChangeDetected: true MediaCompatibility: MediaRemovable: false Model: WDC WD1500ADFD-00NLR5 Optical: false OpticalBlank: false OpticalNumAudioTracks: 0 OpticalNumDataTracks: 0 OpticalNumSessions: 0 OpticalNumTracks: 0 Removable: false Revision: 21.07QR5 RotationRate: -1 Seat: seat0 Serial: WD-WMAP41777367 SiblingId: Size: 150039945216 SortKey: 00coldplug/00fixed/sd____a TimeDetected: 1372219776195072 TimeMediaDetected: 1372219776195072 Vendor: WWN: 0x50014ee0aad7d5cc org.freedesktop.UDisks2.Drive.Ata: AamEnabled: true AamSupported: true AamVendorRecommendedValue: 128 ApmEnabled: false ApmSupported: false PmEnabled: true PmSupported: true SecurityEnhancedEraseUnitMinutes: 0 SecurityEraseUnitMinutes: 0 SecurityFrozen: true SmartEnabled: true SmartFailing: false SmartNumAttributesFailedInThePast: 0 SmartNumAttributesFailing: 0 SmartNumBadSectors: 0 SmartPowerOnSeconds: 115977600 SmartSelftestPercentRemaining: 30 SmartSelftestStatus: inprogress SmartSupported: true SmartTemperature: 305.15000000000003 SmartUpdated: 1372222027 WriteCacheEnabled: true WriteCacheSupported: true udevadm info /sys/class/block/sda P: /devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda N: sda S: disk/by-id/ata-WDC_WD1500ADFD-00NLR5_WD-WMAP41777367 S: disk/by-id/wwn-0x50014ee0aad7d5cc E: DEVLINKS=/dev/disk/by-id/ata-WDC_WD1500ADFD-00NLR5_WD-WMAP41777367 /dev/disk/by-id/wwn-0x50014ee0aad7d5cc E: DEVNAME=/dev/sda E: DEVPATH=/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda E: DEVTYPE=disk E: ID_ATA=1 E: ID_ATA_DOWNLOAD_MICROCODE=1 E: ID_ATA_FEATURE_SET_AAM=1 E: ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=254 E: ID_ATA_FEATURE_SET_AAM_ENABLED=1 E: ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=128 E: ID_ATA_FEATURE_SET_HPA=1 E: ID_ATA_FEATURE_SET_HPA_ENABLED=1 E: ID_ATA_FEATURE_SET_PM=1 E: ID_ATA_FEATURE_SET_PM_ENABLED=1 E: ID_ATA_FEATURE_SET_PUIS=1 E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0 E: ID_ATA_FEATURE_SET_SECURITY=1 E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0 E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=0 E: ID_ATA_FEATURE_SET_SECURITY_FROZEN=1 E: ID_ATA_FEATURE_SET_SMART=1 E: ID_ATA_FEATURE_SET_SMART_ENABLED=1 E: ID_ATA_SATA=1 E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1 E: ID_ATA_WRITE_CACHE=1 E: ID_ATA_WRITE_CACHE_ENABLED=1 E: ID_BUS=ata E: ID_MODEL=WDC_WD1500ADFD-00NLR5 E: ID_MODEL_ENC=WDC\x20WD1500ADFD-00NLR5\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 E: ID_PART_TABLE_TYPE=dos E: ID_REVISION=21.07QR5 E: ID_SERIAL=WDC_WD1500ADFD-00NLR5_WD-WMAP41777367 E: ID_SERIAL_SHORT=WD-WMAP41777367 E: ID_TYPE=disk E: ID_WWN=0x50014ee0aad7d5cc E: ID_WWN_WITH_EXTENSION=0x50014ee0aad7d5cc E: MAJOR=8 E: MINOR=0 E: MPATH_SBIN_PATH=/sbin E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=45304 --- Additional comment from Eddie Lania on 2013-08-13 02:35:10 EDT --- Can you or somebody else apply that patch to F18 please? (In reply to boing891 from comment #2) > On Fedora 19 (libatasmart-0.19-4.fc19.x86_64.rpm) I had the same problem, I > resolved by applying this patch > > https://bugs.freedesktop.org/show_bug.cgi?id=61998#c1 > --- Additional comment from boing891 on 2013-09-08 05:13:30 EDT --- Sorry, but I have no right to make any changes, i'm just a user. I think you have to wait a developer for this, and hear what he thinks --- Additional comment from Alexander Ploumistos on 2013-09-12 06:03:36 EDT --- @boing891: If you own other disks besides WD, can you test if the patch causes some unwanted behavior? I was planning to work on the package in koji, but I was left with little free time, I won't be able to do anything, probably until early October. --- Additional comment from Fedora End Of Life on 2013-12-21 07:08:09 EST --- This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. --- Additional comment from Alexander Ploumistos on 2013-12-22 12:01:12 EST --- Eddie, could you change the version to 19 (or 20 if the issue is still there) so that this may remain open? --- Additional comment from Eddie Lania on 2013-12-23 08:51:11 EST --- Sorry but this system is still on f18 and I think it will not be upgraded shortly, I therefor cannot update this issue. --- Additional comment from Alexander Ploumistos on 2013-12-24 10:23:10 EST --- I am asking because I have the same issue on F19 and since you are the OP, you can change the version in the bug report. If not, I will have to open a duplicate. Dec 24 17:14:44 localhost udisksd[1646]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD1200JB_00GVC0_WD_WMALA1719280: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0) libatasmart-0.19-4.fc19.x86_64 --- Additional comment from Alexander Ploumistos on 2014-01-17 06:59:29 EST --- Fedora 20 with libatasmart-0.19-5.fc20.x86_64 still suffers from this. --- Additional comment from japa-fi on 2014-05-16 02:09:01 EDT --- Same problem: Fedora 19 libatasmart.x86_64 0.19-4.fc19 === START OF INFORMATION SECTION === Model Family: Hitachi/HGST Travelstar Z7K500 Device Model: HGST HTS725032A7E630 Serial Number: TF645AY1GKWT9J LU WWN Device Id: 5 000cca 660c8229b Firmware Version: GHBZB550 User Capacity: 320.072.933.376 bytes [320 GB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 2.6, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri May 16 09:08:32 2014 EEST SMART support is: Available - device has SMART capability. SMART support is: Enabled --- Additional comment from Eddie Lania on 2014-06-10 04:19:12 EDT --- Currently with package libatasmart-0.19-5.fc20.x86_64, I am not seeing this error anymore. --- Additional comment from Alexander Ploumistos on 2014-07-19 08:58:51 EDT --- I had been away for a while and I couldn't check. I upgraded to libatasmart-0.19-5.fc20.x86_64 and I am still seeing this: Jul 19 15:51:20 localhost udisksd[1963]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD1200JB_00GVC0_WD_WMALA1719280: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0) --- Additional comment from Alexander Ploumistos on 2014-07-19 09:00:28 EDT --- I meant that I reinstalled libatasmart. --- Additional comment from on 2014-07-19 10:51:35 EDT --- I'm seeing this one to Jul 19 22:24:57 localhost udisksd[1743]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD2500JD_75HBB0_WD_WCAL72983952: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0) smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.4-200.fc20.x86_64] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org kernel 3.14.4-200.fc20.x86_64 #1 SMP Tue May 13 13:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux --- Additional comment from Didier G on 2014-07-22 09:54:38 EDT --- Similar problem for me today running Fedora 20 Jul 22 15:44:54 pc20 udisksd[1919]: Error performing initial housekeeping for drive /org/freedesktop/UDisks2/drives/TOSHIBA_MK8032GSX_Y6BMF8Q7S: Error updating SMART data: sk_disk_check_sleep_mode: Operation not supported (udisks-error-quark, 0) libatasmart is: libatasmart-0.19-5.fc20.x86_64 USB disk enclosure is: Bus 001 Device 005: ID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp. JM20329 SATA Bridge --- Additional comment from Didier G on 2014-07-22 10:11:49 EDT --- About related problem above, partition is a FAT32 partition. I connected this disk to a Windows 7 system who prompted to analyze and repair this partition. After this analyze and repair by Windows 7, I recovered access to the disk on Fedora. --- Additional comment from Alexander Ploumistos on 2014-12-16 14:44:19 EST --- Proposed patch --- Additional comment from Alexander Ploumistos on 2014-12-16 14:50:09 EST --- I have been using packages built with this patch since Oct 5. I submitted a scratch build to koji that was successful on Oct 25 and a review request, though I was informed that this was not the proper procedure for a package that already exists in fedora. I expect to run a few tests in f21 by the end of this week or the next, but so far I don't think there are any side-effects from using the patch. --- Additional comment from Fedora End Of Life on 2015-05-29 04:55:15 EDT --- This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. --- Additional comment from Fedora End Of Life on 2015-11-04 06:44:14 EST --- This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
It is recorded on messages as the following errors repeat every 10 minutes. The error is not found in smrtctl. Jan 17 03:17:52 localhost udisksd[2143]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/INTEL_SSDSC2BX400G4R_BTHC536301XC400VGN: Error updating SMART data: sk_disk_check_sleep_mode: Input/output error (udisks-error-quark, 0) Is it the same as following Bugzilla? https://bugzilla.redhat.com/show_bug.cgi?id=921430 It seems to use the same libatasmart version from chengelog. #rpm -qp --changelog libatasmart-0.19-6.el7.x86_64.rpm * Fri Jan 24 2014 Daniel Mach <dmach> - 0.19-6 - Mass rebuild 2014-01-24 * Fri Dec 27 2013 Daniel Mach <dmach> - 0.19-5 - Mass rebuild 2013-12-27 * Thu Feb 14 2013 Fedora Release Engineering <rel-eng.org> - 0.19-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
*** Bug 1371595 has been marked as a duplicate of this bug. ***
Any update on this bug? I built rpm with the patch applied and installed the rpm. Still i am seeing the issue. Can someone provide exact details for applying the patch?
I am using Intel SSD. I had already raised a bugzilla at BZ#1371595
(In reply to Nanda Kishore Chinnaram from comment #4) > Can someone provide exact details for applying the patch? Supposing that you have the rpmbuild tree standard set up in your home folder, you need to have the source package http://0pointer.de/public/libatasmart-0.19.tar.xz and the patch https://bugs.freedesktop.org/attachment.cgi?id=76719 (saved as fix-status-io-error.patch) in ~/rpmbuild/SOURCES/ and a spec file like this one https://bugzilla.redhat.com/attachment.cgi?id=969730 in ~/rpmbuild/SPECS/ then build the rpm with rpmbuild -bb ~/rpmbuild/SPECS/libatasmart.spec and if it all succeeds, you'll find the rpm in ~/rpmbuild/RPMS/x86_64/ (if you're on x86_64, else substitute accordingly). This has been working for the past 6 Fedora releases, but I've never tested it on/for RHEL.
(In reply to Alexander Ploumistos from comment #6) > (In reply to Nanda Kishore Chinnaram from comment #4) > > Can someone provide exact details for applying the patch? > > Supposing that you have the rpmbuild tree standard set up in your home > folder, you need to have the source package > http://0pointer.de/public/libatasmart-0.19.tar.xz > and the patch > https://bugs.freedesktop.org/attachment.cgi?id=76719 > (saved as fix-status-io-error.patch) in ~/rpmbuild/SOURCES/ > > and a spec file like this one > https://bugzilla.redhat.com/attachment.cgi?id=969730 > in ~/rpmbuild/SPECS/ > > then build the rpm with > rpmbuild -bb ~/rpmbuild/SPECS/libatasmart.spec > > and if it all succeeds, you'll find the rpm in ~/rpmbuild/RPMS/x86_64/ (if > you're on x86_64, else substitute accordingly). > > This has been working for the past 6 Fedora releases, but I've never tested > it on/for RHEL. Thanks for the help. I have tried the same on RHEL-7 but the issue is not fixed for me.
(In reply to Nanda Kishore Chinnaram from comment #7) > Thanks for the help. I have tried the same on RHEL-7 but the issue is not > fixed for me. Well, if you've used the same files and rpmbuild does not complain about anything, I can only speculate as to what the problem might be. Try bumping the release tag in the spec file, from Release: 8%{?dist} to Release: 9%{?dist} (or a number higher than what's in the RHEL repos) just in case you're getting the official package instead of the one you've built.
(In reply to Alexander Ploumistos from comment #8) > (In reply to Nanda Kishore Chinnaram from comment #7) > > Thanks for the help. I have tried the same on RHEL-7 but the issue is not > > fixed for me. > > Well, if you've used the same files and rpmbuild does not complain about > anything, I can only speculate as to what the problem might be. > > Try bumping the release tag in the spec file, from > > Release: 8%{?dist} > > to > > Release: 9%{?dist} > > (or a number higher than what's in the RHEL repos) > > just in case you're getting the official package instead of the one you've > built. On my system the default libata version is "libatasmart-0.19-6.el7.x86_64". So when i installed rpm that is built using the spec file provided by you and the source file http://0pointer.de/public/libatasmart-0.19.tar.xz , the version bumped from 0.19-6 to 1.19-8.
Do we have any update in this issue? The patch seems not to be the fix in my case. Whatever i have done for applying the patch are explained in the above comments. Do you need any other information ?
Restoring needinfo on Lennart
Karl, Checked with latest test build of RHEL7, issue is still seen. Hope this issue will be addressed.
Even with Snapshot-1 release issue didn't get fixed. Just want to know if there is a plan to get this fixed in RHEL 7.4.
Nanda, I've reached out to Lennart again. At this point though, I doubt it will get fixed fro 7.4GA. Only blocker bugs are being approved at this time.
Metoo. Replaced failed 2TB disk with a 3TB disk, now see these useless udisks errors in the syslog every 10 minutes. (checking if a server zfs disk is sleeping, seriously?) Apparently the fix is pending since 2013: https://bugs.freedesktop.org/show_bug.cgi?id=61998#c1 [root@daqbackup ~]# skdump --overall /dev/sdi Failed to get overall status: Input/output error [root@daqbackup ~]# rpm -qf `which skdump` libatasmart-0.19-6.el7.x86_64 [root@daqbackup ~]# K.O.
Since there is no proposed solution to this problem (disable broken polling of smart data), I looked into it: a) google-suggested solution of using udev rule KERNEL=="sd*[!0-9]", ... ENV{UDISKS_DISABLE_POLLING}="1" or similar does not work. Code inspection of udisks2 shows no trace of support for this. b) udisks2 seems to have a way to disable polling of smart data, maybe via DBUS, this feature does not seem to be documented and I exhausted my time budget to try to figure it out. As bottom line, disable of unwanted polling of smart data can only be done the hard way: systemctl stop udisks2 # stop the udisksd daemon systemctl mask udisks2 # prevent it from restarting K.O.
Looks like a fix for this problem was released for Fedora Linux. Please include this fix in the el stream. Thanks. https://bugzilla.redhat.com/show_bug.cgi?id=921430 K.O.
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7. From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. From the RHEL life cycle page: https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase "During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available." If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes: https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns. [0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7