Bug 2372649 - Please build node-exporter for EPEL 10
Summary: Please build node-exporter for EPEL 10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: node-exporter
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mikel Olasagasti Uranga
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-13 11:10 UTC by Piotr Gliźniewicz
Modified: 2025-08-05 00:37 UTC (History)
4 users (show)

Fixed In Version: node-exporter-1.9.1-2.el10_1
Clone Of:
Environment:
Last Closed: 2025-08-05 00:37:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Piotr Gliźniewicz 2025-06-13 11:10:39 UTC
Description of problem:

There's no golang-github-prometheus-node-exporter in EPEL 10, which means we can't export metrics from new servers. Please, add the package to EPEL 10.

Expected results:

Being able to install golang-github-prometheus-node-exporter from EPEL 10

Comment 1 Mikel Olasagasti Uranga 2025-06-13 17:19:48 UTC
New package name is node-exporter.

Plan is to work updating the package once https://fedoraproject.org/wiki/Changes/GolangPackagesVendoredByDefault is accepted and then work on the EPEL version.

Comment 2 Fedora Update System 2025-07-27 14:15:20 UTC
FEDORA-EPEL-2025-ee03d5072e (node-exporter-1.9.1-2.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-ee03d5072e

Comment 3 Fedora Update System 2025-07-28 01:41:10 UTC
FEDORA-EPEL-2025-ee03d5072e 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-ee03d5072e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2025-08-05 00:37:59 UTC
FEDORA-EPEL-2025-ee03d5072e (node-exporter-1.9.1-2.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.


Note You need to log in before you can comment on or make changes to this bug.