Fedora Account System
Red Hat Associate
Red Hat Customer
# arcctl --config /etc/arc.conf service verify [2025-06-15 16:55:11,703] [ARCCTL.OSPackageManagement] [ERROR] [2991] [Cannot find yum, dnf or apt-get to manage OS packages. You distribution is not supported yet.] Due to this, the arc-arex.service and arc-arex-ws.service daemons fail to start, returning "Error: Configuration validation failed". In /usr/lib64/python3.13/site-packages/arc/control/OSPackage.py, the code checks for the yum and dnf packages: # detect yum try: self.logger.debug('Looking for rpm/yum is installed on the system.') yum_dnf_found = False yum_output = subprocess.Popen(self.command_base + ['rpm', '-q', 'yum'], stdout=subprocess.PIPE, stderr=subprocess.STDOUT) stdout = yum_output.communicate() if yum_output.returncode == 0: self.pm = 'yum' self.pm_cmd = 'yum' yum_dnf_found = True else: # if we are still here instead of OSError: rpm is there but yum is not - try dnf self.logger.debug('Looking for rpm/dnf is installed on the system.') dnf_output = subprocess.Popen(self.command_base + ['rpm', '-q', 'dnf'], stdout=subprocess.PIPE, stderr=subprocess.STDOUT) stdout = dnf_output.communicate() if dnf_output.returncode == 0: self.pm = 'dnf' self.pm_cmd = 'dnf' yum_dnf_found = True However, since Fedora 41, which migrated to DNF5, the package name has changed to dnf5: # rpm -q yum package yum is not installed # rpm -q dnf package dnf is not installed # rpm -q dnf5 dnf5-5.2.13.1-1.fc42.x86_64 See: https://fedoraproject.org/wiki/Changes/SwitchToDnf5 Reproducible: Always Additional Information: nordugrid-arc-arex-7.0.0-3.fc42.x86_64
FEDORA-EPEL-2025-f63b816589 (nordugrid-arc7-7.1.0-1.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f63b816589
FEDORA-EPEL-2025-da0b01a046 (nordugrid-arc7-7.1.0-1.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-da0b01a046
FEDORA-EPEL-2025-a996bb288c (nordugrid-arc7-7.1.0-1.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a996bb288c
FEDORA-EPEL-2025-2a311f3833 (nordugrid-arc7-7.1.0-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2a311f3833
FEDORA-2025-9af08770e6 (nordugrid-arc-7.1.0-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-9af08770e6
FEDORA-2025-9af08770e6 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-9af08770e6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-9af08770e6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-dc4ed0bae8 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-dc4ed0bae8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-dc4ed0bae8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-a996bb288c has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a996bb288c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-2a311f3833 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2a311f3833 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-da0b01a046 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-da0b01a046 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-f63b816589 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f63b816589 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-b6c4045de4 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b6c4045de4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-dc4ed0bae8 (nordugrid-arc-7.1.0-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-a996bb288c (nordugrid-arc7-7.1.0-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-da0b01a046 (nordugrid-arc7-7.1.0-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-9af08770e6 (nordugrid-arc-7.1.0-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-f63b816589 (nordugrid-arc7-7.1.0-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-b6c4045de4 (nordugrid-arc7-7.1.0-1.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-2a311f3833 (nordugrid-arc7-7.1.0-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.