[Bug 1071529] Re: Please merge libapache2-mod-perl2
This bug was fixed in the package libapache2-mod-perl2 - 2.0.7-1ubuntu1 --- libapache2-mod-perl2 (2.0.7-1ubuntu1) raring; urgency=low * Resynchronise with Debian (LP: #1071529). Remaining changes: - Change locales-all to locales. - Drop dwww from a recommends to a suggests to avoid pulling this into main. libapache2-mod-perl2 (2.0.7-1) unstable; urgency=low * New upstream release - fixes FTBFS with perl 5.16 (Closes: #676269) * Partially revert change which removes Apache::Sizelimit::Core as this is still needed (Closes: #661370) libapache2-mod-perl2 (2.0.6-2) unstable; urgency=low * debian/rules: run dh_auto_test with --max-parallel=1. This avoids build failures with -jN and build-arch. * debian/copyright: update to Copyright-Format 1.0. * Update packaging copyright years. libapache2-mod-perl2 (2.0.6-1) unstable; urgency=low * New upstream release - rebase/drop some patches libapache2-mod-perl2 (2.0.5-6) unstable; urgency=low * Bump debhelper compat level to 9 * Apply patch from Niko Tyni fixing FTBFS with -Werror=format-security (Closes: #661540) * Update Standards-Version (no changes) -- Colin Watson cjwat...@ubuntu.com Tue, 27 Nov 2012 23:08:38 + ** Changed in: libapache2-mod-perl2 (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libapache2-mod-perl2 in Ubuntu. https://bugs.launchpad.net/bugs/1071529 Title: Please merge libapache2-mod-perl2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-perl2/+bug/1071529/+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 945177] Re: not lintian clean
Last warnings for lintian (2013.1~g1-0ubuntu1_all): W: nova-common: wrong-name-for-upstream-changelog usr/share/doc/nova-common/ChangeLog.gz W: nova-common: non-standard-executable-perm etc/nova/logging.conf 0655 != 0755 W: nova-common: executable-not-elf-or-script etc/nova/logging.conf W: nova-compute: maintainer-script-needs-depends-on-adduser postinst W: nova-compute-xcp: empty-binary-package W: nova-scheduler: binary-without-manpage usr/bin/nova-clear-rabbit-queues W: nova-scheduler: binary-without-manpage usr/bin/nova-rpc-zmq-receiver W: nova-volume: empty-binary-package W: nova-ajax-console-proxy: transitional-package-should-be-oldlibs-extra net/extra E: nova-xvpvncproxy: duplicate-updaterc.d-calls-in-postrm nova-xvpvncproxy W: nova-api-metadata: breaks-without-version nova-api W: nova-api-os-compute: breaks-without-version nova-api W: nova-api-os-volume: breaks-without-version nova-api W: nova-api-os-volume: empty-binary-package W: nova-api-ec2: breaks-without-version nova-api E: nova-api-ec2: postrm-does-not-call-updaterc.d-for-init.d-script etc/init.d/nova-api-ec2 -- 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/945177 Title: not lintian clean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/945177/+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 1084028] [NEW] openvswitch based interfaces not started in time during boot
Public bug reported: If you create network interfaces (access ports) in openvswitch, and configure them in /etc/network/interfaces, failsafe.conf will kick in and the interfaces get configured after failsafe.conf exits. This adds two minutes to boot time. openvswitch config: ovs-vsctl show 93e6b401-214b-4089-ac51-27ca43009cce Bridge br0 Port br0 Interface br0 type: internal Port vlan128 tag: 128 Interface vlan128 type: internal Port bond0 trunks: [128] Interface eth0 Interface eth5 Bridge br1 Port bond1 trunks: [143, 145] Interface eth1 Interface eth4 Port phy-br1 Interface phy-br1 Port br1 Interface br1 type: internal Port int-br1 Interface int-br1 ovs_version: 1.4.3 cat /etc/network/interfaces: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto eth1 iface eth1 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto eth4 iface eth4 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto eth5 iface eth5 inet manual pre-up ip link set $IFACE up post-down ip link set $IFACE down auto vlan128 iface vlan128 inet static address 172.17.128.102 netmask 255.255.255.0 I expected openvswitch (interfaces/ports/bonds/trunks) to be up-and- running before /etc/network/interfaces gets evaluated. Clint Byrum (Ubuntu) reported me the following: failsafe.conf will exit when all interfaces marked as 'auto' are up. The only time you get a 2 minute delay is when it takes that long to bring those interfaces up. Since you have these vlanXXX interfaces listed, the system is waiting for them to come up. It seems to me that openvswitch needs to be brought up before runlevel 2, and so probably needs an upstart job. This sounds like a clear bug. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+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 1081495] Re: E: Sub-process /usr/bin/dpkg returned an error code (1)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tgt (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1081495 Title: E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1081495/+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 1049908] Re: Upstart control of lxc container instances
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu45 --- lxc (0.8.0~rc1-4ubuntu45) raring; urgency=low [ Stéphane Graber ] * Allow the container to mount efivars on /sys/firmware/efi/efivars. efivars is automatically mounted by mountall on UEFI systems, failure to do so leads to a complete boot failured. * Allow mounts and pivot_roots under /usr/lib/lxc/root/ for compatibility with nested precise lxc hosts (quantal - precise - containers). [ Serge Hallyn ] * update 0227-ubuntu-cloud-parsing to catch a doc typo stgraber had found in the upstream review. * 0228-ignore-kmsg-setup-failure: ignore failure to set up kmsg, since that is not critical. [ Christian Kampka ] * Have upstart run lxc instances (LP: #1049908) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 27 Nov 2012 22:52:10 -0600 ** Changed in: lxc (Ubuntu Raring) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1049908 Title: Upstart control of lxc container instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1049908/+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 959308] Re: kvm does not generate a system uuid by default
** Changed in: whoopsie-daisy (Ubuntu) Status: Fix Committed = Fix Released -- 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/959308 Title: kvm does not generate a system uuid by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/959308/+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 1081701] Re: The metadata address mentioned in the preseed is wrong.
This is not fixed yet, the enlistment user data is not fixed. ** Changed in: maas/trunk Status: Fix Committed = In Progress ** Changed in: maas/trunk Assignee: Gavin Panella (allenap) = Raphaël Badin (rvb) ** Branch linked: lp:~rvb/maas/enlistment-user-data -- 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/1081701 Title: The metadata address mentioned in the preseed is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1081701/+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 1084089] [NEW] lxc-clone shouldn't add fstab line if it wasn't there originally
Public bug reported: Rene K. Mueller reports that when an original container does not have an fstab, lxc-clone still adds a 'lxc.mount = /fstab' line, breaking container start. ** Affects: lxc (Ubuntu) Importance: Medium Status: Triaged ** Changed in: lxc (Ubuntu) Status: New = Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium -- 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/1084089 Title: lxc-clone shouldn't add fstab line if it wasn't there originally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1084089/+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 1079897] Re: walinuxagent mangles server identity and access on upgrade
** Changed in: walinuxagent (Ubuntu Precise) Status: Confirmed = In Progress ** Changed in: walinuxagent (Ubuntu Quantal) Status: Confirmed = In Progress -- 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/1079897 Title: walinuxagent mangles server identity and access on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1079897/+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 1074418] Re: qemu:///sessions fail, when libvirtd hasn't been started properly before
Thank you for your bug report, the issue should be fixed with 1.0 in raring, the commit fixing it seems to be http://libvirt.org/git/?p=libvirt.git;a=patch;h=efe6c8021146d046846ead5b5efc9828d97c1ceb ... I'm looking at backporting it to quantal ** Changed in: libvirt (Ubuntu) Status: Confirmed = Fix Released ** Changed in: libvirt (Ubuntu) Importance: Undecided = High ** Changed in: libvirt (Ubuntu Quantal) Importance: Undecided = High ** Changed in: libvirt (Ubuntu Quantal) Status: New = In Progress ** Description changed: + Impact: + clients using qemu:///session fail to contact the server, that makes e.g gnome-boxes fail to work correctly + + Test case: + - run virsh -c qemu:///session + + it hits this in quantal error: failed to connect to the hypervisor, + with the fix it should work + + Regression potential: + Limited, that commit is only setting some extra environment variables + + - + Starting with 12.10 the libvirt communications mechanism uses the XDG_RUNTIME_DIR environment variable to determine the directory to put in its pipe(s) and controlling files - this normally being /run/user/$USER/libvirt. Now when you run a qemu user(!) session (qemu:///session) and a 'libvirtd'-process owned by the user hasn't already be spawned - e.g. manually - libvirt0 will spawn one itself. When manually spawned from a terminal window, XDG_RUNTIME_DIR is properly set up to /run/user/$USER and everything works well with libvirtd. When libvirt0 spawns the libvirtd, it will use $HOME/.cache/libvirt, the previous (up to and including 12.04) location for this, because this seems to be its fallback-default. Thus when you start such a session with virsh -c qemu:///session or vitual-manager, respectively, it will fail, saying error: Failed to connect socket to '/run/user/$USER/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor in the former case. Either XDG_RUNTIME_DIR is not properly set when libvirt spawns libvirtd, or it is not respected. My assumption is the former, as XDG_RUNTIME_DIR seems to be set by some 'pam'-module, that probably isn't used when libvirt exececutes libvirtd. As a workaround one can set XDG_RUNTIME_DIR=.cache in the environment calling virsh or virtual-manager, the everything uses the old/former settings and works. The problem seems to be to tell libvirt about the proper XDG_RUNTIME_DIR contents or make it the new default. The way it is now, qemu-user-sessions will just fail when started by virsh or virt-manager. By the way, you can test it even with a 'live'-system (USB/DVD) by just adding the libvirt-bin and/or virt-manager packages, thus it is not dependent on the version of the packages installed on the actual system. Nevertheless as I can't see if that information is attached otherwise, here are the system data you require: Description: Ubuntu 12.10 Release: 12.10 libvirt0: Installed: 0.9.13-0ubuntu12 Candidate: 0.9.13-0ubuntu12 Version table: *** 0.9.13-0ubuntu12 0 500 http://de.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status Best regards. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libvirt0 0.9.13-0ubuntu12 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Fri Nov 2 17:13:51 2012 InstallationDate: Installed on 2011-03-05 (608 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1) MarkForUpload: True SourcePackage: libvirt UpgradeStatus: Upgraded to quantal on 2012-10-26 (6 days ago) -- 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/1074418 Title: qemu:///sessions fail, when libvirtd hasn't been started properly before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1074418/+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 1079897] Re: walinuxagent mangles server identity and access on upgrade
** Branch linked: lp:~louis-bouchard/ubuntu/precise/walinuxagent /walinuxagent-lp1079897 -- 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/1079897 Title: walinuxagent mangles server identity and access on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1079897/+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 1084089] Re: lxc-clone shouldn't add fstab line if it wasn't there originally
While fixing this one, can you also have lxc-clone properly change the lxc.mount line to point to the clone (if lxc.mount exists for the source). I thought that was done, but apparently not, I spent half an hour yesterday trying to figure out why a container was ignoring new fstab entries, before noticing that lxc.mount was pointing at another container... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1084089 Title: lxc-clone shouldn't add fstab line if it wasn't there originally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1084089/+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 1084089] Re: lxc-clone shouldn't add fstab line if it wasn't there originally
Quoting Stéphane Graber (stgra...@stgraber.org): While fixing this one, can you also have lxc-clone properly change the lxc.mount line to point to the clone (if lxc.mount exists for the source). Are you sure? I looked at the code before filing this and it was doing the right thing, using Dwight's patch. I thought that was done, but apparently not, I spent half an hour yesterday trying to figure out why a container was ignoring new fstab entries, before noticing that lxc.mount was pointing at another container... I'll take a look, thanks. (Not sure I'm getting to this bug today though) -- 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/1084089 Title: lxc-clone shouldn't add fstab line if it wasn't there originally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1084089/+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 1084089] Re: lxc-clone shouldn't add fstab line if it wasn't there originally
Well, I did a lxc-clone yesterday using a daily build of the staging tree and it definitely was still pointing at the source. Now maybe we have some patch in Ubuntu that's not in staging and that fixes that, or staging recently regressed, not sure... -- 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/1084089 Title: lxc-clone shouldn't add fstab line if it wasn't there originally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1084089/+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 1081701] Re: The metadata address mentioned in the preseed is wrong.
** Branch linked: lp:~rvb/maas/fix-origin-adr -- 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/1081701 Title: The metadata address mentioned in the preseed is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1081701/+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 1079897] Re: walinuxagent mangles server identity and access on upgrade
** Branch linked: lp:~louis-bouchard/ubuntu/quantal/walinuxagent /walinuxagent-lp1079897 -- 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/1079897 Title: walinuxagent mangles server identity and access on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1079897/+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 1081495] Re: E: Sub-process /usr/bin/dpkg returned an error code (1)
potentially relavent information at http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=577925. ** Bug watch added: Debian Bug tracker #577925 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577925 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1081495 Title: E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1081495/+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 1084089] Re: lxc-clone shouldn't add fstab line if it wasn't there originally
Actually it's a bit worse than that. The code in the package was not fixed quite the same way as upstream. Instead of looking for 'lxc.mount[ \t]', it looks for any 'lxc.mount'. If found it removes all those entries and adds a new fstab entry. The problem is that the lxc.conf always can have 'lxc.mount.entry' lines, which will be deleted and replaced by an fstab line in the clone. ** Also affects: lxc (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Raring) Importance: Medium Status: Triaged ** Changed in: lxc (Ubuntu Precise) Status: New = Triaged ** Changed in: lxc (Ubuntu Quantal) Status: New = Triaged ** Changed in: lxc (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu Raring) Importance: Medium = High ** Changed in: lxc (Ubuntu Quantal) Importance: Medium = High ** Changed in: lxc (Ubuntu Precise) Importance: Medium = High -- 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/1084089 Title: lxc-clone shouldn't add fstab line if it wasn't there originally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1084089/+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 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
RE Thomas Hood's #120: That is very interesting, though I admit it is near the outer limits of my current understanding. To address the only questions above: The problem is that the LTSP client, after successfully getting DHCP assignments, fails to download the pxelinux boot image. It reports PXE-E32: TFTP open timeout. To be more specific on the DHCP assignments, it identifies my hardware router as the DHCP server and the default gateway. It identifies the LTSP server as proxy and boot server. Is your LTSP server running Ubuntu and standalone dnsmasq? Then shouldn't the client use your LTSP server as the DHCP server? The LTSP server is running Lubuntu with the default network configuration, whatever that is. I understand you to be saying that this would be a standalone instance of dnsmasq started by an initscript, prepared to handle DHCP and TFTP. And apart from that, network-manager starts another instance of dnsmasq to handle DNS. Regarding whether the client should use the LTSP server as the DHCP server: I imagine that it is prepared to handle DHCP, and probably does in a standard LTSP setup with 2 NIC's and the client connected to the second NIC, but in this LTSP-PNP setup with a single NIC, the client is connected to the router, and the LTSP server defers to the router handling DHCP. -- Your explanation is very interesting because it explains why my blindly- applied work-around is effective. (And kudos to Simon Kelley who is working to make it possible for everything to work as configured right out of the box.) But I don't understand what you said about standalone dnsmasq conflicting with network-manager's instance of dnsmasq when /etc/dnsmasq.d/network-manager is removed. Apart from not understanding how the conflict arises, I wonder: Should this conflict be manifesting itself somehow? Everything seems to be working right now. And would disabling network-manager's DNS-handling instance of dnsmasq then result in the need to set up an alternative DNS handler? I'm willing to apply another solution blindly, as I did in removing /etc/dnsmasq.d/network-manager, but it would be nice to understand more about it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+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-r-maas-next-steps] MAAS next steps
Blueprint changed by Andres Rodriguez: Work items changed: Work items: [andreserl] SRU django 1.4 GenericIpAddressField to 1.3 for 12.04 (LP: #1081391): INPROGRESS [andreserl] SRU django 1.4 prefetch_related to 1.3 for 12.04 (LP: #1081388): INPROGRESS [andreserl] SRU django 1.4 upstream bug bug 15496 to 12.04 (LP: #1081392): INPROGRESS [andreserl] SRU 12.10-stabilization to Quantal: TODO [andreserl] SRU 12.10-stabilization to Precise: TODO [andreserl] SRU python-tx-tftp (0.1~bzr31-0ubuntu7) to Quantal (LP: #1068843): INPROGRESS [andreserl] SRU python-tx-tftp to Precise: TODO - [andreserl] SRU yui3 to Precise: TODO + [andreserl] SRU yui3 to Precise (LP: #1084141): INPROGRESS [andreserl] SRU libjs-raphael to Precise: TODO [andreserl] SRU isc-dhcp apparmor fixes from quantal to precise (LP: #1049177): INPROGRESS [andreserl] SRU Raring features to Quantal: TODO [andreserl] SRU Raring features to Precise: TODO [andreserl] Bug #1073462 fence_cdu power type is missing: TODO [andreserl] Bug #1064224 IPMI detection ends up with power_address of 0.0.0.0: DONE [andreserl] Bug #1064527 detect_ipmi needs improvement. detects non-existant device in nested kvm: TODO [andreserl] maas-ipmi-autodetect and maas-signal should be shipped with MAAS: TODO [maas-maintainers] Bug #975454complete documentation and man pages: TODO [maas-maintainers] Bug #1044503 kernel command line is not easily customizable: DONE [maas-maintainers] Bug #1066775 Main page slow to load with many nodes: DONE [maas-maintainers] Bug #1068843 maas-cluster-controller doesn't have images for provisioning: DONE [maas-maintainers] Bug #1069734 Filestorage is unique to each appserver instance: DONE [maas-maintainers] Bug #1069850 import_pxe_files does not include quantal: DONE [maas-maintainers] Bug #1070522 maas-cli nodes new incomplete documentation: DONE [maas-maintainers] Bug #1070765 DNS forward zone ends up with nonsensical entries: DONE [maas-maintainers] Bug #1070774 The hostname of a node can still be changed once the node is in use: DONE [maas-maintainers] Bug #1070775 The zone name (attached to a cluster controller) can still be changed when it contains in-use nodes and DNS is managed.: DONE [maas-maintainers] Bug #1075597 Duplicated prefix in the url used by the CLI: DONE [maas-maintainers] Bug #1034318 API calls that return a node leak private data: DONE [maas-maintainers] Bug #1059645 URI in API description wrong when accessing machine via alternative interface: DONE [maas-maintainers] Bug #1069603 Error in log when using 'Start node' button: MAASAPINotFound: No user data available for this node.: DONE [maas-maintainers] define supported release combination matrix: TODO -- MAAS next steps https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas-next-steps -- 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 1084141] [NEW] [SRU] yui3 to precise
Public bug reported: [Impact] As part of the MAAS Next Steps bluepring [1], YUI3 is a required dependency for MAAS. In Precise, the 'yui3' libraries are being shipped with 'maas' source. This was done because such libraries weren't in the archives. How that they are, it is imperative for us to be able to separate these from the 'maas' source and SRU these to Precise. [Test Case] 1. Install maas (ppa:maas-maintainers/experimental) 2. Make sure it pulls yui3 libraries 3. Run MAAS 4. Check that no WebUI issues appear. [Regression potential] Minimal. The libraries don't pull any build-deps other than debhelper and have no Depends (other than between the yui3 libraries). This has been tested in quantal as well as precise extensively. ** Affects: yui3 (Ubuntu) Importance: High Status: New ** Changed in: yui3 (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to yui3 in Ubuntu. https://bugs.launchpad.net/bugs/1084141 Title: [SRU] yui3 to precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yui3/+bug/1084141/+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-r-maas-next-steps] MAAS next steps
Blueprint changed by Andres Rodriguez: Work items changed: Work items: [andreserl] SRU django 1.4 GenericIpAddressField to 1.3 for 12.04 (LP: #1081391): INPROGRESS [andreserl] SRU django 1.4 prefetch_related to 1.3 for 12.04 (LP: #1081388): INPROGRESS [andreserl] SRU django 1.4 upstream bug bug 15496 to 12.04 (LP: #1081392): INPROGRESS [andreserl] SRU 12.10-stabilization to Quantal: TODO [andreserl] SRU 12.10-stabilization to Precise: TODO [andreserl] SRU python-tx-tftp (0.1~bzr31-0ubuntu7) to Quantal (LP: #1068843): INPROGRESS [andreserl] SRU python-tx-tftp to Precise: TODO [andreserl] SRU yui3 to Precise (LP: #1084141): INPROGRESS - [andreserl] SRU libjs-raphael to Precise: TODO + [andreserl] SRU libjs-raphael to Precise (LP: #1084146): INPROGRESS [andreserl] SRU isc-dhcp apparmor fixes from quantal to precise (LP: #1049177): INPROGRESS [andreserl] SRU Raring features to Quantal: TODO [andreserl] SRU Raring features to Precise: TODO [andreserl] Bug #1073462 fence_cdu power type is missing: TODO [andreserl] Bug #1064224 IPMI detection ends up with power_address of 0.0.0.0: DONE [andreserl] Bug #1064527 detect_ipmi needs improvement. detects non-existant device in nested kvm: TODO [andreserl] maas-ipmi-autodetect and maas-signal should be shipped with MAAS: TODO [maas-maintainers] Bug #975454complete documentation and man pages: TODO [maas-maintainers] Bug #1044503 kernel command line is not easily customizable: DONE [maas-maintainers] Bug #1066775 Main page slow to load with many nodes: DONE [maas-maintainers] Bug #1068843 maas-cluster-controller doesn't have images for provisioning: DONE [maas-maintainers] Bug #1069734 Filestorage is unique to each appserver instance: DONE [maas-maintainers] Bug #1069850 import_pxe_files does not include quantal: DONE [maas-maintainers] Bug #1070522 maas-cli nodes new incomplete documentation: DONE [maas-maintainers] Bug #1070765 DNS forward zone ends up with nonsensical entries: DONE [maas-maintainers] Bug #1070774 The hostname of a node can still be changed once the node is in use: DONE [maas-maintainers] Bug #1070775 The zone name (attached to a cluster controller) can still be changed when it contains in-use nodes and DNS is managed.: DONE [maas-maintainers] Bug #1075597 Duplicated prefix in the url used by the CLI: DONE [maas-maintainers] Bug #1034318 API calls that return a node leak private data: DONE [maas-maintainers] Bug #1059645 URI in API description wrong when accessing machine via alternative interface: DONE [maas-maintainers] Bug #1069603 Error in log when using 'Start node' button: MAASAPINotFound: No user data available for this node.: DONE [maas-maintainers] define supported release combination matrix: TODO -- MAAS next steps https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas-next-steps -- 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 1084141] Re: [SRU] yui3 to precise
** Description changed: [Impact] As part of the MAAS Next Steps bluepring [1], YUI3 is a required dependency for MAAS. In Precise, the 'yui3' libraries are being shipped with 'maas' source. This was done because such libraries weren't in the archives. How that they are, it is imperative for us to be able to separate these from the 'maas' source and SRU these to Precise. [Test Case] 1. Install maas (ppa:maas-maintainers/experimental) 2. Make sure it pulls yui3 libraries - 3. Run MAAS + 3. Run MAAS 4. Check that no WebUI issues appear. [Regression potential] Minimal. The libraries don't pull any build-deps other than debhelper and have no Depends (other than between the yui3 libraries). This has been tested in quantal as well as precise extensively. + + [1]: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas- + next-steps ** Also affects: yui3 (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: yui3 (Ubuntu) Status: New = Fix Released ** Changed in: yui3 (Ubuntu Precise) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to yui3 in Ubuntu. https://bugs.launchpad.net/bugs/1084141 Title: [SRU] yui3 to precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yui3/+bug/1084141/+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 1084146] [NEW] [SRU] raphael new upstream release (2.1.0)
Public bug reported: [Impact] As part of the MAAS Next Steps bluepring [1], raphael 2.1.0 is a required dependency for MAAS. In Precise, the 'raphael' library is being shipped with 'maas' source. This was done because the library version required wasn't in the archives. However, now that it is, it is imperative for us to be able to separate these from the 'maas' source and SRU it to Precise. [Test Case] 1. Install maas (ppa:maas-maintainers/experimental) 2. Make sure it pulls raphael library 3. Run MAAS 4. Check that no WebUI issues appear. [Regression potential] Minimal. The library only has one build-depends other than debhelper and have no Depends. This package has been tested in Precise and was built against its build-depends in precise. [1]: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas- next-steps ** Affects: raphael (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: raphael (Ubuntu Precise) Importance: High Status: New ** Description changed: [Impact] As part of the MAAS Next Steps bluepring [1], raphael 2.1.0 is a required dependency for MAAS. In Precise, the 'raphael' library is being shipped with 'maas' source. This was done because the library version required wasn't in the archives. However, now that it is, it is imperative for us to be able to separate these from the 'maas' source and SRU it to Precise. [Test Case] 1. Install maas (ppa:maas-maintainers/experimental) 2. Make sure it pulls raphael library 3. Run MAAS 4. Check that no WebUI issues appear. [Regression potential] - Minimal. The library only has one build-depends other than debhelper and have no Depends. This package has been tested in Precise and being built against its build-depends in precise. + Minimal. The library only has one build-depends other than debhelper and have no Depends. This package has been tested in Precise and was built against its build-depends in precise. [1]: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas- next-steps ** Also affects: raphael (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: raphael (Ubuntu) Status: New = Fix Released ** Changed in: raphael (Ubuntu Precise) Importance: Undecided = High ** Summary changed: - [SRU] raphael 2.1.0 to precise + [SRU] raphael new upstream release (2.1.0) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to raphael in Ubuntu. https://bugs.launchpad.net/bugs/1084146 Title: [SRU] raphael new upstream release (2.1.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raphael/+bug/1084146/+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 1084089] Re: lxc-clone shouldn't add fstab line if it wasn't there originally
** Tags added: needssru -- 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/1084089 Title: lxc-clone shouldn't add fstab line if it wasn't there originally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1084089/+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 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
the LTSP server defers to the router handling DHCP. OK, I get it. I don't understand what you said about standalone dnsmasq conflicting with network-manager's instance of dnsmasq when /etc/dnsmasq.d/network-manager is removed. When /etc/dnsmasq.d/network-manager is present, standalone dnsmasq starts in bind-interfaces mode and only listens on the addresses assigned to configured network interfaces. This does not include 127.0.1.1, since 127.0.1.1 is not the address of any configured interface. So in this mode standalone dnsmasq does not conflict with NM- dnsmasq which listens on 127.0.1.1. (At most one process can listen on any given address:port combination.) Remove that file and standalone dnsmasq starts in a mode where it tries to listen at all addresses. But it can't do this if NM-dnsmasq is already listening at some address. Should this conflict be manifesting itself somehow? Everything seems to be working right now. Well, I am not sure which workaround, if any, you are currently relying on. If you commented out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf then there is no conflict because NM doesn't start the NM-dnsmasq process. And would disabling network-manager's DNS-handling instance of dnsmasq then result in the need to set up an alternative DNS handler? No. If NM-dnsmasq is enabled then resolv.conf contains nameserver 127.0.1.1 so that applications using the resolver library access NM- dnsmasq; NM-dnsmasq forwards queries to the upstream nameserver at the address A.A.A.A which was obtained via DHCP or otherwise. If NM-dnsmasq is disabled then resolv.conf simply contains nameserver A.A.A.A. I'm willing to apply another solution blindly, as I did in removing /etc/dnsmasq.d/network-manager, but it would be nice to understand more about it. If you are running Ubuntu 12.04 then the best solution for now is to * comment out the bind-interfaces line in /etc/dnsmasq.d/network-manager; * comment out the dns=dnsmasq line in /etc/NetworkManager/NetworkManager.conf. If you are running Ubuntu 12.10 and have dnsmasq version 2.63-1ubuntu1 then you can, instead, * replace the bind-interfaces line in /etc/dnsmasq.d/network-manager with a bind-dynamic line. The bind-dynamic mode is the new mode that I referred to above and which Simon referred to earlier in comment #94. Please test it! If it works well then it should become the default, as mentioned above in comments ##99, 102. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+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 1070617] Re: package postfix 2.9.3-2ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 75
Thanks for reporting this bug. As the error message indicated, your hostname is purely numeric and not valid. Please change your hostname to something not completely numeric, like 'u10'. Newaliases should then succeed. Please respond if you need more help to get past this. ** Changed in: postfix (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1070617 Title: package postfix 2.9.3-2ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1070617/+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 1070093] Re: package slapd (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
** Changed in: openldap (Ubuntu) Importance: Undecided = Medium -- 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/1070093 Title: package slapd (not installed) failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1070093/+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 1072313] Re: package clamav-milter 0.97.3+dfsg-2.1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: clamav (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1072313 Title: package clamav-milter 0.97.3+dfsg-2.1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1072313/+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 1070093] Re: package slapd (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Thanks for submitting this bug report. I can't reproduce it locally. Could you please do sudo grep slapd /var/log/syslog syslog.slapd.out and attach syslog.slapd.out here? ** Changed in: openldap (Ubuntu) Status: New = Incomplete -- 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/1070093 Title: package slapd (not installed) failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1070093/+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 905872] Re: Cannot connect to EC2 instance after bootstrap
olutayo - could you please file a new bug for your issue using 'ubuntu- bug juju' ? This appears to be a different issue. Please make sure to append a (sanitized) copy of your environments.yaml. ** Changed in: juju (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/905872 Title: Cannot connect to EC2 instance after bootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/905872/+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 1073082] Re: Login always warns about fsck, but doesn't actually fsck on reboot
** Changed in: cloud-init (Ubuntu) Importance: Undecided = Medium -- 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/1073082 Title: Login always warns about fsck, but doesn't actually fsck on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1073082/+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 1084028] Re: openvswitch based interfaces not started in time during boot
I'm not confident enough to mark it Confirmed, but I believe that's right - an upstart job is needed. ** Changed in: openvswitch (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+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 1084028] Re: openvswitch based interfaces not started in time during boot
** Changed in: openvswitch (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+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 1084178] [NEW] auto.net does not handle mutliple mount points from a remote
Public bug reported: When using auto.net and mounting multiple remote exports, only one mount works and autofs steps onto the other mounts. The problem appears in /proc/mounts (see details in walk-thru below) HOSTA * NFS Host (i.e. hosta): $ uname -a Linux hosta 2.6.18-274.3.1.el5 #1 SMP Fri Aug 26 18:49:02 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/exports /opt/logisoft hostb(rw,insecure,sync,nohide,fsid=0,no_root_squash) /home hostb(rw,insecure,sync,nohide,fsid=0,no_root_squash) HOSTB * AutoFS Host (i.e. hostb): $ uname -a Linux hostb 3.2.0-33-generic #52-Ubuntu SMP Thu Oct 18 16:29:15 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux $ df hosta:/opt/logisoft816146560 179367200 594652800 24% /net/hosta/opt/logisoft hosta:/home816146560 179367200 594652800 24% /net/hosta/home $ cd /net/hosta/home $ ls -l drwxrwxrwx 43 91 91 12288 Nov 20 13:03 eci drwxrwxrwx 43 91 91 4096 May 28 2012 oti drwxrwxrwx 5 91 91 4096 Jul 20 2011 shared $ cd /net/hosta/opt/logisoft $ ls -1 drwxrwxrwx 43 91 91 12288 Nov 20 13:03 eci drwxrwxrwx 43 91 91 4096 May 28 2012 oti drwxrwxrwx 5 91 91 4096 Jul 20 2011 shared *** (Note that the listing is the same! This is not correct!) *** *** PROBLEM VISIBLE HERE $ cat /proc/mounts hosta:/home/ /net/hosta/opt/logisoft nfs rw,nosuid,nodev,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.27.101.66,mountvers=3,mountport=960,mountproto=udp,local_lock=none,addr=172.27.101.66 0 0 hosta:/home/ /net/hosta/home nfs rw,nosuid,nodev,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.27.101.66,mountvers=3,mountport=960,mountproto=udp,local_lock=none,addr=172.27.101.66 0 0 $ umount /net/hosta/home $ df hosta:/opt/logisoft816146560 179367200 594652800 24% /net/hosta/opt/logisoft $ umount /net/hosta/opt/logisoft /net/hosta/opt/logisoft was not found in /proc/mounts /net/hosta/opt/logisoft was not found in /proc/mounts *** PROBLEM VISIBLE HERE $ cat /proc/mounts hosta:/home/ /net/hosta/opt/logisoft nfs rw,nosuid,nodev,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.27.101.66,mountvers=3,mountport=960,mountproto=udp,local_lock=none,addr=172.27.101.66 0 0 ** Affects: autofs (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1084178 Title: auto.net does not handle mutliple mount points from a remote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1084178/+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 1084089] Re: lxc-clone shouldn't add fstab line if it wasn't there originally
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu46 --- lxc (0.8.0~rc1-4ubuntu46) raring; urgency=low * 0229-lxc-clone-mount-fix: fix wrong handling of lxc.mount entries in lxc-clone. (LP: #1084089) * debian/apparmor/abstractions-lxc-container-base: deny read/write under /sys/firmware/efi/efivars. -- Serge Hallyn serge.hal...@ubuntu.com Wed, 28 Nov 2012 11:04:17 -0600 ** Changed in: lxc (Ubuntu Raring) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1084089 Title: lxc-clone shouldn't add fstab line if it wasn't there originally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1084089/+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 1073287] Re: tgt-admin fails to read configuration
Could you please show the exact configuration files when working and not working? In which file did the *.conf not work? Certainly the inclusion of /etc/tgt/conf.d/*.conf from /etc/tgt/targets.conf seems to be working (just tested under quantal). ** Changed in: tgt (Ubuntu) Importance: Undecided = Medium ** Changed in: tgt (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1073287 Title: tgt-admin fails to read configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1073287/+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 1074551] Re: package racoon 1:0.8.0-9ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Thanks for reporting this bug. It looks like racoon is failing to stop. Could you please do: sudo service racoon stop sudo service racoon start and show the results here? ** Changed in: ipsec-tools (Ubuntu) Importance: Undecided = Medium ** Changed in: ipsec-tools (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipsec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1074551 Title: package racoon 1:0.8.0-9ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/1074551/+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 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
Thanks for the explanation of how removal of /etc/dnsmasq.d/network- manager sets up a conflict between standalone dnsmasq and NM-dnsmasq. (But also see my surprising observation below.) Should this conflict be manifesting itself somehow? Everything seems to be working right now. Well, I am not sure which workaround, if any, you are currently relying on. If you commented out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf then there is no conflict because NM doesn't start the NM-dnsmasq process. My workaround was simply to remove /etc/dnsmasq.d/network-manager. Everything seemed to work after that. I did not comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf, which apparently should have subjected the system to the conflict described above. But as I say, I saw no problems. Could this be due to some compensation made by the new dnsmasq, since I am in fact running v.2.63? Thanks also for the explanation of how disabling NM-dnsmasq does not break DNS. Since I have dnsmasq v2.63, I tried the experimental solution: I restored /etc/dnsmasq.d/network-manager and replaced the bind- interfaces line with a bind-dynamic line. As far as I can tell, everything works. Thank you! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+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 1077594] Re: package postfix 2.7.0-1ubuntu0.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 75
Thanks for reporting this bug. Could you please tell us exactly what steps or commands you were using, and wat you saw for output? Was postfix already installed? Could you post any results from 'grep postfix /var/log/syslog /var/log/apt/* /var/log/messages /var/log/daemon.log ? ** Changed in: postfix (Ubuntu) Importance: Undecided = Medium ** Changed in: postfix (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1077594 Title: package postfix 2.7.0-1ubuntu0.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1077594/+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 1074713] Re: package vsftpd 2.3.5-1ubuntu2 failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 1
Thanks for reporting this bug. I cannot reproduce this using your modified vsftpd.conf. Do you get more meaningful error messages if you simply do sudo apt-get install --reinstall vsftpd ? ** Changed in: vsftpd (Ubuntu) Importance: Undecided = Medium ** Changed in: vsftpd (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1074713 Title: package vsftpd 2.3.5-1ubuntu2 failed to install/upgrade: le sous- processus script post-removal installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1074713/+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 1080681] Re: debian guests get different IPv4 at every reboot
** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- 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/1080681 Title: debian guests get different IPv4 at every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1080681/+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 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
Question: Why did everything work on your machine when standalone dnsmasq wasn't in bind-interfaces mode but /etc/NM/NM.conf contained dns=dnsmasq? Hypothesis: Standalone dnsmasq started first; network-manager second. NM tried to start NM-dnsmasq but this failed because of the address conflict and NM fell back to non-dnsmasq mode, which works fine. If this hypothesis is correct then there may be lines in the syslog that look like this: [date] [hostname] NetworkManager[pid]: info DNS: starting dnsmasq... [date] [hostname] dnsmasq[pid]: failed to create listening socket for 127.0.1.1: Address already in use -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+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 1075717] Re: mounted-dev must not re-create consoles in a container
As per discussion on #ubuntu-devel, lxc should run MAKEDEV in the container before setting up its devices. To do this, teh setup_autodev() function must be split up. We'll first mount all lxc filesystems (including a fresh /dev), then run MAKEDEV console in the container, then do the rest of setup_autodev() if lxc.autodev = 1. ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Importance: Undecided = High ** Changed in: lxc (Ubuntu) Status: New = Triaged ** Changed in: lxc (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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1075717 Title: mounted-dev must not re-create consoles in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+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 1075717] Re: mounted-dev must not re-create consoles in a container
... except that we can't actually call running-in-container reliably this early in the boot process; /run is not guaranteed to be mounted (or seen to be mounted) before /dev. -- 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/1075717 Title: mounted-dev must not re-create consoles in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+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 1075717] Re: mounted-dev must not re-create consoles in a container
Have talked through this with hallyn in detail. - we don't want to change MAKEDEV itself to not clobber existing device nodes, because in other cases this makes recovery from broken /dev less reliable - we can't side-step this by making /dev not be a mountpoint within the container because in some cases users want to use a read-only rootfs - we can't use devtmpfs instead because there is only *one* devtmpfs in the kernel no matter where it's mounted, so this would make it impossible to make the exact change to node targets that this is about. So I'm convinced that the linked branch is an appropriate solution to this problem. It has no impact on the common case when /dev is a devtmpfs, we don't call MAKEDEV at all in that scenario. -- 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/1075717 Title: mounted-dev must not re-create consoles in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+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 1084261] [NEW] 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project'
Public bug reported: When attempting to change a quota for one of my customers, with the command below, I receive an error message instead of the command succeeding. What I see: $ sudo nova-manage project quota --project= --key=instances --value=15 nova-manage: error: no such option: --project What I expect to see: $ sudo nova-manage project quota --project= --key=instances --value=15 metadata_items: 128 injected_file_content_bytes: 10240 volumes: 5 gigabytes: 1000 ram: 51200 floating_ips: 3 security_group_rules: 20 instances: 15 key_pairs: 100 injected_files: 5 cores: 20 injected_file_path_bytes: 255 security_groups: 50 Debugging: Looking at the `nova-manage` command I notice that the @arg decorators are missing from the `quota` function. Replacing the decorators fixes the problem (see attached patch). I have looked at the current source from Github and the most recent packages from the cloud-archive and these decorators are missing from there are well. System Information: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION=Ubuntu 12.04.1 LTS $ dpkg -S $(which nova-manage) nova-common: /usr/bin/nova-manage $ dpkg-query --show nova-common nova-common 2012.2-0ubuntu3~cloud0 Please let me know if you need any further information? ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack ** Patch added: nova-manage.patch https://bugs.launchpad.net/bugs/1084261/+attachment/3446275/+files/nova-manage.patch -- 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/1084261 Title: 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1084261/+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 1084261] Re: 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project'
** Also affects: nova Importance: Undecided Status: New -- 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/1084261 Title: 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1084261/+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 1080681] Re: debian guests get different IPv4 at every reboot
I think that I found a workaround that solves part of the problem, editing the config file and adding the following line: lxc.network.hwaddr = aa:aa:aa:aa:aa:aa In that way the ipv4 address is kept through reboots. However it is still not the same one stated under lxc.network.ipv4. -- 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/1080681 Title: debian guests get different IPv4 at every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1080681/+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 1075717] Re: mounted-dev must not re-create consoles in a container
** Branch linked: lp:ubuntu/mountall -- 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/1075717 Title: mounted-dev must not re-create consoles in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+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 1075717] Re: mounted-dev must not re-create consoles in a container
A lxc tree which is working for me to do MAKEDEV console in the container is at lp:~serge-hallyn/ubuntu/raring/lxc/lxc-makedev. -- 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/1075717 Title: mounted-dev must not re-create consoles in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+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 1080681] Re: debian guests get different IPv4 at every reboot
@Enrique, near as i can tell this turns out to be not an lxc issue (unless we want the template to be more invasive than it already is). In Ubuntu it looks like ifup simply is smart enough to not follow through with dhcp if the nic is already up with an address. In debian, not. If you want the debian containers to not run dhcp, then you need to edit /etc/network/interfaces to tell ifupdown not to run dhcp on the devices. As I say the lxc debian template could look for a lxc.network.ipv4 entry in the provided lxc.conf and, if present, edit the container's /etc/network/interfaces to make that happen. But it's interesting that the ubuntu template doesn't do that. -- 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/1080681 Title: debian guests get different IPv4 at every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1080681/+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 117736] Re: pam_mount unable to unmount needs root priv
This seems to still be a problem in 12.04. On log out I get pam_mount(spawn.c:128): error setting uid to 0 pam_mount(mount.c:69): umount messages: pam_mount(mount.c:73): umount: /home/me/share is not in the fstab (and you are not root) pam_mount(mount.c:752): unmount of share failed This seems to be a big problem if you log out, lose network connection, and log in using pam-mount. The computer locks up and the user is unable to log in without a reboot. It's easily reproducible. With pam mount log in. Then log out. Verify mounts are still up. Bring down networking. Log in (using su is fine). The terminal hangs. You never log in. -- 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/117736 Title: pam_mount unable to unmount needs root priv To manage notifications about this bug go to: https://bugs.launchpad.net/pam/+bug/117736/+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 1084261] Re: 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project'
The attachment nova-manage.patch of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report. [This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.] ** Tags added: patch -- 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/1084261 Title: 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1084261/+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 1081212] Re: The address of the API in pserv.conf (tftp/generator) is http://localhost/MAAS/api/1.0/pxeconfig/
** Branch linked: lp:~julian-edwards/maas/backport-153-packaging.quantal -- 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/1081212 Title: The address of the API in pserv.conf (tftp/generator) is http://localhost/MAAS/api/1.0/pxeconfig/ To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1081212/+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 1075717] Re: mounted-dev must not re-create consoles in a container
** Changed in: mountall (Ubuntu) Status: Triaged = Fix Committed -- 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/1075717 Title: mounted-dev must not re-create consoles in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+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
