| Anonymous | Login | 2024-04-23 12:55 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0013621 | ClearOS | app-firewall - Firewall | public | 2017-03-09 19:08 | 2020-03-05 04:40 | ||||
| Reporter | user2 | ||||||||
| Assigned To | |||||||||
| Priority | normal | Severity | tweak | Reproducibility | have not tried | ||||
| Status | closed | Resolution | won't fix | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0013621: Detect when IMQ support is not available | ||||||||
| Description | The firewall should avoid trying to run QoS if the underlying kernel does not support it. Scenarios: - When a customer runs a vanilla upstream kernel in order to take advantage of custom drivers - Cloud installs, e.g. Linode | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
|
(0005031) NickH (developer) 2017-03-10 01:20 |
I think this is missing the issue, but is a good idea anyway. The issue is that an el7 kernel (vanilla kernel) has made its way through to the repos and has replaced a proper ClearOS kernel. Mine arrived on 23/02 via the nightly updates on Business. This should never happen. El7 kernels should never get released into the standard repos. The real bug is that an el7 kernel has been released and the real fix is to rush through a v7 kernel to replace the el7 kernel. This bug would only help in the case that a mistake with the kernels was made again in the future. |
|
(0005041) user2 2017-03-10 07:17 |
I'll push through the kernel update. The real real issue is the architecture of the repos and the added complexity in ClearOS 7. We went from a two repo system (free and paid) to a 5 repo system (don't ask). On it. |
|
(0005051) user2 2017-03-10 07:29 |
I see the issue, definitely human error (and mine). The current ClearOS 7 build system architecture has a few gaps in separating minor releases, notably in the ClearOS maintained CentOS and EPEL repos. These repose are manually maintained in a separate silo, but will be re-integrated back into the build system for version 7.4. |
|
(0013401) NickH (developer) 2020-03-05 04:40 |
We have abandoned the IMQ patch now and use a vanilla upstream kernel. QoS has switched to using IFB. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2017-03-09 19:08 | user2 | New Issue | |
| 2017-03-09 19:08 | user2 | Assigned To | => user2 |
| 2017-03-09 19:08 | user2 | Status | new => confirmed |
| 2017-03-10 01:20 | NickH | Note Added: 0005031 | |
| 2017-03-10 07:17 | user2 | Note Added: 0005041 | |
| 2017-03-10 07:29 | user2 | Note Added: 0005051 | |
| 2017-03-10 07:34 | user2 | Relationship added | related to 0013351 |
| 2018-12-14 12:11 | user2 | Status | confirmed => assigned |
| 2018-12-14 12:11 | user2 | Assigned To | user2 => tracker |
| 2020-03-05 04:40 | NickH | Note Added: 0013401 | |
| 2020-03-05 04:40 | NickH | Status | assigned => closed |
| 2020-03-05 04:40 | NickH | Assigned To | tracker => |
| 2020-03-05 04:40 | NickH | Resolution | open => won't fix |
|
Issue History |