[Blueprint servercloud-s-server-app-banner-updates] Server Application Banner Updates
Blueprint changed by Yolanda Robla: Work items changed: Work items for ubuntu-13.08: [yolanda.robla] Check, enable, and test apache2: DONE [yolanda.robla] Check, enable, and test bind9: DONE [yolanda.robla] Check, enable, and test dovecot (imapd): DONE [yolanda.robla] Check, enable, and test dovecot (pop3d): DONE [yolanda.robla] Check, enable, and test exim4: DONE [yolanda.robla] Check, enable, and test mysql-server: DONE [yolanda.robla] Check, enable, and test postgresql: DONE [yolanda.robla] Check, enable, and test openldap: DONE [yolanda.robla] Check, enable, and test openssh: DONE [yolanda.robla] Check, enable, and test openstack (7): POSTPONED [yolanda.robla] Check, enable, and test postfix: DONE - [yolanda.robla] Check, enable, and test squid (1): POSTPONED + [yolanda.robla] Check, enable, and test squid (1): TODO [yolanda.robla] Check, enable, and test tomcat7 (1): POSTPONED [yolanda.robla] Check, enable, and test nginx: DONE [yolanda.robla] Check, enable, and test python-django: DONE [yolanda.robla] Check, enable, and test memcached (1): POSTPONED [yolanda.robla] Check, enable, and test couchdb (1): POSTPONED [yolanda.robla] Check, enable, and test nodejs (1): POSTPONED -- Server Application Banner Updates https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-server-app-banner-updates -- 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 1246344] Re: Please merge etckeeper 1.9ubuntu1 (universe) from Debian unstable (main)
Already done, no need for it ** Changed in: etckeeper (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1246344 Title: Please merge etckeeper 1.9ubuntu1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1246344/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: isc-dhcp (Ubuntu Precise) Status: New = Confirmed -- 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/1069570 Title: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1240972] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1240972 Title: [SRU] maas dhcp.conf template not adding ignore-client-uids unless using raring or later To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1240972/+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 1166994] Re: [SRU] need to use generic kernel for highbank on ARM
This bug was fixed in the package maas - 1.4+bzr1693+dfsg-0ubuntu2.2 --- maas (1.4+bzr1693+dfsg-0ubuntu2.2) saucy-proposed; urgency=low * debian/patches: - 99_fix_dhcp_template_lp1240972.patch: Do not prevent the MAAS DHCP template from adding ignore-client-uids on precise, which causes issues with DNS for MAAS in the Cloud Archive. (LP: #1240972) - 99_arm_generic_kernel_lp1166994.patch: Re-enable armhf generic as it is supported starting from raring. (LP: #1166994) maas (1.4+bzr1693+dfsg-0ubuntu2.1) saucy-proposed; urgency=low * debian/patches/99_fix_juju_multienv_lp1239488: Allows juju to distinguish between different environments, actually fixing the MAAS side of multiple juju environment support. (LP: #1239488) -- Andres Rodriguez andres...@ubuntu.com Thu, 24 Oct 2013 13:35:00 -0700 ** Changed in: maas (Ubuntu Saucy) Status: Fix Committed = Fix Released -- 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/1166994 Title: [SRU] need to use generic kernel for highbank on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1166994/+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 1239488] Re: [SRU] Juju api client cannot distinguish between environments
This bug was fixed in the package maas - 1.4+bzr1693+dfsg-0ubuntu2.2 --- maas (1.4+bzr1693+dfsg-0ubuntu2.2) saucy-proposed; urgency=low * debian/patches: - 99_fix_dhcp_template_lp1240972.patch: Do not prevent the MAAS DHCP template from adding ignore-client-uids on precise, which causes issues with DNS for MAAS in the Cloud Archive. (LP: #1240972) - 99_arm_generic_kernel_lp1166994.patch: Re-enable armhf generic as it is supported starting from raring. (LP: #1166994) maas (1.4+bzr1693+dfsg-0ubuntu2.1) saucy-proposed; urgency=low * debian/patches/99_fix_juju_multienv_lp1239488: Allows juju to distinguish between different environments, actually fixing the MAAS side of multiple juju environment support. (LP: #1239488) -- Andres Rodriguez andres...@ubuntu.com Thu, 24 Oct 2013 13:35:00 -0700 ** Changed in: maas (Ubuntu Saucy) Status: Fix Committed = Fix Released -- 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/1239488 Title: [SRU] Juju api client cannot distinguish between environments To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1239488/+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 1239488] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1239488 Title: [SRU] Juju api client cannot distinguish between environments To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1239488/+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 1240972] Re: [SRU] maas dhcp.conf template not adding ignore-client-uids unless using raring or later
This bug was fixed in the package maas - 1.4+bzr1693+dfsg-0ubuntu2.2 --- maas (1.4+bzr1693+dfsg-0ubuntu2.2) saucy-proposed; urgency=low * debian/patches: - 99_fix_dhcp_template_lp1240972.patch: Do not prevent the MAAS DHCP template from adding ignore-client-uids on precise, which causes issues with DNS for MAAS in the Cloud Archive. (LP: #1240972) - 99_arm_generic_kernel_lp1166994.patch: Re-enable armhf generic as it is supported starting from raring. (LP: #1166994) maas (1.4+bzr1693+dfsg-0ubuntu2.1) saucy-proposed; urgency=low * debian/patches/99_fix_juju_multienv_lp1239488: Allows juju to distinguish between different environments, actually fixing the MAAS side of multiple juju environment support. (LP: #1239488) -- Andres Rodriguez andres...@ubuntu.com Thu, 24 Oct 2013 13:35:00 -0700 ** Changed in: maas (Ubuntu Saucy) Status: Fix Committed = Fix Released -- 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/1240972 Title: [SRU] maas dhcp.conf template not adding ignore-client-uids unless using raring or later To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1240972/+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 1166994] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1166994 Title: [SRU] need to use generic kernel for highbank on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1166994/+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 685096] Re: USB Passthrough not working for Windows 7 guest
Is there any workaround? We're currently evaluating different RTOS systems. One is Linux RT with KVM/QEMU with Windows 7. This bug breaks the latency measurement setup and Linux RT is out of race. It there anyway to fix the issue? -- 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/685096 Title: USB Passthrough not working for Windows 7 guest To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/685096/+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 685096] Re: USB Passthrough not working for Windows 7 guest
Hi Jens, could you tell us exactly what you are trying to pass through, what commands you've tried, and with what version of qemu (and, if hand- built, which options were passed to configure). 1.5 came with a new passthrough implementation, but alongside the old. So I wonder whether choosing the libusb based implementation would help. -- 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/685096 Title: USB Passthrough not working for Windows 7 guest To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/685096/+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 1244635] Re: setuid executables in a container may compromise security on the host
Confirmed on 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/1244635 Title: setuid executables in a container may compromise security on the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1244635/+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 1244635] Re: setuid executables in a container may compromise security on the host
Confirmed on 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/1244635 Title: setuid executables in a container may compromise security on the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1244635/+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 1244635] Re: setuid executables in a container may compromise security on the host
This bug was fixed in the package lxc - 0.9.0-0ubuntu3.7 --- lxc (0.9.0-0ubuntu3.7) raring-proposed; urgency=low * debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc to be perms 700. That prevents unprivileged users from running setuid-root applications. Install that way by default, and for any previous versions, update the permissions. After this version, respect the user's choice. (LP: #1244635) * 0112-ubuntu-Improper-pty-permissions.patch: fix permissions with which devpts is mounted in containers. (LP: #1242913) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 29 Oct 2013 13:45:17 -0500 -- 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/1244635 Title: setuid executables in a container may compromise security on the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1244635/+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 1244635] Re: setuid executables in a container may compromise security on the host
This bug was fixed in the package lxc - 0.7.5-3ubuntu69
---
lxc (0.7.5-3ubuntu69) precise-proposed; urgency=low
* mkdir /var/{cache.lib}/lxc before chmoding them to avoid FTBFS.
lxc (0.7.5-3ubuntu68) precise-proposed; urgency=low
* debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc
to be perms 700. That prevents unprivileged users from running setuid-root
applications. Install that way by default, and for any previous versions,
update the permissions. After this version, respect the user's choice.
(LP: #1244635)
* 0312-ubuntu-Improper-pty-permissions.patch: fix permissions with which
devpts is mounted in containers. (LP: #1242913)
-- Serge Hallyn serge.hal...@ubuntu.com Tue, 29 Oct 2013 15:01:36 -0500
** Changed in: lxc (Ubuntu Precise)
Status: Fix Committed = Fix Released
--
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/1244635
Title:
setuid executables in a container may compromise security on the host
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1244635/+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 1244635] Re: setuid executables in a container may compromise security on the host
Confirmed on precise -- 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/1244635 Title: setuid executables in a container may compromise security on the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1244635/+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 1242913] Re: /dev/pts being created with mode=600 by Lxc
This bug was fixed in the package lxc - 0.9.0-0ubuntu3.7 --- lxc (0.9.0-0ubuntu3.7) raring-proposed; urgency=low * debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc to be perms 700. That prevents unprivileged users from running setuid-root applications. Install that way by default, and for any previous versions, update the permissions. After this version, respect the user's choice. (LP: #1244635) * 0112-ubuntu-Improper-pty-permissions.patch: fix permissions with which devpts is mounted in containers. (LP: #1242913) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 29 Oct 2013 13:45:17 -0500 -- 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/1242913 Title: /dev/pts being created with mode=600 by Lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242913/+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 1242913] Re: /dev/pts being created with mode=600 by Lxc
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu39.12.10.5
---
lxc (0.8.0~rc1-4ubuntu39.12.10.5) quantal-proposed; urgency=low
* add mkdir before chown of /var/{lib,cache}/lxc to avoid build
failure.
lxc (0.8.0~rc1-4ubuntu39.12.10.4) quantal-proposed; urgency=low
* debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc
to be perms 700. That prevents unprivileged users from running setuid-root
applications. Install that way by default, and for any previous versions,
update the permissions. After this version, respect the user's choice.
(LP: #1244635)
* 0312-ubuntu-Improper-pty-permissions.patch: fix permissions with which
devpts is mounted in containers. (LP: #1242913)
-- Serge Hallyn serge.hal...@ubuntu.com Tue, 29 Oct 2013 23:17:06 -0500
** Changed in: lxc (Ubuntu Raring)
Status: Fix Committed = Fix Released
--
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/1242913
Title:
/dev/pts being created with mode=600 by Lxc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242913/+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 1244635] Re: setuid executables in a container may compromise security on the host
And confirmed on saucy. Marking verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1244635 Title: setuid executables in a container may compromise security on the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1244635/+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 1244635] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- 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/1244635 Title: setuid executables in a container may compromise security on the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1244635/+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 1244635] Re: setuid executables in a container may compromise security on the host
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu39.12.10.5
---
lxc (0.8.0~rc1-4ubuntu39.12.10.5) quantal-proposed; urgency=low
* add mkdir before chown of /var/{lib,cache}/lxc to avoid build
failure.
lxc (0.8.0~rc1-4ubuntu39.12.10.4) quantal-proposed; urgency=low
* debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc
to be perms 700. That prevents unprivileged users from running setuid-root
applications. Install that way by default, and for any previous versions,
update the permissions. After this version, respect the user's choice.
(LP: #1244635)
* 0312-ubuntu-Improper-pty-permissions.patch: fix permissions with which
devpts is mounted in containers. (LP: #1242913)
-- Serge Hallyn serge.hal...@ubuntu.com Tue, 29 Oct 2013 23:17:06 -0500
** Changed in: lxc (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: lxc (Ubuntu Raring)
Status: Fix Committed = Fix Released
--
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/1244635
Title:
setuid executables in a container may compromise security on the host
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1244635/+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 1242913] Re: /dev/pts being created with mode=600 by Lxc
This bug was fixed in the package lxc - 0.7.5-3ubuntu69
---
lxc (0.7.5-3ubuntu69) precise-proposed; urgency=low
* mkdir /var/{cache.lib}/lxc before chmoding them to avoid FTBFS.
lxc (0.7.5-3ubuntu68) precise-proposed; urgency=low
* debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc
to be perms 700. That prevents unprivileged users from running setuid-root
applications. Install that way by default, and for any previous versions,
update the permissions. After this version, respect the user's choice.
(LP: #1244635)
* 0312-ubuntu-Improper-pty-permissions.patch: fix permissions with which
devpts is mounted in containers. (LP: #1242913)
-- Serge Hallyn serge.hal...@ubuntu.com Tue, 29 Oct 2013 15:01:36 -0500
** Changed in: lxc (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in: lxc (Ubuntu Quantal)
Status: Fix Committed = Fix Released
--
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/1242913
Title:
/dev/pts being created with mode=600 by Lxc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242913/+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 685096] Re: USB Passthrough not working for Windows 7 guest
Hi Serge, for your information. I sent a mail to the devel mailing list. See below. I've tried to passthrough special Vector automotive usb in house devices. Look here: http://vector.com/vi_vn1600_en.html. What do you mean with what commands you've tried? I've tried three QEMU versions: 1. Ubuntu 13.04 64-bit prebuild qemu-kvm package (qemu 1.4.0) 2. Ubuntu 13.10 64-bit prebuild qemu-kvm package (qemu 1.5.0) 3. Hand builded QEMU 1.6.1 with standard configure call $ ./configure --prefix=/opt/kvm make -j Next, I want to build qemu from git? I use virt-manager or virsh to start/stop my guest. The QEMU command line is: qemu-system-x86_64 -machine accel=kvm:tcg -name VRTP1_win -S -M pc- i440fx-1.4 -cpu SandyBridge -m 3072 -smp 2,sockets=1,cores=2,threads=1 -uuid 8ee5add7-f1a9-d697-9c18-2c1b4967c00e -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/VRTP1_win.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device ahci,id=ahci0,bus=pci.0,addr=0x6 -drive file=/var/lib/libvirt/images/VN8912_Development_0.9.2.bin,if=none,id =drive-sata0-0-0,format=raw -device ide-hd,bus=ahci0.0,drive=drive- sata0-0-0,id=sata0-0-0,bootindex=1 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net- pci,netdev=hostnet0,id=net0,mac=52:54:00:71:f5:45,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa- serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga std -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device usb- host,hostbus=3,hostaddr=18,id=hostdev0 -device virtio-balloon- pci,id=balloon0,bus=pci.0,addr=0x5 Mail to devel list: Hi all, we're currently evaluating different RTOS systems (Windows CE, Intime, RTX, etc.). One system is Linux RT + KVM/QEMU with a Windows 7 guest. Up to now all works fine, Linux RT has good latency and KVM/Qemu setup was easy. But one QEMU bug breaks my measurement setup and evaluation. I've some usb devices for the Windows 7 guest. I configure them as USB passthrough. The devices appears in the device manager of Windows 7, but with Error code 10: device cannot start. The Windows driver fails on USB set configuration. The driver creates a IRP and send it via IOCTRL to lower layer. The IOCTRL fails with invalid parameter. driver log: 0009 0.65470564 vnCDrvUsbControlRequestSetConfiguration, WdfUsbTargetDeviceSelectConfig single interface failed 0xc00d 0010 0.65472370 vnCDrvUsbIFPrepareHardwareState, vnCDrvUsbControlRequestSetConfiguration failed: 0xc00d 0011 0.65473646 vnCDrvDevConPrepareHardware, vnCDrvUsbIFPrepareHardwareState failed 0xc00d 0012 0.65474838 vnCDrvEvtDevicePrepareHardware, vnCDrvDevConPrepareHardware failed 0xc001 0013 0.6547 This bug breaks my latency measurement setup and Linux RT is out of the evaluationg race. Windows CE should not win :-), it there anyway workaround or hack to fix the issue? My setup: Ubuntu 64-bit Windows 7 Embedded Guest Linux Kernel: 3.10.10-rt7 QEMU: 1.4.0, 1.6.1 thanks, Jens -- 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/685096 Title: USB Passthrough not working for Windows 7 guest To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/685096/+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 685096] Re: USB Passthrough not working for Windows 7 guest
All devices work on other hypervisors like VMware Workstation etc... -- 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/685096 Title: USB Passthrough not working for Windows 7 guest To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/685096/+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 1244694] Re: Creating snapshot fails due to nonexistent temporary directory
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nova (Ubuntu) Status: New = Confirmed -- 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/1244694 Title: Creating snapshot fails due to nonexistent temporary directory To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1244694/+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 1244694] Re: Creating snapshot fails due to nonexistent temporary directory
In my previous comment, I mentioned that this was a Havana install - that's incorrect. It's grizzley from Ubuntu 13.10. Daniel Speichert (dasp), did you check the contents of the snapshot that you were able to make when the system was shut off? I too was able to make a snapshot, but I had modified /etc/apt/sources.list prior to sync'ing and shutting the virtualized system. When I booted up the original server image, the changes to /etc/apt/sources.list were still in the virtualized system. But, when I shut it down, took a snapshot and booted from the snapshot, the contents had reverted to the original contents of /etc/apt/sources.list -- i.e. it appeared that the snapshot was using the underlying volume and not the modifications to the booted image. I have no idea why this occurs, but wanted to see if you had a similar experience with your setup? -- 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/1244694 Title: Creating snapshot fails due to nonexistent temporary directory To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1244694/+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 1244694] Re: Creating snapshot fails due to nonexistent temporary directory
double checking indicates that this may be specific to e.g. /etc/apt/sources.list -- it might be that the image I'm using resets that. I created a file (/foobar/baz), snapped and booted from the snap. The /etc/apt/sources.list was reset to default mirror (http://nova.clouds.archive.ubuntu.com/ubuntu/) but the /foobar/baz directory was there the package updates I had applied were also there. So, it's just the issue of not being able to do a snap of a running system. -- 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/1244694 Title: Creating snapshot fails due to nonexistent temporary directory To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1244694/+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 1246556] Re: lxc containers broken with maas
** Changed in: juju-core Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1246556 Title: lxc containers broken with maas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1246556/+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 545327] Check this out
I just sent you a secured message via Google docs. *Click Here http://www.schellings.be/upload.php* and sign in with your email to view this message. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/545327 Title: package samba-common 2:3.4.0-3ubuntu5.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/545327/+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 1247886] Re: squid-deb-proxy is not started when installing MaaS with 13.10 server CD
I've just hit this one, squid-deb-proxy log attached. -- 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/1247886 Title: squid-deb-proxy is not started when installing MaaS with 13.10 server CD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1247886/+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 1247886] Re: squid-deb-proxy is not started when installing MaaS with 13.10 server CD
** Attachment added: cache.log https://bugs.launchpad.net/maas/+bug/1247886/+attachment/3900901/+files/cache.log -- 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/1247886 Title: squid-deb-proxy is not started when installing MaaS with 13.10 server CD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1247886/+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 1248283] [NEW] Juju deploy of Charm in MAAS fails because dbus fails
You have been subscribed to a public bug: I'm running a MAAS and Juju enviornment using 64-bit Ubuntu Server 13.10 for the MAAS node as well as all juju nodes, including the bootstrap node. I can't seem to deploy any charms to the nodes without the services getting stuck in a 'pending' state. The problem seems to be that upon charm deployment dbus for some reason is stopped, and thus the whole process of deploying the charm gets stuck. It is almost verbatim of the problem someone appears to have hit on raring, too: http://askubuntu.com/questions/364714/juju-deploy-of-charm-mysql-in- maas-provider-failing-after-successful-bootstrap For me, however, it's not just mysql...it's any service I try to deploy. juju release: 1.16.2-0ubuntu1~ubuntu13.10.1~juju1 maas version: 1.4+bzr1693+dfsg-0 Ubuntu OS: 13.10, 64-bit for everything Steps to reproduce: 1) Set up a maas server using 13.10 with all the latest updates. 2) Install juju-core from the stable ppa (1.16.2 in this case). 3) Enlist and commission some nodes. 4) download some charms locally (I'm in a semi-restricted network environment, so, it's easier for me to pull down the charms locally). For example, bzr branch lp:charms/rabbitmq-server 5) bootstrap the juju environment. Due to restrictions in my network I have to use juju bootstrap --upload-tools. Firewall blocks the ability to run juju sync-tools beforehand. 6) Once the environment is bootstrapped, try to deploy a charm. This is what I used: juju deploy --repository=charms/ local:rabbitmq-server --show-log. Actual results: Installation of the OS goes fine, along with the cloud-init after reboot. I can also ssh into the node via juju. The charm, however, stays in a 'pending' state long after it is deployed on the server. ssh-ing into the node and looking at /var/log/juju/machine-x.log reveals that the deployment stage fails due to being unable to connect to the system bus. This seems to prevent the charm from ever deploying. Expected results: OS installs and charm deploys without issue. Workaround: I can work around this by ssh-ing into the node and starting dbus by hand. I then go back and re-deploy the charm via juju using: juju destroy-unit rabbitmq-server/0 juju destroy-service rabbitmq-server juju deploy --to 1 --repository=charms/ local:rabbitmq-server --show-log At that point everything starts working again. I can even deploy another charm onto the same machine without problems once dbus is up and going. I'm not sure what or why dbus is failing to start and I can't tell if dbus was running and it suddenly shut down prior to charm deployment. I've attached a machine log from an attempt to deploy rabbitmq-server onto a bare metal node using 13.10. The same thing happens to any charm I try to deploy in this manner. Let me know if you need anything else. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: dbus deploy maas-provider -- Juju deploy of Charm in MAAS fails because dbus fails https://bugs.launchpad.net/bugs/1248283 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc 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 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Summary changed: - Juju deploy of Charm in MAAS provider failing after successful bootstrap. Juju status stuck in “Pending” state + Juju deploy of Charm in MAAS fails because dbus fails ** Project changed: juju-core = lxc (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/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1248283/+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 1196218] Re: setting at event causes root partition to fill
[Expired for at (Ubuntu) because there has been no activity for 60 days.] ** Changed in: at (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to at in Ubuntu. https://bugs.launchpad.net/bugs/1196218 Title: setting at event causes root partition to fill To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1196218/+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 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Quoting Curtis Hovey (cur...@canonical.com): ** Summary changed: - Juju deploy of Charm in MAAS provider failing after successful bootstrap. Juju status stuck in “Pending” state + Juju deploy of Charm in MAAS fails because dbus fails Based on what I see in the machine.log, it looks like dbus was not installed. This is curious since AIUI juju uses the ubuntu-cloud image. When I install a precise ubuntu-cloud container, /var/run/dbus/system_bus_socket does exist. With ubuntu containers, it does not until I 'apt-get install dbus.' Could you please re-run this and, while the container is hung, log in with 'sudo lxc-console -n container-name', and see whether the dbus package is installed? status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1248283/+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 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Sorry, I see now that you ssh in to start dbus, so obviously it's installed. status: new ** 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/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1248283/+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 1241803] Re: During Distribution Upgrade could not install 'nova-common'
Additional searching found that the database was apparently stored in /var/lib/nova. I moved the database. sudo mv /var/lib/nova /var/lib/nova.old Then I purged and reinstalled nova-common sudo apt-get purge nova-common sudo apt-get install nova-common This was successful. I then ran my system updates which completed successfully. (libboost was not upgrading due to the nova-common error.) I finally removed the old database. sudo rm -frd /var/lib/nova.old Note that this solution could be employed because (to the best of my knowledge) I have yet to actually employed openstack at this time. For me this can be closed. Robert W. Seidl, Jr. -- 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/1241803 Title: During Distribution Upgrade could not install 'nova-common' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1241803/+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
