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:
A customer experiences DNF command aborting with SIGABRT while libdnf tries to handle the "freeradius" DNF module.
The libdnf code throws a NoModuleException exception which is not caught.
This happens 100% of the time on his system when executing "/usr/bin/dnf update --security".
coredump:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
#6 0x00007fffbbdbfb8c in __cxxabiv1::__cxa_throw (obj=<optimized out>,
tinfo=0x7fffbccc9560 <typeinfo for ModulePackageContainer::NoModuleException>,
dest=0x7fffbcbf3260 <ModulePackageContainer::NoModuleException::~NoModuleException()>)
at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:95
#7 0x00007fffbcbf5af8 in ModulePackageContainer::Impl::ModulePersistor::getEntry (
this=<optimized out>, moduleName="freeradius") at /usr/include/c++/8/ext/new_allocator.h:86
#8 0x00007fffbcbe80f8 in ModulePackageContainer::Impl::ModulePersistor::getState (
this=<optimized out>, name=...)
at /usr/src/debug/libdnf-0.22.5-5.el8_0.ppc64le/libdnf/module/ModulePackageContainer.cpp:1066
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
libdnf/module/ModulePackageContainer.cpp:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
995 ModulePackageContainer::Impl::ModulePersistor::getEntry(const std::string & moduleName)
996 {
997 try {
998 auto & entry = configs.at(moduleName);
999 return entry;
1000 } catch (std::out_of_range &) {
1001 throw NoModuleException(moduleName);
1002 }
1003 }
1063 const ModulePackageContainer::ModuleState &
1064 ModulePackageContainer::Impl::ModulePersistor::getState(const std::string &name)
1065 {
1066 return getEntry(name).second.state;
1067 }
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
We hit line 1001. From my understanding, nobody catches the exception so it goes through main, causing the SIGABRT to be raised and a coredump to be created.
Version-Release number of selected component (if applicable):
dnf-4.0.9.2-5.el8
libdnf-0.22.5-5.el8_0
How reproducible:
Always on customer system, never on my test system
Additional info:
The customer doesn't use the standard repos, but his own. It is likely related but I don't have more informations for now.
Due to limited amount of information and missing reproducer I have limited possibilities how to provide tested solution. I have a patch (https://github.com/rpm-software-management/libdnf/pull/828) that should prevents the problem. I can provide rhel8 builds (dnf/libdnf/...) for testing purpose if there will be an interest. Is something more what I can do?
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-2020:1823
Description of problem: A customer experiences DNF command aborting with SIGABRT while libdnf tries to handle the "freeradius" DNF module. The libdnf code throws a NoModuleException exception which is not caught. This happens 100% of the time on his system when executing "/usr/bin/dnf update --security". coredump: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- #6 0x00007fffbbdbfb8c in __cxxabiv1::__cxa_throw (obj=<optimized out>, tinfo=0x7fffbccc9560 <typeinfo for ModulePackageContainer::NoModuleException>, dest=0x7fffbcbf3260 <ModulePackageContainer::NoModuleException::~NoModuleException()>) at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:95 #7 0x00007fffbcbf5af8 in ModulePackageContainer::Impl::ModulePersistor::getEntry ( this=<optimized out>, moduleName="freeradius") at /usr/include/c++/8/ext/new_allocator.h:86 #8 0x00007fffbcbe80f8 in ModulePackageContainer::Impl::ModulePersistor::getState ( this=<optimized out>, name=...) at /usr/src/debug/libdnf-0.22.5-5.el8_0.ppc64le/libdnf/module/ModulePackageContainer.cpp:1066 -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- libdnf/module/ModulePackageContainer.cpp: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 995 ModulePackageContainer::Impl::ModulePersistor::getEntry(const std::string & moduleName) 996 { 997 try { 998 auto & entry = configs.at(moduleName); 999 return entry; 1000 } catch (std::out_of_range &) { 1001 throw NoModuleException(moduleName); 1002 } 1003 } 1063 const ModulePackageContainer::ModuleState & 1064 ModulePackageContainer::Impl::ModulePersistor::getState(const std::string &name) 1065 { 1066 return getEntry(name).second.state; 1067 } -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- We hit line 1001. From my understanding, nobody catches the exception so it goes through main, causing the SIGABRT to be raised and a coredump to be created. Version-Release number of selected component (if applicable): dnf-4.0.9.2-5.el8 libdnf-0.22.5-5.el8_0 How reproducible: Always on customer system, never on my test system Additional info: The customer doesn't use the standard repos, but his own. It is likely related but I don't have more informations for now.