Bug 1733602
| Summary: | firewalld Requires kernel, which is no longer available on i686 in F31 and later. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Justin M. Forbes <jforbes> |
| Component: | firewalld | Assignee: | Eric Garver <egarver> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | egarver, j, kkeithle |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | firewalld-0.7.1-2.fc31 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-01 15:12:17 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1728779, 1734866, 1735230 | ||
|
Description
Justin M. Forbes
2019-07-26 17:52:16 UTC
(In reply to Justin M. Forbes from comment #0) > Firewalld has a dependency on kernel. This is understandable, but the > kernel is no longer being built for i686 on F31 and newer. While I would > recommend dropping the arch for firewalld on those releases as well, I > suppose you could also drop the kernel Require. How do I drop the arch? Is it not sufficient to drop the "Requires: kernel ..." for i686 ? Otherwise dropping the arch in firewalld just moves the problem, doesn't it? If you do that then in glusterfs I will have to drop the "Requires: firewalld" (which is probably not correct) or drop the arch as well. Why does firewalld require the kernel? And why does it require a specific version of it? It came in with commit cb592bb "rebase to v0.6.0" about a year ago, but I don't see why it was added. If the idea is to ensure that the kernel be of at least a certain version, then even a simple Conflicts: kernel < 4.18.0 would suffice. It's possible that "Requires: (kernel >= 4.18.0 if kernel)" would also work if you really want to avoid Conflicts:, though I haven't tested it. Or just drop the dependency in rawhide because, you know, the current F31 incarnation of rawhide hasn't ever had a kernel that old. That goes for F30 as well, though not F29 as it had 4.16 prereleases early in its cycle. (In reply to Jason Tibbitts from comment #3) > Why does firewalld require the kernel? And why does it require a specific > version of it? It came in with commit cb592bb "rebase to v0.6.0" about a > year ago, but I don't see why it was added. v0.6.0 was dependent on features/fixes in the 4.18.0 kernel. At the time we were just after the transition to the 4.18 kernel. > If the idea is to ensure that the kernel be of at least a certain version, > then even a simple Conflicts: kernel < 4.18.0 would suffice. It's possible > that "Requires: (kernel >= 4.18.0 if kernel)" would also work if you really > want to avoid Conflicts:, though I haven't tested it. Or just drop the > dependency in rawhide because, you know, the current F31 incarnation of > rawhide hasn't ever had a kernel that old. That goes for F30 as well, though > not F29 as it had 4.16 prereleases early in its cycle. I will drop the Requires in rawhide an f30. |