[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
Przygotowanie do zastąpienia grub-legacy-ec2 0.6.3-0ubuntu1.4 (wykorzystując .../grub-legacy-ec2_0.6.3-0ubuntu1.5~ppa0_all.deb) ... Leaving 'diversion of /usr/sbin/grub-set-default to /usr/sbin/grub-set-default.real by grub-legacy-ec2' Rozpakowanie pakietu zastępującego grub-legacy-ec2 ... Przetwarzanie wyzwalaczy dla man-db... Konfigurowanie isc-dhcp-common (4.1.ESV-R4-0ubuntu5.6) ... Konfigurowanie isc-dhcp-client (4.1.ESV-R4-0ubuntu5.6) ... Konfigurowanie dhcp3-client (4.1.ESV-R4-0ubuntu5.6) ... Konfigurowanie dhcp3-common (4.1.ESV-R4-0ubuntu5.6) ... Konfigurowanie grub-legacy-ec2 (0.6.3-0ubuntu1.5~ppa0) ... Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-3.5.0-22-generic Found kernel: /boot/vmlinuz-3.5.0-21-generic Found kernel: /boot/vmlinuz-3.2.0-36-virtual Found kernel: /boot/vmlinuz-3.2.0-35-virtual Found kernel: /boot/vmlinuz-3.2.0-23-virtual Replacing config file /run/grub/menu.lst with new version Updating /boot/grub/menu.lst ... done so it works fine for me -- 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/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1104137] Re: FTBFS on raring in schroot
** Changed in: nova (Ubuntu) Status: New = Confirmed ** Changed in: nova (Ubuntu) Importance: Undecided = Critical -- 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/1104137 Title: FTBFS on raring in schroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1104137/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103202] Re: grizzly scheduler can not start with import error
Thanks for reporting this Can you provide the Ubuntu version where that error is happening? Also, can you use the command: apt-get install -f And check the results of this? ** Changed in: nova (Ubuntu) Status: New = Incomplete -- 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/1103202 Title: grizzly scheduler can not start with import error To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1103202/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1015104] Re: package winbind 2:3.6.3-2ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 608477 *** https://bugs.launchpad.net/bugs/608477 ** This bug has been marked a duplicate of bug 608477 package winbind 2:3.4.7~dfsg-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- 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/1015104 Title: package winbind 2:3.6.3-2ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1015104/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1102422] Re: setserial deliver errors on installation about do not match LSB Default-Stop values (0 1 6)
** Changed in: setserial (Ubuntu) Status: New = Confirmed ** Changed in: setserial (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to setserial in Ubuntu. https://bugs.launchpad.net/bugs/1102422 Title: setserial deliver errors on installation about do not match LSB Default-Stop values (0 1 6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/setserial/+bug/1102422/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100364] Re: Cron graph generating fails
** Changed in: munin (Ubuntu) Status: New = Confirmed ** Changed in: munin (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/1100364 Title: Cron graph generating fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1100364/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
** Changed in: cloud-init (Ubuntu) Status: New = Confirmed ** 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/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103195] Re: MAAS WebUI crashes when installing maas-region-controller only
To ensure that we accept as master only the cluster controller on the local machine, can the region compare the UUID it's given against the UUID it can see on the filesystem? A simpler way (which we already use to know if we need to update nodegroup.maas_url or not when a cluster connects) is to see if the cluster connects from 'localhost' or a remote host. (Note that this conversation should happen on bug 1104215) -- 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/1103195 Title: MAAS WebUI crashes when installing maas-region-controller only To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1103195/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096081] Re: server reboots because of php5 cron job
The cron job you posted should not be able to cause a system reboot. As this hasn't been confirmed by any other user, and there is surely a huge number of other users running that same cron job, I think it is more likely than not that this is either a hardware fault or some local corruption or misconfiguration, rather than a bug. Please can you try your setup on a different machine to see if you can reproduce the issue. If you can, please reduce the setup to the minimum steps to configure the machine that still causes the problem, and then post those exact steps here so that a developer can try the same thing. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html to see where I'm coming from. Marking Incomplete, pending steps to reproduce. Once you have posted steps to reproduce, please change the bug status back to New. ** Changed in: php5 (Ubuntu) Status: New = Incomplete -- 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/1096081 Title: server reboots because of php5 cron job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1096081/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1104915] [NEW] Wrong expire date in nova-dhcpbridge init output
Public bug reported: TL; DR; nova-dhcpbridge init generated leases file with instance updated_at instead of fixed_ips updated_at, causing every leases to be expired for several month. So everytime dnsmasq is restarted will sent DHCPNAK the first time a client ask for renew its lease. Long version: dnsmasq expected the leases format to have: * one line per lease * first column is the expire date in second since epoc. * we don’t care about other column for this issue :) This is the case for dnsmasq 2.59 and 2.65 (precise version and raring version). But the output of nova-dhcpbridge init (which is called by dnsmasq to load the leases): 1352420950 xx:xx:3e:01:7d:xx 10.0.0.3 app01.domain * 1352421657 xx:xx:3e:7e:0a:xx 10.0.0.4 app02.domain * [...] So the expire date for those entry are: 9 November 2012 around 1am. The script was run the 25 January 2013 at 9am (UTC). With our lease time of 1 day, we expected an expire date at 25 January 2013 at 10am. So when loaded dnsmasq read all leases and found all leases expired and then discard all leases. This cause dnsmasq to reply DHCPNAK for DHCPREQUEST (since for dnsmasq the lease requested didn’t exist because it’s expired). Hopefully, when client come with a DHCPDISCOVER, dnsmasq will get information form configuration file (/var/lib/nova/networks /nova-brxxx.conf) and create a lease with correct expire time. But this lease is only tracker in memory, so next DHCPREQUEST will work until next restart of dnsmasq. At the end everytime dnsmasq is restarted, when client try to renew a lease it will get a DHCPNAK and it’s interface goes down (loss all IP). Even if the DHCPDISCOVER send right after will re-add the IP, this can trouble some services (in our case, pacemaker which manage a virtual IP). Digging a bit on how nova-dhcpbridge generated the leases file, it seems to come from: * _host_lease function in nova/network/linux_net.py: if data['instance_updated']: timestamp = data['instance_updated'] else: timestamp = data['instance_created'] seconds_since_epoch = calendar.timegm(timestamp.utctimetuple()) return '%d %s %s %s *' % (seconds_since_epoch + FLAGS.dhcp_lease_time, data['vif_address'], data['address'], data['instance_hostname'] or '*') data[‘instance_updated’] is took from table instances, and it match the date seen in output of nova-dhcpbridge init. It’s also the date of creation of our machine (more or less few minutes... probably the end of first boot). From my understanding of how nova-dhcpbridge works, every time dnsmasq reply to a client with a new lease, it call the nova-dhcpbridge script which update the database (table fixed_ips, column updated_at). So I think instead of “instance_updated”, we sould use “fixed_ips.updated_at” when generating the leases. Version of software (Ubuntu version): * Ubuntu 12.04 (precise) amd64 * nova-* 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1 * dnsmasq 2.65-1~precise1 The way leases file are generated by nova-dhcpbridge (_host_lease function in nova/network/linux_net.py) is present in nova git repository at both tag 2012.1.3 (b00f759) and master (97a5274 - dated of Thu Jan 24). ** Affects: nova Importance: Undecided Status: New ** Affects: nova (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: nova (Ubuntu) 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/1104915 Title: Wrong expire date in nova-dhcpbridge init output To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1104915/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1104915] Re: Wrong expire date in nova-dhcpbridge init output
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nova (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1104915 Title: Wrong expire date in nova-dhcpbridge init output To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1104915/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1104915] Re: Wrong expire date in nova-dhcpbridge init output
I see two way for fixing the issue. The first one don't change the db/api, but it's the a very nice fix. The second one seems to be the correct way to fix this issue. patch1.diff : always use time.time() + lease_time to set expiry in nova/network/linux_net.py patch2.diff : add updated (models.FixedIp.updated_at) in data returned by db.api.network_get_associated_fixed_ips, and use this time when generating the leases. ** Patch added: always use time.time() + lease_time to set expiry in nova/network/linux_net.py https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1104915/+attachment/3499726/+files/patch1.diff -- 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/1104915 Title: Wrong expire date in nova-dhcpbridge init output To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1104915/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1104915] Re: Wrong expire date in nova-dhcpbridge init output
** Patch added: add updated (models.FixedIp.updated_at) in data returned by db.api.network_get_associated_fixed_ips, and use this time when generating the leases. https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1104915/+attachment/3499727/+files/patch2.diff -- 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/1104915 Title: Wrong expire date in nova-dhcpbridge init output To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1104915/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097776] Re: genshi 0.6-2ubuntu1 FTBFS on amd64 in raring
Bug 1097783 is now fixed in raring, so just this issue remains. I've updated upstream and am waiting to hear back from them. Unless they have a better suggestion or an objection, hardcoding the old definition of PseudoToken in a patch makes sense to me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to genshi in Ubuntu. https://bugs.launchpad.net/bugs/1097776 Title: genshi 0.6-2ubuntu1 FTBFS on amd64 in raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/genshi/+bug/1097776/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097312] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1097312 Title: container startup must not fail if setup_kmsg fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1097312/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097312] Re: container startup must not fail if setup_kmsg fails
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu39.12.10.1 --- lxc (0.8.0~rc1-4ubuntu39.12.10.1) quantal-proposed; urgency=low * 0228-ignore-kmsg-setup-failure: ignore failure to set up kmsg, since that is not critical. (LP: #1097312) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 08 Jan 2013 10:25:43 -0600 ** Changed in: lxc (Ubuntu Quantal) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1097312 Title: container startup must not fail if setup_kmsg fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1097312/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: cgroup-bin (deleted) init scripts stick around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: cgroup-bin (deleted) init scripts stick around
This bug was fixed in the package libcgroup - 0.38-1ubuntu1.12.10.1 --- libcgroup (0.38-1ubuntu1.12.10.1) quantal-proposed; urgency=low * Properly remove the old init scripts. (LP: #1096771) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 08 Jan 2013 08:40:52 -0600 ** Changed in: libcgroup (Ubuntu Quantal) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: cgroup-bin (deleted) init scripts stick around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100787] Re: Samba 3.6.3 segfault or panic.
Had two crashes today so far and I've managed to pull some more info from the logs and reports. We use the squid Kerberos authentication plugin to authenticate the user and their password, then we use the wbinfo_group.pl script to check the users membership of an AD group. It appears that the checking for a group stage is where winbind crashes. Interestingly the Kerberos authentication stage carries on authenticating users properly even after the crash. Users that have had their authentication cached by squid can carry on accessing the internet as normal for a short time. Any new authentication attempts fail. The SID in each initial segfault report was the SID for the Domain Users group. The SIDs in the following segfaults are a mix of random groups and users, different after each crash. The last successful user to be looked up before each crash was also different. After the first segfault I had to force a server restart as it became totally unresponsive. The second time I managed to kill the Winbind service and restart it. No other faults so far but it does seem to be a quiet period at the moment, so the server isn't under a lot of load. -- 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/1100787 Title: Samba 3.6.3 segfault or panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1100787/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1104915] Re: Wrong expire date in nova-dhcpbridge init output
The attachment always use time.time() + lease_time to set expiry in nova/network/linux_net.py 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/1104915 Title: Wrong expire date in nova-dhcpbridge init output To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1104915/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1075456] Re: wrong path given in README
** Bug watch added: Debian Bug tracker #698941 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698941 ** Also affects: dovecot (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698941 Importance: Unknown Status: Unknown ** Tags removed: needs-upstream-report ** Changed in: dovecot (Ubuntu) Status: Triaged = In Progress ** Changed in: dovecot (Ubuntu) Assignee: (unassigned) = Alessandro Losavio (alo21) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1075456 Title: wrong path given in README To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1075456/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1085255] Re: Meta bug for tracking Openstack 2012.2.1 Stable Update
These updates have been in -proposed for nearly a month and have been tested in the CI lab under three different deployment topologies; please can the packages move to -updates now? -- 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/1085255 Title: Meta bug for tracking Openstack 2012.2.1 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1085255/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100787] Re: Samba 3.6.3 segfault or panic.
Thank you for taking the time to report this bug and helping to make Ubuntu better. From your stack trace, it looks likely to me that the crash is in libtdb rather than winbind itself, unless winbind is corrupting memory somehow. Can you check all tdb files for corruption using tdbtool (I presume this needs to be done when winbind and samba are shut down), and if you are able then run winbind under valgrind? It isn't clear to me whether this really is a bug or local corruption or a hardware fault or something like that. These steps might give us something really obvious to help decide. Please also report exact package numbers. The command apport-collect 1100787 will do this for you automatically. Please change the bug status back to New when you are done. Thanks! ** Changed in: samba (Ubuntu) Status: New = Incomplete -- 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/1100787 Title: Samba 3.6.3 segfault or panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1100787/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common
The source of this problem is in the debian packaging repository for 2.7.11-1. The /usr/lib/ruby/1.8/puppet/util/instrumentation/listeners/process_name.rb file is included in the debian/2.7.11-1 packaging when it shouldn't. The difference in the puppet source between the upstream and the packaging branches reverts back to expected when 2.7.12 is imported, so the problem is isolated to 2.7.11, which unfortunately is in an LTS release. It should be safe to remove this file from the 2.7.11 packaging for an eventual point release. All it does, if present, is to change the process name in the process table. I've tested operation on a precise puppet node before and after removing the file. I have observed the process hanging before removing the file. It runs normally after removing it, and I have not observed hangs for the last 20 runs. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/995719 Title: process_name.rb removed in 2.7.11 but still provided by puppet-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1104589] Re: python-websockify UNAVAILABLE
Sorry, wrong project, resubmitted at https://bugs.launchpad.net/openstack-ubuntu-testing/+bug/1105292 -- 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/1104589 Title: python-websockify UNAVAILABLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1104589/+subscriptions -- Ubuntu-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-lxc] LXC work for R
Blueprint changed by Stéphane Graber:
Work items changed:
Work items:
[serge-hallyn] Send user namespace delta to kernel-team ASAP: DONE
[serge-hallyn] Post syslog namespace design wiki page: DONE
[serge-hallyn] Send syslog namespace prototype to lkml: DONE
[serge-hallyn] Send syslog namespace description to kernel-team ASAP: DONE
[serge-hallyn] Add set_cgroup_item() and get_cgroup_item() to C API: DONE
[daniel-lezcano] Improved monitor notification support: TODO
[stgraber] Fix lxc-ls (re-write using api): DONE
[serge-hallyn] lxc-create or template option to specify userns mapping: TODO
[serge-hallyn] push user namespace lxc delta upstream: DONE
[serge-hallyn] add config options for loglevel and output file: DONE
[serge-hallyn] drop lxccontainer.log default logging in api: DONE
[serge-hallyn] lxc-create - set a default log file in
/var/log/lxc/$container: DONE
[serge-hallyn] lxc.autodev: push lxc patch upstream: DONE
[serge-hallyn] lxc.autodev: push lxc patch into package: DONE
[serge-hallyn] lxc.autodev: push mountall patch into package: DONE
[serge-hallyn] list broken functionality in ubuntu container in user
namespace: TODO
[serge-hallyn] improve ubuntu container experience in user namespace: TODO
[serge-hallyn] add config option for RLIMIT_NPROC in userns container: TODO
[stgraber] add (not container) to upstart jobs which just fail: DONE
[stgraber] write tool to pass devices into container: DONE
[stgraber] create a separate package for templates: DONE
[stgraber] have lxc-create record the name of template used in container
config file for debugging: DONE
[stgraber] support templates outside of $templatedir (pushed to git): DONE
[stgraber] investigate what's needed to support containers outside of
/var/lib/lxc (part of the scheduled API work): DONE
[serge-hallyn] test apparmor profile stacking; implement any lxc changes
needed to support it: BLOCKED
[stgraber] rebase staging branch on upstream master: DONE
[serge-hallyn] test attach support in userns kernel; shout if anything
missing: DONE
[daniel-lezcano] investigate/use http://lxc.sourceforge.net/download/procfs
to filter /proc/{cpuinfo,meminfo,etc}: TODO
[stgraber] investigate: does dnsmasq save mac-ip across host reboots? (it
does): DONE
[stgraber] Port arkose to python3 (and make it pep8 clean): DONE
[stgraber] Port arkose to python3-lxc: BLOCKED
[stgraber] Port auto-dist-upgrader to python3-lxc: DONE
- [stgraber] Tweak the tests to ensure auto-dist-upgrader on LXC gives the same
results as on kvm: INPROGRESS
+ [stgraber] Tweak the tests to ensure auto-dist-upgrader on LXC gives the same
results as on kvm: DONE
[stgraber] Check what it'd take to make lxc work fine when
creating/starting/stopping containers in parallel (improved locking of
templates): DONE
[stgraber] Add code to detect and install langpacks in containers (at least
-base-en): DONE
[stgraber] Get LXC into main: INPROGRESS
[ebiederm] Push current userns patchset upstream: DONE
[ebiederm] Add support for tmpfs mounts in userns: TODO
--
LXC work for R
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-lxc
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065589] Re: initctl list shows 11974 instances of network-interface-security after two days of uptime
Where does this stand? A fully updated 12.04.1 system is still seeing lots of interfaces; 2015 network-interface 4028 network-interface-security and toggling an lxc container up and down four times seemed to result in one extra network-interface and four extra network-interface-security's. -- 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/1065589 Title: initctl list shows 11974 instances of network-interface-security after two days of uptime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065589/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065589] Re: initctl list shows 11974 instances of network-interface-security after two days of uptime
I fixed the userspace side of this in 13.04 and the 3.8 kernel contains the matching kernel fix. I could probably backport the fix to 12.04, though it won't work until the 13.04 kernel is backported and people explicitly move to it. -- 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/1065589 Title: initctl list shows 11974 instances of network-interface-security after two days of uptime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065589/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1101371] Re: [SRU] Integrate v1.3 of Windows Azure Linux Agent
** Summary changed: - Integrate v1.3 of Windows Azure Linux Agent + [SRU] Integrate v1.3 of Windows Azure Linux Agent ** Description changed: + [Impact] + 5% of all instance launches are affected by not having these changes backported into Ubuntu series. + The version fixing this is tag 1.3 Windows Azure Linux Agent: + * https://github.com/Windows-Azure/WALinuxAgent/tags + Fixes error checking and robustness to the DVD mounting procedure as well as other fixes. + * https://code.launchpad.net/~utlemming/ubuntu/raring/walinuxagent/v1.3 + + [Test Case] + Boot enough instances to get at least one of them fail. + + [Regression potential] + During our testing we were unable to reproduce the problem both with the old version and the new version. But, we can trust the upstream who is the author of the patches since this changes might impact an app that is used only within upstream's service. + + + Original report: + Hello! We have tagged version 1.3 of the Windows Azure Linux Agent. Please pull the new agent source or download directly from the following location: - https://github.com/Windows-Azure/WALinuxAgent/tags + https://github.com/Windows-Azure/WALinuxAgent/tags The important change in this release adds some error checking and robustness to our DVD mounting procedure, as well as a few minor bugfixes. Please test and let us know if you have any questions/comments. Thanks! Stephen A. Zarkos Microsoft Open Source Technology Center -- 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/1101371 Title: [SRU] Integrate v1.3 of Windows Azure Linux Agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 967410] Re: Windows clients cannot connect to shared printers
I have swat , samba 3.6.3 , ubuntu 12.04 server 64 , CUPS 1.5.3 I have printer1 without portname [], printer 1 and 2 are the same model and I use the same protocol and ppd . enumprinters 5 printername:[\\LOCALHOST\printer1] portname:[] attributes:[0x1048] device_not_selected_timeout:[0x0] transmission_retry_timeout:[0x0] printername:[\\LOCALHOST\printer2] portname:[Samba Printer Port] attributes:[0x1048] device_not_selected_timeout:[0x0] transmission_retry_timeout:[0x0] printername:[\\LOCALHOST\printe3] portname:[Samba Printer Port] attributes:[0x1048] device_not_selected_timeout:[0x0] transmission_retry_timeout:[0x0] if I run command : enumprinters 2 I can see that : servername:[\\LOCALHOST] printername:[\\LOCALHOST\print1] sharename:[print1] portname:[] drivername:[print1] comment:[print1] location:[floor] sepfile:[] printprocessor:[] datatype:[] parameters:[] attributes:[0x1048] priority:[0x0] defaultpriority:[0x0] starttime:[0x0] untiltime:[0x0] status:[0x0] cjobs:[0x0] averageppm:[0x0] So empty : portname:[] default is : portname:[Samba Printer Port] printprocessor:[] default is : printprocessor:[winprint] datatype:[]default is : datatype:[RAW] from windows printer 2-3 works fine , when I try to install on windows 7 in background download the driver but give a error : windows cannot connect to the printer print processor does not exist -- 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/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/967410/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1105411] [NEW] apache2 default conf file contains Listen directive
Public bug reported: The default Apache 2 config file /etc/apache2/ports.conf contains a Listen directive. This directive is extraneous and unnecessary: The default configuration includes a VirtualHost that listens on Port 80. SSL configurations listen on Port 443. Removing the global Listen directives does not change this behavior; however if the default site is removed or moved to another port, Apache continues to listen on that port. For example, if Apache listens on Port 80 and you change the default site to listen on port 1080, Apache will listen on Port 80 and Port 1080 due to the Listen directive in ports.conf. By removing or commenting the Listen directive, Apache will no longer listen on Port 80 if no VirtualHost exists that specifies Port 80. This reduces the number of open ports, and leaves Port 80 open for other applications. Leaving the Listen directive in ports.conf as-is is not particularly harmful; it does however lead to minor, momentary confusion or excessive open ports when unfamiliar users configure Apache in exotic ways. As it is unnecessary, it should be disabled. ** Affects: apache2 (Ubuntu) Importance: Low Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1105411 Title: apache2 default conf file contains Listen directive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100920] Re: In Ubuntu 12.10, the legacy 'user' cloud-config option is not handled properly
** Changed in: cloud-init Status: In Progress = 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/1100920 Title: In Ubuntu 12.10, the legacy 'user' cloud-config option is not handled properly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1105411] Re: apache2 default conf file contains Listen directive
Importance: Low. Reason: not really a bug that prevents operation, more rather a bug that addresses minor housekeeping of the default configs. Requested via IRC, by bluefoxxx. Processed by myself (TheLordOfTime): [15:13:33] bluefoxxx That should be a very low importance but I can't triage my own bugs. [15:13:45] TheLordOfTime triage requires bugcontrol usually, which bug? [15:13:53] bluefoxxx 1105411 [15:13:58] TheLordOfTime LP Bug 1105411 [15:13:59] ubot2 Launchpad bug 1105411 in apache2 (Ubuntu) apache2 default conf file contains Listen directive [Undecided,New] https://launchpad.net/bugs/1105411 [15:14:43] TheLordOfTime bugs usually need to be confirmed before we triage, but i agree on the low importance [15:14:47] * TheLordOfTime sets the bug as Low Importance [15:14:47] bluefoxxx It's low priority because it's effectively meaningless housekeeping minimizing the configuration [15:15:06] TheLordOfTime agreed, which is why i set it :) I'm not marking this as triaged, yet, as I have not confirmed this bug yet. (although a fix for this bug should be exceptionally minor) ** Changed in: apache2 (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1105411 Title: apache2 default conf file contains Listen directive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1075456] Re: wrong path given in README
** Changed in: dovecot (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1075456 Title: wrong path given in README To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1075456/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1105411] Re: apache2 default conf file contains Listen directive
** Bug watch added: Debian Bug tracker #698967 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698967 ** Also affects: apache2 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698967 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1105411 Title: apache2 default conf file contains Listen directive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 967410] Re: Windows clients cannot connect to shared printers
My solution to reset the rpcclient : 1) Stop Samba 2) Delete files: /var/lib/samba/registry.tdb /var/cache/samba/printing/* 4) Restart Samba yeah ! -- 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/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/967410/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 943502] Re: whois doesn't properly query .hr/.sx/.pe TLDs and incorrect format for whois.arin.net
I have just verified this works and passes all the test cases. ** 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 whois in Ubuntu. https://bugs.launchpad.net/bugs/943502 Title: whois doesn't properly query .hr/.sx/.pe TLDs and incorrect format for whois.arin.net To manage notifications about this bug go to: https://bugs.launchpad.net/oneiric-backports/+bug/943502/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1105411] Re: apache2 default conf file contains Listen directive
** Changed in: apache2 (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1105411 Title: apache2 default conf file contains Listen directive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions -- Ubuntu-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 1105411] Re: apache2 default conf file contains Listen directive
I think I'm completely wrong on this, my fault for doing this completely from memory without verifying that it actually works. The problem is more of Apache's completely unexpected behavior: it listens on whatever port you tell it. You have only a virtual host on *:1080? Listen 80, it comes up and listens on 80, does not serve your site. You have multiple virtual hosts on one port, and multiple others on other ports? You can't have multiple Listen directives on the same port, Apache won't start. The same information is in two places and it doesn't have to make sense. I should have actually checked before I filed this invalid report; the actual issue I want to report is something completely different and upstream. On Fri, Jan 25, 2013 at 4:22 PM, Bug Watch Updater 1105...@bugs.launchpad.net wrote: ** Changed in: apache2 (Debian) Status: Unknown = New -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1105411 Title: apache2 default conf file contains Listen directive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1105411 Title: apache2 default conf file contains Listen directive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065589] Re: initctl list shows 11974 instances of network-interface-security after two days of uptime
Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1065589 Title: initctl list shows 11974 instances of network-interface-security after two days of uptime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065589/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1105411] Re: apache2 default conf file contains Listen directive
Marked invalid per email response from original poster. ** Changed in: apache2 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1105411 Title: apache2 default conf file contains Listen directive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions -- Ubuntu-server-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] Re: [SRU] raphael new upstream release (2.1.0)
As Clint says, this doesn't fit the SRU policy. If the raphael source is already bundled in the maas source package in precise, we should keep it this way; I don't see any reason that it's worth splitting this out, clobbering the existing raphael package in precise, in an SRU when keeping it in the maas source requires much less verification effort. Rejecting from the queue and marking this 'wontfix'. ** Changed in: raphael (Ubuntu Precise) Status: New = Won't Fix -- 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
[Blueprint servercloud-r-webscale] WebScale Packaging and Main Promotions
Blueprint changed by James Page: Work items set to: Work items: Identify specific advantages of nginx over apache: TODO Review security track record of nginx: TODO Speak with nginx upstream re main inclusion appetite: TODO Prepare MIR for nginx: BLOCKED Evaluate nodejs core in supported seed: TODO Confirm npm not suitable for inclusion: TODO Prepare MIR for nodejs: BLOCKED Evalute mongodb for supported seed: TODO Confirm mongodb upstream appetite: TODO Hook up with go juju team with dependency on mongodb: TODO Prepare MIR for mongodb: BLOCKED [ivoks] Determine if there is value in including varnish in main: TODO [ivoks] Prepare MIR for varnish: BLOCKED -- WebScale Packaging and Main Promotions https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-webscale -- Ubuntu-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-webscale] WebScale Packaging and Main Promotions
Blueprint changed by James Page: Whiteboard changed: --- User Stories --- + + Frank wants to deploy nginx instead of apache to support a specific + requirement he has which cannot but fulfilled bu apache; he's able to + use a fully supported solution when using Ubuntu. + + Toby is a nodejs developer; Ubuntu has the latest and greatest packaged + and easily installable. + + Ante has been deploying varnish for some time; Ubuntu now fully supports + varnish so he can stop cutting his own security updates. --- Risks --- + Upstream appetite + Volatility/release frequency of upstream projects (nodejs specifically). + --- Test Plans --- + + TBC --- Release Note --- + [NGINX|nodejs|MongoDB|Varnish] is now in Ubuntu main and will recieved + Security Updates from the Ubuntu Security Team. + --- Blog Post --- - (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] + Maybe --- UDS Discussion --- Etherpad from UDS session: Webscale Packaging Improvements and main promotions + * Nginx - Has become de-facto scalable web server, and grown up as an OSS project now - Bug tracker? Now addressed - Supporting tooling might need some work to get feature parity with Apache: - nginxensite/nginxenmod etc - http://nginx.org/en/security_advisories.html - Better backend support sounds compelling - [] identify specific advantages of nginx over apache: TODO - [] review security track record of nginx: TODO - [] speak with upstream re main inclusion appetite: TODO - [] prepare MIR for nginx (depends on above): BLOCKED + * Node.js - Gaining popularity fast, and *SHOULD* be a build-dep of OpenStack Horizon - Also a direct dependency of the new Juju GUI - Azure tooling - Openstack Horizon Build Dependency - RBD's should drive seeding... - ?? Default interpreter name ?? - [] evaluate nodejs core in supported seed: TODO - [] confirm npm not suitable for inclusion: TODO - [] prepare MIR for nodejs: BLOCKED + * MongoDB (also headed for main as part of juju) - Dependency for Go Juju - Required support for TLS - needs looking at - ceilometer support required this Cons: large codebase Pros: good upstream development process. - [] evalute mongodb for supported seed: TODO - [] confirm upstream appetite: TODO - [] hook up with go juju team with dependency on mongodb: TODO - [] prepare MIR for mongodb: BLOCKED - Clint to look after mongo and nginx as the blue print owner. + * Varnish (if time) Popular heavily used caching. More configurable--language based. - [ivoks] determine if there is value in including in main: TODO - [ivoks] prepare MIR for varnish: BLOCKED + -- Others? - seed prunin. Anything that can be dropped? - Varnish? -- WebScale Packaging and Main Promotions https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-webscale -- Ubuntu-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-webscale] WebScale Packaging and Main Promotions
Blueprint changed by James Page: Definition Status: Discussion = Approved -- WebScale Packaging and Main Promotions https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-webscale -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1101002] Re: Frequently stops working for 15-30 seconds at a time on Ubuntu 12.10
** Changed in: bind9 (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1101002 Title: Frequently stops working for 15-30 seconds at a time on Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1101002/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078699] Re: winbind won't start at boot
** Changed in: samba (Ubuntu) Status: Incomplete = 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/1078699 Title: winbind won't start at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1078699/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1029977] Re: dnsmasq-base should ship the dnsmasq dbus configuration file
Hello Mathieu, or anyone else affected, Accepted dnsmasq into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/dnsmasq/2.59-4ubuntu0.1 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! ** Changed in: dnsmasq (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1029977 Title: dnsmasq-base should ship the dnsmasq dbus configuration file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1029977/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
