ClearFoundation Tracker - ClearOS | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0022291 | ClearOS | app-network - Network Settings | public | 2018-11-08 09:00 | 2019-02-23 17:39 |
| Reporter | user2 | ||||
| Assigned To | tracker | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | suspended | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | 7.6.0 Updates | Fixed in Version | |||
| Summary | 0022291: Change recent virbrX behavior | ||||
| Description | Tracker 0014241 requested virbrX interfaces to be added like brX interfaces. However, these are different beasts: - brX interfaces are created by admins for bridging network interfaces. At this point, the brX interface can be treated just like any plain old interface. - virbrX interfaces are used by libvirt and should be managed through virsh, e.g. virsh net-edit default. virbrX interfaces should be hidden or set as read-only. Do the same for dockerX interfaces - these should be managed through Docker configuration files. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2018-11-08 09:00 | user2 | New Issue | |||
| 2018-11-08 09:00 | user2 | Assigned To | => user2 | ||
| 2018-11-08 09:00 | user2 | Status | new => confirmed | ||
| 2018-12-14 11:58 | dloper | Target Version | 7.6.0 => 7.6.0 Updates | ||
| 2018-12-14 12:10 | user2 | Status | confirmed => assigned | ||
| 2018-12-14 12:10 | user2 | Assigned To | user2 => tracker | ||
| 2019-02-23 17:39 | dloper | Note Added: 0009801 | |||
| 2019-02-23 17:39 | dloper | Status | assigned => closed | ||
| 2019-02-23 17:39 | dloper | Resolution | open => suspended | ||
| Notes | |||||
|
|
|||||
|
|
||||