Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1935773 - freeipa-healthcheck does not build usable package for Fedora -> ELN -> RHEL pipeline
Summary: freeipa-healthcheck does not build usable package for Fedora -> ELN -> RHEL p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: freeipa-healthcheck
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rob Crittenden
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F34BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2021-03-05 14:03 UTC by Rob Crittenden
Modified: 2021-03-12 01:36 UTC (History)
8 users (show)

Fixed In Version: freeipa-healthcheck-0.8-4.fc34 freeipa-healthcheck-0.8-5.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-12 01:36:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rob Crittenden 2021-03-05 14:03:33 UTC
Description of problem:

The freeipa-healthcheck package is used to identify common issues in an IPA installation.

Like the freeipa package, the naming is different in RHEL: ipa-* instead of freeipa-*.

The freeipa-healthcheck spec file lacks the ability to generate different names depending on the distribution it is built on.

This means that when the freeipa-healthcheck package is built for downstream distributions (ELN/RHEL 9) the package names are freeipa-healthcheck-* which don't satisfy the requirements.

This is blocking pki-core from building at all since it requires ipa-healthcheck-core.

Propose to use a similar system from freeipa.spec:

%if 0%{?rhel}
%global package_name ipa
%global alt_name freeipa
%else
%global package_name freeipa
%global alt_name ipa
%endif

Version-Release number of selected component (if applicable):

freeipa-healthcheck-0.8-4

Comment 2 Rob Crittenden 2021-03-05 14:04:41 UTC
Changes merged but we cannot build in F34 yet.

Comment 3 Fedora Blocker Bugs Application 2021-03-05 14:09:30 UTC
Proposed as a Freeze Exception for 34-beta by Fedora user rcritten using the blocker tracking app because:

 Because of the freeze the package can't be built so it is blocking rebuilds from succeeding in ELN and RHEL 9 since Fedora feeds into those. This will prevent further work for several weeks until the release is completed.

The pki-core package requires ipa-healthcheck but this isn't available since dynamic package naming wasn't previously possible with the freeipa-healthcheck package.

IPA requires pki-core so this one change is blocking it from building in the stream.

The specific change allows packages to be named based on the distribution it is built on: ipa-healthcheck-* on ?rhel and freeipa-healthcheck on anything else.

Comment 4 Adam Williamson 2021-03-08 16:02:20 UTC
+3 in https://pagure.io/fedora-qa/blocker-review/issue/284 , marking accepted.

Comment 5 Fedora Update System 2021-03-08 21:45:29 UTC
FEDORA-2021-bd8fc5db04 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-bd8fc5db04

Comment 6 Fedora Update System 2021-03-09 22:46:21 UTC
FEDORA-2021-bd8fc5db04 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-bd8fc5db04`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-bd8fc5db04

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

Comment 7 Fedora Update System 2021-03-12 01:36:15 UTC
FEDORA-2021-bd8fc5db04 has been pushed to the Fedora 34 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.