testcase: test_lxc_api returns error in raring lxc server smoke tests

Bug #1130029 reported by Para Siva
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Test Cases
Fix Released
High
Serge Hallyn

Bug Description

The amd64 and i386 raring lxc server smoke tests fail with the following post installation error,

- cmd_type: testcase_test
  command: bash test.sh
  extra_info:
    action: |-
      1. Execute "test.sh"
    dependencies: n/a
    description: LXC test.
    expected_results: |-
      1. Return 0
  returncode: 2
  start_time: '2013-02-19 03:43:37'
  stderr: |-
    You have not informed bzr of your Launchpad ID, and you must do this to
    write to Launchpad or access private data. See "bzr help launchpad-login".
    Most recent Ubuntu Raring version: 0.9.0~alpha3-0ubuntu2
    Packaging branch status: CURRENT
    Most recent Ubuntu Raring version: 0.9.0~alpha3-0ubuntu2
    Packaging branch status: CURRENT
    Branched 224 revisions.
  stdout: ''
  testcase: test_lxc_api
  testsuite: /var/lib/utah/testsuites/lxc
  time_delta: '0:00:36.577046'
  user: root

This failure occurred on the 20130219 images both amd64 and i386.

The impacted jobs are,
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-amd64-smoke-lxc/95/
and
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-i386-smoke-lxc/97/

A failed yaml output is also attached.

Steps to reproduce:

(The how to setup utah is given in http://utah.readthedocs.org/en/latest/introduction.html#how-to-start-running-tests)
The steps are
sudo -u utah -i run_utah_tests.py -p lp:ubuntu-test-cases/server/preseeds/lxc.preseed -i /path/to/iso/raring-server.iso lp:ubuntu-test-cases/server/runlists/lxc.run -x /etc/utah/bridged-network-vm.xml

Related branches

Revision history for this message
Para Siva (psivaa) wrote :
Revision history for this message
Para Siva (psivaa) wrote :

d-i syslog of the same job is also attached

Revision history for this message
Javier Collado (javier.collado) wrote :

From what I see in the `test.sh`, the line that failed is:
python3 lxc/src/python-lxc/examples/api_test.py > /tmp/apiout 2>&1

Given that the output from the `api_test.py` is redirected to `/tmp/apiout/`,
it's hard to figure out what happened. Either the script should be updated to
have that information in the report or further troubleshooting has to be done
to get some error message from `api_test.py` output.

Changed in ubuntu-test-cases:
assignee: nobody → Serge Hallyn (serge-hallyn)
Para Siva (psivaa)
Changed in ubuntu-test-cases:
importance: Undecided → High
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

When I try to reproduce, I get http://paste.ubuntu.com/1683416/

@Javier,

should debug output just go to stdout? I just want confirmation on that, I can make that change trivially of course.

Revision history for this message
Javier Collado (javier.collado) wrote :

@Serge

Yes, just printing the debug output to stdout would be what we need to capture
it in the yaml report.

Regarding the timeout issue when running the lxc runlist, I'm going to check if
I get the same problem.

Revision history for this message
Javier Collado (javier.collado) wrote :

@Serge

Please note that the "-x /etc/utah/bridged-network-vm.xml" part works well in
the lab, but to reproduce the issue locally the defaults are good enough.

The command that I've used to reproduce the problem is:
sudo -u utah -i run_utah_tests.py \
    -p lp:ubuntu-test-cases/server/preseeds/lxc.preseed \
    -i /path/to/server/iso \
    lp:ubuntu-test-cases/server/runlists/lxc.run

Changed in ubuntu-test-cases:
status: New → Confirmed
Revision history for this message
Javier Collado (javier.collado) wrote :

I'm attaching the report for that I obtained for the command in the previous comment.

I also added (-n) to avoid destroying the vm, so if you need me to gather
further information to troubleshoot the problem, I should be able to do that.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks. Actually that still doesn't work, but I'll just fix up the obvious errors. The api test is actually now generated by configure, so we need to first run autogen.sh and ./configure before running that test. I'll file a merge proposal to fix this. Thanks.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :
Revision history for this message
Para Siva (psivaa) wrote :

I was able to reproduce the issue on my local machine as well, but the host OS is Quantal. Not sure if Serge is also using quantal host.

Now, I tested the above fix, on a pre-installed VM and obtained the attached result.yaml outout. The VM was installed using,

sudo -u utah -i run_utah_tests.py -p lp:ubuntu-test-cases/server/preseeds/lxc.preseed -i /path/to/iso/raring-server.iso lp:ubuntu-test-cases/server/runlists/lxc.run -n -d -x /etc/utah/bridged-network-vm.xml

Then on the VM, run
            sudo utah -f yaml -r /path/to/new_lxc.run

Please note that there is one failure in the results. Not sure if the failure is due to the fact that there has already been a set of lxc tests run on the VM, but I would assume cleanup steps would have left the VM in a fresh state after the tests.

new_lxc.run is also attached.

Revision history for this message
Para Siva (psivaa) wrote :
Changed in ubuntu-test-cases:
status: Confirmed → Fix Committed
Revision history for this message
Javier Collado (javier.collado) wrote :

@Serge

I've taken a look at lp:ubuntu-test-cases/server and haven't seen the changes committed. Am I looking at the right branch?

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

@Javier,

no, the fixes are at https://code.launchpad.net/~serge-hallyn/ubuntu-test-cases/server-lxc2 , but have not yet been merged.

Changed in ubuntu-test-cases:
status: Fix Committed → Fix Released
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.