Bug 2163841
Summary: | F38FailsToInstall: linux-system-roles | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fedora Fails To Install <fti-bugs> |
Component: | linux-system-roles | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | maxwell, mikedep333, nathans, nhosoi, opensource, pcahyna, rmeggins, spetrosi, stg, systemroles-owner, user-cont-team+packit-fas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | linux-system-roles-1.33.9-1.fc38 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-01-24 22:00:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2117177 |
Description
Fedora Fails To Install
2023-01-24 14:01:40 UTC
You'll need to package ansible-collection-community-postgresql. (In reply to Maxwell G from comment #1) > You'll need to package ansible-collection-community-postgresql. Well, it's stupider than that. The rhc role requires mysql and postgresql for *testing*. not at *runtime* (it installs a candlepin server for testing). We use the (non-standard) meta/collection-requirements.yml for *runtime* requirements, and tests/collection-requirements.yml for *test-time* requirements. https://linux-system-roles.github.io/documentation/role-requirements.html Unfortunately, the CI system we are using currently only works with meta/collection-requirements.yml because the functionality to use tests/collection-requirements.yml has not yet been deployed to production https://gitlab.com/testing-farm/gluetool-modules/-/merge_requests/279 So the rhc team put the test requirements into meta/collection-requirements.yml so that CI testing would work https://github.com/linux-system-roles/rhc/blob/main/meta/collection-requirements.yml You might at this point say "Well, rpmbuild doesn't know or care about either meta/collection-requirements.yml or tests/collection-requirements.yml" and you would be right. As part of the phase of our spec file which builds the collection https://src.fedoraproject.org/rpms/linux-system-roles/blob/rawhide/f/linux-system-roles.spec#_513 we construct the galaxy.yml dependencies from the individual role meta/collection-requirements.yml and I'm guessing rpmbuild is picking up on these dependencies and translating them into ansible-collection(xxx) requirements. The goal is to remove mysql and postgresql from rhc meta/collection-requirements.yml ASAP. However, in the meantime * do this on all platforms, not just rhel: https://src.fedoraproject.org/rpms/linux-system-roles/blob/rawhide/f/linux-system-roles.spec#_500 This means rpmbuild would not be able to automatically add ansible-collection(xxx) requirements * somehow defeat the rpmbuild auto ansible-collection(xxx) requirements generator Can you 'sed -E '/community\.(postgresql|mysql)/d'` the final galaxy.yml? (In reply to Maxwell G from comment #3) > Can you 'sed -E '/community\.(postgresql|mysql)/d'` the final galaxy.yml? Good idea! Let me see. Can I assume that if `rpm-install-test` is SUCCESS, that means the bug is fixed? https://src.fedoraproject.org/rpms/linux-system-roles/pull-request/147#comment-128016 (In reply to Rich Megginson from comment #5) > Can I assume that if `rpm-install-test` is SUCCESS, that means the bug is > fixed? > https://src.fedoraproject.org/rpms/linux-system-roles/pull-request/ > 147#comment-128016 Indeed FEDORA-2023-92b037257b has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-92b037257b FEDORA-2023-92b037257b has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. |