http://bugzilla.opensuse.org/show_bug.cgi?id=1079320 Oliver Kurz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okurz@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1079320 http://bugzilla.opensuse.org/show_bug.cgi?id=1079320#c5 Nick Singer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org Flags| |needinfo?(dimstar@opensuse. | |org) --- Comment #5 from Nick Singer --- (In reply to Oliver Kurz from comment #4)

Hi nicksinger, you as the test writer, any ideas? Can you take a look into the logs?

This one looks really weird. Obviously the gnome-applet itself can communicate with the NM backend (it can scan networks, It sees the adapters, etc.). However, after issuing the nmcli commands all of a sudden the GNOME-NetworkManager-UI pops up (https://openqa.opensuse.org/tests/601692#step/NM_wpa2_enterprise/19). The empty "Visible Networks" section and the two empty buttons on top (https://openqa.opensuse.org/tests/601692#step/NM_wpa2_enterprise/19) give me the suspicion that the dbus communication between the gnome-network-settings and NM are somehow misbehaving. Unfortunately there are no logs available (no network on upload). (In reply to Dominique Leuenberger from comment #0)

This seems to be an interaction issue between GNOME Control Center and NetworkManager 1.10 (?)

As can be seen in the screenshots, the connection has been established, just g-c-c seems not able to show the status (something which somehow I could not yet reprodcue on my own machine)

No offense, but are you sure you tested the GNOME (control center) interface of NM or did you actually check the "native" NM-GUI on your local machine? In which screenshot did you see that the connection is established? https://openqa.opensuse.org/tests/601692#step/NM_wpa2_enterprise/24 unfortunately only shows that it clicks "connect". Afterwards I was unable to see any indication if the connection is actually established (I'm not a gnome user after all - sry). However. Since we still see the same error in the most recent snapshot (https://openqa.opensuse.org/tests/647737#step/NM_wpa2_enterprise/26) I'll try to extract more logs on a local machine and maybe even improve debugging here. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1079320 http://bugzilla.opensuse.org/show_bug.cgi?id=1079320#c8 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent --- Comment #8 from Ludwig Nussel --- so who can take care of this to fix the openqa test? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1079320 Yifan Jiang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gwang@suse.com, | |qkzhu@suse.com, | |yfjiang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1079320 http://bugzilla.opensuse.org/show_bug.cgi?id=1079320#c11 --- Comment #11 from Oliver Kurz --- (In reply to Jonathan Kang from comment #9)

Needles in that test are still in gnome-control-center 3.20 era. We've upgrade GNOME to 3.26 for quite a long time.

I don't see what you are referring to or how that should be relevant. This is not how openQA tests work. https://openqa.opensuse.org/tests/674191#step/NM_wpa2_enterprise/26 is the latest failure on openSUSE Tumbleweed in the snapshot 20180510. And the test fails because of the errors described in this bug - the gnome control center does not show the network the system should be connected to. https://openqa.opensuse.org/tests/673837#step/NM_wpa2_enterprise/26 is the corresponding openSUSE Leap 15.0 test showing the same symptoms. So what screen have you looked at? Our reference should be https://openqa.opensuse.org/tests/589033#step/NM_wpa2_enterprise/25 from openSUSE Tumbleweed build 20180122 where the test still worked as expected. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1079320 http://bugzilla.opensuse.org/show_bug.cgi?id=1079320#c20 --- Comment #20 from Oliver Kurz --- (In reply to Jonathan Kang from comment #14)

wlan1 is the radio used for connecting to "foobar", and it's placed in the second place of that tab(GtkStackSwitcher). So if you want to see connections available in wlan1, you need do one more click. […] To fix this, you can use wlan1 as "router" and wlan0 as "client". So the first tab(shown by default) shows the connections available.

@dheidler, @nsinger could one of you guys try this workaround in openQA tests please? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1079320 http://bugzilla.opensuse.org/show_bug.cgi?id=1079320#c22 --- Comment #22 from Dominique Leuenberger --- (In reply to Dominik Heidler from comment #21)

According to https://openqa.opensuse.org/tests/676887/modules/hwsim_wpa2_enterprise_setup... steps/1/src (line 47) networkmanager should actually ignore wlan0.

That should probably rather be done via:

nmcli device set wlan0 managed off

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1079320 http://bugzilla.opensuse.org/show_bug.cgi?id=1079320#c24 --- Comment #24 from Oliver Kurz --- https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5072 as a workaround -- You are receiving this mail because: You are on the CC list for the bug.