[Bug 1268421] Re: Test failures if subunit module is installed
** Changed in: subunit Importance: High = Wishlist ** Summary changed: - Test failures if subunit module is installed + Test failures if tests are run from an installed copy of subunit -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to subunit in Ubuntu. https://bugs.launchpad.net/bugs/1268421 Title: Test failures if tests are run from an installed copy of subunit To manage notifications about this bug go to: https://bugs.launchpad.net/subunit/+bug/1268421/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1268421] Re: Test failures if subunit module is installed
So this indicates that the wrong copy of subunit is being picked up by the test suite in this mode. Would love a patch. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to subunit in Ubuntu. https://bugs.launchpad.net/bugs/1268421 Title: Test failures if subunit module is installed To manage notifications about this bug go to: https://bugs.launchpad.net/subunit/+bug/1268421/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1316475] Re: trusty hang on first boot post deploy
+1 on disabling cloudsigma by default. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1316475 Title: trusty hang on first boot post deploy To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1316475/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1280941] Re: metadata agent throwing AttributeError: 'HTTPClient' object has no attribute 'auth_tenant_id' with latest release
** Changed in: tripleo Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-neutronclient in Ubuntu. https://bugs.launchpad.net/bugs/1280941 Title: metadata agent throwing AttributeError: 'HTTPClient' object has no attribute 'auth_tenant_id' with latest release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1280941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1280941] Re: metadata agent throwing AttributeError: 'HTTPClient' object has no attribute 'auth_tenant_id' with latest release
@ihar please do submit a patch :). Note that the requirements.txt in question is neutrons one. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-neutronclient in Ubuntu. https://bugs.launchpad.net/bugs/1280941 Title: metadata agent throwing AttributeError: 'HTTPClient' object has no attribute 'auth_tenant_id' with latest release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1280941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1280936] [NEW] /etc/default/libvirt-bin does not affect libvirt's upstart job
Public bug reported: In the upstart job it says: # /etc/default/libvirt-bin will be deprecated soon. # If you used to set $libvirtd_opts in /etc/default/libvirt-bin, # change the 'exec' line here instead. script [ -r /etc/default/libvirt-bin ] . /etc/default/libvirt-bin exec /usr/sbin/libvirtd $libvirtd_opts end script But, this as it stands doesn't work - I changed /e/default/libvirt-bin to add -l to the libvirtd daemon flags, and it had no effect, when I altered the libvirt-bin.conf upstart job and did the same to the env line near the top it worked. The bug is the claim that the old, simple, unconflated style is deprecated: its broken. I think it would be better to either keep supporting it (please!) or not claim that its deprecated when (at least AFAICT) its broken. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1280936 Title: /etc/default/libvirt-bin does not affect libvirt's upstart job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1280936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1270649] [NEW] weird tunnel behaviour with openvswitch 2.0.1 dkms module + saucy 3.11 kernel
Public bug reported:
I wrote this up here - http://lists.openstack.org/pipermail/openstack-
operators/2014-January/003893.html originally .
Firstly, outbound GRE packets are sent just fine. On a machine running
1.10.2, they are received and processed correctly.
Inbound GRE packets are not received though.
tcpdump shows them on the physical interface(eth2) and the local
bridged (br-untagged) but they don't hit br-tun at all:
ovs-ofctl dump-flows br-tun
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=471.219s, table=0, n_packets=483, n_bytes=39986,
idle_age=1, priority=1,in_port=1 actions=resubmit(,1)
cookie=0x0, duration=470.535s, table=0, n_packets=0, n_bytes=0,
idle_age=470, priority=1,in_port=2 actions=resubmit(,2)
...
note the n_packets=0 on in_port 2, which is the gre port:
...
2(gre-10.10.16.17): addr:92:07:f1:42:f3:a4
config: 0
state: 0
speed: 0 Mbps now, 0 Mbps max
oddly but perhaps unrelated?, that port name is truncated -
Bridge br-tun
Port br-tun
Interface br-tun
type: internal
Port gre-10.10.16.175
Interface gre-10.10.16.175
type: gre
options: {in_key=flow, local_ip=10.10.16.176,
out_key=flow, remote_ip=10.10.16.175}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
The kernel datapath doesn't bring up the incoming flow - for instance,
on 1.10.2 we'd see:
# ovs-appctl dpif/dump-flows br-tun
tunnel(tun_id=0x1,src=10.10.16.175,dst=10.10.16.176,tos=0x0,ttl=64,flags(key)),in_port(3),eth(src=fa:16:3e:c7:fd:70,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=10.0.0.1,tip=10.0.0.6,op=1,sha=fa:16:3e:c7:fd:70,tha=00:00:00:00:00:00),
packets:3963, bytes:166446, used:0.756s,
actions:push_vlan(vid=1,pcp=0),1,pop_vlan,8,16,14,push_vlan(vid=1,pcp=0),6,pop_vlan,12,10
in_port(2),eth(src=56:96:98:5e:94:4a,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0800),ipv4(src=0.0.0.0,dst=255.255.255.255,proto=17,tos=0x10,ttl=128,frag=no),udp(src=68,dst=67),
packets:0, bytes:0, used:4.610s, actions:drop
#
but on 2.0.1 we see:
# ovs-appctl dpif/dump-flows br-tun
#
There's nothing in iptables-save to suggest we're filtering GRE (and
in fact just replacing the openvswitch module without rebooting or
running iptables commands).
I'm not sure how/where the incoming GRE packets are handled - I
suspect it's in-kernel and somewhat inaccessible for debugging...
We'd like to get the dkms datapath working so we can support NXVLAN
which still requires the openvswitch supplied module; I haven't tried
plain 2.1 at this point. I guess the first thing is to see if you can
reproduce this, or if it's an oddity in my environment.
** Affects: openvswitch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1270649
Title:
weird tunnel behaviour with openvswitch 2.0.1 dkms module + saucy 3.11
kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1270649/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1254338] Re: lxc containers failing dhcp
Indeed - running sudo iptables -t mangle -A POSTROUTING -o lxcbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill In the host permits networking to work correctly. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1254338 Title: lxc containers failing dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1254338/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1254338] [NEW] lxc containers failing dhcp
Public bug reported: I just noticed this about a week ago when I was leaving Hong Kong after the ODS. My older containers (e.g. precise, or lucid) are failing to bring up networking. Checking syslog in the container: Nov 23 06:39:59 subunit-lucid dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Nov 23 06:39:59 subunit-lucid dhclient: 5 bad udp checksums in 5 packets Nov 23 06:40:07 subunit-lucid dhclient: No DHCPOFFERS received. Nov 23 06:40:07 subunit-lucid dhclient: No working leases in persistent database - sleeping. Nov 23 06:44:03 subunit-lucid dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Which makes me think that the host lxc bridge no longer does checksum fixups, which will break older containers. Without networking updating the containers to do a local fix is uhm, hard - if I'm right there's a bunch of folk out there scratching their heads and recreating containers (with appropriate swear words...) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1254338 Title: lxc containers failing dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1254338/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1254338] Re: lxc containers failing dhcp
Adding
iptables -t mangle -A POSTROUTING -o ${LXC_NETWORK} -p udp -m udp
--dport 68 -j CHECKSUM --checksum-fill
to /etc/init/lxc-net.conf
will fix it on boot for anyone suffering this - I'm happy to wrap that
up in a debdiff if this is considered an appropriate fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1254338
Title:
lxc containers failing dhcp
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1254338/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1254338] Re: lxc containers failing dhcp
I can see this: dhcp3 (3.1.3-2ubuntu3.5) lucid-proposed; urgency=low * Include patch from RedHat/Fedora to deal with hardware/xen/virtio offload of UDP checksums. (LP: #930962) * Update apparmor profile to add required the network packet raw rule for the checksum change. -- Stéphane Graber stgra...@ubuntu.com Thu, 23 May 2013 19:58:28 -0400 In the dhcp3-client changelog, but this won't help anyone with existing containers: surely the thing to do is to wait for that to be in the default for all new containers (e.g. 5 years) then remove the checksum-fill support? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1254338 Title: lxc containers failing dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1254338/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1226855] Re: Cannot use open-iscsi inside LXC container
** Changed in: lxc (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1201938] Re: excessive memory use from libvirtd
Stable memory use after three days. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to netcf in Ubuntu. https://bugs.launchpad.net/bugs/1201938 Title: excessive memory use from libvirtd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1201938/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1201938] Re: excessive memory use from libvirtd
This is much better for me, but I have seen an increase of 1M over 5 hours so far - so there may be another lower-frequency leak. I will file a new bug if I find that to be the case. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to netcf in Ubuntu. https://bugs.launchpad.net/bugs/1201938 Title: excessive memory use from libvirtd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1201938/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1193594] Re: lxc-create hanging
*** This bug is a duplicate of bug 1182540 *** https://bugs.launchpad.net/bugs/1182540 Ok cool - thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1193594 Title: lxc-create hanging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1193594/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1193594] Re: lxc-create hanging
Oh and yes, / is btrfs, and /var/lib/lxc is on that fs. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1193594 Title: lxc-create hanging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1193594/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1193594] Re: lxc-create hanging
ps -ef | pastebinit http://paste.ubuntu.com/5796412/ sudo lsof http://paste.ubuntu.com/5796420/ Yes, I see no sign of debootstrap happening While hung: ps -ef | pastebinit http://paste.ubuntu.com/5796427/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1193594 Title: lxc-create hanging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1193594/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1193594] Re: lxc-create hanging
*** This bug is a duplicate of bug 1182540 *** https://bugs.launchpad.net/bugs/1182540 Indeed, that worked - thanks. Will everyone upgrading encounter this? If so, perhaps a forced flush on new version runs would be a good idea? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1193594 Title: lxc-create hanging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1193594/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1193594] [NEW] lxc-create hanging
Public bug reported: Running sudo lxc-create -n troveclient -t ubuntu -- --bindhome $(whoami) -a i386 is hanging: lxc-create: No config file specified, using the default config /etc/lxc/default.conf I've left it for 15+ m with no further output. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Jun 22 22:29:02 2013 InstallationDate: Installed on 2013-01-13 (159 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-04-22 (61 days ago) lxcsyslog: ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1193594 Title: lxc-create hanging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1193594/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1193594] Re: lxc-create hanging
When I ctrl-C it I get ^CDelete subvolume '/var/lib/lxc/troveclient/rootfs' lxc-create: aborted -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1193594 Title: lxc-create hanging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1193594/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1098641] Re: visible_hostname defaults to hostname of first http_port IP, not get_hostname()
Please open this upstream - using 127.0.0.1 as the visible hostname would never be sensible IMO. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1098641 Title: visible_hostname defaults to hostname of first http_port IP, not get_hostname() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1098641/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1098641] Re: visible_hostname defaults to hostname of first http_port IP, not get_hostname()
(Though I think 3.3.3 may be fixed). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1098641 Title: visible_hostname defaults to hostname of first http_port IP, not get_hostname() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1098641/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
robertc@lifelessdesktop:~$ sudo lxc-start -n lucid-test-lp -linfo -o /tmp/output lxc-start: No cgroup mounted on the system lxc-start: failed to spawn 'lucid-test-lp' robertc@lifelessdesktop:~$ less /tmp/output lxc-start 1357584051.325 INFO lxc_conf - tty's configured lxc-start 1357584051.325 INFO lxc_start - 'lucid-test-lp' is initialized lxc-start 1357584051.356 INFO lxc_conf - opened /var/lib/lxc/lucid-test-lp/rootfs.hold as fd 18 lxc-start 1357584051.357 ERRORlxc_cgroup - No cgroup mounted on the system lxc-start 1357584051.372 ERRORlxc_start - failed to spawn 'lucid-test-lp' ** Changed in: lxc (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
robertc@lifelessdesktop:~$ sudo lxc-start -n lucid-test-lp -ldebug -o /tmp/output lxc-start: No cgroup mounted on the system lxc-start: failed to spawn 'lucid-test-lp' robertc@lifelessdesktop:~$ less /tmp/output lxc-start 1357584371.308 DEBUGlxc_conf - allocated pty '/dev/pts/3' (4/5) lxc-start 1357584371.308 DEBUGlxc_conf - allocated pty '/dev/pts/7' (6/7) lxc-start 1357584371.308 DEBUGlxc_conf - allocated pty '/dev/pts/8' (8/9) lxc-start 1357584371.308 DEBUGlxc_conf - allocated pty '/dev/pts/9' (10/11) lxc-start 1357584371.308 INFO lxc_conf - tty's configured lxc-start 1357584371.308 DEBUGlxc_console - using '/dev/tty' as console lxc-start 1357584371.308 DEBUGlxc_start - sigchild handler set lxc-start 1357584371.308 INFO lxc_start - 'lucid-test-lp' is initialized lxc-start 1357584371.312 DEBUGlxc_start - Not dropping cap_sys_boot or watching utmp lxc-start 1357584371.314 DEBUGlxc_conf - mac address of host interface 'vethY1hl2O' changed to private fe:0e:89:11:b6:c1 lxc-start 1357584371.316 DEBUGlxc_conf - instanciated veth 'vethY1hl2O/vethzYYWp8', index is '19' lxc-start 1357584371.316 INFO lxc_conf - opened /var/lib/lxc/lucid-test-lp/rootfs.hold as fd 18 lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/' (rootfs) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/sys' (sysfs) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/proc' (proc) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/dev' (devtmpfs) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/dev/pts' (devpts) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/run' (tmpfs) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/' (ext4) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/sys/fs/fuse/connections' (fusectl) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/sys/kernel/debug' (debugfs) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/sys/kernel/security' (securityfs) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/run/lock' (tmpfs) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/run/shm' (tmpfs) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/run/user' (tmpfs) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/proc/sys/fs/binfmt_misc' (binfmt_misc) lxc-start 1357584371.318 DEBUGlxc_cgroup - checking '/run/user/robertc/gvfs' (fuse.gvfsd-fuse) lxc-start 1357584371.318 ERRORlxc_cgroup - No cgroup mounted on the system lxc-start 1357584371.332 ERRORlxc_start - failed to spawn 'lucid-test-lp' -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
robertc@lifelessdesktop:~$ cat /proc/self/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=8129608k,nr_inodes=2032402,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=3257152k,mode=755 0 0 /dev/disk/by-uuid/9dce3ded-5110-40ec-9401-0e46a11f281d / ext4 rw,relatime,errors=remount-ro,stripe=32,data=ordered 0 0 none /sys/fs/fuse/connections fusectl rw,relatime 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 none /sys/kernel/security securityfs rw,relatime 0 0 none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0 none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 gvfsd-fuse /run/user/robertc/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 robertc@lifelessdesktop:~$ cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=8129608k,nr_inodes=2032402,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=3257152k,mode=755 0 0 /dev/disk/by-uuid/9dce3ded-5110-40ec-9401-0e46a11f281d / ext4 rw,relatime,errors=remount-ro,stripe=32,data=ordered 0 0 none /sys/fs/fuse/connections fusectl rw,relatime 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 none /sys/kernel/security securityfs rw,relatime 0 0 none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0 none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 gvfsd-fuse /run/user/robertc/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 robertc@lifelessdesktop:~$ mount /dev/mapper/isw_bichcdfhcg_ARRAY0p6 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu) cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct) cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfsd-fuse on /run/user/robertc/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=robertc) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
cat /etc/mtab /dev/mapper/isw_bichcdfhcg_ARRAY0p6 / ext4 rw,errors=remount-ro 0 0 proc /proc proc rw,noexec,nosuid,nodev 0 0 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0 none /sys/fs/fuse/connections fusectl rw 0 0 none /sys/kernel/debug debugfs rw 0 0 none /sys/kernel/security securityfs rw 0 0 udev /dev devtmpfs rw,mode=0755 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0 tmpfs /run tmpfs rw,noexec,nosuid,size=10%,mode=0755 0 0 none /run/lock tmpfs rw,noexec,nosuid,nodev,size=5242880 0 0 none /run/shm tmpfs rw,nosuid,nodev 0 0 none /run/user tmpfs rw,noexec,nosuid,nodev,size=104857600,mode=0755 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0 cgroup /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0 gvfsd-fuse /run/user/robertc/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,user=robertc 0 0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
robertc@lifelessdesktop:~$ less /etc/init/cgroup-lite.conf
description mount available cgroup filesystems
author Serge Hallyn serge.hal...@canonical.com
start on mounted MOUNTPOINT=/sys
pre-start script
test -x /bin/cgroups-mount || { stop; exit 0; }
test -d /sys/fs/cgroup || { stop; exit 0; }
/bin/cgroups-mount
end script
post-stop script
if [ -x /bin/cgroups-umount ]
then
/bin/cgroups-umount
fi
end script
robertc@lifelessdesktop:~$ sudo /bin/cgroups-mount
robertc@lifelessdesktop:~$ cat /proc/self/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=8129608k,nr_inodes=2032402,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=3257152k,mode=755 0 0
/dev/disk/by-uuid/9dce3ded-5110-40ec-9401-0e46a11f281d / ext4
rw,relatime,errors=remount-ro,stripe=32,data=ordered 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0
none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc
rw,nosuid,nodev,noexec,relatime 0 0
gvfsd-fuse /run/user/robertc/gvfs fuse.gvfsd-fuse
rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
cgroup /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0
cgroup /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1096771
Title:
error 'No cgroup mounted on the system' but cgroup mounted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
robertc@lifelessdesktop:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc/proc procnodev,noexec,nosuid 0 0 /dev/mapper/isw_bichcdfhcg_ARRAY0p6 / ext4errors=remount-ro 0 1 /dev/mapper/isw_bichcdfhcg_ARRAY0p5 noneswapsw 0 0 /dev/mapper/isw_bichcdfhcg_ARRAY0p5 noneswapsw 0 0 #/mnt/16GB.swap none swap sw 0 0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
sudo cat /proc/1/mountinfo 15 20 0:14 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw 16 20 0:3 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw 17 20 0:5 / /dev rw,relatime - devtmpfs udev rw,size=8129608k,nr_inodes=2032402,mode=755 18 17 0:11 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts rw,gid=5,mode=620,ptmxmode=000 19 20 0:15 / /run rw,nosuid,relatime - tmpfs tmpfs rw,size=3257152k,mode=755 20 1 252:8 / / rw,relatime - ext4 /dev/disk/by-uuid/9dce3ded-5110-40ec-9401-0e46a11f281d rw,errors=remount-ro,stripe=32,data=ordered 21 15 0:16 / /sys/fs/fuse/connections rw,relatime - fusectl none rw 23 15 0:6 / /sys/kernel/debug rw,relatime - debugfs none rw 25 15 0:10 / /sys/kernel/security rw,relatime - securityfs none rw 26 19 0:19 / /run/lock rw,nosuid,nodev,noexec,relatime - tmpfs none rw,size=5120k 27 19 0:20 / /run/shm rw,nosuid,nodev,relatime - tmpfs none rw 28 19 0:21 / /run/user rw,nosuid,nodev,noexec,relatime - tmpfs none rw,size=102400k,mode=755 36 16 0:29 / /proc/sys/fs/binfmt_misc rw,nosuid,nodev,noexec,relatime - binfmt_misc binfmt_misc rw 22 28 0:17 / /run/user/robertc/gvfs rw,nosuid,nodev,relatime - fuse.gvfsd-fuse gvfsd-fuse rw,user_id=1000,group_id=1000 24 15 0:18 / /sys/fs/cgroup rw,relatime - tmpfs cgroup rw,mode=755 29 24 0:22 / /sys/fs/cgroup/cpuset rw,relatime - cgroup cgroup rw,cpuset,clone_children 30 24 0:23 / /sys/fs/cgroup/cpu rw,relatime - cgroup cgroup rw,cpu,clone_children 31 24 0:24 / /sys/fs/cgroup/cpuacct rw,relatime - cgroup cgroup rw,cpuacct,clone_children 32 24 0:25 / /sys/fs/cgroup/memory rw,relatime - cgroup cgroup rw,memory,clone_children 33 24 0:26 / /sys/fs/cgroup/devices rw,relatime - cgroup cgroup rw,devices,clone_children 34 24 0:27 / /sys/fs/cgroup/freezer rw,relatime - cgroup cgroup rw,freezer,clone_children 35 24 0:28 / /sys/fs/cgroup/blkio rw,relatime - cgroup cgroup rw,blkio,clone_children 38 24 0:30 / /sys/fs/cgroup/perf_event rw,relatime - cgroup cgroup rw,perf_event,clone_children -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
sudo cat /proc/1/mountsrobertc@lifelessdesktop:~$ sudo cat /proc/1/mounts [sudo] password for robertc: rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=8129608k,nr_inodes=2032402,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=3257152k,mode=755 0 0 /dev/disk/by-uuid/9dce3ded-5110-40ec-9401-0e46a11f281d / ext4 rw,relatime,errors=remount-ro,stripe=32,data=ordered 0 0 none /sys/fs/fuse/connections fusectl rw,relatime 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 none /sys/kernel/security securityfs rw,relatime 0 0 none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0 none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 gvfsd-fuse /run/user/robertc/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 robertc@lifelessdesktop:~$ sudo cat /etc/mtab /dev/mapper/isw_bichcdfhcg_ARRAY0p6 / ext4 rw,errors=remount-ro 0 0 proc /proc proc rw,noexec,nosuid,nodev 0 0 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0 none /sys/fs/fuse/connections fusectl rw 0 0 none /sys/kernel/debug debugfs rw 0 0 none /sys/kernel/security securityfs rw 0 0 udev /dev devtmpfs rw,mode=0755 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0 tmpfs /run tmpfs rw,noexec,nosuid,size=10%,mode=0755 0 0 none /run/lock tmpfs rw,noexec,nosuid,nodev,size=5242880 0 0 none /run/shm tmpfs rw,nosuid,nodev 0 0 none /run/user tmpfs rw,noexec,nosuid,nodev,size=104857600,mode=0755 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0 cgroup /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0 gvfsd-fuse /run/user/robertc/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,user=robertc 0 0 robertc@lifelessdesktop:~$ sudo ls /sys/fs/cgroup -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
robertc@lifelessdesktop:~$ cat /proc/self/mountinfo 15 20 0:14 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw 16 20 0:3 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw 17 20 0:5 / /dev rw,relatime - devtmpfs udev rw,size=8129608k,nr_inodes=2032402,mode=755 18 17 0:11 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts rw,gid=5,mode=620,ptmxmode=000 19 20 0:15 / /run rw,nosuid,relatime - tmpfs tmpfs rw,size=3257152k,mode=755 20 1 252:8 / / rw,relatime - ext4 /dev/disk/by-uuid/9dce3ded-5110-40ec-9401-0e46a11f281d rw,errors=remount-ro,stripe=32,data=ordered 21 15 0:16 / /sys/fs/fuse/connections rw,relatime - fusectl none rw 23 15 0:6 / /sys/kernel/debug rw,relatime - debugfs none rw 25 15 0:10 / /sys/kernel/security rw,relatime - securityfs none rw 26 19 0:19 / /run/lock rw,nosuid,nodev,noexec,relatime - tmpfs none rw,size=5120k 27 19 0:20 / /run/shm rw,nosuid,nodev,relatime - tmpfs none rw 28 19 0:21 / /run/user rw,nosuid,nodev,noexec,relatime - tmpfs none rw,size=102400k,mode=755 36 16 0:29 / /proc/sys/fs/binfmt_misc rw,nosuid,nodev,noexec,relatime - binfmt_misc binfmt_misc rw 22 28 0:17 / /run/user/robertc/gvfs rw,nosuid,nodev,relatime - fuse.gvfsd-fuse gvfsd-fuse rw,user_id=1000,group_id=1000 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
robertc@lifelessdesktop:~$ sudo ls /sys/fs/cgroup robertc@lifelessdesktop:~$ echo $? 0 robertc@lifelessdesktop:~$ ls -d /sys/fs/cgroup /sys/fs/cgroup -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
status cgroup-lite cgroup-lite start/running -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
exec 21 1/run/cgroup.debug
exec 21 1/run/cgroup.debug
set -x
cgroup.debug during boot: (.1)
cat /run/cgroup.debug.1
+ grep /sys/fs/cgroup /proc/mounts
+ [ -n ]
+ grep -v ^# /etc/fstab
+ grep -q cgroup
+ grep -q cgroup /proc/mounts
+ [ ! -e /proc/cgroups ]
+ mount -t tmpfs -o uid=0,gid=0,mode=0755 cgroup /sys/fs/cgroup
+ sed -e 1d;s/\([^\t]\)\t.*$/\1/ /proc/cgroups
+ mkdir /sys/fs/cgroup/cpuset
+ mount -n -t cgroup -o cpuset cgroup /sys/fs/cgroup/cpuset
+ mkdir /sys/fs/cgroup/cpu
+ mount -n -t cgroup -o cpu cgroup /sys/fs/cgroup/cpu
+ mkdir /sys/fs/cgroup/cpuacct
+ mount -n -t cgroup -o cpuacct cgroup /sys/fs/cgroup/cpuacct
+ mkdir /sys/fs/cgroup/memory
+ mount -n -t cgroup -o memory cgroup /sys/fs/cgroup/memory
+ mkdir /sys/fs/cgroup/devices
+ mount -n -t cgroup -o devices cgroup /sys/fs/cgroup/devices
+ mkdir /sys/fs/cgroup/freezer
+ mount -n -t cgroup -o freezer cgroup /sys/fs/cgroup/freezer
+ mkdir /sys/fs/cgroup/blkio
+ mount -n -t cgroup -o blkio cgroup /sys/fs/cgroup/blkio
+ mkdir /sys/fs/cgroup/perf_event
+ mount -n -t cgroup -o perf_event cgroup /sys/fs/cgroup/perf_event
+ exit 0
And after boot:
cat /run/cgroup.debug
+ grep /sys/fs/cgroup /proc/mounts
+ [ -n ]
+ + grep -v ^# /etc/fstab -q cgroup
+ grep -q cgroup /proc/mounts
+ [ ! -e /proc/cgroups ]
+ mount -t tmpfs -o uid=0,gid=0,mode=0755 cgroup /sys/fs/cgroup
+ sed -e 1d;s/\([^\t]\)\t.*$/\1/ /proc/cgroups
+ mkdir /sys/fs/cgroup/cpuset
+ mount -n -t cgroup -o cpuset cgroup /sys/fs/cgroup/cpuset
+ mkdir /sys/fs/cgroup/cpu
+ mount -n -t cgroup -o cpu cgroup /sys/fs/cgroup/cpu
+ mkdir /sys/fs/cgroup/cpuacct
+ mount -n -t cgroup -o cpuacct cgroup /sys/fs/cgroup/cpuacct
+ mkdir /sys/fs/cgroup/memory
+ mount -n -t cgroup -o memory cgroup /sys/fs/cgroup/memory
+ mkdir /sys/fs/cgroup/devices
+ mount -n -t cgroup -o devices cgroup /sys/fs/cgroup/devices
+ mkdir /sys/fs/cgroup/freezer
+ mount -n -t cgroup -o freezer cgroup /sys/fs/cgroup/freezer
+ mkdir /sys/fs/cgroup/blkio
+ mount -n -t cgroup -o blkio cgroup /sys/fs/cgroup/blkio
+ mkdir /sys/fs/cgroup/perf_event
+ mount -n -t cgroup -o perf_event cgroup /sys/fs/cgroup/perf_event
+ exit 0
And the diff:
$ diff -u /run/cgroup.debug{.1,}
--- /run/cgroup.debug.1 2013-01-08 09:25:32.756067804 +1300
+++ /run/cgroup.debug 2013-01-08 09:30:18.507748375 +1300
@@ -1,7 +1,6 @@
+ grep /sys/fs/cgroup /proc/mounts
+ [ -n ]
-+ grep -v ^# /etc/fstab
-+ grep -q cgroup
++ + grep -v ^# /etc/fstab -q cgroup
+ grep -q cgroup /proc/mounts
+ [ ! -e /proc/cgroups ]
+ mount -t tmpfs -o uid=0,gid=0,mode=0755 cgroup /sys/fs/cgroup
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1096771
Title:
error 'No cgroup mounted on the system' but cgroup mounted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
ls /etc/init acpid.conf console-setup.conf friendly-recovery.conf modemmanager.conf mountkernfs.sh.conf procps.conf ssh.conf upstart-socket-bridge.conf alsa-restore.confcontainer-detect.confgdm.conf module-init-tools.conf mountnfs.sh.conf pulseaudio.conf tgt.conf upstart-udev-bridge.conf alsa-store.conf control-alt-delete.conf hostname.conf mountall.conf mysql.confqemu-kvm.conf tty1.confureadahead.conf anacron.conf cron.confhwclock.conf mountall-net.conf networking.conf rc.conf tty2.confureadahead-other.conf apport.conf cryptdisks-enable.conf hwclock-save.conf mountall-reboot.confnetwork-interface.confrcS.conf tty3.confwait-for-state.conf atd.conf cryptdisks-udev.conf hybrid-gfx.conf mountall.sh.confnetwork-interface-container.conf rc-sysinit.conf tty4.confwhoopsie.conf avahi-daemon.confcups.confirqbalance.conf mountall-shell.conf network-interface-security.conf resolvconf.conf tty5.confwinbind.conf binfmt-support.conf dbus.confiscsi-network-interface.conf mountdevsubfs.sh.conf network-manager.conf rfkill-restore.conf tty6.conf bluetooth.conf dmesg.conf libvirt-bin.conf mounted-debugfs.confpasswd.conf rfkill-store.conf udev.conf cgconfig.confecryptfs-utils-restore.conf libvirt-cgconfig-wait.conf mounted-dev.confplymouth.conf rsyslog.conf udev-fallback-graphics.conf cgred.conf ecryptfs-utils-save.conf libvirt-cgred-wait.conf mounted-proc.conf plymouth-log.conf screen-cleanup.conf udev-finish.conf cgroup-lite.conf failsafe.conflightdm.conf mounted-run.confplymouth-splash.conf setvtrgb.conf udevmonitor.conf console.conf failsafe-x.conf lxc.conf mounted-tmp.confplymouth-stop.confshutdown.conf udevtrigger.conf console-font.confflush-early-job-log.conf lxc-net.conf mounted-var.confplymouth-upstart-bridge.conf squid3.conf ufw.conf robertc@lifelessdesktop:~$ ls /etc/init.d/ acpid bluetooth cups hwclock lightdm nullmailer procps rfkill-store skeleton udev-fallback-graphics whoopsie acpi-supportbootlogd dbus hwclock-save lxc ondemand pulseaudio rsync speech-dispatcher udev-finish winbind alsa-restorebrltty dmesg ipmievd lxc-net openipmi qemu-kvm rsyslog squid3udevmonitor x11-common alsa-store cgroup-litedns-clean irqbalance modemmanager open-iscsi rabbitmq-server saned ssh udevtrigger zfs-fuse anacron console-font ebtables iscsi-network-interface module-init-toolspasswd rc saslauthd stop-bootlogd ufw apache2 console-setup failsafe-x kdump mysqlplymouth rc.local screen-cleanupstop-bootlogd-single umountfs apparmorcron friendly-recovery kerneloops networking plymouth-log rcS scsitools-pre.sh sudo umountiscsi.sh apport cryptdisks gdmkexec network-interfaceplymouth-splash README scsitools.sh sysstat umountnfs.sh atd cryptdisks-early grub-commonkexec-load network-interface-container plymouth-stopreboot sendsigs tgt umountroot avahi-daemoncryptdisks-enable halt killprocs network-interface-security plymouth-upstart-bridge resolvconf setvtrgb tor unattended-upgrades binfmt-support cryptdisks-udevhostname libvirt-bin network-manager
[Bug 1096771] [NEW] error 'No cgroup mounted on the system' but cgroup mounted
Public bug reported: $ sudo lxc-start -n lucid-test-lp -lDEBUG lxc-start: No cgroup mounted on the system lxc-start: failed to spawn 'lucid-test-lp' robertc@lifelessdesktop:~$ mount /dev/mapper/isw_bichcdfhcg_ARRAY0p6 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu) cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct) cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfsd-fuse on /run/user/robertc/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=robertc) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lxc 0.8.0~rc1-4ubuntu39 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Jan 7 19:14:58 2013 MarkForUpload: True ProcEnviron: LANGUAGE=en_NZ:en TERM=screen PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to quantal on 2012-10-30 (69 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1078530] Re: upstart job fails to start under lxc
Well, its hard to run the openstack test suite in a container *without* qemu-kvm, because python-libvirt depends on libvirt depends on qemu-kvm. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1078530] Re: upstart job fails to start under lxc
On Fri, Dec 21, 2012 at 9:20 AM, Serge Hallyn 1078...@bugs.launchpad.net wrote: @lifeless, the upstart job is only responsible for setting up the kvm kernel module and related kernel settings. With my new proposed change, the upstart job would detect it's in a container and consider itself done. Cool, thanks. -Rob -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1088971] Re: squid3 is not compiled with ssl support
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=180886 is the Debian bug of record. We (squid) need signoff from all contributors ever to add such an excemption, and I'm fairly sure thats impossible. Work is going on to use GNUTLS I think. ** Bug watch added: Debian Bug tracker #180886 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=180886 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1088971 Title: squid3 is not compiled with ssl support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1088971/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078530] [NEW] upstart job fails to start under lxc
Public bug reported: The KSM_ENABLED setting (on by default) for the qemu-kvm job fails under lxc but the kernel files still appear writable. Thats likely an lxc bug (either in defaults or device mapping), but there is no need for qemu- kvm's job to fail if those settings can't be written to IMNSHO. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078530] Re: upstart job fails to start under lxc
http://paste.ubuntu.com/1356944/ has a debdiff of the (trivial) fix, adjusted to not version conflict with my nbd patch. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] [NEW] qemu-nbd -r -c taints device for subsequent usage, even after -d
Public bug reported: Something about qemu-nbd -r -c /dev/nbd0 someimg leaves cruft behind - subsequent connections get marked readonly. This is on quantal, haven't checked precise or raring. To demonstrate: # use one image qemu-img create -f qcow2 /tmp/1.qcow2 100M sudo qemu-nbd -c /dev/nbd2 /tmp/1.qcow2 sudo mkfs -t ext4 /dev/nbd2 sudo qemu-nbd -d /dev/nbd2 # use a second one on the same nbd device, shows that reuse works: qemu-img create -f qcow2 /tmp/2.qcow2 100M sudo qemu-nbd -c /dev/nbd2 /tmp/2.qcow2 sudo mkfs -t ext4 /dev/nbd2 sudo qemu-nbd -d /dev/nbd2 # connect an image in read only mode sudo qemu-nbd -r -c /dev/nbd2 /tmp/2.qcow2 sudo dumpe2fs /dev/nbd2 | head -n 3 sudo qemu-nbd -d /dev/nbd2 # now try to reuse in read-write mode again: qemu-img create -f qcow2 /tmp/3.qcow2 100M sudo qemu-nbd -c /dev/nbd2 /tmp/3.qcow2 sudo mkfs -t ext4 /dev/nbd2 # here it goes boom: mke2fs 1.42.5 (29-Jul-2012) /dev/nbd2: Operation not permitted while setting up superblock # still need to cleanup sudo qemu-nbd -d /dev/nbd2 ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
Quick code read - I think that this block:
if (flags NBD_FLAG_READ_ONLY) {
int read_only = 1;
TRACE(Setting readonly attribute);
if (ioctl(fd, BLKROSET, (unsigned long) read_only) 0) {
int serrno = errno;
LOG(Failed setting read-only attribute);
return -serrno;
}
}
in nbd.c should be
{
int read_only = 0;
if (flags NBD_FLAG_READ_ONLY)
read_only = 1;
TRACE(Setting readonly attribute);
if (ioctl(fd, BLKROSET, (unsigned long) read_only) 0) {
int serrno = errno;
LOG(Failed setting read-only attribute);
return -serrno;
}
}
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1077838
Title:
qemu-nbd -r -c taints device for subsequent usage, even after -d
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
http://paste.ubuntu.com/1352684/ is a debdiff, uploading the source format 3 patch as well ** Attachment added: Force the readonly bit to the appropriate state on startup. https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431096/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3.debian.tar.gz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
** Attachment added: qemu-kvm_1.2.0+noroms-0ubuntu3.dsc https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431097/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3.dsc -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
** Attachment added: qemu-kvm_1.2.0+noroms-0ubuntu3_source.changes https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431098/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3_source.changes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
Fixed patch - I had my sense inverted... http://paste.ubuntu.com/1352711/ ** Attachment added: Corrected patch https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431143/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3.debian.tar.gz ** Patch removed: Force the readonly bit to the appropriate state on startup. https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431096/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3.debian.tar.gz ** Attachment removed: qemu-kvm_1.2.0+noroms-0ubuntu3.dsc https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431097/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3.dsc ** Attachment removed: qemu-kvm_1.2.0+noroms-0ubuntu3_source.changes https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431098/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3_source.changes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1060550] [NEW] lxc-ls with ephemeral containers reports too many containers
Public bug reported: use lxc-start-ephemeral to start four ephemeral containers then lxc-ls reports twice as many as it should: $ ls /var/lib/lxc/ lptests lptests-temp-1FaKWwb lptests-temp-c8jcW0W lptests-temp-qoZ6ncr lptests-temp-wbvIQLE jenkins@ip-10-218-67-147:~$ watch lxc-ls $ lxc-ls Wed Oct 3 lptests lptests-temp-1FaKWwb lptests-temp-c8jcW0W lptests-temp-qoZ6ncr lptests-temp-wbvIQLE lptests-temp-1FaKWwb lptests-temp-c8jcW0W lptests-temp-qoZ6ncr lptests-temp-wbvIQLE ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1060550 Title: lxc-ls with ephemeral containers reports too many containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1060550/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1059943] [NEW] lxc-start-ephemeral masks process exit code
*** This bug is a duplicate of bug 1050351 *** https://bugs.launchpad.net/bugs/1050351 Public bug reported: lxc-start-ephemeral command e.g. lxc-start-ephemeral run-my-tests does 'exit 0' after running the command - see handle_container. This masks the exit code the command provides, and makes rnuning commands via fail in hard to programmatically diagnose ways. ssh, the underlying remote-execution tool used, *does* preserve exit code: robertc@lifeless-64:~$ ssh -n localhost -- 'exit 1' robertc@lifeless-64:~$ echo $? 1 robertc@lifeless-64:~$ ssh -n localhost -- 'exit 0' robertc@lifeless-64:~$ echo $? 0 So it should be very straight forward to capture the exit code and propogate it out of the script. IIRC our prototype versions did this implicitly, and its been lost since. This bugs affects the robustness of the Launchpad test suite under lxc. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1059943 Title: lxc-start-ephemeral masks process exit code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1059943/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 546536] Re: --help and --version should be available without specifying hypervisor and suite
** Changed in: vmbuilder Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/546536 Title: --help and --version should be available without specifying hypervisor and suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/546536/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 519062] Re: Unable to connect to Eucalyptus Service on port 8773
** Changed in: eucalyptus (Ubuntu) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/519062 Title: Unable to connect to Eucalyptus Service on port 8773 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/519062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1031043] [NEW] -t ubuntu -- -h still creates container
Public bug reported: $ sudo lxc-create -n sso -t ubuntu -- --help No config file specified, using the default config /usr/lib/lxc/templates/lxc-ubuntu -h|--help [-a|--arch] [-b|--bindhome user] [--trim] [-d|--debug] [-F | --flush-cache] [-r|--release release] [ -S | --auth-key keyfile] release: the ubuntu release (e.g. precise): defaults to host release on ubuntu, otherwise uses latest LTS trim: make a minimal (faster, but not upgrade-safe) container bindhome: bind user's home into the container The ubuntu user will not be created, and user will have sudo access. arch: the container architecture (e.g. amd64): defaults to host arch auth-key: SSH Public key file to inject into container 'ubuntu' template installed 'sso' created ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1031043 Title: -t ubuntu -- -h still creates container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1031043/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 958210] Re: squid ABRT due to storeLocateVaryRead()
This is http://bugs.squid-cache.org/show_bug.cgi?id=2752 ** Bug watch added: Squid Bugzilla #2752 http://bugs.squid-cache.org/show_bug.cgi?id=2752 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/958210 Title: squid ABRT due to storeLocateVaryRead() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/958210/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1027154] Re: Unable to look up a node based on mac address
On Mon, Jul 23, 2012 at 11:50 AM, Julian Edwards 1027...@bugs.launchpad.net wrote: To clarify, why would someone very likely would want to query by the mac address. What's the use case? If they are staring at a rack full of hardware, one of which has a fault light lit, the only data they have at hand is the MAC address of the ethernet card, which is (for servers) often printed on the card, for exactly this reason. -Rob -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1027154 Title: Unable to look up a node based on mac address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1027154/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1019913] Re: Lazy load of attribute fails for instance_type.rxtx_factor
To reproduce, use the ec2 provider in juju (from precise) to talk to the cluster, and fire up a number of instances in rapid succession - e.g. 8-10. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1019913 Title: Lazy load of attribute fails for instance_type.rxtx_factor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1019913/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978356] Re: squid3 gets killed at startup with dnsmasq and no networkmanager
the squid patch looks reasonable to me; please forward to the squid-dev list with a [PATCH] subject. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/978356 Title: squid3 gets killed at startup with dnsmasq and no networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/978356/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 936762] Re: lxc-ubuntu template sets user shell, without checking it's installed
** Changed in: launchpad Assignee: Martin Pool (mbp) = (unassigned) ** No longer affects: launchpad -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/936762 Title: lxc-ubuntu template sets user shell, without checking it's installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/936762/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 981955] Re: lxc-execute does not seem to work in precise
Hi, the wiki page I was following had no container, it was using an implicit one or something - that gave me the impression it could just act as an isolation layer around / , isolating only the things configured (e.g. dev access, or networking). That said, lxc-execute with an ephemeral mode looks like it would do exactly what LP needs for test running :) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/981955 Title: lxc-execute does not seem to work in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/981955/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 981955] Re: lxc-execute does not seem to work in precise
Thanks Serge! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/981955 Title: lxc-execute without config does not seem to work in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/981955/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 802950] Re: no gui visible in unity
I don't have time to commit to this bug. Also please ask before assigning - I am subscribed so can claim things myself :-) ** Changed in: txaws Assignee: Robert Collins (lifeless) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to txaws in Ubuntu. https://bugs.launchpad.net/bugs/802950 Title: no gui visible in unity To manage notifications about this bug go to: https://bugs.launchpad.net/txaws/+bug/802950/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 625798] Re: Don't use int constants with a long data type.
** Tags added: easy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tickcount in Ubuntu. https://bugs.launchpad.net/bugs/625798 Title: Don't use int constants with a long data type. To manage notifications about this bug go to: https://bugs.launchpad.net/tickcount/+bug/625798/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 914169] Re: lxc-start-ephemeral script does not support in-line programmatic commands to ephemeral containers
@gary @serge - that dhcp vs dhcp3 thing is probably a case where the script needs to handle both: the dhcp client version changed between lucid and oneiric. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/914169 Title: lxc-start-ephemeral script does not support in-line programmatic commands to ephemeral containers To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/914169/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 902865] Re: lucid udev upgrade failure on oneiric hosted lxc container
*** This bug is a duplicate of bug 902190 *** https://bugs.launchpad.net/bugs/902190 Ah, I missed that (because its fix released and I searched in the default context). I will dup this on that bug. Will there be an SRU ? ** This bug has been marked a duplicate of bug 902190 udev fails to update (oneric host, lucid container) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/902865 Title: lucid udev upgrade failure on oneiric hosted lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/902865/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 902865] Re: lucid udev upgrade failure on oneiric hosted lxc container
*** This bug is a duplicate of bug 902190 *** https://bugs.launchpad.net/bugs/902190 On Tue, Dec 13, 2011 at 5:20 AM, Serge Hallyn 902...@bugs.launchpad.net wrote: *** This bug is a duplicate of bug 902190 *** https://bugs.launchpad.net/bugs/902190 @Robert: an SRU to oneiric is under way. It's trivial enough that an SRU to lucid doesn't bother me, but until NETNS is re-enabled in lucid kernel not many people will want to verify it - will you verify it? SRU to oneiric is what we need for this for LP - we don't do lucid on lucid, just lucid on oneiric, and soon \o/ lucid on precise. That said, I'm happy to spin up a lucid kvm vm and have a play for you. -Rob -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/902865 Title: lucid udev upgrade failure on oneiric hosted lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/902865/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 902865] [NEW] lucid udev upgrade failure on oneiric hosted lxc container
Public bug reported: Setting up udev (151-12.3) ... mknod: `/lib/udev/devices/ppp': Operation not permitted dpkg: error processing udev (--configure): subprocess installed post-installation script returned error exit status 1 I realise that this is arguably a config issue, or a udev issue. However, folk experiencing this problem will come looking in lxc for a solution (and lxc really needs to be the place where we identify collate and fix this sort of thing... doesn't it?) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/902865 Title: lucid udev upgrade failure on oneiric hosted lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/902865/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 902865] Re: lucid udev upgrade failure on oneiric hosted lxc container
Would it be appropriate to open a lucid task on udev? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/902865 Title: lucid udev upgrade failure on oneiric hosted lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/902865/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 892892] [NEW] mountall upgrade fails to install within lucid lxc container
Public bug reported: Unpacking replacement mountall ... dpkg: error processing /var/cache/apt/archives/mountall_2.15.3_i386.deb (--unpack): unable to make backup link of `./lib/init/fstab' before installing new version: Invalid cross-device link ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/892892 Title: mountall upgrade fails to install within lucid lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/892892/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 870448] Re: check_http fails to decode chunked encoding before performing string checks
(Note that chunked is a MUST requirement for http 1.1 clients) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/870448 Title: check_http fails to decode chunked encoding before performing string checks To manage notifications about this bug go to: https://bugs.launchpad.net/nagios-plugins/+bug/870448/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 801002] Re: Provide a default network and configurationss
forwarding is definitely not equivalent. Consider offline (train/plane/park) usage and wifi usage (two separate cases). In the former there is no default route to forward too. In the second case you have to do iptables SNAT to avoid firmware limits on forwarded MAC addresses. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/801002 Title: Provide a default network and configurations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/801002/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 807351] Re: it would be cool to be able to clone an lxc container onto aufs for test runs - ephemeral containers
updated script that handles slower startup and doesn't leak LXC_DIRs ** Attachment added: lxc-start-aufs https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/807351/+attachment/2251192/+files/lxc-start-aufs ** Attachment removed: a script to bring up and remove aufs layered containers https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/807351/+attachment/2196930/+files/lxc-start-aufs -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/807351 Title: it would be cool to be able to clone an lxc container onto aufs for test runs - ephemeral containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/807351/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 820715] [NEW] sudo poweroff -n within a container just hangs
Public bug reported: Thats about it really it seems to just sit there doing nada. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/820715 Title: sudo poweroff -n within a container just hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/820715/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 820720] [NEW] lxc-ps -n NAME does not work (but --name NAME does)
Public bug reported: This is inconsistent with the rest of lxc which accepts -n NAME ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/820720 Title: lxc-ps -n NAME does not work (but --name NAME does) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/820720/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
So now I made a clean container; copied it to (sudo cp -a ) to a temp dir, ran the original, and now have a diff of the changes. I've not yet tested to see if reverting them fixes it.?field.comment=So now I made a clean container; copied it to (sudo cp -a ) to a temp dir, ran the original, and now have a diff of the changes. I've not yet tested to see if reverting them fixes it. the mtab being nonempty in the nonrunning container is a little suspect as are the .udev files *on disk* (mainly symlinks it appears) ** Attachment added: diff of broken, working containers https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+attachment/2248777/+files/brokendiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
ps fax for the broken container starting up; 4134 pts/0S+ 0:00 | \_ sudo lxc-start -n lucid-test-lp 4135 pts/0S+ 0:00 | \_ lxc-start -n lucid-test-lp 4150 ?Ss 0:00 | \_ /sbin/init 4192 ?S 0:00 | \_ upstart-udev-bridge --daemon 4197 ?Ss0:00 | \_ udevd --daemon 4273 ?S 0:00 | | \_ udevd --daemon 4274 ?S 0:00 | | \_ udevd --daemon 4200 ?Ss 0:00 | \_ /usr/sbin/sshd -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Pre breakage: 4534 pts/0S+ 0:00 | \_ sudo lxc-start -n lucid-test-lp 4535 pts/0S+ 0:00 | \_ lxc-start -n lucid-test-lp 4546 ?Ss 0:00 | \_ /sbin/init 4593 ?S 0:00 | \_ upstart-udev-bridge --daemon 4597 ?Ss0:00 | \_ udevd --daemon 4728 ?S 0:00 | | \_ udevd --daemon 4729 ?S 0:00 | | \_ udevd --daemon 4936 pts/4Ss+0:00 | \_ /sbin/getty -8 38400 tty4 4937 pts/2Ss+0:00 | \_ /sbin/getty -8 38400 tty2 4939 pts/3Ss+0:00 | \_ /sbin/getty -8 38400 tty3 4945 ?S 0:00 | \_ /bin/sh /etc/init.d/ondemand background 4957 ?S 0:00 | | \_ sleep 60 4952 pts/1Ss+0:00 | \_ /sbin/getty -8 38400 tty1 4953 pts/5Ss+0:00 | \_ /sbin/getty -8 38400 /dev/console 4982 ?Ss 0:00 | \_ dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0 4997 ?Ss 0:00 | \_ /usr/sbin/sshd -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
4936 pts/4 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty4 4937 pts/2 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty2 4939 pts/3 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty3 4945 ? S 0:00 | \_ /bin/sh /etc/init.d/ondemand background 4957 ? S 0:00 | | \_ sleep 60 4952 pts/1 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty1 4953 pts/5 Ss+ 0:00 | \_ /sbin/getty -8 38400 /dev/console 4982 ? Ss 0:00 | \_ dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0 look to be the unique processes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
(Meta: does ondemand make any sense for containers anyhow?) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
indeed, brilliant - thanks. I guess this needs a new lxcguest package? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
This workaround is a little coarse - it breaks utmp depending things (like postgresql :P) so rm -rf /var/run touch /var/run/utmp chmod root:utmp /var/run/utmp That seems to be more robust. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
** Attachment added: utmp safe version https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+attachment/2250880/+files/lxcmount.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] [NEW] container start failure after calling poweroff -n
Public bug reported: The following recipe appears to reliably nuke a lxc i386 lucid container running on a oneiric amd64 host: lxc-start -n name (login) sudo poweroff -n - hangs in another terminal sudo lxc-stop -n name then sudo lxc-start -n name shows sudo lxc-start -n lucid-test-lp init: plymouth-splash main process (170) terminated with status 2 init: plymouth main process (7) killed by ABRT signal init: ssh main process (37) terminated with status 255 the output from poweroff is this: Broadcast message from robertc@lucid-test-lp (/dev/console) at 4:23 ... The system is going down for power off NOW! robertc@lucid-test-lp:~$ init: tty4 main process (225) killed by TERM signal init: tty2 main process (226) killed by TERM signal init: tty3 main process (228) killed by TERM signal init: tty1 main process (241) killed by TERM signal init: console main process (2534) killed by TERM signal Checking for running unattended-upgrades: * Asking all remaining processes to terminate... ...done. * All processes ended within 1 seconds ...done. * Deconfiguring network interfaces... ...done. * Deactivating swap... ...fail! * Unmounting weak filesystems... ...done. mount: / is busy * Will now halt ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: container start failure after calling poweroff -n To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Further investigation shows that just: logging into the new container installing some packages (see https://dev.launchpad.net/Running/LXC) and calling lxc-stop from another terminal will cause this. Am progressing with shorter and shorter tests ** Summary changed: - container start failure after calling poweroff -n + lucid container start failure after calling lxc-stop (fails across reboots) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
start, login, log out, lxc-stop from another terminal - the broken situation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
And confirmed its still nuked after a reboot. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819040] [NEW] cannot find archive-keyring making onieric guest
Public bug reported: I'm on oneiric and ran sudo lxc-create -n ensemble-0 -t ubuntu -f /etc/lxc/local.conf -- -r oneiric the config file is lxc.network.type=veth lxc.network.link=virbr0 lxc.network.flags=up Setting up apt (0.8.15.4ubuntu2) ... ERROR: Can't find the archive-keyring Is the ubuntu-keyring package installed? dpkg: error processing apt (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: apt ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819040 Title: cannot find archive-keyring making onieric guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819040/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819040] Re: cannot find archive-keyring making onieric guest
Seems to be coming from apt-key update being called in apts postinst; which is perhaps a bit crackful given theres no guarantee of being online. ** Package changed: lxc (Ubuntu) = apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819040 Title: cannot find archive-keyring making onieric guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/819040/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 712108] Re: shared ssl session cache support not possible out of the box
Scott has packaged distcache and its in NEW now. ** Changed in: apache2 (Ubuntu) Assignee: (unassigned) = Scott Moser (smoser) ** Changed in: apache2 (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. https://bugs.launchpad.net/bugs/712108 Title: shared ssl session cache support not possible out of the box -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 712108] Re: shared ssl session cache support not possible out of the box
Bah I fail at IRC nicks; chuck short has packaged it. ** Changed in: apache2 (Ubuntu) Assignee: Scott Moser (smoser) = Chuck Short (zulcss) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. https://bugs.launchpad.net/bugs/712108 Title: shared ssl session cache support not possible out of the box -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 712108] [NEW] shared ssl session cache support not possible out of the box
Public bug reported: Binary package hint: apache2 Out of the box apache supports distcache ssl session caching, but distcache isn't packaged in Ubuntu. Or 2.3 supports memcache but 2.3 isn't released yet (and we'd like something for Lucid). This would allow session sharing between Launchpad SSL front end servers - and similarly for anyone using Ubuntu. ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. https://bugs.launchpad.net/bugs/712108 Title: shared ssl session cache support not possible out of the box -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 573853] Re: Cannot control squid Unknown instance
Clint, in 3.2 we use a process farm: executed-squid (daemonises to create: supervisor (listens) worker worker worker -N will simply mean that the executed process is the supervisor rather than a daemoniser. Details may vary but I know of no reason that that wouldn't be doable, easily, in the 3.2 main.cc. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. https://bugs.launchpad.net/bugs/573853 Title: Cannot control squid Unknown instance -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 625798] Re: Don't use int constants with a long data type.
** Changed in: tickcount Status: New = Triaged ** Changed in: tickcount Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tickcount in ubuntu. https://bugs.launchpad.net/bugs/625798 Title: Don't use int constants with a long data type. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 640511] Re: squid in lucid adds bogus port number to Host: line if one isn't provided (in original or via vport=)
Confirming, because it was confused :). We'll want to put this patch in the 2.7 packages; it is surprising sysadmins. ** Changed in: squid Status: Invalid = In Progress ** Changed in: squid (Ubuntu) Status: Invalid = Confirmed -- squid in lucid adds bogus port number to Host: line if one isn't provided (in original or via vport=) https://bugs.launchpad.net/bugs/640511 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 640511] Re: squid in lucid adds bogus port number to Host: line if one isn't provided (in original or via vport=)
@Amos defaulting the port is one thing; setting it rather arbitrarily in the forwarded header is another thing altogether. @Henrik - thanks for finding that, I'll have a poke shortly at it. -- squid in lucid adds bogus port number to Host: line if one isn't provided (in original or via vport=) https://bugs.launchpad.net/bugs/640511 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 615708] Re: help for domname contains Launchpad translations metadata?
just libvirt based on jtv's comments. ** Changed in: launchpad Status: New = Invalid -- help for domname contains Launchpad translations metadata? https://bugs.launchpad.net/bugs/615708 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 594403] [NEW] cannot be made to cache responses with no LMT/Date/Expires
Public bug reported: Binary package hint: squid Squid has a hardcoded exclusion of caching for all objects with none of expires/LMT/Date, but this is unneeded. ** Affects: squid Importance: Unknown Status: Unknown ** Affects: squid (Ubuntu) Importance: Wishlist Status: Triaged ** Changed in: squid (Ubuntu) Status: New = Triaged ** Changed in: squid (Ubuntu) Importance: Undecided = Wishlist ** Bug watch added: bugs.squid-cache.org/ #2950 http://bugs.squid-cache.org/show_bug.cgi?id=2950 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=2950 Importance: Unknown Status: Unknown -- cannot be made to cache responses with no LMT/Date/Expires https://bugs.launchpad.net/bugs/594403 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 546536] [NEW] no help
Public bug reported: ~$ ubuntu-vm-builder --help Usage: ubuntu-vm-builder hypervisor suite [options] ubuntu-vm-builder: error: You need to specify at least the hypervisor type and the series Even if the help is specific to a hypervisor and suite, this message is useless: it needs to document the valid options for hypervisor and suite, or users will run into a brick wall. ProblemType: Bug Architecture: amd64 Date: Thu Mar 25 11:26:28 2010 DistroRelease: Ubuntu 10.04 Package: ubuntu-vm-builder 0.12.2-0ubuntu3 PackageArchitecture: all ProcEnviron: LANGUAGE=tlh_GB:tlh PATH=(custom, user) LANG=la_AU.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 SourcePackage: vm-builder Uname: Linux 2.6.32-17-generic x86_64 ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- no help https://bugs.launchpad.net/bugs/546536 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 546536] Re: no help
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/41891495/Dependencies.txt -- no help https://bugs.launchpad.net/bugs/546536 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 520336] Re: something strange about describeImages
further to that, perhaps this bug is just a dup of bug 356389? -- something strange about describeImages https://bugs.launchpad.net/bugs/520336 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 520336] Re: something strange about describeImages
If that is fixed, this should be. Sadly my UEC hudson plugin, where I found this, needs a code tweak - that code path was blocked by this bug, so its a little stale after upstream did some refactoring. I've filed a bug upstream and when that is fixed will review this bug. I'd be fine with you closing it if you believe its fixed though. -- something strange about describeImages https://bugs.launchpad.net/bugs/520336 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 519648] Re: After all-in-one setup node-cert.pem and node-pk.pem not found
I've just done a fresh install on lucid, on one system, and these files were in place. -- After all-in-one setup node-cert.pem and node-pk.pem not found https://bugs.launchpad.net/bugs/519648 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
