Bug 1823011
| Summary: | It's not possible to configure network devices in TUI | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Stodola <jstodola> | ||||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | anaconda-maint-list, awilliam, bcotton, jkonecny, jonathan, kellin, kparal, lruzicka, robatino, rvykydal, sgallagh, vanmeeuwen+fedora, vponcova, wwoods | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | AcceptedBlocker | ||||||||
| Fixed In Version: | anaconda-32.24.6-1.fc32 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-04-16 01:41:40 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: | 1705305 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1677917 [details]
anaconda.log
Created attachment 1677918 [details]
syslog
Version-Release number of selected component (if applicable):
anaconda-33.9-1.fc33
It is reproducible also on latest F32. Proposed as a Freeze Exception for 32-final by Fedora user rvykydal using the blocker tracking app because: It is impossible to configure a network device in text mode. The fix is easy and isolated. Proposed as a Blocker for 32-final by Fedora user sgallagh using the blocker tracking app because: "When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces." (basic release criteria) plus "The installer must be able to use all supported local and remote package and installer sources." (Final criteria) I'd argue that if you cannot configure the network for anything other than default operation (DHCP auto-detection) in text mode, it's not meeting these criteria. Definitely +1 FE, but really, I might be +1 blocker on this? It seems like a big problem... ...yeah, what sgallagh said. :) So, I'm +1 blocker here, with +1 FE if others disagree with calling it a blocker. +1 blocker, +1 FE if blocker is rejected FEDORA-2020-0ef5c91a97 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0ef5c91a97 So we're actually +3 blocker here. Accepting. With F32 RC1.3, I can configure network devices. I haven't really tried to configure them, but the options are there. With F32 RC1.3, the option is there, however on my T460s (which uses a normal and a wifi card) I can only configure the normal ethernet (en.. something) and the other card, usually seen as wl... something, is not visible and thus cannot be configured. In the graphical anaconda, I can normally manipulate both of that cards. In text mode only configuration of wired network devices is supported. FEDORA-2020-0ef5c91a97 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. (In reply to Radek Vykydal from comment #15) > In text mode only configuration of wired network devices is supported. I will notice that, but can you explain why? We've always been trying to use existing UIs to configure networking in Anaconda. In GUI we are using NetworkManager connection editor. For TUI we don't have similar tool that would be easy to integrate. Using terminal and nmcli seems like a better option than trying to create our own UI, a good enough solution for the (rather rare ?) cases when more advanced configuration is required - we haven't been actually seeing much requests to extend the UI for network configuration in text mode. We don't expect to bring TUI to par with GUI regarding configuration of network devices but maybe wireless would be something to consider - if we had user requests. |
Description of problem: When running anaconda in text mode, it's not possible to configure network devices. The only option in "Network configuration" is "Set host name": Installation 1) [x] Language settings 2) [x] Time settings (English (United States)) (America/New_York timezone) 3) [!] Installation source 4) [!] Software selection (Processing...) (Processing...) 5) [!] Installation Destination 6) [x] Network configuration (Processing...) (Connected: enp8s0, enp7s0, enp1s0) 7) [x] Root password 8) [!] User creation (Root account is disabled.) (No user will be created) Please make a selection from the above ['b' to begin installation, 'h' to help, 'q' to quit, 'r' to refresh]: 6 ================================================================================ ================================================================================ Network configuration Host Name: localhost.localdomain Current host name: localhost 1) Set host name Please make a selection from the above ['c' to continue, 'h' to help, 'q' to quit, 'r' to refresh]: Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Run installation in text mode (use "text" on the kernel command line) 2. Enter the "Network configuration" spoke 3. Try to configure network devices Actual results: No option to configure network devices. Expected results: It's possible to edit network devices in text mode.