Bug 1552276 - Enable the CTDB PMDA for performance monitoring
Summary: Enable the CTDB PMDA for performance monitoring
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 34
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: Guenther Deschner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-06 21:25 UTC by Nathan Scott
Modified: 2021-07-15 23:02 UTC (History)
11 users (show)

Fixed In Version: samba-4.15.0-0.0.rc1.fc35
Clone Of:
Environment:
Last Closed: 2021-07-15 23:02:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Nathan Scott 2018-03-06 21:25:19 UTC
Please enable the ctdb Performance Co-Pilot PMDA in the Samba build.  The spec file in the upstream Samba repo ctdb/packaging/RPM/ctdb.spec.in shows how this can be done.

Thanks!

Comment 1 Jan Kurik 2018-08-14 10:59:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 2 Ben Cotton 2019-10-31 20:45:25 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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.

Comment 3 Ben Cotton 2020-02-11 15:47:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 4 Fedora Program Management 2021-04-29 17:08:32 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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.

Comment 5 Guenther Deschner 2021-07-14 09:54:01 UTC
Looking into enabling this finally for one of the next f34 updates.

Comment 6 Nathan Scott 2021-07-14 10:38:11 UTC
(In reply to Guenther Deschner from comment #5)
> Looking into enabling this finally for one of the next f34 updates.

Thanks Guenther!

Comment 7 Fedora Update System 2021-07-15 23:02:34 UTC
FEDORA-2021-7f387246d6 has been pushed to the Fedora 35 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.