test_lxc_api test fails during container creation

Bug #1207675 reported by Para Siva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Test Cases
Fix Released
Undecided
Unassigned
lxc (Ubuntu)
Fix Released
Medium
Serge Hallyn

Bug Description

The following error is reported during the lxc smoke tests with saucy server installations starting from 20130801.

 lxc_container: container creation template for 5a76cd30-fb51-11e2-a901-5254008aabee exited with 1

    Traceback (most recent call last):
      File "src/python-lxc/examples/api_test.py", line 58, in <module>
        == container.get_config_item("lxc.utsname"))
    AssertionError
  stdout: pwd
/var/lib/utah/testsuites/lxc/lxc/test_lxc_api
id
uid=0(root) gid=0(root) groups=0(root),1000(utah)
/proc/self/status
Name: cat
State: R (running)
Tgid: 3762
Pid: 3762
PPid: 3760
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0 1000
VmPeak: 4260 kB
VmSize: 4260 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 548 kB
VmRSS: 548 kB
VmData: 160 kB
VmStk: 136 kB
VmExe: 44 kB
VmLib: 1844 kB
VmPTE: 24 kB
VmSwap: 0 kB
Threads: 1
SigQ: 0/3830
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000001000000
SigCgt: 0000000000000000
CapInh: 0000000000000000
CapPrm: 0000001fffffffff
CapEff: 0000001fffffffff
CapBnd: 0000001fffffffff
Seccomp: 0
Cpus_allowed: 1
Cpus_allowed_list: 0
Mems_allowed: 1
Mems_allowed_list: 0
voluntary_ctxt_switches: 0
nonvoluntary_ctxt_switches: 0
ls /
bin
boot
dev
etc
home
initrd.img
initrd.img.old
lib
lost+found
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var
vmlinuz
vmlinuz.old
ls /proc
1
10
11
12
121
122
13
14
15
16
17
17482
1750
1798
18
18556
19
2
20
21
22
24
2401
25
250
26
27
271
275
2771
28
29
3
336
344
350
352
3522
3523
3527
3528
3529
354
363
3758
3759
3760
3764
387
40
43
44
46
5
531
566
6
66
67
68
6881
7
730
739
750
755
759
8
804
816
818
819
831
894
9
911
936
acpi
buddyinfo
bus
cgroups
cmdline
consoles
cpuinfo
crypto
devices
diskstats
dma
dri
driver
execdomains
fb
filesystems
fs
interrupts
iomem
ioports
irq
kallsyms
kcore
key-users
kmsg
kpagecount
kpageflags
latency_stats
loadavg
locks
mdstat
meminfo
misc
modules
mounts
net
pagetypeinfo
partitions
sched_debug
schedstat
scsi
self
slabinfo
softirqs
stat
swaps
sys
sysrq-trigger
sysvipc
timer_list
timer_stats
tty
uptime
version
version_signature
vmallocinfo
vmstat
zoneinfo
I am 3760
Getting instance for '5a76cd30-fb51-11e2-a901-5254008aabee'
Creating rootfs using 'ubuntu'
=======================
This had happened twice out of 4 installations and happens with both amd64 and i386. Please see below link for more details.
https://jenkins.qa.ubuntu.com/view/Saucy/view/Smoke%20Testing/job/saucy-server-amd64-smoke-lxc/96/artifact/utah-12380-saucy-server-amd64_lxc.run_2013-08-01_10-08-42.yaml/*view*/

The impacted smoke tests are:
https://jenkins.qa.ubuntu.com/view/Saucy/view/Smoke%20Testing/job/saucy-server-i386-smoke-lxc/91/
and
https://jenkins.qa.ubuntu.com/view/Saucy/view/Smoke%20Testing/job/saucy-server-amd64-smoke-lxc/96/

Steps to reproduce:
1. Install utah using
   sudo apt-add-repository -y ppa:utah/stable
   sudo apt-get update
   sudo apt-get install utah

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

Revision history for this message
Para Siva (psivaa) wrote :
Revision history for this message
Para Siva (psivaa) wrote :
Para Siva (psivaa)
description: updated
Changed in lxc (Ubuntu):
assignee: nobody → Serge Hallyn (serge-hallyn)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Updated the lxc_test_api testcase to always grab the latest source with pull-lp-source. This fixed it for me in saucy.

(the failure was a result of an API mis-match)

Changed in lxc (Ubuntu):
status: In Progress → Fix Released
Changed in ubuntu-test-cases:
status: New → 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.