|
Bugzilla – Full Text Bug Listing |
| Summary: | 'yast2 lan' tool does not store WIRELESS_WPA_PSK credentials in the WLAN wireless configuration file | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Sebastian Makowiecki <soocki> |
| Component: | YaST2 | Assignee: | Knut Alejandro Anderssen González <kanderssen> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | alynx.zhou, jreidinger, kanderssen, mmanu84, soocki |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2log | ||
|
Description
Sebastian Makowiecki
2019-11-01 10:34:09 UTC
(In reply to Sebastian Makowiecki from comment #0) > Fresh Tumbleweed install, when trying to establish connection to a WPA-PSK > protected WLAN network the 'yast2 lan' tool exits silently, the wireless > interface stays down with no apparent effect. The only symptom/indication > (besides the lack of connection) of the things not going right is the error > of the wicked systemd service in the form of ’WIRELESS_WPA_PSK value not > specified'. > > The solution/workaround is to manually add the WIRELESS_WPA_PSK='passphrase' > line to the wireless interface wicked configuration file at > '/etc/sysconfig/network/ifcfg-wlp4s0' followed by the restart of thw wicked > systemd service. If at any time after that the 'yast2 lan' tool is used > again the line disappears from the file and the procedure need to be > repeated. > > This issue was briefly discussed in the forum at: > > https://forums.opensuse.org/showthread.php/538061-Wicked-can-t-connect-WLAN- > WIRELESS_WPA_PSK-value-not-specified-systemd-wicked-unit-error?p=2918607 Thanks for report. Can you please attach your yast logs? (output of save_y2logs ) It will help us to point to specific part of code responsible for it. Thanks Created attachment 823324 [details]
y2log
y2log, as requested.
Should be fixed in yast2-network-4.2.26: https://github.com/yast/yast-network/pull/1001 |