wireless connection test item failed with permission error

[Alex Tu]

It always get error :

"Error: Failed to add/activate new connection: Not authorized to control networking."

Full message of that error: https://pastebin.canonical.com/p/MqNJcRHmKh/

## Connection attempt
+ nmcli d wifi connect ubuntu-cert-bg-wpa-tpelab password insecure ifname wlp2s0 name TEST_CON
Error: Failed to add/activate new connection: Not authorized to control networking.
+ nmcli -m tabular -t -f GENERAL.STATE d show wlp2s0
30 (disconnected)

## Cleaning up NM connections
+ nmcli -t -f TYPE,UUID,NAME c

------------------------------------------------------------------------- >8 ---
Outcome: job failed

jenkins job:
https://taipei-jenkins-docker.redirectme.net/job/sanity-3-testflinger-dell-bto-bionic-bucky-n5-v5-201807-26321/43/

C3 submission url:
https://certification.canonical.com/submissions/status/23200374-660b-4797-8c6c-2dfd7272ebe0

[Sylvain Pineau (sylvain-pineau)]

Many of you are trying to run checkbox over ssh via jenkins jobs. You need to take special care doing so.

The error you reported can be solved via a polkit rule (pkla file).
But in general adopt what I did for the checkbox-oem-qa snap:

https://git.launchpad.net/~oem-qa/oem-qa-checkbox/+git/checkbox-oem-qa/tree/snap/hooks/install

The relevant bits for your error are:

cat <<EOF > /etc/polkit-1/localauthority/50-local.d/com.canonical.certification.checkbox.pkla
[Checkbox]
Identity=unix-group:sudo
Action=org.freedesktop.NetworkManager.*
ResultAny=yes
ResultInactive=yes
ResultActive=yes
EOF

[Taihsiang Ho (tai271828)]

The comment#1 works for bucky CID 201807-26321. Thanks!

[Alex Tu (alextu)]

followed #2 result, we land that solution by job yaml, but get another error:

00:05:48 ## Calling a rescan
00:05:48 + nmcli d wifi rescan
00:05:48 Error: org.freedesktop.NetworkManager.network-control request failed: not authorized.

full log:
https://taipei-jenkins-docker.redirectme.net/view/Daily-Auto-Sanity/job/sanity-3-testflinger-dell-bto-bionic-bucky-n5-v5-201807-26321/67/consoleFull

[Taihsiang Ho (tai271828)]

@alex

It does not related to checkbox-ng itself.

You missed this configuration and it may matter:

echo "%sudo ALL=(ALL:ALL) NOPASSWD: ALL" > /etc/sudoers.d/checkbox

From the console log:

23:54:53 + _put etc.sudoers.d.checkbox /home/ubuntu
23:54:53 + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null etc.sudoers.d.checkbox ubuntu@10.101.49.101:/home/ubuntu
23:54:53 etc.sudoers.d.checkbox: No such file or directory
23:54:53 + _run sudo mv /home/ubuntu/etc.sudoers.d.checkbox /etc/sudoers.d/
23:54:53 + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@10.101.49.101 sudo mv /home/ubuntu/etc.sudoers.d.checkbox /etc/sudoers.d/
23:54:53 mv: cannot stat '/home/ubuntu/etc.sudoers.d.checkbox': No such file or directory

It seems a typo or something in the job.yaml