Can't run canonical-certification-server without password on a maas provisioned node [offline]

Bug #1311927 reported by Samantha Jian-Pielak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PlainBox (Toolkit)
New
Undecided
Unassigned

Bug Description

Summary:
When running canonical-certification-server on a maas provisioned node, authentication failed and c-c-s stopped:
==========================[ Loading Jobs Definition ]===========================
===============================[ Authentication ]===============================
Error executing command as another user: Not authorized

This incident has been reported.

c-c-s is installed from the offline tarball.

Steps to reproduce:
1. Provision the SUT via MaaS server.
2. After SUT is installed, ssh in from the MaaS server.
3. On the MaaS Server, wget http://certification-static.canonical.com/checkbox-offline/trusty-server-amd64-canonical-certification-server.tar.gz and then scp the tarball to the SUT
4. tar -zxvf the tarball, cd to the new folder, sudo ./add_offline_repository -u, sudo apt-get install checkbox-ng plainbox-provider-certification-server
5. Run canonical-certification-server, click continue on the welcome msg, choose server-full-14.04 and click ok.

Expected results:
In 5, c-c-s loads the test menu.

Actual results:
==========================[ Loading Jobs Definition ]===========================
===============================[ Authentication ]===============================
Error executing command as another user: Not authorized

This incident has been reported.

Additional info:
1. The authentication passed if c-c-s is installed via APT.
2. This happens to the legacy checkbox (http://certification-static.canonical.com/checkbox-offline/trusty-server-amd64.tar.gz) as well.

Revision history for this message
Samantha Jian-Pielak (samantha-jian) wrote :

I thought the same happend to the legacy checkbox as well, but it kept going even thought it complained about the authentication.

/ polkit-agent-helper-1: pam_authenticate failed: Authentication failure
==== AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.
/ ==== AUTHENTICATING FOR org.freedesktop.policykit.pkexec.run-checkbox-backend ===
SYSTEM TESTING: Please enter your password. Some tests require root access to run properly. Your password will never be stored and will never be submitted with test results.
Authenticating as: Ubuntu (ubuntu)
Password|
Gathering information from your system...
polkit-agent-helper-1: pam_authenticate failed: Authentication failure

Choose tests to run on your system:

* b: Benchmarks tests
* c: CPU tests
* r: Create resource info for supported optical actions
* d: Disk tests
* e: Ethernet Device tests
* f: Floppy disk tests
* i: Informational tests
* m: Memory tests
* s: Miscellaneous tests
* o: Optical Drive tests
* p: Power Management tests
* t: Stress tests
* u: USB tests
* v: Virtualization tests
  +: Combine with character above to expand node
   : Space when finished

Please choose (b/c/r/d/e/f/i/m/s/o/p/t/u/v/+/ ):

Revision history for this message
Daniel Manrique (roadmr) wrote :

This looks like a duplicate of : https://bugs.launchpad.net/plainbox/+bug/1299201. To sum up, plainbox tries to use policykit to run privileged jobs, but polkit is unhappy over ssh with our secure policy.

The odd behaviors you see can be explained as follows:

- checkbox (old) tries to launch a privileged backend at the beginning. If authentication fails, the non-privileged frontend will continue but will be unable to run root jobs.

- I think if you install over APT you probably get the insecure policy (see linked bug to learn why this works). Whereas perhaps the tarball includes the secure policy. I'll check the policy packages and see what you get and whether switching policies is likely to help.

affects: checkbox-ng → plainbox
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.