[Bug 1302772] Re: update of maas-cluster-controller on trusty dumps traceback and crashes
The latest build in ppa:maas-maintainers/dailybuilds should have the fix. Could you try again, but with that package? -- 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/1302772 Title: update of maas-cluster-controller on trusty dumps traceback and crashes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302772/+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 1295072] Re: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0
It looks like libfte-dev before 1.4 was merely unusable because the mentioned file - libfdt_env.h - is included by the main libfdt.h too, even in version 1.3, so if libfdt_env.h is missing, libfdt-dev is simply unusable. At least that's what it was on debian, see http://bugs.debian.org/706137 . So I think it is not qemu who should depend on =1.4 libfdt-dev, but qemu should depend on _working_ libfdt- dev. BTW, how this bug is related to CVE-2013-4377? ** Bug watch added: Debian Bug tracker #706137 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706137 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1295072 Title: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1295072/+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 1301036] Re: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration
** Changed in: heat Assignee: (unassigned) = Thomas Herve (therve) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1301036 Title: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1301036/+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 1302772] Re: update of maas-cluster-controller on trusty dumps traceback and crashes
On Monday 07 Apr 2014 16:03:39 you wrote: Also, to answer Julian in comment #2, Correct, I chose N when asked about overwriting pserv.yaml. I never allow automatic overwriting of config files, and I would well imagine that most people do likewise as that tends to break things when custom configs disappear automatically during upgrades... (been bitten by that more than once, so I just never do it anymore). I do hope you merge back changes from the upstream config? MAAS makes a lot of tweaks to them from time to time. -- 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/1302772 Title: update of maas-cluster-controller on trusty dumps traceback and crashes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302772/+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 1302772] Re: update of maas-cluster-controller on trusty dumps traceback and crashes
** Changed in: maas Status: In Progress = Fix Committed -- 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/1302772 Title: update of maas-cluster-controller on trusty dumps traceback and crashes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302772/+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 1302772] Re: update of maas-cluster-controller on trusty dumps traceback and crashes
** Changed in: maas Milestone: 14.10 = None -- 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/1302772 Title: update of maas-cluster-controller on trusty dumps traceback and crashes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302772/+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 1301036] Re: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration
Fix proposed to branch: master Review: https://review.openstack.org/85941 ** Changed in: heat Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1301036 Title: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1301036/+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 1304237] [NEW] package python3-networkx (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/share/doc/python-networkx/examples/basic/read_write.py presente anche nel pacch
Public bug reported: Installation of package python3-networkx failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python3-networkx (not installed) ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 AptOrdering: python3-networkx: Install python3-networkx: Configure Architecture: amd64 Date: Mon Apr 7 12:01:22 2014 DuplicateSignature: package:python3-networkx:(not installed):tentata sovrascrittura di /usr/share/doc/python-networkx/examples/basic/read_write.py presente anche nel pacchetto python-networkx 1.8.1-0ubuntu3 ErrorMessage: tentata sovrascrittura di /usr/share/doc/python-networkx/examples/basic/read_write.py presente anche nel pacchetto python-networkx 1.8.1-0ubuntu3 InstallationDate: Installed on 2013-12-28 (100 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131228) SourcePackage: python-networkx Title: package python3-networkx (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/share/doc/python-networkx/examples/basic/read_write.py presente anche nel pacchetto python-networkx 1.8.1-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-networkx (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-networkx in Ubuntu. https://bugs.launchpad.net/bugs/1304237 Title: package python3-networkx (not installed) failed to install/upgrade: tentata sovrascrittura di /usr/share/doc/python- networkx/examples/basic/read_write.py presente anche nel pacchetto python-networkx 1.8.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-networkx/+bug/1304237/+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 1271183] Re: ipv6 host key not added with non-default port
Thanks for the thorough investigation. Simply removing the IPv4 entry and connecting with v6 does the trick! And no need to drop interfaces, just using -4 works for me. It's still a bug though (different behavior depending on v4/v6), will it be pushed upstream? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1271183 Title: ipv6 host key not added with non-default port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1271183/+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 1271183] Re: ipv6 host key not added with non-default port
Actually, to correct my previous post, ssh-keygen -R hostname is enough to allow the v6 key to be added properly. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1271183 Title: ipv6 host key not added with non-default port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1271183/+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 1284718] Re: interface-attach to external network a) works and b) results in undeletable instances
Reviewed: https://review.openstack.org/85823 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 Submitter: Jenkins Branch:milestone-proposed commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 Author: Salvatore Orlando salv.orla...@gmail.com Date: Thu Apr 3 14:54:11 2014 -0700 Require admin context for interfaces on ext network Currently any user can attach an interface to a neutron external network, if the neutron plugin supports the port binding extension. In this case, nova will create neutron ports using the admin client, thus bypassing neutron authZ checks for creating ports on external networks. This patch adds a check in nova to verify the API request has an admin context when a request for an interface is made on a neutron external network. Change-Id: I5fb0bdcbf19eb82746ea3b192c1f65899bfb3c0b Closes-Bug: 1284718 (cherry picked from commit 7d1b4117fda7709307a35e56625cfa7709a6b795) ** Changed in: nova Status: Fix Committed = Fix Released -- 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/1284718 Title: interface-attach to external network a) works and b) results in undeletable instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1284718/+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 1304309] [NEW] Bind mounting for cloned containers is too hard; provide equivalent of lxc-start-ephemeral --bind option
Public bug reported: In order to efficiently exchange data with a test bed in a container, I make ample use of lxc-start-ephemeral's --bdir option to bind-mount a temp dir from the host into the container. However, we can't use ephemeral in autopkgtest production as that leads to failure of some tests due to bugs in overlayfs/aufs. The problem is that with lxc-clone and lxc-start there is no counterpart at all for the --bdir option. So to do the equivalent thing, one needs to detect the LXC path (lxc-config lxc.lxcpath), make assumptions about the file layout in the container dir (/rootfs, /config), manually mkdir -p the bind mount path, and add the bind mount to config. This feels like poking around in internals way too much and thus not very future- proof, and it's also a lot of effort: http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=commitdiff;h=5fbbe3f05f4 Could lxc-clone or lxc-start grow a --bdir option as well, to make this simpler and keep the knowledge of paths and file layouts within LXC itself? ** 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/1304309 Title: Bind mounting for cloned containers is too hard; provide equivalent of lxc-start-ephemeral --bind option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1304309/+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 1303926] Re: qemu-system-x86_64 crashed with SIGABRT
** Attachment removed: CoreDump.gz https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1303926/+attachment/4072413/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1303926 Title: qemu-system-x86_64 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1303926/+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 936756] Re: lxc complains about cgroup not available
I had to remove cgroup-lite and install cgroup-bin in order to avoid this error. cgroup-lite was not mounting /sys/fs/cgroup which lxc- execute required. Once I installed cgroup-bin and invoked /etc/init.d/cgconfig everything worked fine on my 12.04.3 LTS -- 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/936756 Title: lxc complains about cgroup not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/936756/+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 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
Hi Serge, You should be able to reproduce this with any iso from http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/10.0/ Let me know if you need more information. -- 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/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+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 1304377] [NEW] powernapd runaway
Public bug reported: Very occasionally powernapd runs away on me and starts using almost 100% of available CPU cycles. I'm running version 2.17-0ubuntu2 on i386, Ubuntu 12.04.4. The hardware is a Fujitsu Siemens LifeBook S7020 with BIOS version 1.05. The last two entries in /var/log/powernap.log are: 2014-04-08_12:49:54 WARNING Taking action [/usr/sbin/powernap] 2014-04-08_13:54:37 WARNING Taking recover action [/usr/sbin/pm-powersave false] I assume that something goes wrong during the transition away from powersave. Attaching to the running /usr/sbin/powernapd process with gdb yields the following backtrace: #0 0x002b5416 in __kernel_vsyscall () #1 0x00549bd1 in select () at ../sysdeps/unix/syscall-template.S:82 #2 0x080fbdf3 in time_sleep.52928 () #3 0x08137591 in PyEval_EvalFrameEx () #4 0x08137abc in PyEval_EvalFrameEx () #5 0x0813da90 in PyEval_EvalCodeEx () #6 0x0813e361 in run_mod () #7 0x0813e851 in PyRun_FileExFlags () #8 0x08087565 in PyRun_SimpleFileExFlags () #9 0x0808909f in Py_Main () #10 0x0805eabb in main () I'm attaching a few seconds' worth of strace output. My only workaround so far is to run service powernap restart (or equivalent) whenever this happens. Unfortunately I don't know how to reproduce the problem at will. ** Affects: powernap (Ubuntu) Importance: Undecided Status: New ** Attachment added: powernap.trace https://bugs.launchpad.net/bugs/1304377/+attachment/4074620/+files/powernap.trace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to powernap in Ubuntu. https://bugs.launchpad.net/bugs/1304377 Title: powernapd runaway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/1304377/+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 1303692] Re: New upstream version 1.4.1
I tried to upload a (hacked) version to my PPA for others to test, but this FTBFS (see issue 0). Now fixed, and built in ppa:racb/experimental (freeipmi 1.4.1-1~test2). There are still many packaging issues that need to be resolved, as described in my previous comment. But this should at least make it possible to begin testing changes made upstream for the pieces that were already functional. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1303692 Title: New upstream version 1.4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1303692/+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 1302638] Re: augeas-tools fails to parse krb5.conf (solution provided)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Have you sent this patch upstream? And does it cause any changes to the structure of the tree? Once you've responded, please change the bug status back to New. Thanks! ** Changed in: augeas (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to augeas in Ubuntu. https://bugs.launchpad.net/bugs/1302638 Title: augeas-tools fails to parse krb5.conf (solution provided) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1302638/+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 1304407] [NEW] juju bootstrap on openstack cloud defaults to i386
Public bug reported: 'juju bootstrap' on a private cloud with streams data for juju tools and images defaults to i386. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: juju-core 1.18.0-0ubuntu1 ProcVersionSignature: User Name 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 8 12:56:12 2014 Dependencies: gcc-4.9-base 4.9-20140330-0ubuntu1 libc6 2.19-0ubuntu3 libgcc1 1:4.9-20140330-0ubuntu1 multiarch-support 2.19-0ubuntu3 Ec2AMI: ami-0039 Ec2AMIManifest: FIXME Ec2AvailabilityZone: serverstack-az-1 Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core Importance: Undecided Status: New ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images trusty ** Also affects: juju-core Importance: Undecided Status: New -- 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/1304407 Title: juju bootstrap on openstack cloud defaults to i386 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1304407/+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 1304403] Re: Precise to Trusty - all of main - fails: The package 'postgresql-server-dev-9.1' is marked for removal but it's in the removal blacklist
** Also affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Precise to Trusty - all of main - fails: The package 'postgresql-server-dev-9.1' is marked for removal but it's in the removal blacklist + Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1302724] Re: libvirt 1.1.1 wasn't compiled with LXC support
*** This bug is a duplicate of bug 1287232 *** https://bugs.launchpad.net/bugs/1287232 I believe this to be a duplicate of bug 1287232. ** This bug has been marked a duplicate of bug 1287232 /usr/lib/libvirt-lxc.so missing from libvirt-dev -- 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/1302724 Title: libvirt 1.1.1 wasn't compiled with LXC support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1302724/+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 1304446] [NEW] git is removed when apt-get remove libldap-2.4-2
Public bug reported: I'm making a script for installing ldap server and posting the script to git. But every time i remove libldap-2.4-2 and only this package, git is also removed. I feel this is a bit unnecessary. Install command: sudo apt-get install slapd ldap-utils libldap-2.4-2 libnss-ldap remove command sudo apt-get purge -y slapd ldap-utils libldap-2.4-2 libnss-ldap apt-get -y autoremove apt-get autoclean you can see that git is removed when running apt-get remove libldap-2.4-2 I'm running build: Linux prosjekt2-server 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 15:31:16 UTC 2013 i686 i686 i386 GNU/Linux By first bug report yay!. ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: git libldap-2.4-2 remove ** Tags added: remove ** Tags added: git libldap-2.4-2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1304446 Title: git is removed when apt-get remove libldap-2.4-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1304446/+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 1304407] Re: juju bootstrap on openstack cloud defaults to i386
** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = High ** Tags added: metadata -- 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/1304407 Title: juju bootstrap on openstack cloud defaults to i386 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1304407/+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 1303477] Re: unbound default configuration only works after reload
I can't reproduce this issue on 1.4.22-1ubuntu4/trusty packages. ** Changed in: unbound (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unbound in Ubuntu. https://bugs.launchpad.net/bugs/1303477 Title: unbound default configuration only works after reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1303477/+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 1304407] Re: juju bootstrap on openstack cloud defaults to i386
I wonder if this is a bug in juju metadata. I noticed recently that when I generate data for tools , 1.15.0 is always the version for amd64. I think the version is selected from the oldest tool found for the series+arch. Metadata might be unrelated. Juju is trying to be smarter about selecting sane archs for clouds. Previously it assumed the remote arch was the same as the local arch. I don't see much evidence of i386 being a sane selection for a cloud. The primary use of juju i386 is to provide a client that can work with amd64 clouds. ** Changed in: juju-core Milestone: None = 1.19.1 -- 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/1304407 Title: juju bootstrap on openstack cloud defaults to i386 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1304407/+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 1304309] Re: Bind mounting for cloned containers is too hard; provide equivalent of lxc-start-ephemeral --bind option
You could use something like: lxc-start -n my-container -s lxc.mount.entry=/path/on/host path/in/container none bind,create=dir 0 0 Which will bind-mount /path/on/host to rootfs/path/in/container and create the target path if missing. -- 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/1304309 Title: Bind mounting for cloned containers is too hard; provide equivalent of lxc-start-ephemeral --bind option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1304309/+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 1304309] Re: Bind mounting for cloned containers is too hard; provide equivalent of lxc-start-ephemeral --bind option
Yay, I completely missed that possibility. Thanks! ** Changed in: lxc (Ubuntu) Status: New = Invalid -- 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/1304309 Title: Bind mounting for cloned containers is too hard; provide equivalent of lxc-start-ephemeral --bind option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1304309/+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 1287943] Re: vm-builder needs trusty suite
Thanks Brian, updating to proposed sources (vmbuilder version
0.12.4.r475) solved the problem for me on precise.
Meanwhile, in this revision, when calling vmbuilder --version, a python
error is raised. The cause is that 'revno' returned by the
VMBuilder.get_version_info is of type str, not int.
VMBuilder/contrib/cli.py:282
-print ('%(major)d.%(minor)d.%(micro)s.r%(revno)d' %
+print ('%(major)d.%(minor)d.%(micro)s.r%(revno)s' %
--
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/1287943
Title:
vm-builder needs trusty suite
To manage notifications about this bug go to:
https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 936756] Re: lxc complains about cgroup not available
Ah, are you running a saucy or trusty backport kernel? the precise cgroup-lite still is 'start on mounted MOUNTPOINT=/sys', whereas later it had to become 'MOUNTPOINT=/sys/fs/cgroup', It sounds like we need to update the precise job to handle both cases. -- 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/936756 Title: lxc complains about cgroup not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/936756/+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 1302638] Re: augeas-tools fails to parse krb5.conf (solution provided)
I'm the one who should do the thanking: I'm using your distro. I have not sent the changes upstream. I'm not very familiar with the jargon of parse tree structure. I'd say it obviously causes changes in the structure of the tree: it adds leaves. But I presume the question is meant: Are there any trees that are parseable by both the unpatched and the patched lens, but which do not give identical trees? I do not know whether to answer yes or no. The 'shapes' (in terms of number of edges from each node) will be identical, but some nodes will have differently named types, although the renames are quite trivial: of consequence only to the innards of the lens, not to its output. I see that my description of it is already getting longer than the patch itself. I'll happily send the patch upstream if you say that's a better way to go about this. ** Changed in: augeas (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to augeas in Ubuntu. https://bugs.launchpad.net/bugs/1302638 Title: augeas-tools fails to parse krb5.conf (solution provided) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1302638/+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 1295072] Re: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0
Yes, thanks Michael, as we discussed on irc this needs to be fixed in device-tree-compiler in precise (and quantal). Once that is done we can remove the versioned dependency in trusty qemu. ** Also affects: device-tree-compiler (Ubuntu) Importance: Undecided Status: New ** Changed in: device-tree-compiler (Ubuntu) Status: New = Triaged ** Also affects: qemu (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: device-tree-compiler (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: device-tree-compiler (Ubuntu Quantal) Importance: Undecided Status: New ** Changed in: device-tree-compiler (Ubuntu) Status: Triaged = Fix Released ** Changed in: device-tree-compiler (Ubuntu Precise) Status: New = Triaged ** Changed in: device-tree-compiler (Ubuntu Quantal) Status: New = Triaged ** Changed in: device-tree-compiler (Ubuntu) Importance: Undecided = High ** Changed in: qemu (Ubuntu Precise) Status: New = Invalid ** Changed in: qemu (Ubuntu Quantal) Status: New = Invalid ** Changed in: device-tree-compiler (Ubuntu Precise) Importance: Undecided = High ** Changed in: device-tree-compiler (Ubuntu Quantal) Importance: Undecided = High ** Changed in: device-tree-compiler (Ubuntu Precise) Status: Triaged = Confirmed ** Changed in: device-tree-compiler (Ubuntu Quantal) Status: Triaged = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1295072 Title: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/device-tree-compiler/+bug/1295072/+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 1295072] Re: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0
Hm, the CVE link was added by a (errant?) bot... I removed the link. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1295072 Title: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/device-tree-compiler/+bug/1295072/+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 1302638] Re: augeas-tools fails to parse krb5.conf (solution provided)
I'd say it obviously causes changes in the structure of the tree: it adds leaves. But I presume the question is meant: Are there any trees that are parseable by both the unpatched and the patched lens, but which do not give identical trees? Just to be clear, I think even just adding leaves could cause a future backwards compatibility problem, if upstream decide to add leaves with the same meaning but with different names. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to augeas in Ubuntu. https://bugs.launchpad.net/bugs/1302638 Title: augeas-tools fails to parse krb5.conf (solution provided) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1302638/+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 1302638] Re: augeas-tools fails to parse krb5.conf (solution provided)
Thank you for your reply! I'm the one who should do the thanking: I'm using your distro. I guess it's a two way thing; you're contributing, too! :) Let me give you an example of why I ask the question. Let's say that in Ubuntu, we take your patch. Upstream later decide to achieve the same thing, but in a different way, so the tree looks different. In the future, will behaviour on Ubuntu then differ from upstream behaviour, such that we won't be able to switch Ubuntu to upstream's behaviour without regressing somebody who is depending on Ubuntu's tree structure for krb5.conf? The risk is that we end up with an indefinite maintenance burden on Ubuntu because we accidentally forked upstream. For this reason, sending the patch upstream is better for us in general. But if there's some particular reason that we should make a change in Ubuntu ahead of upstream, then it can be considered, just with careful thought to the risk I have tried to explain above. A better way would be to cherry-pick patches from upstream's VCS - preferably after an upstream release. Then we know that upstream intend to support the change in terms of backwards compatibility. Does that make sense? For this reason I think submitting this upstream would be better in this case, where users will see a behavioural change that they may depend on, and that we don't want to be forced to regress in the future. ** Tags added: needs-upstream-report ** Changed in: augeas (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to augeas in Ubuntu. https://bugs.launchpad.net/bugs/1302638 Title: augeas-tools fails to parse krb5.conf (solution provided) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1302638/+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 1302638] Re: augeas-tools fails to parse krb5.conf (solution provided)
hat type=augeas_dev I'll be happy to merge your patch. Please open a PR against https://github.com/hercules-team/augeas and add unit tests for your bug, and I'll merge it. /hat hat type=ubuntu_dev If you think this should be fixed in trusty, I can also get the patch into the package and see if it will pass into the repository as a bugfix (once it's merged upstream). /hat -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to augeas in Ubuntu. https://bugs.launchpad.net/bugs/1302638 Title: augeas-tools fails to parse krb5.conf (solution provided) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1302638/+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 1295093] Re: [FFe] Merge docker.io 0.9.1 from Debian unstable
** Also affects: docker.io (Ubuntu Trusty) Importance: High Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1295093 Title: [FFe] Merge docker.io 0.9.1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1295093/+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 1287943] Re: vm-builder needs trusty suite
Hi Amir, please open a new bug for the crash you are seeing. Indeed revno should be an int not str in vcsersion.py -- 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/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1302229] Re: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support
** Changed in: cloud-init (Ubuntu Precise) Status: New = Fix Committed -- 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/1302229 Title: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1302229/+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 1304496] [NEW] add --version to squid3
Public bug reported: It would be helpful to have a --version parameter for the squid3 command printing the current version of the binary. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New -- 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/1304496 Title: add --version to squid3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1304496/+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 1268050] Re: Deprovision breaks iDNS registration when using cloud-init
Fix tested and verified. Marking as 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 walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1268050 Title: Deprovision breaks iDNS registration when using cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1268050/+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 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
** Description changed: Precise to Trusty upgrade + all of main failure: - 2014-04-08 12:58:48,335 DEBUG blacklist expr '^postgresql-.*[0-9]\.[0-9].*' matches 'postgresql-server-dev-9.1' 2014-04-08 12:58:48,335 DEBUG The package 'postgresql-server-dev-9.1' is marked for removal but it's in the removal blacklist 2014-04-08 12:58:48,357 ERROR Dist-upgrade failed: 'The package 'postgresql-server-dev-9.1' is marked for removal but it is in the removal blacklist.' 2014-04-08 12:58:48,358 DEBUG abort called + + REPRODUCER: + * Start a precise schroot + * apt-get install krb5-multidev + * Switch apt sources to trusty + * apt-get update + * apt-get dist-upgrade → This will remove krb5-multidev instead of upgrading ** Changed in: krb5 (Ubuntu Trusty) Status: New = Triaged ** Changed in: krb5 (Ubuntu Trusty) Importance: Undecided = High ** Changed in: ubuntu-release-upgrader (Ubuntu Trusty) Status: Confirmed = Won't Fix ** Changed in: krb5 (Ubuntu Trusty) Assignee: (unassigned) = Martin Pitt (pitti) ** Changed in: krb5 (Ubuntu Trusty) Milestone: None = ubuntu-14.04 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1295072] Re: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0
** Also affects: device-tree-compiler (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706137 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1295072 Title: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/device-tree-compiler/+bug/1295072/+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 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
Marking as high as it breaks the upgrade. There are two options: * -server-dev-9.1 isn't important to keep after upgrading, so we could adjust blacklist regexp to not cover -server-dev. * We resolve the krb-dev transition bug that keeps it from updating (might turn out to be tricky). That aspect would have low priority. ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided = High ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New = Confirmed ** Also affects: krb5 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Trusty) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1304518] [NEW] Confusing wording in the IPMI section of node power data
Public bug reported: New to the power management part of node info is this text: MAC address - the IP is looked up with ARP and is used if IP address is empty. This is better when the BMC uses DHCP. What is better when the BMC uses DHCP? Does using DHCP make using ARP better? or more accurate? I can't really seem to grok what this explanation of MAC Address actually means. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.5+bzr2227-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 8 12:09:59 2014 InstallationDate: Installed on 2014-01-13 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1304518 Title: Confusing wording in the IPMI section of node power data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1304518/+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 1304008] Re: user not added to libvirtd group with iso trusty 'virtual machine host' installation method
** Changed in: libvirt (Ubuntu) Status: Triaged = Fix Released -- 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/1304008 Title: user not added to libvirtd group with iso trusty 'virtual machine host' installation method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1304008/+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 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
Trivial fix uploaded. I tested this with a local apt-ftparchive, and it succeeds now. libkadm5srv-mit8 is now correctly removed, and the rest upgraded. ** Changed in: krb5 (Ubuntu Trusty) Status: Triaged = Fix Committed ** Changed in: krb5 (Ubuntu Trusty) Assignee: Martin Pitt (pitti) = (unassigned) ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1302229] Re: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support
Hello Ben, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- 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/1302229 Title: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1302229/+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 1295072] Re: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0
Re-marking confirmed for qemu to remind us that we must remove the version from the libfdt-dev dependency for qemu. ** Description changed: + == + Impact: libfdt-dev is unusable + Fix: we use the patch from debian wheezy to export the needed .h file. + Test case: download qemu package from trusty, remove the 1.4.0 versioning from the libfdt-dev dependency, and try to build + Regression Potential there should be none, we simply export another .h file. + == + The configure scripts checks for fdt by looking at libfdt_env.h configure:2610: #include libfdt_env.h This file only exists in libfdt-dev version 1.4.0 and onwards, so it makes sense to specify build-dependency on that version. Otherwise, configure fails with: - error_exit DTC not present. Your options: \ - (1) Preferred: Install the DTC devel package \ - (2) Fetch the DTC submodule, using: \ - git submodule update --init dtc + error_exit DTC not present. Your options: \ + (1) Preferred: Install the DTC devel package \ + (2) Fetch the DTC submodule, using: \ + git submodule update --init dtc ** Changed in: qemu (Ubuntu) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1295072 Title: qemu 1.7 should build-depend on libfdt-dev higher than 1.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/device-tree-compiler/+bug/1295072/+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 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
Ok that log is interesting as it shows that Ubuntu have re-named the QEMU machine types ... -machine trusty,accel=tcg,usb=off ... See 'trusty' is the machine type there instead of the more usual pc- i440fx-1.6 This unfortunately breaks the ability of libvirt to figure out what type of base board is used by the VM - it can't distinguish i440fx from q35. I'm guessing Ubuntu was probably inspired by the fact that we did a similar thing in RHEL-6, replacing 'pc' with 'rhel-6.1.0'. The recommendation for distros who want to customize the machine types without breaking libvirt is to *not* replace the entire machine type name, but instead to just replace the upstream version number with a distro specific suffix. eg change 'pc-i440fx-1.6' to be 'pc-i440fx-trusty'. That way libvirt can still see that this is an i440fx machine type and do the right thing with PCI address validation. As a reference point, RHEL7 does this correctly now too, using 'pc- i440fx-rhel7.0.0' as machine type name. Unfortunately there's nothing OpenStack Nova can do to workaround this. Either Ubuntu have to change their QEMU machine type name as illustrated, to maintain the right prefix, or they'll have to hack their libvirt build to cope with the bare name 'trusty' :-( ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1304107/+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 936756] Re: lxc complains about cgroup not available
Filed bug 1304538 for the cgroup-lite bug. -- 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/936756 Title: lxc complains about cgroup not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/936756/+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 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
** Changed in: nova Status: New = Invalid ** Tags removed: icehouse-backport-potential icehouse-rc-potential -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1304107/+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 1304538] [NEW] precise and quantal must be able to start on mounted MOUNTPOINT=sys/fs/cgroup
Public bug reported: From raring kernel onward, /sys/fs/cgroup is mounted separately. cgroup-lite in raring and later therefore has the upstart job start on mounted MOUNTPOINT=/sys/fs/cgroup instead of MOUNTPOINT=/sys. Now that precise users are using HWE kernels, cgroup-lite in precise must be able to handle that. ** Affects: cgroup-lite (Ubuntu) Importance: High Status: Fix Released ** Affects: cgroup-lite (Ubuntu Precise) Importance: High Status: Confirmed ** Affects: cgroup-lite (Ubuntu Quantal) Importance: High Status: Confirmed ** Changed in: cgroup-lite (Ubuntu) Status: New = Fix Released ** Also affects: cgroup-lite (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: cgroup-lite (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: cgroup-lite (Ubuntu) Importance: Undecided = High ** Changed in: cgroup-lite (Ubuntu Precise) Importance: Undecided = High ** Changed in: cgroup-lite (Ubuntu Quantal) Importance: Undecided = High ** Changed in: cgroup-lite (Ubuntu Precise) Status: New = Confirmed ** Changed in: cgroup-lite (Ubuntu Quantal) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1304538 Title: precise and quantal must be able to start on mounted MOUNTPOINT=sys/fs/cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1304538/+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 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
Thanks, Daniel. Yes, the intent here was to try and avoid the situation, in the future, that we currently have with distinguishing migrations from precise hosts from migrations from saucy hosts with older machine types. I'll fix this post haste in qemu ** Changed in: qemu (Ubuntu) Importance: Undecided = High ** Changed in: qemu (Ubuntu) Status: New = Triaged ** Changed in: qemu (Ubuntu) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1304107/+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 1302229] Re: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support
Confirmed test case #2 and test case #3 with existing build. I've asked rcj to confirm test cases as well. -- 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/1302229 Title: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1302229/+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 1302229] Re: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support
Building new image for test case #1 when package is confirmed to be in -proposed. -- 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/1302229 Title: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1302229/+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 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1304107/+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 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) = Chuck Short (zulcss) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1304107/+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 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
Excellent work... thanks so much! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1304107/+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 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
my libvirt is 1.2.2-0ubuntu7~cloud0 running Ubuntu 12.04 Phil -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1304107/+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 1304023] Re: [FFE] update walinuxagent to 2.0.4
This bug was fixed in the package walinuxagent - 2.0.4-0ubuntu1 --- walinuxagent (2.0.4-0ubuntu1) trusty; urgency=medium * Update to latest upstream version 2.0.4 (LP: #1304023). - Includes ability for agent injection. -- Ben Howard ben.how...@ubuntu.com Mon, 07 Apr 2014 16:48:16 -0600 ** Changed in: walinuxagent (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1304023 Title: [FFE] update walinuxagent to 2.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1304023/+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 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
** Branch linked: lp:ubuntu/trusty-proposed/krb5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1303926] Re: qemu-system-x86_64 crashed with SIGABRT
** Changed in: qemu (Ubuntu) Importance: Undecided = High ** Changed in: qemu (Ubuntu) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1303926 Title: qemu-system-x86_64 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1303926/+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 1304557] [NEW] rmdir: failed to remove ‘/etc/dhcp3/dhclient-enter-hooks.d’: No such file or directory
Public bug reported: I did an apt-get dist-upgrade on my Trusty machine and samba-common failed to upgrade. It looks like it's trying to remove a directory that no longer exists (dhcp3 vs. dhcp). Here is the output. sciri@iriguchi:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libhdb9-heimdal linux-headers-3.13.0-20 linux-headers-3.13.0-20-generic linux-image-3.13.0-20-generic linux-image-extra-3.13.0-20-generic Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up samba-common (2:4.1.6+dfsg-1ubuntu2) ... rmdir: failed to remove ‘/etc/dhcp3/dhclient-enter-hooks.d’: No such file or directory dpkg: error processing package samba-common (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of smbclient: smbclient depends on samba-common (= 2:4.1.6+dfsg-1ubuntu2); however: Package samba-common is not configured yet. dpkg: error processing package smbclient (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of samba-common-bin: samba-common-bin depends on samba-common (= 2:4.1.6+dfsg-1ubuntu2); however: Package samba-common is not configured yet. dpkg: error processing package samba-common-bin (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. sciri@iriguchi:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Codename: trusty sciri@iriguchi:~$ apt-cache policy samba-common samba-common: Installed: 2:4.1.6+dfsg-1ubuntu2 Candidate: 2:4.1.6+dfsg-1ubuntu2 Version table: *** 2:4.1.6+dfsg-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 2:3.6.3-2ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages sciri@iriguchi:~$ apt-cache policy isc-dhcp-server isc-dhcp-server: Installed: 4.2.4-7ubuntu12 Candidate: 4.2.4-7ubuntu12 Version table: *** 4.2.4-7ubuntu12 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 4.1.ESV-R4-0ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages sciri@iriguchi:~$ ls -al /etc/dhcp3/ ls: cannot access /etc/dhcp3/: No such file or directory sciri@iriguchi:~$ ls -al /etc/dhcp/ total 44 drwxr-xr-x 5 root root 4096 Apr 8 06:27 . drwxr-xr-x 126 root root 12288 Apr 8 13:08 .. drwxr-x--- 2 root dhcpd 4096 Sep 11 2012 ddns-keys -rw-r--r-- 1 root root 63 May 26 2011 dhclient.conf -rw-r--r-- 1 root root 1830 Mar 14 2013 dhclient.conf.dpkg-dist drwxr-xr-x 2 root root 4096 Apr 8 06:27 dhclient-enter-hooks.d drwxr-xr-x 2 root root 4096 Apr 8 06:27 dhclient-exit-hooks.d -rw-r--r-- 1 root root 4311 Feb 25 18:11 dhcpd.conf ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 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/1304557 Title: rmdir: failed to remove ‘/etc/dhcp3/dhclient-enter-hooks.d’: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1304557/+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 1302229] Re: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support
I have also verified test cases #2 and #3. -- 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/1302229 Title: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1302229/+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 1304565] [NEW] package php5-gd 5.4.6-1ubuntu1.8 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 2
Public bug reported: when i install lamp-server and uninstall lamp-server for twice,then install again,then the bug come out. please help me!thanks! ProblemType: Package DistroRelease: Ubuntu 12.10 Package: php5-gd 5.4.6-1ubuntu1.8 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 AptOrdering: phpmyadmin: Purge php5-gd: Configure Architecture: amd64 Date: Wed Apr 9 00:53:21 2014 ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 2 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: php5 Title: package php5-gd 5.4.6-1ubuntu1.8 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package quantal -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1304565 Title: package php5-gd 5.4.6-1ubuntu1.8 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1304565/+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 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
This bug was fixed in the package krb5 - 1.12+dfsg-2ubuntu3 --- krb5 (1.12+dfsg-2ubuntu3) trusty; urgency=medium * Add missing versioned Replaces: libkadm5srv-mit8 to the libkdb5-7 package. Fixes upgrades from trusty. (LP: #1304403) -- Martin Pitt martin.p...@ubuntu.com Tue, 08 Apr 2014 18:04:14 +0200 ** Changed in: krb5 (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1304566] [NEW] package libapache2-mod-php5 5.5.3+dfsg-1ubuntu2.3 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Public bug reported: trying to install LAMP server using tasksel ProblemType: Package DistroRelease: Ubuntu 13.10 Package: libapache2-mod-php5 5.5.3+dfsg-1ubuntu2.3 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Tue Apr 8 19:29:44 2014 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2014-04-01 (7 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016) MarkForUpload: True SourcePackage: php5 Title: package libapache2-mod-php5 5.5.3+dfsg-1ubuntu2.3 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1304566 Title: package libapache2-mod-php5 5.5.3+dfsg-1ubuntu2.3 failed to install/upgrade: il sottoprocesso installato script di post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1304566/+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 1302229] Re: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support
Confirmed that test case works against new image build. ** 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 cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1302229 Title: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1302229/+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 1299588] Re: LXC permission denied issue with 1.17.7
I lowered the trunk task to High because the fix was delivered to users in 1.18.0 ** Changed in: juju-core Importance: Critical = High -- 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/1299588 Title: LXC permission denied issue with 1.17.7 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1299588/+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 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
This bug was fixed in the package libvirt - 1.2.2-0ubuntu11 --- libvirt (1.2.2-0ubuntu11) trusty; urgency=medium * debian/patches/recognize-trusty-machine-type.patch: Revert patch since it was causing issues with virtio deivces. (LP: #1304107) -- Chuck Short zul...@ubuntu.com Tue, 08 Apr 2014 12:51:55 -0400 ** Changed in: libvirt (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1304107/+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 1303926] Re: qemu-system-x86_64 crashed with SIGABRT
And it is not just with vnc either. ** Changed in: qemu (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1303926 Title: qemu-system-x86_64 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1303926/+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 1304304] Re: nginx ubuntu package possibly affected by CVE 2014-0160
Did you restart nginx or reboot your system after applying the update? Thanks ** Information type changed from Private Security to Public Security ** Changed in: nginx (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1304304 Title: nginx ubuntu package possibly affected by CVE 2014-0160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1304304/+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 1302956] Re: maas.ubuntu.com only shows the documentation for the most recent MAAS version
** Branch linked: lp:ubuntu/trusty-proposed/maas -- 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/1302956 Title: maas.ubuntu.com only shows the documentation for the most recent MAAS version To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302956/+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 1302772] Re: update of maas-cluster-controller on trusty dumps traceback and crashes
** Branch linked: lp:ubuntu/trusty-proposed/maas -- 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/1302772 Title: update of maas-cluster-controller on trusty dumps traceback and crashes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302772/+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 1302638] Re: augeas-tools fails to parse krb5.conf (solution provided)
Ok, I cloned the GitHub repository, forked, making changes. As for unit tests, it looks to me like an entire lens is the unit of testing, so I would edit lenses/tests/test_krb5.aug to include some previously unparsed in- and output. Is that what you want me to do? Also, it's not unlikely that I'll need more changes to this particular lens in the near future (weeks to months). Am I right assuming that - it's better to send multiple PRs than to accumulate, and - patches that can pass for a bugfix will get into Trusty even after it is released, whereas ones that seriously change the parse tree won't make it into Trusty even if I were to open the PR tomorrow? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to augeas in Ubuntu. https://bugs.launchpad.net/bugs/1302638 Title: augeas-tools fails to parse krb5.conf (solution provided) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1302638/+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 1304304] Re: nginx ubuntu package possibly affected by CVE 2014-0160
Yes, I did restart the system. I think I've found the solution in the meantime: it's not sufficient to just update the openssl package, it's also necessary to update libssl1.0.0. After doing this and restarting nginx, the system does not respond to heartbeat requests anymore. Sorry, this was not clear for me just by reading the security note. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1304304 Title: nginx ubuntu package possibly affected by CVE 2014-0160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1304304/+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 1302229] Re: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support
This bug was fixed in the package cloud-init - 0.6.3-0ubuntu1.13 --- cloud-init (0.6.3-0ubuntu1.13) precise-proposed; urgency=medium * debian/patches/lp-1302229-fix_futils_azure.patch: fixed imports and util usage for new disk detection and format w/ Azure DS (LP: #1302229). -- Ben Howard ben.how...@ubuntu.com Thu, 03 Apr 2014 16:26:50 -0600 ** Changed in: cloud-init (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 cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1302229 Title: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1302229/+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 1302229] Update Released
The verification of the Stable Release Update for cloud-init 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 cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1302229 Title: [SRU] cloud-init Windows Azure does not have correct futil support for disk format support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1302229/+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 1302956] Re: maas.ubuntu.com only shows the documentation for the most recent MAAS version
This bug was fixed in the package maas - 1.5+bzr2230-0ubuntu1 --- maas (1.5+bzr2230-0ubuntu1) trusty; urgency=medium * New upstream bugfix release: - Fix Cluster Controller to handle deprecated config items gracefull. Otherwise it fails on upgrades. (LP: #1302772) - Fix documentation generation and referencing. (LP: #1302956) - Ensure we PXE boot when we turn on SM15K systems. (LP: #1303915) -- Andres Rodriguez andres...@ubuntu.com Mon, 07 Apr 2014 10:26:51 -0400 ** Changed in: maas (Ubuntu) Status: Invalid = 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/1302956 Title: maas.ubuntu.com only shows the documentation for the most recent MAAS version To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302956/+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 1254872] Re: libvirtError: Timed out during operation: cannot acquire state change lock
This bug was fixed in the package libvirt - 0.9.8-2ubuntu17.18 --- libvirt (0.9.8-2ubuntu17.18) precise-proposed; urgency=medium * d/p/ubuntu/qemu-fix-race-between-async-and-query-jobs.patch: fix a race between asynchronous and query jobs. (LP: #1254872) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 11 Mar 2014 14:14:38 -0500 ** Changed in: libvirt (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 libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1254872 Title: libvirtError: Timed out during operation: cannot acquire state change lock To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1254872/+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 992012] Re: No /openssl.cnf file could be found because of a wrong regex in whichopensslcnf
This bug was fixed in the package openvpn - 2.2.1-8ubuntu1.2 --- openvpn (2.2.1-8ubuntu1.2) precise-proposed; urgency=low * d/p/lp992012-detect-openssl-properly.patch: fix openssl.cnf file could be found error using easy-rsa by parsing openssl version properly. (LP: #992012) -- Nobuto MURATA nob...@ubuntu.com Tue, 18 Feb 2014 14:35:32 +0900 ** Changed in: openvpn (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 openvpn in Ubuntu. https://bugs.launchpad.net/bugs/992012 Title: No /openssl.cnf file could be found because of a wrong regex in whichopensslcnf To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/992012/+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 1302772] Re: update of maas-cluster-controller on trusty dumps traceback and crashes
This bug was fixed in the package maas - 1.5+bzr2230-0ubuntu1 --- maas (1.5+bzr2230-0ubuntu1) trusty; urgency=medium * New upstream bugfix release: - Fix Cluster Controller to handle deprecated config items gracefull. Otherwise it fails on upgrades. (LP: #1302772) - Fix documentation generation and referencing. (LP: #1302956) - Ensure we PXE boot when we turn on SM15K systems. (LP: #1303915) -- Andres Rodriguez andres...@ubuntu.com Mon, 07 Apr 2014 10:26:51 -0400 ** Changed in: maas (Ubuntu) Status: Confirmed = 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/1302772 Title: update of maas-cluster-controller on trusty dumps traceback and crashes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302772/+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 992012] Update Released
The verification of the Stable Release Update for openvpn 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 openvpn in Ubuntu. https://bugs.launchpad.net/bugs/992012 Title: No /openssl.cnf file could be found because of a wrong regex in whichopensslcnf To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/992012/+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 1268050] Re: Deprovision breaks iDNS registration when using cloud-init
This bug was fixed in the package walinuxagent - 1.3.2-0ubuntu6 --- walinuxagent (1.3.2-0ubuntu6) saucy; urgency=low * Fixes for (LP: #1268050): - Change /etc/dhcp/dhclient.conf 'send host-name' during post-inst to fix snapshotting instances. - Backport of send-hostname fix from 1.4.1 per MS request. -- Ben Howard ben.how...@ubuntu.com Wed, 19 Mar 2014 16:58:58 -0600 ** Changed in: walinuxagent (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 walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1268050 Title: Deprovision breaks iDNS registration when using cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1268050/+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 1268050] Update Released
The verification of the Stable Release Update for walinuxagent 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 walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1268050 Title: Deprovision breaks iDNS registration when using cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1268050/+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 1268050] Re: Deprovision breaks iDNS registration when using cloud-init
This bug was fixed in the package walinuxagent - 1.3.2-0ubuntu4~12.04.6 --- walinuxagent (1.3.2-0ubuntu4~12.04.6) precise; urgency=low * Fixes for (LP: #1268050): - Change /etc/dhcp/dhclient.conf 'send host-name' during post-inst to fix snapshotting instances sending wrong hostname via DHCP to fabric. - Backport of send-hostname fix from 1.4.1 per MS request. -- Ben Howard ben.how...@ubuntu.com Wed, 19 Mar 2014 07:14:02 -0600 ** Changed in: walinuxagent (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 walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1268050 Title: Deprovision breaks iDNS registration when using cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1268050/+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 1304304] Re: nginx ubuntu package possibly affected by CVE 2014-0160
Correct me if I'm wrong, but doesn't this bug affect OpenSSL? The Security team released a fix for this in OpenSSL. I will check to see if it's statically linked, but the last I checked it was not. I haven't recently checked this though. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1304304 Title: nginx ubuntu package possibly affected by CVE 2014-0160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1304304/+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 1302638] Re: augeas-tools fails to parse krb5.conf (solution provided)
On Tue, Apr 8, 2014 at 8:40 PM, Jurjen Bokma j.bo...@rug.nl wrote: Ok, I cloned the GitHub repository, forked, making changes. As for unit tests, it looks to me like an entire lens is the unit of testing, so I would edit lenses/tests/test_krb5.aug to include some previously unparsed in- and output. Is that what you want me to do? It's quite common indeed to use the entire lens as the unit of testing. Just add a new test case after the last one in `lenses/tests/test_krb5.aug`. Make sure it fails before you patch, and then add the patch. Also, it's not unlikely that I'll need more changes to this particular lens in the near future (weeks to months). Am I right assuming that - it's better to send multiple PRs than to accumulate, and Indeed, unless they strongly depend on each other, in which case it might make it hard to manage if there's a need to modify them before merging. - patches that can pass for a bugfix will get into Trusty even after it is released, whereas ones that seriously change the parse tree won't make it into Trusty even if I were to open the PR tomorrow? Yes, that's right. Patches that are not backwards-compatible are less likely be accepted as bugfix. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to augeas in Ubuntu. https://bugs.launchpad.net/bugs/1302638 Title: augeas-tools fails to parse krb5.conf (solution provided) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1302638/+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 1274247] Re: [MIR] Glusterfs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glusterfs (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1274247 Title: [MIR] Glusterfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1274247/+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 1304613] [NEW] nodes can't get out to the internet beyond the maas server by default
Public bug reported: by default, there's no way for a node started by maas to talk to the internet. There is also no way on the maas dashboard that I can see that allows me to control this sort of network behaviour either. For now, we are using a shell script to start NAT rules in iptables so that a node can actually talk to the internet. Scenario one: node commissioned and started, uses d-i to do a basic install. This works fine however, if you have the pressed do something like add a PPA for some different packages during late_command, you can never complete installation because add-apt-repository can't talk to the outside. And if you add the repo manually, I do not believe you can actually pull the packages from ppa.launchpad.net. Scenario two: node commissioned and started, using fast-path install. After fast-path is done and note reboots, you ssh into the node and want to add the PPA manually and install packages. This is impossible because again, add-apt-repository fails to get stuff from launchpad.net. Solution to both, for now, is to set up NAT with the following rules: echo 1 /proc/sys/net/ipv4/ip_forward /sbin/iptables -t nat -A POSTROUTING -o $EXTERNAL -j MASQUERADE /sbin/iptables -A FORWARD -i $EXTERNAL -o $INTERNAL -m state --state RELATED,ESTABLISHED -j ACCEPT /sbin/iptables -A FORWARD -i $INTERNAL -o $EXTERNAL -j ACCEPT ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.5+bzr2227-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 8 15:11:12 2014 InstallationDate: Installed on 2014-01-13 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1304613 Title: nodes can't get out to the internet beyond the maas server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1304613/+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 1304304] Re: nginx ubuntu package possibly affected by CVE 2014-0160
Kai, thanks, that makes more sense. Have fun! ** Changed in: nginx (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1304304 Title: nginx ubuntu package possibly affected by CVE 2014-0160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1304304/+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 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
This bug was fixed in the package qemu - 2.0.0~rc1+dfsg-0ubuntu2 --- qemu (2.0.0~rc1+dfsg-0ubuntu2) trusty; urgency=medium * define-trusty-machine-type.patch: update the trusty machine type name to pc-i440fx-trusty (LP: #1304107) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 08 Apr 2014 11:49:04 -0500 ** Changed in: qemu (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1304107/+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 1304621] [NEW] package samba4 (not installed) failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 255
Public bug reported: package samba4 (not installed) failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 255 ProblemType: Package DistroRelease: Ubuntu 13.10 Package: samba4 (not installed) ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Mon Mar 31 15:40:20 2014 DuplicateSignature: package:samba4:(not installed):sub-processo script post-installation instalado retornou estado de saída de erro 255 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 255 InstallationDate: Installed on 2014-02-15 (52 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016) MarkForUpload: True SourcePackage: samba4 Title: package samba4 (not installed) failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 255 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba4 in Ubuntu. https://bugs.launchpad.net/bugs/1304621 Title: package samba4 (not installed) failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1304621/+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 1304304] Re: nginx ubuntu package possibly affected by CVE 2014-0160
Refer to USN-2165-1 for the OpenSSL notice on this vulnerability, and about it being fixed. This applies to libssl as well. I am almost certain nginx doesn't static-link to libssl. Again, I'll double check this. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1304304 Title: nginx ubuntu package possibly affected by CVE 2014-0160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1304304/+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 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
Not criticising here, but asking. At a level deeper than it causes apt to work correctly, why is adding replaces a reasonable fix? Nothing in libkdb5-7 actually replases libkadm5-mit8 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1304538] Re: precise and quantal must be able to start on mounted MOUNTPOINT=sys/fs/cgroup
** Changed in: cgroup-lite (Ubuntu Precise) Status: Confirmed = Invalid ** Changed in: cgroup-lite (Ubuntu Quantal) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1304538 Title: precise and quantal must be able to start on mounted MOUNTPOINT=sys/fs/cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1304538/+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 1303926] Re: qemu-system-x86_64 crashed with SIGABRT
** Also affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1303926 Title: qemu-system-x86_64 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1303926/+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
[Blueprint servercloud-1403-server-misc] Miscellaneous work that needs to be done for Server
Blueprint changed by Scott Moser: Work items changed: Work items: [racb] Post to ubuntu-release for clarity on how release bugs should be tracked: TODO [racb] Pre final-freeze merge review: DONE [louis-bouchard] uvtool documentation in server guide (coordinate with beisner and caribou): DONE [smoser] Document simplestreams: TODO - [smoser] get some documentation for cloud-install: TODO + [smoser] get some documentation for curtinl: TODO -- Miscellaneous work that needs to be done for Server https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1403-server-misc -- 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 1303926] Re: qemu-system-x86_64 crashed with SIGABRT
2f487a3d40faff1772e14da6b921900915501f9a was ok, so bisecting right now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1303926 Title: qemu-system-x86_64 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1303926/+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 1304446] Re: git is removed when apt-get remove libldap-2.4-2
libldap-2.4-2 is a system library, required by a lot of applications and other libraries. I don't think this would be considered a bug. Why do you want to remove it? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1304446 Title: git is removed when apt-get remove libldap-2.4-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1304446/+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
