Bug 2086146 - drbd-pacemaker: fails to install
Summary: drbd-pacemaker: fails to install
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: drbd
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hanecak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2087022
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-14 06:21 UTC by Carl George 🤠
Modified: 2022-07-19 02:19 UTC (History)
3 users (show)

Fixed In Version: drbd-9.21.3-1.fc37 drbd-9.21.3-1.fc36 drbd-9.21.3-1.el8 drbd-9.21.3-1.el9 drbd-9.21.3-1.fc35
Clone Of:
Environment:
Last Closed: 2022-07-10 16:52:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Carl George 🤠 2022-05-14 06:21:43 UTC
Description of problem:
drbd-pacemaker fails to install when using just the EPEL Target Base [0], i.e baseos, appstream, and crb.  It requires pacemaker, which is only available in the highavailability or resilientstorage repos.  EPEL Policy states that all requires must be satisfiable within the Target Base [1].  Some possible solutions:

1. Disable the drbd-pacemaker subpackage from the drbd spec file when built for epel9.
2. Change the requires to a recommends (allowed by policy) if that is correct for the software.
3. If the requirement isn't actually necessary, remove it.
4. Add pacemaker to epel9.


Version-Release number of selected component (if applicable):
drbd-pacemaker-9.20.2-1.el9


How reproducible:
whenever the highavailability or resilientstorage repos are not enabled


Steps to Reproduce:
1. dnf install drbd-pacemaker


Actual results:
Error: 
 Problem: conflicting requests
  - nothing provides pacemaker needed by drbd-pacemaker-9.20.2-1.el9.x86_64


Expected results:
successful installation


Additional info:
[0] https://docs.fedoraproject.org/en-US/epel/epel-policy/#_policy
[1] https://docs.fedoraproject.org/en-US/epel/epel-packaging/#package_dependencies

Comment 1 Peter Hanecak 2022-06-05 10:26:33 UTC
According to light study of DRBD sources it is correct as it is (i.e. "Requires: pacemaker"). And since I do not have an EPEL9 installation to test with, I'm not brave enough to fiddle with the package. But I'm willing to review and merge pull-request with a fix, if somebody is willing and able to prepare and test that.

Comment 2 Carl George 🤠 2022-06-14 23:16:46 UTC
https://src.fedoraproject.org/rpms/drbd/pull-request/2

Comment 3 Fedora Update System 2022-07-10 16:33:42 UTC
FEDORA-2022-c6b994b571 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c6b994b571

Comment 4 Fedora Update System 2022-07-10 16:52:29 UTC
FEDORA-2022-c6b994b571 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2022-07-10 17:06:58 UTC
FEDORA-EPEL-2022-598e9b771e has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-598e9b771e

Comment 6 Fedora Update System 2022-07-10 17:07:03 UTC
FEDORA-2022-5409dd3d72 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5409dd3d72

Comment 7 Fedora Update System 2022-07-10 17:07:08 UTC
FEDORA-EPEL-2022-4b320b0b1c has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b320b0b1c

Comment 8 Fedora Update System 2022-07-10 17:07:13 UTC
FEDORA-2022-df2febd09b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-df2febd09b

Comment 9 Fedora Update System 2022-07-11 02:41:27 UTC
FEDORA-2022-5409dd3d72 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-5409dd3d72`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5409dd3d72

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

Comment 10 Fedora Update System 2022-07-11 02:52:31 UTC
FEDORA-EPEL-2022-598e9b771e 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-2022-598e9b771e

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

Comment 11 Fedora Update System 2022-07-11 02:55:55 UTC
FEDORA-2022-df2febd09b has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-df2febd09b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-df2febd09b

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

Comment 12 Fedora Update System 2022-07-11 03:02:34 UTC
FEDORA-EPEL-2022-4b320b0b1c 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-2022-4b320b0b1c

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

Comment 13 Fedora Update System 2022-07-19 01:40:04 UTC
FEDORA-2022-df2febd09b has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2022-07-19 01:46:33 UTC
FEDORA-EPEL-2022-598e9b771e has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2022-07-19 02:06:33 UTC
FEDORA-EPEL-2022-4b320b0b1c has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2022-07-19 02:19:58 UTC
FEDORA-2022-5409dd3d72 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.