Automated screen unlock not working on wily images

Bug #1498541 reported by Francis Ginther
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Test Cases
Invalid
Undecided
Unassigned
unity8 (Ubuntu)
Invalid
High
Unassigned

Bug Description

The method to automatically unlock the screen prior to running autopilot tests is not working on wily images. For example:

https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily-mako/417/console

The CI automation uses this script to setup and perform the unlock:
http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh

The failure is seen on images from "ubuntu-touch/devel-proposed/ubuntu", in this case image 276.

Attached is the full console log from that run.

[The relavent messages are:]
I: Unlock attempt 1 failed, script output: 'initctl: unable to determine sessions
initctl: unable to determine sessions
Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
'
I: Unlock attempt 2 failed, script output: 'initctl: unable to determine sessions
initctl: unable to determine sessions
Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
'
I: Unlock attempt 3 failed, script output: 'initctl: unable to determine sessions
initctl: unable to determine sessions
Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
'
I: Unlock attempt 4 failed, script output: 'initctl: unable to determine sessions
initctl: unable to determine sessions
Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
'
I: Unlock attempt 5 failed, script output: 'initctl: unable to determine sessions
initctl: unable to determine sessions
Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
'
I: Too many unlock failures, giving up

Revision history for this message
Francis Ginther (fginther) wrote :
kevin gunn (kgunn72)
Changed in unity8 (Ubuntu):
importance: Undecided → High
Revision history for this message
Michał Sawicz (saviq) wrote :

The above log suggests it's not the tool that's failing, but rather the shell environment isn't complete - i.e. dbus and upstart details are not available.

kevin gunn (kgunn72)
Changed in unity8 (Ubuntu):
assignee: nobody → Josh Arenson (josharenson)
Revision history for this message
Michał Sawicz (saviq) wrote :
Download full text (10.9 KiB)

I just tried following http://ubuntu-test-cases-touch.readthedocs.org/en/latest/ on mako with devel-proposed:

$> IMAGE_OPT="--bootstrap --developer-mode --channel=ubuntu-touch/devel-proposed" ./scripts/provision.sh -w
FLASHING DEVICE
Attempting adb reboot bootloader
=========== Device in fastboot ==========
WARNING --developer-mode and --password are dangerous as they remove security features from your device
2015/09/22 19:00:23 Expecting the device to be in the bootloader... waiting
2015/09/22 19:00:23 Device is |mako|
2015/09/22 19:00:23 Flashing version 311 from ubuntu-touch/devel-proposed channel and server https://system-image.ubuntu.com to device mako
6.29 MB / 6.29 MB [========================================================================================================================================================================================================================================] 100.00 % 5.02 MB/s
52.43 MB / 52.43 MB [======================================================================================================================================================================================================================================] 100.00 % 9.61 MB/s
302.71 MB / 302.71 MB [===================================================================================================================================================================================================================================] 100.00 % 16.90 MB/s
2015/09/22 19:00:59 Start pushing /home/michal/.cache/ubuntuimages/pool/ubuntu-347a20361b2397d6875cbacec432acd51a6771f82038a2ee29afd5a74d5d4938.tar.xz to device
2015/09/22 19:00:59 Start pushing /home/michal/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2015/09/22 19:00:59 Start pushing /home/michal/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2015/09/22 19:00:59 Start pushing /home/michal/.cache/ubuntuimages/pool/custom-a4fc258c566f523739147a951e9dd53c03b46d7b0ca768dd4d5dd5a3738a0a4d.tar.xz to device
2015/09/22 19:00:59 Start pushing /home/michal/.cache/ubuntuimages/pool/device-00f7ea9bb6e1b445460b981872b273c4a49cea282a4478831543ccf9d83d7ab2.tar.xz to device
2015/09/22 19:00:59 Start pushing /home/michal/.cache/ubuntuimages/ubuntu-touch/devel-proposed/ubuntu/mako/version-311.tar.xz to device
2015/09/22 19:00:59 Done pushing /home/michal/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2015/09/22 19:00:59 Done pushing /home/michal/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2015/09/22 19:00:59 Done pushing /home/michal/.cache/ubuntuimages/ubuntu-touch/devel-proposed/ubuntu/mako/version-311.tar.xz to device
2015/09/22 19:01:02 Done pushing /home/michal/.cache/ubuntuimages/pool/custom-a4fc258c566f523739147a951e9dd53c03b46d7b0ca768dd4d5dd5a3738a0a4d.tar.xz to device
2015/09/22 19:01:13 Done pushing /home/michal/.cache/ubuntuimages/pool/device-00f7ea9bb6e1b445460b981872b273c4a49cea282a4478831543ccf9d83d7ab2.tar.xz to device
2015/09/22 19:01:59 Done pushing /home/michal/.cache/ubuntuimages/pool/ubuntu-347a20361b2397d6875cbacec432acd51a6771f82038a2ee29afd5a74d5d4938.tar.xz to device
2015/09/22 19:01:59 Created ubuntu_command: /home/michal/.cache/ubuntuimages...

Changed in unity8 (Ubuntu):
status: New → Incomplete
assignee: Josh Arenson (josharenson) → nobody
Revision history for this message
Michał Sawicz (saviq) wrote :

I just noticed:

+ export REVISION=--revision=276
[...]
2015/09/22 12:38:36 Flashing version 276 from ubuntu-touch/devel-proposed/ubuntu channel and server https://system-image.ubuntu.com to device mako

The job seems hardcoded on image 276 for some reason, when we're at 311 already, and that's what I've tested. Trying with image 276 now.

Revision history for this message
Francis Ginther (fginther) wrote :

The jenkins job was indeed hardcoded to use image 276 due to an unbootable image at 277. We then failed to remove this once the image was fixed. Image 311 is working and unlock is successful:

https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily-mako/421/consoleFull

[log snippet]
INFO:reboot-and-wait:Network is active
I: Unlock attempt 1 failed, script output: 'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files
'
I: Unlock passed

This is now working (transient failed attempts are expected). I think we can close this.

Michał Sawicz (saviq)
Changed in unity8 (Ubuntu):
status: Incomplete → Invalid
Changed in ubuntu-test-cases:
status: New → Invalid
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.