Checkbox : wireless testing

snap
1

when i run this job com.canonical.certification::wireless/wireless_connection_wpa_bg , i get cannot delete unkonw connections?

is it mandatory required to delete con in this part of code in wireless/jobs.pxu?
trap “nmcli con delete id $WPA_BG_SSID” EXIT

if by default nothing is connected from wifi delete is not required. please suggest.

--------------------[ wireless/wireless_connection_wpa_bg ]---------------------
ID: com.canonical.certification::wireless/wireless_connection_wpa_bg
Category: com.canonical.plainbox::wireless
... 8< -------------------------------------------------------------------------
Can't write to /etc/NetworkManager/system-connections/IFC. Is this command being run as root?
Error: unknown connection 'IFC'
Error: cannot delete unknown connection(s): 'IFC'.
2

does your image actually use network-manager ? else that test is moot … (i’m not sure if plainbox has a wlan test for the default network setup via netplan though … )

3

i do have network-manager snap installed which uses nmcli commands

$snap list
network-manager 1.2.2-13 232 canonical devmode

removed this del command and tried
–trap “nmcli con delete id $WPA_BG_SSID” EXIT

ID: com.canonical.certification::wireless/wireless_connection_wpa_bg
Category: com.canonical.plainbox::wireless
... 8< -------------------------------------------------------------------------
**Can't write to /etc/NetworkManager/system-connections/IFC.** Is this command being run as root?

plainbox uses nmcli commands to test the wifi interafces

4

plainbox-provider-checkbox , create_connection “Failed to register”

is it not possible to run the below 2 commands in one command?

$ nmcli con add con-name $WPA_BG_SSID ifname wlan0 type wifi ssid $WPA_BG_SSID
$ nmcli c modify $WPA_BG_SSID wifi-sec.key-mgmt wpa-psk wifi-sec.psk $WPA_BG_PSK

if i manually run the above 2 commands and then run the job wireless/wireless_connection_wpa_bg, test passes.
fyi, #write_connection_file(name, wifi_connection) , i would assume this is not required for ubuntu snap core.

when ethernet and wlan0 connected, wlan0 “ping test fails” is this expected behaviour or do we need to change ethernet to control from network-manager

5

The job you’re using comes from plainbox-provider-checkbox, which mainly dealt with desktops.
plainbox-provider-snappy has wireless/wireless_connection_wpa_bg_nm_{{ interface }} jobs for snappy systems.
I recommend you try those.

Also, if there are two similar jobs that come from those two providers, then on snappy you should always use the one from plainbox-provider-snappy.

Also browsing test plans can be useful as they include the right ones.

6

when i tried to run the wireless/wireless_connection_wpa_bg_nm_{{ interface }} , i get this below error.

-------------------[ Collect information about connections ]--------------------
ID: com.canonical.certification::connections
Category: com.canonical.plainbox::uncategorised
... 8< -------------------------------------------------------------------------
slot: core:alsa
plug: alsa-utils:alsa

slot: core:home
plug: alsa-utils:home

slot: bluez:service
plug: bluez:client

slot: core:uhid
plug: bluez:uhid

slot: core:network-bind
plug: checkbox-snappy:network-bind

slot: core:classic-support
plug: classic:classic-support

slot: core:core-support
plug: core:core-support-plug

slot: core:lxd-support
plug: lxd:lxd-support

slot: core:network
plug: lxd:network

slot: core:firewall-control
plug: network-manager:firewall-control

slot: core:network-setup-observe
plug: network-manager:network-setup-observe

slot: network-manager:service
plug: network-manager:nmcli

slot: core:ppp
plug: network-manager:ppp

slot: core:firewall-control
plug: wifi-ap:firewall-control

slot: core:network
plug: wifi-ap:network

slot: core:network-bind
plug: wifi-ap:network-bind

slot: core:network-control
plug: wifi-ap:network-control

slot: network-manager:service
plug: wifi-ap:network-manager

----------------[ System can discover Wi-Fi networks on wlan0 ]-----------------
ID: com.canonical.certification::wireless/wireless_scanning_wlan0
Category: com.canonical.certification::wifi
Job cannot be started because:
 - resource expression "connections.slot == 'network-manager:service' and connections.plug == 'checkbox-snappy:network-manager'" evaluates to false
Outcome: job cannot be started

D: com.canonical.certification::wireless/wireless_connection_open_bg_nm_wlan0
Category: com.canonical.certification::wifi
Job cannot be started because:
 - resource expression "connections.slot == 'network-manager:service' and connections.plug == 'checkbox-snappy:network-manager'" evaluates to false
Outcome: job cannot be started

vinaysimha@localhost:~$ snap interfaces | grep network-manager
:firewall-control            network-manager
:network-setup-observe       network-manager
:ppp                         network-manager
network-manager:service      network-manager:nmcli
-                            checkbox-snappy:network-manager
-                            network-manager:modem-manager
-                            network-manager:wpa

vinaysimha@localhost:~$ systemctl status snap.networkmanager
● snap.networkmanager.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
7

The hyphen (-) in the first column indicates that the checkbox-snappy:network-manager plug is not connected to a slot. Run the following to connect it:

$ snap connect checkbox-snappy:network-manager network-manager:service
8

is it possible to set this command in launcher

snap connect checkbox-snappy:network-manager network-manager:service

9

On the assumption that you’ve installed the snap using --devmode then it is possible.