[Blueprint servercloud-q-bigdata-hadoop] Next steps for Hadoop on Ubuntu
Blueprint changed by James Page: Work items changed: Work items: Update bigtop-utils and hadoop charms to support openjdk-7: DONE Testing of existing hadoop charms with openjdk-7: DONE - Update hadoop charms to support kerberos based authentication: TODO - Review use of puppet modules in hadoop charms: INPROGRESS + Update hadoop charms to support kerberos based authentication: POSTPONED + Review use of puppet modules in hadoop charms: DONE Write/update charms to use bigtop 0.4.0 release repositories: INPROGRESS Setup automated testing of charms using bigtop tests: POSTPONED Support usage of Oracle EJRE for ARM based deployements for hadoop 1.0.x: INPROGRESS -- Next steps for Hadoop on Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-bigdata-hadoop -- Ubuntu-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-q-openflow-controller] OpenFlow Controller for Ubuntu
Blueprint changed by James Page: Work items changed: Work items for quantal-alpha-3: [james-page] Package required thrift components: DONE [james-page] Package restlet for Ubuntu: DONE [lanerl] Package simple for Ubuntu: DONE [james-page] Verify that openvswitch will be enabled with the kernel team now that it is in the kernel: DONE [james-page] Create floodlight and mininet projects in launchpad: DONE [james-page] Check with nicira regarding openvswitch versions for usage (current version (1.4.1+gitsnap) is OK but DKMS does not support 3.5 kernel - will be removed): DONE Work items for ubuntu-12.10-beta-1: [lanerl] Package floodlight for Ubuntu: DONE [james-page] Support packaging of mininet: DONE Work items for ubuntu-12.10: - [med] keep up with quantum changes wrt to functionality and distributed plugins (davidmed, bigswitch): TODO + [med] keep up with quantum changes wrt to functionality and distributed plugins (davidmed, bigswitch): DONE [gandelman-a] Update openstack charms to support quantum: TODO Package trema for Ubuntu (trema is a framework for openflow controller developement - if something depends on this then we can revisit): POSTPONED [james-page] Setup a test lab/scenario for QA (qalab, nbarcet+bigswitch) - UTAH test using floodlight, openvswitch and mininet: DONE -- OpenFlow Controller for Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-openflow-controller -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 782298] Re: command injections in mysqld_multi
Yes, if some other program (GUI , Server side scripts , etc ...) use a user supplied data as input to mysqld_multi command in vulnerable operations it will be a security issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/782298 Title: command injections in mysqld_multi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/782298/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 156085] Re: Could not open /proc/bus/usb/devices
** Changed in: qemu (openSUSE) Importance: Unknown = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/156085 Title: Could not open /proc/bus/usb/devices To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/156085/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 991023] [NEW] mysql server cannot start
You have been subscribed to a public bug: Problem starting mysql daemon because error in apparmor profile. The file /etc/apparmor.d/local/usr.sbin.mysqld does not exist. Can be corrected by: sudo -s umask 022 touch /etc/apparmor.d/local/usr.sbin.mysqld ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- mysql server cannot start https://bugs.launchpad.net/bugs/991023 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063680] Re: php5-fpm crashed with SIGSEGV
** Visibility changed to: Public -- 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/1063680 Title: php5-fpm crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1063680/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063680]
StacktraceTop: ?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2 ?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2 ?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2 ?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2 ?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2 -- 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/1063680 Title: php5-fpm crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1063680/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063680] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1063680/+attachment/3385815/+files/Stacktrace.txt -- 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/1063680 Title: php5-fpm crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1063680/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063680] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1063680/+attachment/3385816/+files/StacktraceSource.txt -- 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/1063680 Title: php5-fpm crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1063680/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063680] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1063680/+attachment/3385817/+files/ThreadStacktrace.txt ** Changed in: php5 (Ubuntu) Status: New = Invalid -- 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/1063680 Title: php5-fpm crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1063680/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063680] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: outdated debug symbol package for libstdc++6: package version 4.7.2-2ubuntu1 dbgsym version 4.6.3-1ubuntu5 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1063680/+attachment/3385773/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- 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/1063680 Title: php5-fpm crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1063680/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063697] [NEW] [FFe] Please update to new snapshot release
Public bug reported: The latest updates to juju trunk include a number of bug fixes and one major refactor which are important for quantal Features: - Refactoring to Local provider to use Ubuntu Cloud Images; this resolves a number of networking issues with the local provider (removes the dependency on libvirt) and makes the local provider instances behave more like those used in cloud deployments. Two key regressions: * Regresses HTTPS apt support for local provider because cloud-init doesn't have a way to make the distinction. * Regresses performance for the case where the download is cached. rsync'ing from the debootstrap is a little faster than extracting the tar.gz. Also we now do a full apt-get upgrade, so all updates have to be unpacked/configured. - MAAS constraints; currently only machine-name is supported; this makes the MAAS provider in Juju much more useful; change in behaviour of MAAS provider so some regression potential. - Juju: Add --version option - no regression potential. Bug Fixes: - Openstack Folsom compatibility - Fix reporting of exceptions For full details see - https://code.launchpad.net/~juju/juju/trunk commits 586-592 ** Affects: juju (Ubuntu) Importance: High Status: New ** Affects: juju (Ubuntu Quantal) Importance: High Status: New ** Description changed: The latest updates to juju trunk include a number of bug fixes and one major refactor which are important for quantal - Feature: + Features: -- Refactoring to Local provider to use Ubuntu Cloud Images; this resolves a number of networking issues with the local provider (removes the dependency on libvirt) and makes the local provider instances behave more like those used in cloud deployments. Two key regressions: - * Regresses HTTPS apt support for local provider because cloud-init doesn't have a way to make the distinction. - * Regresses performance for the case where the download is cached. rsync'ing from the debootstrap is a little faster than extracting the tar.gz. Also we now do a full apt-get upgrade, so all updates have to be unpacked/configured. + - Refactoring to Local provider to use Ubuntu Cloud Images; this resolves a number of networking issues with the local provider (removes the dependency on libvirt) and makes the local provider instances behave more like those used in cloud deployments. Two key regressions: + * Regresses HTTPS apt support for local provider because cloud-init doesn't have a way to make the distinction. + * Regresses performance for the case where the download is cached. rsync'ing from the debootstrap is a little faster than extracting the tar.gz. Also we now do a full apt-get upgrade, so all updates have to be unpacked/configured. + + - MAAS constraints; currently only machine-name is supported; this makes + the MAAS provider in Juju much more useful; change in behaviour of MAAS + provider so some regression potential. + + - Juju: Add --version option - no regression potential. Bug Fixes: - - Openstack folsom compatibility - - Misc MAAS provider fixes - - Fix reporting of exceptions + - Openstack Folsom compatibility + - Fix reporting of exceptions For full details see - https://code.launchpad.net/~juju/juju/trunk commits 586-592 -- 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/1063697 Title: [FFe] Please update to new snapshot release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1063697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063697] Re: [FFe] Please update to new snapshot release
** Changed in: juju (Ubuntu) Importance: Undecided = High ** Also affects: juju (Ubuntu Quantal) Importance: High Status: New ** Attachment added: Build Log https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1063697/+attachment/3386018/+files/juju_0.5.99%2Bbzr592-0ubuntu1_amd64.build ** Description changed: The latest updates to juju trunk include a number of bug fixes and one major refactor which are important for quantal Features: - Refactoring to Local provider to use Ubuntu Cloud Images; this resolves a number of networking issues with the local provider (removes the dependency on libvirt) and makes the local provider instances behave more like those used in cloud deployments. Two key regressions: * Regresses HTTPS apt support for local provider because cloud-init doesn't have a way to make the distinction. * Regresses performance for the case where the download is cached. rsync'ing from the debootstrap is a little faster than extracting the tar.gz. Also we now do a full apt-get upgrade, so all updates have to be unpacked/configured. - MAAS constraints; currently only machine-name is supported; this makes the MAAS provider in Juju much more useful; change in behaviour of MAAS provider so some regression potential. - Juju: Add --version option - no regression potential. Bug Fixes: - Openstack Folsom compatibility - Fix reporting of exceptions For full details see - https://code.launchpad.net/~juju/juju/trunk commits 586-592 + + Build log: see attached + + Testing: + + - Tested local provider with 12.04 cloud images; worked fine + - Tested openstack provider with OpenStack Folsom: TBC + - Tested interoperability with existing Openstack Essex environment: OK -- 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/1063697 Title: [FFe] Please update to new snapshot release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1063697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063697] Re: [FFe] Please update to new snapshot release
** Description changed: The latest updates to juju trunk include a number of bug fixes and one major refactor which are important for quantal Features: - Refactoring to Local provider to use Ubuntu Cloud Images; this resolves a number of networking issues with the local provider (removes the dependency on libvirt) and makes the local provider instances behave more like those used in cloud deployments. Two key regressions: * Regresses HTTPS apt support for local provider because cloud-init doesn't have a way to make the distinction. * Regresses performance for the case where the download is cached. rsync'ing from the debootstrap is a little faster than extracting the tar.gz. Also we now do a full apt-get upgrade, so all updates have to be unpacked/configured. - MAAS constraints; currently only machine-name is supported; this makes the MAAS provider in Juju much more useful; change in behaviour of MAAS provider so some regression potential. - Juju: Add --version option - no regression potential. Bug Fixes: - Openstack Folsom compatibility - Fix reporting of exceptions For full details see - https://code.launchpad.net/~juju/juju/trunk commits 586-592 Build log: see attached Testing: - Tested local provider with 12.04 cloud images; worked fine - - Tested openstack provider with OpenStack Folsom: TBC + - Tested openstack provider with OpenStack Folsom: OK - Tested interoperability with existing Openstack Essex environment: OK ** Description changed: The latest updates to juju trunk include a number of bug fixes and one major refactor which are important for quantal Features: - Refactoring to Local provider to use Ubuntu Cloud Images; this resolves a number of networking issues with the local provider (removes the dependency on libvirt) and makes the local provider instances behave more like those used in cloud deployments. Two key regressions: * Regresses HTTPS apt support for local provider because cloud-init doesn't have a way to make the distinction. * Regresses performance for the case where the download is cached. rsync'ing from the debootstrap is a little faster than extracting the tar.gz. Also we now do a full apt-get upgrade, so all updates have to be unpacked/configured. - MAAS constraints; currently only machine-name is supported; this makes the MAAS provider in Juju much more useful; change in behaviour of MAAS provider so some regression potential. - Juju: Add --version option - no regression potential. Bug Fixes: - Openstack Folsom compatibility - Fix reporting of exceptions For full details see - https://code.launchpad.net/~juju/juju/trunk commits 586-592 Build log: see attached Testing: - - Tested local provider with 12.04 cloud images; worked fine + - Tested local provider with 12.04 cloud images; OK - Tested openstack provider with OpenStack Folsom: OK - Tested interoperability with existing Openstack Essex environment: OK -- 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/1063697 Title: [FFe] Please update to new snapshot release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1063697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063697] Re: [FFe] Please update to new snapshot release ~bzr592
** Summary changed: - [FFe] Please update to new snapshot release + [FFe] Please update to new snapshot release ~bzr592 -- 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/1063697 Title: [FFe] Please update to new snapshot release ~bzr592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1063697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063697] Re: [FFe] Please update to new snapshot release ~bzr592
** Description changed: The latest updates to juju trunk include a number of bug fixes and one major refactor which are important for quantal Features: - Refactoring to Local provider to use Ubuntu Cloud Images; this resolves a number of networking issues with the local provider (removes the dependency on libvirt) and makes the local provider instances behave more like those used in cloud deployments. Two key regressions: * Regresses HTTPS apt support for local provider because cloud-init doesn't have a way to make the distinction. * Regresses performance for the case where the download is cached. rsync'ing from the debootstrap is a little faster than extracting the tar.gz. Also we now do a full apt-get upgrade, so all updates have to be unpacked/configured. - MAAS constraints; currently only machine-name is supported; this makes the MAAS provider in Juju much more useful; change in behaviour of MAAS provider so some regression potential. - Juju: Add --version option - no regression potential. Bug Fixes: - Openstack Folsom compatibility - Fix reporting of exceptions For full details see - https://code.launchpad.net/~juju/juju/trunk commits 586-592 Build log: see attached Testing: - Tested local provider with 12.04 cloud images; OK - Tested openstack provider with OpenStack Folsom: OK - Tested interoperability with existing Openstack Essex environment: OK + - Tested with ec2 provider: OK -- 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/1063697 Title: [FFe] Please update to new snapshot release ~bzr592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1063697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 989243] Re: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openldap (Ubuntu) Status: New = Confirmed -- 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/989243 Title: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/989243/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063770] Re: cloud lxc template leaves half-written files if interrupted
** Also affects: juju Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1063770 Title: cloud lxc template leaves half-written files if interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1063770/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063770] [NEW] cloud lxc template leaves half-written files if interrupted
Public bug reported: Happened two times already for me, once on a network glitch (where the wget failed) and once where it never finished so I had to kill wget. Eg: drwx-- 2 root root 4096 Oct 8 10:28 tmp.jFQHxoBsm0 -rw-r--r-- 1 root root 179044352 Oct 8 01:02 ubuntu-12.04-server-cloudimg-amd64-root.tar.gz -rw-r--r-- 1 root root 1556480 Oct 8 10:28 ubuntu-12.04-server-cloudimg-amd64.tar.gz Doesn't seem like the script can recover from that situation, it just tries to extract the incomplete tarball and fails. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lxc 0.8.0~rc1-4ubuntu37 ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 10:28:52 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120901) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) lxcsyslog: Oct 8 14:28:15 sidnei-laptop kernel: [36639.644912] type=1400 audit(1349702895.900:334): apparmor=STATUS operation=profile_replace name=lxc-container-default pid=15205 comm=apparmor_parser Oct 8 14:28:15 sidnei-laptop kernel: [36639.645230] type=1400 audit(1349702895.900:335): apparmor=STATUS operation=profile_replace name=lxc-container-default-with-nesting pid=15205 comm=apparmor_parser Oct 8 14:28:15 sidnei-laptop kernel: [36639.699162] type=1400 audit(1349702895.952:336): apparmor=STATUS operation=profile_replace name=/usr/bin/lxc-start pid=15209 comm=apparmor_parser modified.conffile..etc.dnsmasq.d.lxc: [modified] modified.conffile..etc.lxc.lxc.conf: [modified] mtime.conffile..etc.dnsmasq.d.lxc: 2012-09-04T09:08:59.313752 mtime.conffile..etc.lxc.lxc.conf: 2012-09-04T09:08:47.312726 ** Affects: juju Importance: Undecided Status: New ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- 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/1063770 Title: cloud lxc template leaves half-written files if interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1063770/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063770] Re: cloud lxc template leaves half-written files if interrupted
*** This bug is a duplicate of bug 1037331 *** https://bugs.launchpad.net/bugs/1037331 ** This bug has been marked a duplicate of bug 1037331 lxc-create should clear the cache when interrupted -- 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/1063770 Title: cloud lxc template leaves half-written files if interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1063770/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1037331] Re: lxc-create should clear the cache when interrupted
I think this would be worth fixing in precise. ** Also affects: lxc (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Precise) Status: New = Triaged ** Changed in: lxc (Ubuntu Precise) Importance: Undecided = Medium ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1037331 Title: lxc-create should clear the cache when interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1037331/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063806] [NEW] ntp deadlock while exiting and never stop
Public bug reported: Software version: * Description:Ubuntu 12.04.1 LTS * arch : x86_64 * ntp 1:4.2.6.p3+dfsg-1ubuntu3.1 * libc6 2.15-0ubuntu10.2 We hit a strang behavious on some machine, where ntp refuse to quit if stopped right after startup: When running the following command: /etc/init.d/ntp start /etc/init.d/ntp stop ntp still running and ignoring further kill. In syslog we can see the stop is effectivly taken in account: Oct 8 12:45:36 app01 ntpd[16713]: ntpd exiting on signal 15 Sending more kill 16713 do nothing. We have the start and just after stop behavious on our server, because of https://bugs.launchpad.net/nova/+bug/887162. Short summary: dhcp server don't reply until dhcp client lost the IP and request new IP using broadcast request: * (AFAIK) when dhcp don't get answer from DHCP and remove the IP is call a hook which restart ntp (/etc/dhcp/dhclient-exit-hooks.d/ntp) * dhcp retry just after to grab a new IP and get the IP. Interface goes up, a hook restart one more the ntpd (/etc/network/if-up.d/ntpdate) After digging further, I reproduced the issue on my local machine by using a simple script which start and kill ntpd until we reach the issue. Once the issue reproduced I attached gdb to the process and showed stack (see gdb-stack-dbg.txt). Looking to this stack, it seems that the issue is syslog function which is not re-entrant. When signal SIGTERM occure while main thread called syslog, this cause a deadlock. I also attached gdb-stack.txt using packaged ntpd (so no debuging symbol for ntpd function). And I attached ntpd_loop.py : the basic script which start and kill ntpd until it hang. You may need to change the short sleep between start/stop and/or run other resource consuming process on other terminal (I usually do a find /). ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Attachment added: gdb info stack during deadlock (with debuging symbols) https://bugs.launchpad.net/bugs/1063806/+attachment/3386608/+files/gdb-stack-dbg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1063806 Title: ntp deadlock while exiting and never stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1063806/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063806] Re: ntp deadlock while exiting and never stop
** Attachment added: gdb info stack during deadlock (with packaged ntpd) https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1063806/+attachment/3386609/+files/gdb-stack.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1063806 Title: ntp deadlock while exiting and never stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1063806/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063806] Re: ntp deadlock while exiting and never stop
** Attachment added: script used to show the problem on my workstation https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1063806/+attachment/3386619/+files/ntpd_loop.py -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1063806 Title: ntp deadlock while exiting and never stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1063806/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 744371] Re: PHP5-FPM doesn't always restart on 10.10
Hello, and thanks for filing a bug to try and make Ubuntu better! This is currently filed against Ubuntu Maverick (10.10), which is no longer supported. Can you please test this bug against 11.10, which is a currently-supported version of Ubuntu, or any other currently-supported release of Ubuntu? (I am skipping 11.04, as it will EndOfLife at some point this month) -- Thomas Ward Ubuntu BugSquad Member ** Tags added: maverick -- 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/744371 Title: PHP5-FPM doesn't always restart on 10.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/744371/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 744371] Re: PHP5-FPM doesn't always restart on 10.10
I can't reproduce this in oneiric, and the init script has changed quite a bit there. -- 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/744371 Title: PHP5-FPM doesn't always restart on 10.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/744371/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
** Changed in: qemu-kvm (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 744371] Re: PHP5-FPM doesn't always restart on 10.10
** Tags added: natty -- 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/744371 Title: PHP5-FPM doesn't always restart on 10.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/744371/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 744371] Re: PHP5-FPM doesn't always restart on 10.10
Marked Fix released. It should be fixed in oneiric+. With one month left in natty, we don't believe it is worth targetting the bug at natty at this point. ** Changed in: php5 (Ubuntu) Status: Confirmed = Fix Released -- 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/744371 Title: PHP5-FPM doesn't always restart on 10.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/744371/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063857] [NEW] Cluster controller fails to start because MAAS_URL is not set.
You have been subscribed to a public bug: Testing the package in the daily ppa (0.1+bzr1170+dfsg-0+1215+119~ppa0~quantal1), the cluster controller is unable to start: $ sudo tail -f /var/log/upstart/maas-cluster-celery.log usage: __main__.py start-cluster-controller [-h] [--user USER] [--group GROUP] URL __main__.py start-cluster-controller: error: too few arguments I think this is because /etc/maas/maas_cluster.conf contains: # [...] MAAS_URL= If I put MAAS_URL=http://localhost/MAAS in that file, the cluster controller starts ok and fires the cluster worker fine. ** Affects: maas (Ubuntu) Importance: Critical Status: Triaged -- Cluster controller fails to start because MAAS_URL is not set. https://bugs.launchpad.net/bugs/1063857 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
** Changed in: qemu-kvm (Ubuntu Precise) Status: Fix Released = Fix Committed -- 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/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063857] [NEW] Cluster controller fails to start because MAAS_URL is not set.
Public bug reported: Testing the package in the daily ppa (0.1+bzr1170+dfsg-0+1215+119~ppa0~quantal1), the cluster controller is unable to start: $ sudo tail -f /var/log/upstart/maas-cluster-celery.log usage: __main__.py start-cluster-controller [-h] [--user USER] [--group GROUP] URL __main__.py start-cluster-controller: error: too few arguments The cluster controller is started by: exec /usr/sbin/maas-provision start-cluster-controller $MAAS_URL -u maas -g maas (see /etc/init/maas-cluster-celery.conf) I think this is because /etc/maas/maas_cluster.conf contains: # [...] MAAS_URL= If I put MAAS_URL=http://localhost/MAAS in that file, the cluster controller starts ok and fires the cluster worker fine. ** Affects: maas (Ubuntu) Importance: Critical Assignee: Andres Rodriguez (andreserl) Status: Triaged ** Project changed: maas = maas (Ubuntu) ** Description changed: Testing the package in the daily ppa (0.1+bzr1170+dfsg-0+1215+119~ppa0~quantal1), the cluster controller is unable to start: $ sudo tail -f /var/log/upstart/maas-cluster-celery.log usage: __main__.py start-cluster-controller [-h] [--user USER] [--group GROUP] - URL + URL __main__.py start-cluster-controller: error: too few arguments + + The cluster controller is started by: + exec /usr/sbin/maas-provision start-cluster-controller $MAAS_URL -u maas -g maas + (see /etc/init/maas-cluster-celery.conf) I think this is because /etc/maas/maas_cluster.conf contains: # [...] MAAS_URL= If I put MAAS_URL=http://localhost/MAAS in that file, the cluster controller starts ok and fires the cluster worker fine. -- 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/1063857 Title: Cluster controller fails to start because MAAS_URL is not set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1063857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063857] Re: Cluster controller fails to start because MAAS_URL is not set.
At Andres' request, here is the output of sudo dpkg-reconfigure -phigh maas-cluster-controller : $ sudo dpkg-reconfigure -phigh maas-cluster-controller maas-cluster-celery stop/waiting /var/lib/dpkg/info/maas-cluster-controller.config: 26: /var/lib/dpkg/info/maas-cluster-controller.config: db_input: not found /var/lib/dpkg/info/maas-cluster-controller.config: 27: /var/lib/dpkg/info/maas-cluster-controller.config: db_go: not found -- 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/1063857 Title: Cluster controller fails to start because MAAS_URL is not set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1063857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063857] Re: Cluster controller fails to start because MAAS_URL is not set.
** Changed in: maas (Ubuntu) Assignee: (unassigned) = Andres Rodriguez (andreserl) -- 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/1063857 Title: Cluster controller fails to start because MAAS_URL is not set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1063857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1029889] Re: LVM Based KVM VM taking 100% CPU on first start and hangs.
@Lewdmole, have you had a chance to try this out without lvm? ** Changed in: libvirt (Ubuntu) Status: New = Incomplete ** Changed in: qemu-kvm (Ubuntu) Status: New = Incomplete -- 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/1029889 Title: LVM Based KVM VM taking 100% CPU on first start and hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1029889/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 615077] Re: [Maverick] SDL local window broken in last update
(Marked invalid in libvirt as this seems to be related mainly to virtinst) ** Changed in: libvirt (Ubuntu) Status: New = Invalid -- 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/615077 Title: [Maverick] SDL local window broken in last update To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/615077/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1057024] Re: kvm kernel module always loaded
** Summary changed: - internal error Process exited while reading console log output: char device redirected to /dev/pts/1 error when creating a vm + kvm kernel module always loaded ** Also affects: udev (Ubuntu) Importance: Undecided Status: New ** Summary changed: - kvm kernel module always loaded + kvm kernel module always loaded, without setting /dev/kvm permissions ** Changed in: udev (Ubuntu) Status: New = Invalid ** Changed in: libvirt (Ubuntu) Importance: High = Critical ** No longer affects: udev (Ubuntu) ** Package changed: libvirt (Ubuntu) = qemu-kvm (Ubuntu) -- 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/1057024 Title: kvm kernel module always loaded, without setting /dev/kvm permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1057024] Re: kvm kernel module always loaded, without setting /dev/kvm permissions
Root cause found: udev automatically loads kvm_intel even when qemu-kvm is not installed. The kvm group and udev file causing /dev/kvm to be chgrp'd to kvm and set its permissions are installed by qemu-kvm. If it were only a question of permissions I'd say the udev package should be setting those. However it would also have to add the kvm group. So the qemu-kvm postinst should set the permissions on /dev/kvm if that already exists. ** Changed in: qemu-kvm (Ubuntu) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) ** Changed in: qemu-kvm (Ubuntu) Importance: Critical = High -- 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/1057024 Title: kvm kernel module always loaded, without setting /dev/kvm permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1057024] Re: kvm kernel module always loaded, without setting /dev/kvm permissions
No, I was looking in the wrong place - qemu-kvm.postinst already does exactly that! In fact, I'm starting to wonder whether the way to reproduce this would be to not 'apt-get install kvm' before installing libvirt-bin. The kvm kernel module will be loaded, but won't be configured for use by libvirt. I'm not sure whether we should consider that a bug, or mis- configuration by the admin. -- 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/1057024 Title: kvm kernel module always loaded, without setting /dev/kvm permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1057024] Re: kvm kernel module always loaded, without setting /dev/kvm permissions
If kvm is not configured, then virt-manager tells me at the first 'New virtual machine screen that: Error: No hypervisor options were found for this connection. This usually means that QEMU or KVM is not installed on your machine, or the KVM kernel modules are not loaded. So I simply cannot reproduce this. At this point I will mark the bug 'incomplete' meaning that we need more information to resolve it (per discussions at last UDS). If more information becomes available, please do comment here. psivaa, Will you be at UDS? Would it be at all possible for you to bring one of these laptops so we can watch this happen together? ** Changed in: qemu-kvm (Ubuntu) Assignee: Serge Hallyn (serge-hallyn) = (unassigned) ** Changed in: qemu-kvm (Ubuntu) Status: Confirmed = Incomplete -- 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/1057024 Title: kvm kernel module always loaded, without setting /dev/kvm permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1057024] Re: kvm kernel module always loaded, without setting /dev/kvm permissions
@Serge, I will be at the UDS and Ill bring the machine there. Thanks -- 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/1057024 Title: kvm kernel module always loaded, without setting /dev/kvm permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1054096] Re: Openstack folsom compatibility
I've tested trunk against Canonical's internal canonistack folsom region, as has Martin Packman, and it seems to work fine. This seems to be specifically about RAX. I'll target this at 0.7 then, as I suspect it may be a lot of work, and not just a simple backportable fix. ** Changed in: juju Milestone: 0.6 = 0.7 ** Summary changed: - Openstack folsom compatibility + Openstack folsom compatibility (Rackspace Cloud Specifically) ** Changed in: juju Importance: Critical = High ** Changed in: juju (Ubuntu Quantal) Milestone: ubuntu-12.10 = None ** Changed in: juju (Ubuntu Quantal) Status: Confirmed = Won't Fix ** Changed in: juju (Ubuntu Quantal) Importance: Critical = Wishlist -- 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/1054096 Title: Openstack folsom compatibility (Rackspace Cloud Specifically) To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1054096/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1061277] Re: ssh ignores ssh_config
shouldn't it still generate an error on startup if you get that wrong? -- 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/1061277 Title: ssh ignores ssh_config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1061277/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063857] Re: Cluster controller fails to start because MAAS_URL is not set.
** Branch linked: lp:~andreserl/maas/packaging_updates -- 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/1063857 Title: Cluster controller fails to start because MAAS_URL is not set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1063857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1062518] Re: [FFe] New upstream release
** Branch linked: lp:~andreserl/maas/packaging_updates -- 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/1062518 Title: [FFe] New upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1062518/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063946] [NEW] maas-enlsit does not take power-type and power-settings parameters
Public bug reported: Power settings are not being sent on enlistment. ** Affects: maas-enlist (Ubuntu) Importance: Undecided Assignee: Andres Rodriguez (andreserl) Status: New ** Changed in: maas-enlist (Ubuntu) Assignee: (unassigned) = Andres Rodriguez (andreserl) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas-enlist in Ubuntu. https://bugs.launchpad.net/bugs/1063946 Title: maas-enlsit does not take power-type and power-settings parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1063946/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1050934] Re: VM stops receiving packets on heavy load from virtio network interface briged to a bonded interface on kvm hypervisor
*** This bug is a duplicate of bug 997978 *** https://bugs.launchpad.net/bugs/997978 @Itec I've marked this as a duplicate of 997978 as you suggested above. If you find that the fix for that bug does NOT solve your issue, then please go ahead and un-mark this as a duplicate. ** This bug has been marked a duplicate of bug 997978 KVM images lose connectivity with bridged network -- 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/1050934 Title: VM stops receiving packets on heavy load from virtio network interface briged to a bonded interface on kvm hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1050934/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
** 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 qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063857] Re: Cluster controller fails to start because MAAS_URL is not set.
** Branch linked: lp:~andreserl/maas/packaging_update_cluster -- 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/1063857 Title: Cluster controller fails to start because MAAS_URL is not set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1063857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1063857] Re: Cluster controller fails to start because MAAS_URL is not set.
I've tested the most recent package (0.1+bzr1223+dfsg-0ubuntu1~ppa1) and the problem is fixed. ** Changed in: maas (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1063857 Title: Cluster controller fails to start because MAAS_URL is not set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1063857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1056462] Re: The '--print' option to ceph-authtool is incorrect
I've also queued this patch in the stable branch so that it'll be included in the next stable point release (0.48.3). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1056462 Title: The '--print' option to ceph-authtool is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1056462/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1062518] Re: [FFe] New upstream release
** Description changed:
New MAAS upstream release.
This new upstream release introduces various new features and mayor
bugfixes. Another important thing is that the packaging has changed and
now it ships cluster and region controllers. All of these changes have
been QA'd.
- maas (0.1+bzr1199+dfsg-0ubuntu1) quantal; urgency=low
+ maas (0.1+bzr1223+dfsg-0ubuntu1) quantal; urgency=low
- * New upstream release.
+ * New upstream release. (LP: #1062518)
- [ Julian Edwards ]
- * Ensure isc-dhcp-server is disabled when installing maas-dhcp.
- * Ensure maas-dns creates the maas user before trying to chown files.
- * Make maas-cluster-controller autoconfigure itself when upgrading from the
- old maas package. (LP: #1059416)
- * Add missing prerm file for maas-cluster-controller so that .pyc files
- are cleaned up. (LP: #1059973)
+ [ Julian Edwards ]
+ * Ensure isc-dhcp-server is disabled when installing maas-dhcp.
+ * Ensure maas-dns creates the maas user before trying to chown files.
+ * Make maas-cluster-controller autoconfigure itself when upgrading from the
+ old maas package. (LP: #1059416)
+ * Add missing prerm file for maas-cluster-controller so that .pyc files
+ are cleaned up. (LP: #1059973)
- [ Raphaël Badin ]
- * Split celery config into cluster and region configs.
- * Add region celeryd upstart config.
- * Define CELERY_CONFIG_MODULE in
- maas-cluster-controller.maas-cluster-celery.upstart
+ [ Raphaël Badin ]
+ * Split celery config into cluster and region configs.
+ * Add region celeryd upstart config.
+ * Define CELERY_CONFIG_MODULE in
+ maas-cluster-controller.maas-cluster-celery.upstart
- [ Jeroen Vermeulen ]
- * Make maas_local_celery_config.py non-world readable.
- * Make maas_local_celeryconfig_cluster.py non-world readable.
- * Set root:maas ownership of local cluster config only *after*
- the maas user/group have been created
+ [ Jeroen Vermeulen ]
+ * Make maas_local_celery_config.py non-world readable.
+ * Make maas_local_celeryconfig_cluster.py non-world readable.
+ * Set root:maas ownership of local cluster config only *after*
+ the maas user/group have been created
- [ Andres Rodriguez ]
- * debian/maas-dhcp.postinst: Stop isc-dhcp-server not isc_dhcp_server.
- * debian/maas-region-controller.postinst:
- - Always update passwords on upgrade. No longer check versioning. (LP:
#1060094).
- - Add MAAS server to allowed mirror in squid-deb-proxy
- - Source dbconfig conf file for maas-region-controller on upgrade because
- it writes a new config file and no longer preservers the previous
password.
- * debian/maas-cluster-controller.maas-cluster-celery.upstart: Remove
set{uid/gid}.
- * debian/control: Depends on python-netifaces, python-lxml.
- * debian/maas-region-controller: Install maas-import-squashfs
- * Handle removal of non existant files (LP: #1059556):
- - debian/maintscript: Added to handle removal of conffiles.
- - debian/control: Add Pre-depends and bump debhelper version.
- * update po files for the templates.
- * debian/extras/99-maas: Install in usr/share/maas/conf and symlink to the
- appropriate etc dir.
+ [ Andres Rodriguez ]
+ * debian/maas-dhcp.postinst: Stop isc-dhcp-server not isc_dhcp_server.
+ * debian/maas-region-controller.postinst:
+ - Always update passwords on upgrade. No longer check versioning. (LP:
#1060094).
+ - Add MAAS server to allowed mirror in squid-deb-proxy
+ - Source dbconfig conf file for maas-region-controller on upgrade because
+ it writes a new config file and no longer preservers the previous
password.
+ * debian/maas-cluster-controller.maas-cluster-celery.upstart: Remove
set{uid/gid}.
+ * debian/control: Depends on python-netifaces, python-lxml.
+ * debian/maas-region-controller: Install maas-import-squashfs
+ * Handle removal of non existant files (LP: #1059556):
+ - debian/maintscript: Added to handle removal of conffiles.
+ - debian/control: Add Pre-depends and bump debhelper version.
+ * update po files for the templates.
+ * debian/extras/99-maas: Install in usr/share/maas/conf and symlink to the
+ appropriate etc dir.
+ * debian/maas-cluster-controller.config: Source debconf at the beginning of
the
+ script. (LP: #1063857)
+ * debian/patches/99-temporary-fix-constraints.patch: Fix constraints maaping
+ when deploying with juju. Temporary until it gets merged upstream
- -- Andres Rodriguez andres...@ubuntu.com Thu, 04 Oct 2012 13:34:12
+ [ Robie Basak ]
+ * Add maas-cluster-controller dependency on uuid-runtime, needed for uuidgen
+ by postinst.
+
+ -- Andres Rodriguez andres...@ubuntu.com Mon, 08 Oct 2012 13:10:23
-0400
maas (0.1+bzr1110+dfsg-0ubuntu1) quantal; urgency=low
- * New Upstream Release
+ * New Upstream Release
- [ Julian Edwards ]
- * Split packaging of 'maas' into
[Bug 1062518] Re: [FFe] New upstream release
** Description changed:
New MAAS upstream release.
This new upstream release introduces various new features and mayor
bugfixes. Another important thing is that the packaging has changed and
now it ships cluster and region controllers. All of these changes have
been QA'd.
maas (0.1+bzr1223+dfsg-0ubuntu1) quantal; urgency=low
* New upstream release. (LP: #1062518)
[ Julian Edwards ]
+ * Split packaging of 'maas' into maas-{region,cluster}-controller
+ - debian/control: Update accordingly.
+ - debian/*.install: Move files accordingly
+ - debian/*.{postinst,postrm,preinst}: Move files accordingly.
* Ensure isc-dhcp-server is disabled when installing maas-dhcp.
* Ensure maas-dns creates the maas user before trying to chown files.
* Make maas-cluster-controller autoconfigure itself when upgrading from the
old maas package. (LP: #1059416)
* Add missing prerm file for maas-cluster-controller so that .pyc files
are cleaned up. (LP: #1059973)
[ Raphaël Badin ]
+ * Install maas_local_celeryconfig.py in /etc/maas and symlink to
+ /usr/share/maas.
+ * debian/maas.postinst: Create rabbitmq celery user/vhost.
+ * debian/maas.postinst: Update BROKER_URL in maas_local_celeryconfig.py.
+ * Use maas_local_celeryconfig_cluster.py as the local celery
+ configuration file for the cluster worker.
+ * debian/maas-region-controller.maas-region-celery.upstart: Add region
+ worker upstart script.
+ * Rename cluster worker upstart script into
+ maas-cluster-controller.maas-clluster-celery.upstart.
+ * maas-cluster-controller.maas-celery.upstart: use celeryconfig_cluster
+ as the Celery config module.
+ * debian/maas-common.install: Install celeryconfig_common.py.
+ * debian/maas-cluster-controller.install: Install celeryconfig_cluster.py.
+ * debian/maas-region-controller.install: Install celeryconfig.py.
* Split celery config into cluster and region configs.
* Add region celeryd upstart config.
* Define CELERY_CONFIG_MODULE in
maas-cluster-controller.maas-cluster-celery.upstart
[ Jeroen Vermeulen ]
* Make maas_local_celery_config.py non-world readable.
* Make maas_local_celeryconfig_cluster.py non-world readable.
* Set root:maas ownership of local cluster config only *after*
the maas user/group have been created
[ Andres Rodriguez ]
+ * debian/maas.postinst:
+ - Always restart apache2.
+ - Handle upgrades for new upstream release.
+ - Handle upgrades for celery rabbitmq worker.
+ * Add binary package to install client tool.
+ - debian/extras/maas-cli: Add binary.
+ - debian/maas-cli.install: Add. Install maascli and apiclient.
+ - debian/control: Add binary package.
+ * debian/control:
+ - Depends on freeipmi-tools instead of ipmitool.
+ - Conflicts/Replaces on maas for python-maas-client.
+ - Depends on python-netifaces, python-lxml.
+ * Add python-maas-client binary package:
+ - debian/python-maas-client.install: Add. Install 'apiclient' python
module.
+ - debian/control: Add package. python-django-maas and maas-cli now
+ Depend on it.
+ * debian/rules: Install maas-dhcp-server upstart job.
+ * debian/maas.postrm: Remove celery worker rabbitmq user and host.
+ * debian/extras/99-maas-sudoers: Add for maas-dhcp-server upstart job
+ instead of isc-dhcp-server (LP: #1055951)
+ * debian/maas-region-controller.postinst: Cleanup upgrade rules.
+ * debian/maas-cluster-controller.postinst: Fix 'local' usage.
+ * debian/maas-common.install: Install celeryconfig in appropriate location.
+ * debian/maas-cluster-controller.postrm: Add and delete maas user.
* debian/maas-dhcp.postinst: Stop isc-dhcp-server not isc_dhcp_server.
* debian/maas-region-controller.postinst:
- Always update passwords on upgrade. No longer check versioning. (LP:
#1060094).
- Add MAAS server to allowed mirror in squid-deb-proxy
- Source dbconfig conf file for maas-region-controller on upgrade because
it writes a new config file and no longer preservers the previous
password.
* debian/maas-cluster-controller.maas-cluster-celery.upstart: Remove
set{uid/gid}.
- * debian/control: Depends on python-netifaces, python-lxml.
- * debian/maas-region-controller: Install maas-import-squashfs
+ * debian/maas-region-controller.install: Install maas-import-squashfs
* Handle removal of non existant files (LP: #1059556):
- debian/maintscript: Added to handle removal of conffiles.
- debian/control: Add Pre-depends and bump debhelper version.
* update po files for the templates.
* debian/extras/99-maas: Install in usr/share/maas/conf and symlink to the
appropriate etc dir.
* debian/maas-cluster-controller.config: Source debconf at the beginning of
the
script. (LP: #1063857)
* debian/patches/99-temporary-fix-constraints.patch: Fix constraints maaping
[Bug 1062518] Re: [FFe] New upstream release
This bug was fixed in the package maas - 0.1+bzr1223+dfsg-0ubuntu1
---
maas (0.1+bzr1223+dfsg-0ubuntu1) quantal; urgency=low
* New upstream release. (LP: #1062518)
[ Julian Edwards ]
* Split packaging of 'maas' into maas-{region,cluster}-controller
- debian/control: Update accordingly.
- debian/*.install: Move files accordingly
- debian/*.{postinst,postrm,preinst}: Move files accordingly.
* Ensure isc-dhcp-server is disabled when installing maas-dhcp.
* Ensure maas-dns creates the maas user before trying to chown files.
* Make maas-cluster-controller autoconfigure itself when upgrading from the
old maas package. (LP: #1059416)
* Add missing prerm file for maas-cluster-controller so that .pyc files
are cleaned up. (LP: #1059973)
[ Raphaël Badin ]
* Install maas_local_celeryconfig.py in /etc/maas and symlink to
/usr/share/maas.
* debian/maas.postinst: Create rabbitmq celery user/vhost.
* debian/maas.postinst: Update BROKER_URL in maas_local_celeryconfig.py.
* Use maas_local_celeryconfig_cluster.py as the local celery
configuration file for the cluster worker.
* debian/maas-region-controller.maas-region-celery.upstart: Add region
worker upstart script.
* Rename cluster worker upstart script into
maas-cluster-controller.maas-clluster-celery.upstart.
* maas-cluster-controller.maas-celery.upstart: use celeryconfig_cluster
as the Celery config module.
* debian/maas-common.install: Install celeryconfig_common.py.
* debian/maas-cluster-controller.install: Install celeryconfig_cluster.py.
* debian/maas-region-controller.install: Install celeryconfig.py.
* Split celery config into cluster and region configs.
* Add region celeryd upstart config.
* Define CELERY_CONFIG_MODULE in
maas-cluster-controller.maas-cluster-celery.upstart
[ Jeroen Vermeulen ]
* Make maas_local_celery_config.py non-world readable.
* Make maas_local_celeryconfig_cluster.py non-world readable.
* Set root:maas ownership of local cluster config only *after*
the maas user/group have been created
[ Andres Rodriguez ]
* debian/maas.postinst:
- Always restart apache2.
- Handle upgrades for new upstream release.
- Handle upgrades for celery rabbitmq worker.
* Add binary package to install client tool.
- debian/extras/maas-cli: Add binary.
- debian/maas-cli.install: Add. Install maascli and apiclient.
- debian/control: Add binary package.
* debian/control:
- Depends on freeipmi-tools instead of ipmitool.
- Conflicts/Replaces on maas for python-maas-client.
- Depends on python-netifaces, python-lxml.
* Add python-maas-client binary package:
- debian/python-maas-client.install: Add. Install 'apiclient' python module.
- debian/control: Add package. python-django-maas and maas-cli now
Depend on it.
* debian/rules: Install maas-dhcp-server upstart job.
* debian/maas.postrm: Remove celery worker rabbitmq user and host.
* debian/extras/99-maas-sudoers: Add for maas-dhcp-server upstart job
instead of isc-dhcp-server (LP: #1055951)
* debian/maas-region-controller.postinst: Cleanup upgrade rules.
* debian/maas-cluster-controller.postinst: Fix 'local' usage.
* debian/maas-common.install: Install celeryconfig in appropriate location.
* debian/maas-cluster-controller.postrm: Add and delete maas user.
* debian/maas-dhcp.postinst: Stop isc-dhcp-server not isc_dhcp_server.
* debian/maas-region-controller.postinst:
- Always update passwords on upgrade. No longer check versioning. (LP:
#1060094).
- Add MAAS server to allowed mirror in squid-deb-proxy
- Source dbconfig conf file for maas-region-controller on upgrade because
it writes a new config file and no longer preservers the previous
password.
* debian/maas-cluster-controller.maas-cluster-celery.upstart: Remove
set{uid/gid}.
* debian/maas-region-controller.install: Install maas-import-squashfs
* Handle removal of non existant files (LP: #1059556):
- debian/maintscript: Added to handle removal of conffiles.
- debian/control: Add Pre-depends and bump debhelper version.
* update po files for the templates.
* debian/extras/99-maas: Install in usr/share/maas/conf and symlink to the
appropriate etc dir.
* debian/maas-cluster-controller.config: Source debconf at the beginning of
the
script. (LP: #1063857)
* debian/patches/99-temporary-fix-constraints.patch: Fix constraints maaping
when deploying with juju. Temporary until it gets merged upstream
[ Robie Basak ]
* Add maas-cluster-controller dependency on uuid-runtime, needed for uuidgen
by postinst.
[ Scott Moser ]
* debian/maas-dhcp.{install,apparmor,postrm} install apparmor profile into
/etc/apparmor.d/dhcpd.d (LP: #1049177), and update apparmor profile for
/usr/sbin/dhcpd on install/remove
* get the ip address for the dhcp server in config
[ Diogo Matsubara ]
* Add initial tests to be run by
[Bug 1059973] Re: purging packages can't remove files because dirs are not empty
This bug was fixed in the package maas - 0.1+bzr1223+dfsg-0ubuntu1
---
maas (0.1+bzr1223+dfsg-0ubuntu1) quantal; urgency=low
* New upstream release. (LP: #1062518)
[ Julian Edwards ]
* Split packaging of 'maas' into maas-{region,cluster}-controller
- debian/control: Update accordingly.
- debian/*.install: Move files accordingly
- debian/*.{postinst,postrm,preinst}: Move files accordingly.
* Ensure isc-dhcp-server is disabled when installing maas-dhcp.
* Ensure maas-dns creates the maas user before trying to chown files.
* Make maas-cluster-controller autoconfigure itself when upgrading from the
old maas package. (LP: #1059416)
* Add missing prerm file for maas-cluster-controller so that .pyc files
are cleaned up. (LP: #1059973)
[ Raphaël Badin ]
* Install maas_local_celeryconfig.py in /etc/maas and symlink to
/usr/share/maas.
* debian/maas.postinst: Create rabbitmq celery user/vhost.
* debian/maas.postinst: Update BROKER_URL in maas_local_celeryconfig.py.
* Use maas_local_celeryconfig_cluster.py as the local celery
configuration file for the cluster worker.
* debian/maas-region-controller.maas-region-celery.upstart: Add region
worker upstart script.
* Rename cluster worker upstart script into
maas-cluster-controller.maas-clluster-celery.upstart.
* maas-cluster-controller.maas-celery.upstart: use celeryconfig_cluster
as the Celery config module.
* debian/maas-common.install: Install celeryconfig_common.py.
* debian/maas-cluster-controller.install: Install celeryconfig_cluster.py.
* debian/maas-region-controller.install: Install celeryconfig.py.
* Split celery config into cluster and region configs.
* Add region celeryd upstart config.
* Define CELERY_CONFIG_MODULE in
maas-cluster-controller.maas-cluster-celery.upstart
[ Jeroen Vermeulen ]
* Make maas_local_celery_config.py non-world readable.
* Make maas_local_celeryconfig_cluster.py non-world readable.
* Set root:maas ownership of local cluster config only *after*
the maas user/group have been created
[ Andres Rodriguez ]
* debian/maas.postinst:
- Always restart apache2.
- Handle upgrades for new upstream release.
- Handle upgrades for celery rabbitmq worker.
* Add binary package to install client tool.
- debian/extras/maas-cli: Add binary.
- debian/maas-cli.install: Add. Install maascli and apiclient.
- debian/control: Add binary package.
* debian/control:
- Depends on freeipmi-tools instead of ipmitool.
- Conflicts/Replaces on maas for python-maas-client.
- Depends on python-netifaces, python-lxml.
* Add python-maas-client binary package:
- debian/python-maas-client.install: Add. Install 'apiclient' python module.
- debian/control: Add package. python-django-maas and maas-cli now
Depend on it.
* debian/rules: Install maas-dhcp-server upstart job.
* debian/maas.postrm: Remove celery worker rabbitmq user and host.
* debian/extras/99-maas-sudoers: Add for maas-dhcp-server upstart job
instead of isc-dhcp-server (LP: #1055951)
* debian/maas-region-controller.postinst: Cleanup upgrade rules.
* debian/maas-cluster-controller.postinst: Fix 'local' usage.
* debian/maas-common.install: Install celeryconfig in appropriate location.
* debian/maas-cluster-controller.postrm: Add and delete maas user.
* debian/maas-dhcp.postinst: Stop isc-dhcp-server not isc_dhcp_server.
* debian/maas-region-controller.postinst:
- Always update passwords on upgrade. No longer check versioning. (LP:
#1060094).
- Add MAAS server to allowed mirror in squid-deb-proxy
- Source dbconfig conf file for maas-region-controller on upgrade because
it writes a new config file and no longer preservers the previous
password.
* debian/maas-cluster-controller.maas-cluster-celery.upstart: Remove
set{uid/gid}.
* debian/maas-region-controller.install: Install maas-import-squashfs
* Handle removal of non existant files (LP: #1059556):
- debian/maintscript: Added to handle removal of conffiles.
- debian/control: Add Pre-depends and bump debhelper version.
* update po files for the templates.
* debian/extras/99-maas: Install in usr/share/maas/conf and symlink to the
appropriate etc dir.
* debian/maas-cluster-controller.config: Source debconf at the beginning of
the
script. (LP: #1063857)
* debian/patches/99-temporary-fix-constraints.patch: Fix constraints maaping
when deploying with juju. Temporary until it gets merged upstream
[ Robie Basak ]
* Add maas-cluster-controller dependency on uuid-runtime, needed for uuidgen
by postinst.
[ Scott Moser ]
* debian/maas-dhcp.{install,apparmor,postrm} install apparmor profile into
/etc/apparmor.d/dhcpd.d (LP: #1049177), and update apparmor profile for
/usr/sbin/dhcpd on install/remove
* get the ip address for the dhcp server in config
[ Diogo Matsubara ]
* Add initial tests to be run by
[Bug 1059556] Re: /etc/init/maas-celery.conf not removed on upgrade
This bug was fixed in the package maas - 0.1+bzr1223+dfsg-0ubuntu1
---
maas (0.1+bzr1223+dfsg-0ubuntu1) quantal; urgency=low
* New upstream release. (LP: #1062518)
[ Julian Edwards ]
* Split packaging of 'maas' into maas-{region,cluster}-controller
- debian/control: Update accordingly.
- debian/*.install: Move files accordingly
- debian/*.{postinst,postrm,preinst}: Move files accordingly.
* Ensure isc-dhcp-server is disabled when installing maas-dhcp.
* Ensure maas-dns creates the maas user before trying to chown files.
* Make maas-cluster-controller autoconfigure itself when upgrading from the
old maas package. (LP: #1059416)
* Add missing prerm file for maas-cluster-controller so that .pyc files
are cleaned up. (LP: #1059973)
[ Raphaël Badin ]
* Install maas_local_celeryconfig.py in /etc/maas and symlink to
/usr/share/maas.
* debian/maas.postinst: Create rabbitmq celery user/vhost.
* debian/maas.postinst: Update BROKER_URL in maas_local_celeryconfig.py.
* Use maas_local_celeryconfig_cluster.py as the local celery
configuration file for the cluster worker.
* debian/maas-region-controller.maas-region-celery.upstart: Add region
worker upstart script.
* Rename cluster worker upstart script into
maas-cluster-controller.maas-clluster-celery.upstart.
* maas-cluster-controller.maas-celery.upstart: use celeryconfig_cluster
as the Celery config module.
* debian/maas-common.install: Install celeryconfig_common.py.
* debian/maas-cluster-controller.install: Install celeryconfig_cluster.py.
* debian/maas-region-controller.install: Install celeryconfig.py.
* Split celery config into cluster and region configs.
* Add region celeryd upstart config.
* Define CELERY_CONFIG_MODULE in
maas-cluster-controller.maas-cluster-celery.upstart
[ Jeroen Vermeulen ]
* Make maas_local_celery_config.py non-world readable.
* Make maas_local_celeryconfig_cluster.py non-world readable.
* Set root:maas ownership of local cluster config only *after*
the maas user/group have been created
[ Andres Rodriguez ]
* debian/maas.postinst:
- Always restart apache2.
- Handle upgrades for new upstream release.
- Handle upgrades for celery rabbitmq worker.
* Add binary package to install client tool.
- debian/extras/maas-cli: Add binary.
- debian/maas-cli.install: Add. Install maascli and apiclient.
- debian/control: Add binary package.
* debian/control:
- Depends on freeipmi-tools instead of ipmitool.
- Conflicts/Replaces on maas for python-maas-client.
- Depends on python-netifaces, python-lxml.
* Add python-maas-client binary package:
- debian/python-maas-client.install: Add. Install 'apiclient' python module.
- debian/control: Add package. python-django-maas and maas-cli now
Depend on it.
* debian/rules: Install maas-dhcp-server upstart job.
* debian/maas.postrm: Remove celery worker rabbitmq user and host.
* debian/extras/99-maas-sudoers: Add for maas-dhcp-server upstart job
instead of isc-dhcp-server (LP: #1055951)
* debian/maas-region-controller.postinst: Cleanup upgrade rules.
* debian/maas-cluster-controller.postinst: Fix 'local' usage.
* debian/maas-common.install: Install celeryconfig in appropriate location.
* debian/maas-cluster-controller.postrm: Add and delete maas user.
* debian/maas-dhcp.postinst: Stop isc-dhcp-server not isc_dhcp_server.
* debian/maas-region-controller.postinst:
- Always update passwords on upgrade. No longer check versioning. (LP:
#1060094).
- Add MAAS server to allowed mirror in squid-deb-proxy
- Source dbconfig conf file for maas-region-controller on upgrade because
it writes a new config file and no longer preservers the previous
password.
* debian/maas-cluster-controller.maas-cluster-celery.upstart: Remove
set{uid/gid}.
* debian/maas-region-controller.install: Install maas-import-squashfs
* Handle removal of non existant files (LP: #1059556):
- debian/maintscript: Added to handle removal of conffiles.
- debian/control: Add Pre-depends and bump debhelper version.
* update po files for the templates.
* debian/extras/99-maas: Install in usr/share/maas/conf and symlink to the
appropriate etc dir.
* debian/maas-cluster-controller.config: Source debconf at the beginning of
the
script. (LP: #1063857)
* debian/patches/99-temporary-fix-constraints.patch: Fix constraints maaping
when deploying with juju. Temporary until it gets merged upstream
[ Robie Basak ]
* Add maas-cluster-controller dependency on uuid-runtime, needed for uuidgen
by postinst.
[ Scott Moser ]
* debian/maas-dhcp.{install,apparmor,postrm} install apparmor profile into
/etc/apparmor.d/dhcpd.d (LP: #1049177), and update apparmor profile for
/usr/sbin/dhcpd on install/remove
* get the ip address for the dhcp server in config
[ Diogo Matsubara ]
* Add initial tests to be run by
[Bug 1055951] Re: maas-dhcp has no sudoers permission to start maas-dhcp-server
This bug was fixed in the package maas - 0.1+bzr1223+dfsg-0ubuntu1
---
maas (0.1+bzr1223+dfsg-0ubuntu1) quantal; urgency=low
* New upstream release. (LP: #1062518)
[ Julian Edwards ]
* Split packaging of 'maas' into maas-{region,cluster}-controller
- debian/control: Update accordingly.
- debian/*.install: Move files accordingly
- debian/*.{postinst,postrm,preinst}: Move files accordingly.
* Ensure isc-dhcp-server is disabled when installing maas-dhcp.
* Ensure maas-dns creates the maas user before trying to chown files.
* Make maas-cluster-controller autoconfigure itself when upgrading from the
old maas package. (LP: #1059416)
* Add missing prerm file for maas-cluster-controller so that .pyc files
are cleaned up. (LP: #1059973)
[ Raphaël Badin ]
* Install maas_local_celeryconfig.py in /etc/maas and symlink to
/usr/share/maas.
* debian/maas.postinst: Create rabbitmq celery user/vhost.
* debian/maas.postinst: Update BROKER_URL in maas_local_celeryconfig.py.
* Use maas_local_celeryconfig_cluster.py as the local celery
configuration file for the cluster worker.
* debian/maas-region-controller.maas-region-celery.upstart: Add region
worker upstart script.
* Rename cluster worker upstart script into
maas-cluster-controller.maas-clluster-celery.upstart.
* maas-cluster-controller.maas-celery.upstart: use celeryconfig_cluster
as the Celery config module.
* debian/maas-common.install: Install celeryconfig_common.py.
* debian/maas-cluster-controller.install: Install celeryconfig_cluster.py.
* debian/maas-region-controller.install: Install celeryconfig.py.
* Split celery config into cluster and region configs.
* Add region celeryd upstart config.
* Define CELERY_CONFIG_MODULE in
maas-cluster-controller.maas-cluster-celery.upstart
[ Jeroen Vermeulen ]
* Make maas_local_celery_config.py non-world readable.
* Make maas_local_celeryconfig_cluster.py non-world readable.
* Set root:maas ownership of local cluster config only *after*
the maas user/group have been created
[ Andres Rodriguez ]
* debian/maas.postinst:
- Always restart apache2.
- Handle upgrades for new upstream release.
- Handle upgrades for celery rabbitmq worker.
* Add binary package to install client tool.
- debian/extras/maas-cli: Add binary.
- debian/maas-cli.install: Add. Install maascli and apiclient.
- debian/control: Add binary package.
* debian/control:
- Depends on freeipmi-tools instead of ipmitool.
- Conflicts/Replaces on maas for python-maas-client.
- Depends on python-netifaces, python-lxml.
* Add python-maas-client binary package:
- debian/python-maas-client.install: Add. Install 'apiclient' python module.
- debian/control: Add package. python-django-maas and maas-cli now
Depend on it.
* debian/rules: Install maas-dhcp-server upstart job.
* debian/maas.postrm: Remove celery worker rabbitmq user and host.
* debian/extras/99-maas-sudoers: Add for maas-dhcp-server upstart job
instead of isc-dhcp-server (LP: #1055951)
* debian/maas-region-controller.postinst: Cleanup upgrade rules.
* debian/maas-cluster-controller.postinst: Fix 'local' usage.
* debian/maas-common.install: Install celeryconfig in appropriate location.
* debian/maas-cluster-controller.postrm: Add and delete maas user.
* debian/maas-dhcp.postinst: Stop isc-dhcp-server not isc_dhcp_server.
* debian/maas-region-controller.postinst:
- Always update passwords on upgrade. No longer check versioning. (LP:
#1060094).
- Add MAAS server to allowed mirror in squid-deb-proxy
- Source dbconfig conf file for maas-region-controller on upgrade because
it writes a new config file and no longer preservers the previous
password.
* debian/maas-cluster-controller.maas-cluster-celery.upstart: Remove
set{uid/gid}.
* debian/maas-region-controller.install: Install maas-import-squashfs
* Handle removal of non existant files (LP: #1059556):
- debian/maintscript: Added to handle removal of conffiles.
- debian/control: Add Pre-depends and bump debhelper version.
* update po files for the templates.
* debian/extras/99-maas: Install in usr/share/maas/conf and symlink to the
appropriate etc dir.
* debian/maas-cluster-controller.config: Source debconf at the beginning of
the
script. (LP: #1063857)
* debian/patches/99-temporary-fix-constraints.patch: Fix constraints maaping
when deploying with juju. Temporary until it gets merged upstream
[ Robie Basak ]
* Add maas-cluster-controller dependency on uuid-runtime, needed for uuidgen
by postinst.
[ Scott Moser ]
* debian/maas-dhcp.{install,apparmor,postrm} install apparmor profile into
/etc/apparmor.d/dhcpd.d (LP: #1049177), and update apparmor profile for
/usr/sbin/dhcpd on install/remove
* get the ip address for the dhcp server in config
[ Diogo Matsubara ]
* Add initial tests to be run by
[Bug 1049177] Re: isc-dhcp-server apparmor profile should have include .d
This bug was fixed in the package maas - 0.1+bzr1223+dfsg-0ubuntu1
---
maas (0.1+bzr1223+dfsg-0ubuntu1) quantal; urgency=low
* New upstream release. (LP: #1062518)
[ Julian Edwards ]
* Split packaging of 'maas' into maas-{region,cluster}-controller
- debian/control: Update accordingly.
- debian/*.install: Move files accordingly
- debian/*.{postinst,postrm,preinst}: Move files accordingly.
* Ensure isc-dhcp-server is disabled when installing maas-dhcp.
* Ensure maas-dns creates the maas user before trying to chown files.
* Make maas-cluster-controller autoconfigure itself when upgrading from the
old maas package. (LP: #1059416)
* Add missing prerm file for maas-cluster-controller so that .pyc files
are cleaned up. (LP: #1059973)
[ Raphaël Badin ]
* Install maas_local_celeryconfig.py in /etc/maas and symlink to
/usr/share/maas.
* debian/maas.postinst: Create rabbitmq celery user/vhost.
* debian/maas.postinst: Update BROKER_URL in maas_local_celeryconfig.py.
* Use maas_local_celeryconfig_cluster.py as the local celery
configuration file for the cluster worker.
* debian/maas-region-controller.maas-region-celery.upstart: Add region
worker upstart script.
* Rename cluster worker upstart script into
maas-cluster-controller.maas-clluster-celery.upstart.
* maas-cluster-controller.maas-celery.upstart: use celeryconfig_cluster
as the Celery config module.
* debian/maas-common.install: Install celeryconfig_common.py.
* debian/maas-cluster-controller.install: Install celeryconfig_cluster.py.
* debian/maas-region-controller.install: Install celeryconfig.py.
* Split celery config into cluster and region configs.
* Add region celeryd upstart config.
* Define CELERY_CONFIG_MODULE in
maas-cluster-controller.maas-cluster-celery.upstart
[ Jeroen Vermeulen ]
* Make maas_local_celery_config.py non-world readable.
* Make maas_local_celeryconfig_cluster.py non-world readable.
* Set root:maas ownership of local cluster config only *after*
the maas user/group have been created
[ Andres Rodriguez ]
* debian/maas.postinst:
- Always restart apache2.
- Handle upgrades for new upstream release.
- Handle upgrades for celery rabbitmq worker.
* Add binary package to install client tool.
- debian/extras/maas-cli: Add binary.
- debian/maas-cli.install: Add. Install maascli and apiclient.
- debian/control: Add binary package.
* debian/control:
- Depends on freeipmi-tools instead of ipmitool.
- Conflicts/Replaces on maas for python-maas-client.
- Depends on python-netifaces, python-lxml.
* Add python-maas-client binary package:
- debian/python-maas-client.install: Add. Install 'apiclient' python module.
- debian/control: Add package. python-django-maas and maas-cli now
Depend on it.
* debian/rules: Install maas-dhcp-server upstart job.
* debian/maas.postrm: Remove celery worker rabbitmq user and host.
* debian/extras/99-maas-sudoers: Add for maas-dhcp-server upstart job
instead of isc-dhcp-server (LP: #1055951)
* debian/maas-region-controller.postinst: Cleanup upgrade rules.
* debian/maas-cluster-controller.postinst: Fix 'local' usage.
* debian/maas-common.install: Install celeryconfig in appropriate location.
* debian/maas-cluster-controller.postrm: Add and delete maas user.
* debian/maas-dhcp.postinst: Stop isc-dhcp-server not isc_dhcp_server.
* debian/maas-region-controller.postinst:
- Always update passwords on upgrade. No longer check versioning. (LP:
#1060094).
- Add MAAS server to allowed mirror in squid-deb-proxy
- Source dbconfig conf file for maas-region-controller on upgrade because
it writes a new config file and no longer preservers the previous
password.
* debian/maas-cluster-controller.maas-cluster-celery.upstart: Remove
set{uid/gid}.
* debian/maas-region-controller.install: Install maas-import-squashfs
* Handle removal of non existant files (LP: #1059556):
- debian/maintscript: Added to handle removal of conffiles.
- debian/control: Add Pre-depends and bump debhelper version.
* update po files for the templates.
* debian/extras/99-maas: Install in usr/share/maas/conf and symlink to the
appropriate etc dir.
* debian/maas-cluster-controller.config: Source debconf at the beginning of
the
script. (LP: #1063857)
* debian/patches/99-temporary-fix-constraints.patch: Fix constraints maaping
when deploying with juju. Temporary until it gets merged upstream
[ Robie Basak ]
* Add maas-cluster-controller dependency on uuid-runtime, needed for uuidgen
by postinst.
[ Scott Moser ]
* debian/maas-dhcp.{install,apparmor,postrm} install apparmor profile into
/etc/apparmor.d/dhcpd.d (LP: #1049177), and update apparmor profile for
/usr/sbin/dhcpd on install/remove
* get the ip address for the dhcp server in config
[ Diogo Matsubara ]
* Add initial tests to be run by
[Bug 1060549] Re: maas-dns fails to install because maas user hasn't been created yet
** Changed in: maas (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1060549 Title: maas-dns fails to install because maas user hasn't been created yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1060549/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1060237] Re: apt-get install maas maas-dhcp maas-dns fails
** Changed in: maas (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1060237 Title: apt-get install maas maas-dhcp maas-dns fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1060237/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1050185] Re: dhcpd.conf is not updated after dpkg-reconfigure maas
Marking this as invalid given that maas-dhcp does not longer handles this. ** Changed in: maas (Ubuntu) Status: Confirmed = Invalid -- 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/1050185 Title: dhcpd.conf is not updated after dpkg-reconfigure maas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1050185/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064096] [NEW] Please update clamav to 0.97.6
Public bug reported: [IMPACT] * Providing this bugfix only update to clamav will, in addition to providing the fixes included in the update, allow users of current Ubuntu releases to process all virus signatures for clamav (release increases the FLEVEL, so there will be signatures older releases can't use). [TESTCASE] * Install the clamav packages you use and verify they continue to work as expected. * We also need to run the Security Team's QA regression test for clamav (see https://code.launchpad.net/~ubuntu-bugcontrol/qa-regression- testing/master) as described at https://wiki.ubuntu.com/ClamavUpdates [Regression Potential] * Regression risks are minimal. Packages will be uploaded and tested in the Ubuntu Clamav PPA prior to upload to *-proposed. [Other Info] * Clamav has a micro-release exception from the Ubuntu Tech Board. ** Affects: hardy-backports Importance: Undecided Status: New ** Affects: lucid-backports Importance: Undecided Status: New ** Affects: clamav (Ubuntu) Importance: High Assignee: Scott Kitterman (kitterman) Status: Fix Released ** Affects: clamav (Ubuntu Natty) Importance: High Assignee: Scott Kitterman (kitterman) Status: In Progress ** Affects: clamav (Ubuntu Oneiric) Importance: High Assignee: Scott Kitterman (kitterman) Status: In Progress ** Affects: clamav (Ubuntu Precise) Importance: High Assignee: Scott Kitterman (kitterman) Status: In Progress ** Also affects: clamav (Ubuntu Natty) Importance: Undecided Status: New ** Also affects: clamav (Ubuntu Oneiric) Importance: Undecided Status: New ** Also affects: clamav (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: lucid-backports Importance: Undecided Status: New ** Also affects: hardy-backports Importance: Undecided Status: New ** Changed in: clamav (Ubuntu) Status: New = Fix Released ** Changed in: clamav (Ubuntu) Importance: Undecided = High ** Changed in: clamav (Ubuntu) Assignee: (unassigned) = Scott Kitterman (kitterman) ** Changed in: clamav (Ubuntu Natty) Status: New = In Progress ** Changed in: clamav (Ubuntu Oneiric) Status: New = In Progress ** Changed in: clamav (Ubuntu Precise) Status: New = In Progress ** Changed in: clamav (Ubuntu Natty) Importance: Undecided = High ** Changed in: clamav (Ubuntu Oneiric) Importance: Undecided = High ** Changed in: clamav (Ubuntu Precise) Importance: Undecided = High ** Changed in: clamav (Ubuntu Natty) Assignee: (unassigned) = Scott Kitterman (kitterman) ** Changed in: clamav (Ubuntu Oneiric) Assignee: (unassigned) = Scott Kitterman (kitterman) ** Changed in: clamav (Ubuntu Precise) Assignee: (unassigned) = Scott Kitterman (kitterman) ** Changed in: clamav (Ubuntu Precise) Milestone: None = ubuntu-12.04.2 ** Changed in: clamav (Ubuntu Oneiric) Milestone: None = oneiric-updates ** Changed in: clamav (Ubuntu Natty) Milestone: None = natty-updates ** Changed in: clamav (Ubuntu) Milestone: None = ubuntu-12.10 -- 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/1064096 Title: Please update clamav to 0.97.6 To manage notifications about this bug go to: https://bugs.launchpad.net/hardy-backports/+bug/1064096/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064096] Re: Please update clamav to 0.97.6
Packages for hardy/lucid/natty/oneiric/precise uploaded to clamav ppa. -- 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/1064096 Title: Please update clamav to 0.97.6 To manage notifications about this bug go to: https://bugs.launchpad.net/hardy-backports/+bug/1064096/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 925609] Re: install throws errors about SADeprecationWarning
** Changed in: glance Status: Fix Released = In Progress ** Changed in: glance Assignee: Chuck Short (zulcss) = David Ripton (dripton) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/925609 Title: install throws errors about SADeprecationWarning To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/925609/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
