Bug 1929798
Summary: | Package needed for EPEL 7 and 8 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | nicolas.baratto |
Component: | golang-github-prometheus | Assignee: | Robert-André Mauchin 🐧 <zebob.m> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 34 | CC: | david.taillois, go-sig, xavier, zebob.m |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | golang-github-prometheus-2.24.1-3.el8.1 golang-github-prometheus-2.24.1-3.el7.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-03-07 15:44:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
nicolas.baratto
2021-02-17 16:43:25 UTC
This is in good way, I have prepared the build for EPEL7 and 8 for prometheus (I assume you don't need to use it as a library so I only packaged the binary). For node_exporter, I've built the new deps (only 2) for Fedora and prepared it also for EPEL. However I don't know if some kind of default configuration is needed. I might need to add a Systemd file. Ok I have systemd and set up a node_exporter user as described in https://github.com/prometheus/node_exporter/tree/master/examples/systemd Now I need to wait for the scm requests for the new branches to be processed. It is an excellent news ! Thanks FEDORA-EPEL-2021-fb2ae94f8a has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-fb2ae94f8a FEDORA-EPEL-2021-0780b85304 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-0780b85304 FEDORA-EPEL-2021-fb2ae94f8a 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-2021-fb2ae94f8a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2021-0780b85304 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-0780b85304 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. (In reply to nicolas.baratto from comment #3) > It is an excellent news ! Thanks I've built golang-github-prometheus-node-exporter on F33-35 and EPEL7/8. It should be available on EPEL within 2 weeks after testing. (In reply to Robert-André Mauchin 🐧 from comment #8) > (In reply to nicolas.baratto from comment #3) > > It is an excellent news ! Thanks > > I've built golang-github-prometheus-node-exporter on F33-35 and EPEL7/8. It > should be available on EPEL within 2 weeks after testing. Excellent, I can already test the both packages in testing. Thanks FEDORA-EPEL-2021-fb2ae94f8a 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-2021-0780b85304 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. Hello, I think that there is a bug on the package golang-github-prometheus-node-exporter-1.1.1-1.el8.x86_64 After his installation the executable node_exporter is put in /usr/bin/node_exporter. But on the configuration file /etc/systemd/system/node_exporter.service , the executable is set on /usr/sbin/node_exporter. So the service node-exporter.service can't start without changing the executable path. A made manually the change and it's work. Thanks for your feedback. David T Hello, Also i forget to ask sorry. Regarding the package golang-github-prometheus-2.24.1-3.el8.1.x86_64 Could it be possible on the futur to be able to reload the service prometheus.service ? sudo systemctl reload prometheus.service Failed to reload prometheus.service: Job type reload is not applicable for unit prometheus.service. Many thanks David T (In reply to David Taillois from comment #12) > Hello, > > I think that there is a bug on the package > golang-github-prometheus-node-exporter-1.1.1-1.el8.x86_64 > > After his installation the executable node_exporter is put in > /usr/bin/node_exporter. > But on the configuration file /etc/systemd/system/node_exporter.service , > the executable is set on /usr/sbin/node_exporter. So the service > node-exporter.service can't start without changing the executable path. > > A made manually the change and it's work. > > Thanks for your feedback. > > David T I've pushed an update with this. (In reply to David Taillois from comment #13) > Hello, > > Also i forget to ask sorry. Regarding the package > golang-github-prometheus-2.24.1-3.el8.1.x86_64 > > Could it be possible on the futur to be able to reload the service > prometheus.service ? > > sudo systemctl reload prometheus.service > Failed to reload prometheus.service: Job type reload is not applicable for > unit prometheus.service. > > > Many thanks > > David T Not really a specialist of service files, I took hints from Arch and Debian: [Unit] Description=Prometheus service monitoring system and time series database Documentation=https://prometheus.io/docs/introduction/overview/ man:prometheus(1) Wants=network-online.target After=network-online.target [Service] Restart=on-failure EnvironmentFile=/etc/sysconfig/prometheus User=prometheus Group=prometheus ExecStart=/usr/bin/prometheus \ --config.file=${CONFIG_FILE} \ --storage.tsdb.path=${STORAGE_TSDB_PATH} \ --web.console.libraries=${WEB_CONSOLE_LIBRARIES_PATH} \ --web.console.templates=${WEB_CONSOLE_TEMPLATES_PATH} \ --web.listen-address=${WEB_LISTEN_ADDRESS} ExecReload=/bin/kill -HUP $MAINPID TimeoutStopSec=20s SendSIGKILL=no [Install] WantedBy=multi-user.target |