[Bug 578176] Re: ospfd crashes with assertion failed on lucid
*** This bug is a duplicate of bug 523812 *** https://bugs.launchpad.net/bugs/523812 I've now had 0.99.20 running fully stable for 24 hours. My ospfd issues have gone and everything appears to be much more stable. It seems a lot of ospfd issues were patched upstream at 0.99.18+ For reference, i'm using the ubuntu quagga_0.99.20-3_amd64.deb package (from 12.04LTS beta) on our production 10.04LTS boxes. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quagga in Ubuntu. https://bugs.launchpad.net/bugs/578176 Title: ospfd crashes with assertion failed on lucid To manage notifications about this bug go to: https://bugs.launchpad.net/quagga/+bug/578176/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 944684] [NEW] Error installing keystone selecting dbconfig-common and sqlite3 as the backend
Public bug reported: Dialog selections: select configure database for keystone with dbconfig-common select sqlite3 dpkg output: - Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: keystone 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/14.9 kB of archives. After this operation, 126 kB of additional disk space will be used. ySelecting previously unselected package keystone. (Reading database ... 296043 files and directories currently installed.) Unpacking keystone (from .../keystone_2012.1~e4~20120203.1574-0ubuntu3_all.deb) ... Processing triggers for man-db ... Processing triggers for ureadahead ... Setting up keystone (2012.1~e4~20120203.1574-0ubuntu3) ... dbconfig-common: writing config to /etc/dbconfig-common/keystone.conf Creating config file /etc/dbconfig-common/keystone.conf with new version creating database keystone: success. verifying database keystone exists: success. SUCCESS: Role Admin created successfully. SUCCESS: Role Member created successfully. SUCCESS: Role KeystoneAdmin created successfully. SUCCESS: Role KeystoneServiceAdmin created successfully. SUCCESS: Role sysadmin created successfully. SUCCESS: Role netadmin created successfully. Traceback (most recent call last): File /usr/bin/keystone-manage, line 35, in module keystone.manage2.main() File /usr/lib/python2.7/dist-packages/keystone/manage2/__init__.py, line 107, in main exit(cmd.run(args)) File /usr/lib/python2.7/dist-packages/keystone/manage2/commands/sync_database.py, line 19, in run self.sync_database(version=args.version) File /usr/lib/python2.7/dist-packages/keystone/manage2/commands/sync_database.py, line 15, in sync_database migration.db_sync(Command._get_connection_string(), version=version) File /usr/lib/python2.7/dist-packages/keystone/backends/sqlalchemy/migration.py, line 168, in db_sync _version_control(sql_connection) File /usr/lib/python2.7/dist-packages/keystone/backends/sqlalchemy/migration.py, line 157, in _version_control return versioning_api.version_control(sql_connection, repo_path) File string, line 2, in version_control File /usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py, line 159, in with_engine return f(*a, **kw) File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 250, in version_control ControlledSchema.create(engine, repository, version) File /usr/lib/python2.7/dist-packages/migrate/versioning/schema.py, line 139, in create table = cls._create_table_version(engine, repository, version) File /usr/lib/python2.7/dist-packages/migrate/versioning/schema.py, line 180, in _create_table_version if not table.exists(): File /usr/lib/python2.7/dist-packages/sqlalchemy/schema.py, line 549, in exists self.name, schema=self.schema) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 2274, in run_callable conn = self.contextual_connect() File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 2340, in contextual_connect self.pool.connect(), File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 210, in connect return _ConnectionFairy(self).checkout() File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 371, in __init__ rec = self._connection_record = pool._do_get() File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 758, in _do_get return self._create_connection() File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 174, in _create_connection return _ConnectionRecord(self) File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 256, in __init__ self.connection = self.__connect() File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 316, in __connect connection = self.__pool._creator() File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/strategies.py, line 80, in connect return dialect.connect(*cargs, **cparams) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py, line 280, in connect return self.dbapi.connect(*cargs, **cparams) sqlalchemy.exc.OperationalError: (OperationalError) unable to open database file None None dpkg: error processing keystone (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: keystone E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: keystone 2012.1~e4~20120203.1574-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.93-0ubuntu2 Architecture: amd64 CheckboxSubmission: dd51e7fcfe82b504f848036cca204d88 CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b Date: Fri Mar 2 11:20:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10
[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/944684 Title: Error installing keystone selecting dbconfig-common and sqlite3 as the backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/944684/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend
First clean keystone install. ** Branch linked: lp:~openstack-ubuntu-packagers/keystone/ubuntu -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/944684 Title: Error installing keystone selecting dbconfig-common and sqlite3 as the backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/944684/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend
Thanks for this bug report. Today, keystone should have a major change, which has been held back until now. The 'upstream' of keystone has performed a rewrite, which should land today. I'd be interested if you could try to reproduce this after it is uploaded. Thanks. ** Changed in: keystone (Ubuntu) Status: New = Incomplete ** Changed in: keystone (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/944684 Title: Error installing keystone selecting dbconfig-common and sqlite3 as the backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/944684/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 934064] Re: Installing openstack-dashboard on Precise removes Keystone package
** Changed in: keystone (Ubuntu) Status: New = Triaged ** Changed in: openstack-dashboard (Ubuntu) Status: New = Triaged ** Changed in: keystone (Ubuntu) Assignee: (unassigned) = Chuck Short (zulcss) ** Changed in: openstack-dashboard (Ubuntu) Assignee: (unassigned) = Chuck Short (zulcss) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/934064 Title: Installing openstack-dashboard on Precise removes Keystone package To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/934064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 911812] Re: processor fact does not handle arm, others
It looks like this patch is already applied in Precise, based on a visual inspection of /usr/lib/ruby/1.8/facter/util/processor.rb. On a Pandaboard freshly installed with a Precise armhf netinst today: root@panda0:~# facter processorcount 2 root@panda0:~# facter processor0 processor1 processor0 = ARMv7 Processor rev 2 (v7l) processor1 = ARMv7 Processor rev 2 (v7l) root@panda0:~# facter physicalprocessorcount 1 root@panda0:~# dpkg-query -W facter facter 1.6.5-1ubuntu1 LaMont: is this the behaviour you are expecting? ** Changed in: facter (Ubuntu Precise) Assignee: Andres Rodriguez (andreserl) = Robie Basak (racb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/911812 Title: processor fact does not handle arm, others To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/911812/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 934064] Re: Installing openstack-dashboard on Precise removes Keystone package
This will be fixed in today's upload. ** Changed in: python-keystoneclient (Ubuntu) Status: Confirmed = In Progress ** Changed in: openstack-dashboard (Ubuntu) Status: Triaged = In Progress ** Changed in: keystone (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/934064 Title: Installing openstack-dashboard on Precise removes Keystone package To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/934064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 911812] Re: processor fact does not handle arm, others
rbasak lamont: can I mark the bug Fix Released for precise, or would you like to check further first? lamont 'tever - if it's returning good facts, I'm happy ** Changed in: facter (Ubuntu Precise) Status: Triaged = Fix Released ** Changed in: facter (Ubuntu Precise) Assignee: Robie Basak (racb) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/911812 Title: processor fact does not handle arm, others To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/911812/+subscriptions -- Ubuntu-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-p-php54] PHP 5.4 for Ubuntu 12.04
Blueprint changed by Clemens Kalb: Whiteboard changed: Status: 5.4 has not released yet, though it is in final rc stages. Debian has not been tracking the RC's, nor have we been able to devote enough resources to that in Ubuntu. Given the proximity to feature freeze and low priority given to this task, it looks like we'll ship 5.3. Work items: [ubuntu-server] In january, assess situation based on Debian status and decide 5.4 or 5.3 then: DONE [clint-fewbar] maintain a merged 5.4 in a PPA for until archive decision is made: POSTPONED [clint-fewbar] setup rebuilds for extensions that build-dep on php5-dev: POSTPONED [clint-fewbar] setup backport for lucid to allow wider PHP 5.4 testing before the upgrade: POSTPONED Question: Does this require discussion or just rubber stamping? -- Daviey Answer: It is not entirely clear whether 5.4.0 will be sufficiently similar to 5.3.x to include in this release. The more conservative approach is just to ship 5.3.9 or 5.3.10 and leave 5.4.0 for 12.10, but the PHP community is interested in weighing in on the issue and I'd also like to hear the security team's take on the matter. * provide packages for both precise and lucid in the ppa (or lucid-backports) so people can test before upgrade * provide rebuilt extensions against the new ABI + + Question: + With both PHP 5.4.0 final and Ubuntu 12.04 Beta 1 released today, is it correct to assume that the chances of PHP 5.4 being shipped with Ubuntu 12.04 are basically non existant? -Clemens -- PHP 5.4 for Ubuntu 12.04 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-php54 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 942850] Re: lxc-ubuntu: don't fail if getent group returns error
This bug was fixed in the package lxc - 0.7.5-3ubuntu31 --- lxc (0.7.5-3ubuntu31) precise; urgency=low * 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a snapshot of the same size as the original. (LP: #939765) * run our dnsmasq as user 'lxc-dnsmasq' (LP: #939774) - add debian/lxc.postinst to create the user - debian/lxc.lxc-net.upstart: run dnsmasq as lxc-dnsmasq user * 0051-lxc-create-lvm-use-1G: bump lvm blockdev size to 1G (LP: #942338) * 0052-ubuntu-bind-user-conflict: don't create 'ubuntu' user when a user gets bound in. (LP: #942144) * 0053-lxc-start-pin-rootfs: don't let the container remount an underlying shared fs readonly (LP: #942325) * 0054-ubuntu-debug: add --debug option to ubuntu and ubuntu-cloud templates (LP: #942847) * 0055-ubuntu-handle-badgrp: fix the group handling to not assume a user's group has the user's name. (LP: #942850) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 28 Feb 2012 15:03:45 -0600 ** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/942850 Title: lxc-ubuntu: don't fail if getent group returns error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/942850/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 942847] Re: add a debug option to lxc-ubuntu template
This bug was fixed in the package lxc - 0.7.5-3ubuntu31 --- lxc (0.7.5-3ubuntu31) precise; urgency=low * 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a snapshot of the same size as the original. (LP: #939765) * run our dnsmasq as user 'lxc-dnsmasq' (LP: #939774) - add debian/lxc.postinst to create the user - debian/lxc.lxc-net.upstart: run dnsmasq as lxc-dnsmasq user * 0051-lxc-create-lvm-use-1G: bump lvm blockdev size to 1G (LP: #942338) * 0052-ubuntu-bind-user-conflict: don't create 'ubuntu' user when a user gets bound in. (LP: #942144) * 0053-lxc-start-pin-rootfs: don't let the container remount an underlying shared fs readonly (LP: #942325) * 0054-ubuntu-debug: add --debug option to ubuntu and ubuntu-cloud templates (LP: #942847) * 0055-ubuntu-handle-badgrp: fix the group handling to not assume a user's group has the user's name. (LP: #942850) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 28 Feb 2012 15:03:45 -0600 ** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/942847 Title: add a debug option to lxc-ubuntu template To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/942847/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 942338] Re: Make default lvm blockdev size 1G
This bug was fixed in the package lxc - 0.7.5-3ubuntu31 --- lxc (0.7.5-3ubuntu31) precise; urgency=low * 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a snapshot of the same size as the original. (LP: #939765) * run our dnsmasq as user 'lxc-dnsmasq' (LP: #939774) - add debian/lxc.postinst to create the user - debian/lxc.lxc-net.upstart: run dnsmasq as lxc-dnsmasq user * 0051-lxc-create-lvm-use-1G: bump lvm blockdev size to 1G (LP: #942338) * 0052-ubuntu-bind-user-conflict: don't create 'ubuntu' user when a user gets bound in. (LP: #942144) * 0053-lxc-start-pin-rootfs: don't let the container remount an underlying shared fs readonly (LP: #942325) * 0054-ubuntu-debug: add --debug option to ubuntu and ubuntu-cloud templates (LP: #942847) * 0055-ubuntu-handle-badgrp: fix the group handling to not assume a user's group has the user's name. (LP: #942850) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 28 Feb 2012 15:03:45 -0600 ** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/942338 Title: Make default lvm blockdev size 1G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/942338/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 942325] Re: keep container from marking shared rootfs readonly on shutdown
This bug was fixed in the package lxc - 0.7.5-3ubuntu31 --- lxc (0.7.5-3ubuntu31) precise; urgency=low * 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a snapshot of the same size as the original. (LP: #939765) * run our dnsmasq as user 'lxc-dnsmasq' (LP: #939774) - add debian/lxc.postinst to create the user - debian/lxc.lxc-net.upstart: run dnsmasq as lxc-dnsmasq user * 0051-lxc-create-lvm-use-1G: bump lvm blockdev size to 1G (LP: #942338) * 0052-ubuntu-bind-user-conflict: don't create 'ubuntu' user when a user gets bound in. (LP: #942144) * 0053-lxc-start-pin-rootfs: don't let the container remount an underlying shared fs readonly (LP: #942325) * 0054-ubuntu-debug: add --debug option to ubuntu and ubuntu-cloud templates (LP: #942847) * 0055-ubuntu-handle-badgrp: fix the group handling to not assume a user's group has the user's name. (LP: #942850) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 28 Feb 2012 15:03:45 -0600 ** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/942325 Title: keep container from marking shared rootfs readonly on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/942325/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 942144] Re: Using bindhome option of ubuntu template conflicts with ubuntu user
This bug was fixed in the package lxc - 0.7.5-3ubuntu31 --- lxc (0.7.5-3ubuntu31) precise; urgency=low * 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a snapshot of the same size as the original. (LP: #939765) * run our dnsmasq as user 'lxc-dnsmasq' (LP: #939774) - add debian/lxc.postinst to create the user - debian/lxc.lxc-net.upstart: run dnsmasq as lxc-dnsmasq user * 0051-lxc-create-lvm-use-1G: bump lvm blockdev size to 1G (LP: #942338) * 0052-ubuntu-bind-user-conflict: don't create 'ubuntu' user when a user gets bound in. (LP: #942144) * 0053-lxc-start-pin-rootfs: don't let the container remount an underlying shared fs readonly (LP: #942325) * 0054-ubuntu-debug: add --debug option to ubuntu and ubuntu-cloud templates (LP: #942847) * 0055-ubuntu-handle-badgrp: fix the group handling to not assume a user's group has the user's name. (LP: #942850) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 28 Feb 2012 15:03:45 -0600 ** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/942144 Title: Using bindhome option of ubuntu template conflicts with ubuntu user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/942144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 939774] Re: dnsmasq should run as lxc-dnsmasq user
This bug was fixed in the package lxc - 0.7.5-3ubuntu31 --- lxc (0.7.5-3ubuntu31) precise; urgency=low * 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a snapshot of the same size as the original. (LP: #939765) * run our dnsmasq as user 'lxc-dnsmasq' (LP: #939774) - add debian/lxc.postinst to create the user - debian/lxc.lxc-net.upstart: run dnsmasq as lxc-dnsmasq user * 0051-lxc-create-lvm-use-1G: bump lvm blockdev size to 1G (LP: #942338) * 0052-ubuntu-bind-user-conflict: don't create 'ubuntu' user when a user gets bound in. (LP: #942144) * 0053-lxc-start-pin-rootfs: don't let the container remount an underlying shared fs readonly (LP: #942325) * 0054-ubuntu-debug: add --debug option to ubuntu and ubuntu-cloud templates (LP: #942847) * 0055-ubuntu-handle-badgrp: fix the group handling to not assume a user's group has the user's name. (LP: #942850) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 28 Feb 2012 15:03:45 -0600 ** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/939774 Title: dnsmasq should run as lxc-dnsmasq user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/939774/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 939765] Re: lxc-clone should duplicate original size for lvm devices
This bug was fixed in the package lxc - 0.7.5-3ubuntu31 --- lxc (0.7.5-3ubuntu31) precise; urgency=low * 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a snapshot of the same size as the original. (LP: #939765) * run our dnsmasq as user 'lxc-dnsmasq' (LP: #939774) - add debian/lxc.postinst to create the user - debian/lxc.lxc-net.upstart: run dnsmasq as lxc-dnsmasq user * 0051-lxc-create-lvm-use-1G: bump lvm blockdev size to 1G (LP: #942338) * 0052-ubuntu-bind-user-conflict: don't create 'ubuntu' user when a user gets bound in. (LP: #942144) * 0053-lxc-start-pin-rootfs: don't let the container remount an underlying shared fs readonly (LP: #942325) * 0054-ubuntu-debug: add --debug option to ubuntu and ubuntu-cloud templates (LP: #942847) * 0055-ubuntu-handle-badgrp: fix the group handling to not assume a user's group has the user's name. (LP: #942850) -- Serge Hallyn serge.hal...@ubuntu.com Tue, 28 Feb 2012 15:03:45 -0600 ** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/939765 Title: lxc-clone should duplicate original size for lvm devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/939765/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 930916] Re: amavis start-stop script fails to stop amavisd
Attached Fix. ** Patch added: Patch https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/930916/+attachment/2801291/+files/amavisd-new_2.6.5-0ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/930916 Title: amavis start-stop script fails to stop amavisd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/930916/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 930916] Re: amavis start-stop script fails to stop amavisd
Thanks Vibhav for your work on this. Can you verify that in your patch you replaced the old debian/amavisd- new.init with the new debian/amavisd-new.init? Because the changes in the attached patch are rather large. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/930916 Title: amavis start-stop script fails to stop amavisd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/930916/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 944866] [NEW] Sync puppet 2.7.11-1 (main) from Debian sid (main)
Public bug reported: Please sync puppet 2.7.11-1 (main) from Debian sid (main) Explanation of the Ubuntu delta and why it can be dropped: * Use maintscript support in dh_installdeb rather than writing out dpkg-maintscript-helper commands by hand. We now simply Pre-Depend on a new enough version of dpkg rather than using 'dpkg-maintscript-helper supports' guards, leading to more predictable behaviour on upgrades. Ubuntu delta merged back to debian in 2.7.10-2 Changelog entries since current precise version 2.7.10-1ubuntu1: puppet (2.7.11-1) unstable; urgency=high * New upstream release * Urgency set to high due to regressions in previous release and security vulnerabilities * Execs when run with a user specified, but no group, get the root group. Similarly unexpected privileges are given to providers and types (egid remains as root), this is fixed with a patch from upstream (CVE-2012-1053) * Fix Klogin write through symlink (CVE-2012-1054) -- Micah Anderson mi...@debian.org Thu, 23 Feb 2012 18:24:48 -0500 puppet (2.7.10-2) unstable; urgency=low * Use maintscript support in dh_installdeb (Closes: #659612) -- Micah Anderson mi...@debian.org Thu, 16 Feb 2012 12:22:45 -0500 ** Affects: puppet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/944866 Title: Sync puppet 2.7.11-1 (main) from Debian sid (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/944866/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941905] Re: keystone user should not have a primary group of nogroup
This bug was fixed in the package keystone - 2012.1~e4-0ubuntu1
---
keystone (2012.1~e4-0ubuntu1) precise; urgency=low
[ Chuck Short ]
* New upstream release.
* debian/keystone.upstart: Update for ksl.
* debian/control: Add python-keystoneclient as dependency.
* debian/control: Fix typo.
* debian/keystone.postinst: Update due to redux branch change.
* debian/keystone.templates, debian/keystone.preinst, debian/kestone.postinst,
debian/keystone.config, debian/README.Debian: Make keystone installation
less interactive. (LP: #931236)
* debian/keystone.postinst: Don't create users or run a database sync
since its not working correctly.
* debian/control: Dropped python-coverage and python-nosexcover.
* debian/changelog: Fixed changelog.
* debian/keystone.templates: Set it to false.
* debian/control: Fix lintian warnings.
* debian/patches/keystone-auth.patch: Backport auth token improvements,
this can be dropped in the next snapshot.
* debian/control: Add python-memcache as a build dependency.
* debian/keystone-doc.docs: Fix keystone doc builds.
* debian/rules: Temporarily disable doc install.
* debian/control: Add python-ldap and python-lxml.
[ Joseph Heck ]
* debian/control: Dropped python-cli.
[ Adam Gandelman ]
* debian/control: Alphabetize python depends
* debian/control: Add python-{eventlet, greenlet, passlib} to keystone
depends
* debian/control: Add python-lxml to python-keystone Depends
* Drop 0001-Fix-keystone-all-failure-to-start.patch
* debian/logging.conf: Temporarily use old logging.conf until upstream
ships something usable
* debain/patches/sql_connection.patch: Switch backends to use SQL backends
* debian/keystone.preinst: Create directories
* debian/keystone.postinst: Remove create_users stuff, add call to 'db_sync'
on install
[ Dave Walker ]
* debian/patches/sql_connection.patch: Refreshed and reintroduced DEP-3
headers.
* debian/control: Added Vcs-Bzr field.
[ Andrew Glen-Young ]
* debian/keystone.preinst: Set the primary group to keystone. (LP: #941905)
-- Chuck Short zul...@ubuntu.com Fri, 02 Mar 2012 09:55:24 -0500
** Changed in: keystone (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/941905
Title:
keystone user should not have a primary group of nogroup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/941905/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 931236] Re: keystone install is unnecessarily interactive
This bug was fixed in the package keystone - 2012.1~e4-0ubuntu1
---
keystone (2012.1~e4-0ubuntu1) precise; urgency=low
[ Chuck Short ]
* New upstream release.
* debian/keystone.upstart: Update for ksl.
* debian/control: Add python-keystoneclient as dependency.
* debian/control: Fix typo.
* debian/keystone.postinst: Update due to redux branch change.
* debian/keystone.templates, debian/keystone.preinst, debian/kestone.postinst,
debian/keystone.config, debian/README.Debian: Make keystone installation
less interactive. (LP: #931236)
* debian/keystone.postinst: Don't create users or run a database sync
since its not working correctly.
* debian/control: Dropped python-coverage and python-nosexcover.
* debian/changelog: Fixed changelog.
* debian/keystone.templates: Set it to false.
* debian/control: Fix lintian warnings.
* debian/patches/keystone-auth.patch: Backport auth token improvements,
this can be dropped in the next snapshot.
* debian/control: Add python-memcache as a build dependency.
* debian/keystone-doc.docs: Fix keystone doc builds.
* debian/rules: Temporarily disable doc install.
* debian/control: Add python-ldap and python-lxml.
[ Joseph Heck ]
* debian/control: Dropped python-cli.
[ Adam Gandelman ]
* debian/control: Alphabetize python depends
* debian/control: Add python-{eventlet, greenlet, passlib} to keystone
depends
* debian/control: Add python-lxml to python-keystone Depends
* Drop 0001-Fix-keystone-all-failure-to-start.patch
* debian/logging.conf: Temporarily use old logging.conf until upstream
ships something usable
* debain/patches/sql_connection.patch: Switch backends to use SQL backends
* debian/keystone.preinst: Create directories
* debian/keystone.postinst: Remove create_users stuff, add call to 'db_sync'
on install
[ Dave Walker ]
* debian/patches/sql_connection.patch: Refreshed and reintroduced DEP-3
headers.
* debian/control: Added Vcs-Bzr field.
[ Andrew Glen-Young ]
* debian/keystone.preinst: Set the primary group to keystone. (LP: #941905)
-- Chuck Short zul...@ubuntu.com Fri, 02 Mar 2012 09:55:24 -0500
** Changed in: keystone (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/931236
Title:
keystone install is unnecessarily interactive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/931236/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 934064] Re: Installing openstack-dashboard on Precise removes Keystone package
This bug was fixed in the package python-keystoneclient - 2012.1~e4-0ubuntu1 --- python-keystoneclient (2012.1~e4-0ubuntu1) precise; urgency=low * New upstream release. * debian/disbale-argparse.patch: Dropped. * debian/control: dont conflict on keystone. (LP: #934064) * debian/control: Drop python-argparse as a build depends. -- Chuck Short zul...@ubuntu.com Fri, 02 Mar 2012 10:31:44 -0500 ** Changed in: python-keystoneclient (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/934064 Title: Installing openstack-dashboard on Precise removes Keystone package To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/934064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 934064] Re: Installing openstack-dashboard on Precise removes Keystone package
** Branch linked: lp:ubuntu/python-keystoneclient -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/934064 Title: Installing openstack-dashboard on Precise removes Keystone package To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/934064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 940780] Re: nova-volume fails to start: OSError: [Errno 2] No such file or directory: '/var/lock/nova'
This bug was fixed in the package nova - 2012.1~e4-0ubuntu1
---
nova (2012.1~e4-0ubuntu1) precise; urgency=low
[ Adam Gandleman ]
* debian/patches/libvirt-use-console-pipe.patch: Refreshed.
* debain/nova-volume.upstart.in: Ensure lock directory is created
(LP: #940780)
* debain/control: Fix nova-compute-$flavor Depends
* debian/control: Add python-iso8601 to python-nova Depends
[ Chuck Short ]
* debian/rules: Fix FTBFS.
* Merge Ubuntu/Debian packaging:
- Thanks to Julien Danjou, Ghe Rivero, and Thomas Goirand
- debian/copyright: Update copyright file.
- debian/nova-api.init, debian/nova-compute.init,
debian/nova-network.init, debian/nova-objectstore,
debian/nova-scheduler, debian/nova-volume.init:
Synchronize init scripts.
- nova-common.install, debian/rules: Install policy.json
- debian/rules, debian/nova-xcp-network.install,
debian/nova-xcp-plugins.install, nova-xcp-plugins.postrm,
debian/nova-xcp-plugins.doc, debian/nova-xcp-plugins.postinst,
debian/README.xcp_and_openstack, debian/control,
debian/ubuntu_xen-openvswitch-nova.rules,
debian/patches/path-to-the-xenhost.conf-fixup.patch:
Add Xen XCP support.
- debian/control,
debian/nova-compute-{kvm,lxc,qemu,xen,uml}.postinst: Make
nova-compute a virtual package.
- Dropped ubuntu_ubuntu_control_vars: We dont use it
* New upstream release.
* Dropped python-babel, it will be handled by langpacks.
* debian/patches/ec2-fixes.patch: Backport turnk fix for ec2
permissions.
* debian/patches/path-to-the-xenhost.conf-fixup.patch: Refreshed.
-- Chuck Short zul...@ubuntu.com Fri, 02 Mar 2012 11:04:04 -0500
** Changed in: nova (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/940780
Title:
nova-volume fails to start: OSError: [Errno 2] No such file or
directory: '/var/lock/nova'
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/940780/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend
Thanks Dave, Installing works now, but removing throws an error: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: keystone 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 106 kB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 295329 files and directories currently installed.) Removing keystone ... dpkg: error processing keystone (--remove): subprocess installed pre-removal script returned error exit status 10 postinst called with unknown argument `abort-remove' Errors were encountered while processing: keystone E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/944684 Title: Error installing keystone selecting dbconfig-common and sqlite3 as the backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/944684/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend
Also dpkg-reconfigure keystone and using sqlite3 throws the following error: Traceback (most recent call last): File /usr/bin/keystone-manage, line 28, in module cli.main(argv=sys.argv, config_files=config_files) File /usr/lib/python2.7/dist-packages/keystone/cli.py, line 147, in main return run(cmd, (args[:1] + args[2:])) File /usr/lib/python2.7/dist-packages/keystone/cli.py, line 133, in run return CMDS[cmd](argv=args).run() File /usr/lib/python2.7/dist-packages/keystone/cli.py, line 35, in run return self.main() File /usr/lib/python2.7/dist-packages/keystone/cli.py, line 56, in main driver.db_sync() File /usr/lib/python2.7/dist-packages/keystone/identity/backends/sql.py, line 120, in db_sync migration.db_sync() File /usr/lib/python2.7/dist-packages/keystone/common/sql/migration.py, line 50, in db_sync current_version = db_version() File /usr/lib/python2.7/dist-packages/keystone/common/sql/migration.py, line 66, in db_version return db_version_control(0) File /usr/lib/python2.7/dist-packages/keystone/common/sql/migration.py, line 72, in db_version_control CONF.sql.connection, repo_path, version) File string, line 2, in version_control File /usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py, line 159, in with_engine return f(*a, **kw) File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 250, in version_control ControlledSchema.create(engine, repository, version) File /usr/lib/python2.7/dist-packages/migrate/versioning/schema.py, line 139, in create table = cls._create_table_version(engine, repository, version) File /usr/lib/python2.7/dist-packages/migrate/versioning/schema.py, line 180, in _create_table_version if not table.exists(): File /usr/lib/python2.7/dist-packages/sqlalchemy/schema.py, line 549, in exists self.name, schema=self.schema) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 2274, in run_callable conn = self.contextual_connect() File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 2340, in contextual_connect self.pool.connect(), File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 210, in connect return _ConnectionFairy(self).checkout() File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 371, in __init__ rec = self._connection_record = pool._do_get() File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 758, in _do_get return self._create_connection() File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 174, in _create_connection return _ConnectionRecord(self) File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 256, in __init__ self.connection = self.__connect() File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 316, in __connect connection = self.__pool._creator() File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/strategies.py, line 80, in connect return dialect.connect(*cargs, **cparams) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py, line 280, in connect return self.dbapi.connect(*cargs, **cparams) sqlalchemy.exc.OperationalError: (OperationalError) unable to open database file None None -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/944684 Title: Error installing keystone selecting dbconfig-common and sqlite3 as the backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/944684/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 944684] Re: Error installing keystone selecting dbconfig-common and sqlite3 as the backend
keystone: Installed: 2012.1~e4-0ubuntu1 Candidate: 2012.1~e4-0ubuntu1 Version table: *** 2012.1~e4-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/944684 Title: Error installing keystone selecting dbconfig-common and sqlite3 as the backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/944684/+subscriptions -- Ubuntu-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-p-php54] PHP 5.4 for Ubuntu 12.04
Blueprint changed by Clint Byrum: Whiteboard changed: - Status: 5.4 has not released yet, though it is in final rc stages. - Debian has not been tracking the RC's, nor have we been able to devote - enough resources to that in Ubuntu. Given the proximity to feature - freeze and low priority given to this task, it looks like we'll ship - 5.3. + Status: with 5.4.0 arriving after beta1, there is no conceivable way + that it can be shipped in 12.04 without potentially disrupting testing + efforts by early beta testers. 5.3 will be the PHP release in Ubuntu + 12.04. 5.4 will most *certainly* be shipped in precise+1, and should be + a good candidate for precise-backports. Work items: [ubuntu-server] In january, assess situation based on Debian status and decide 5.4 or 5.3 then: DONE [clint-fewbar] maintain a merged 5.4 in a PPA for until archive decision is made: POSTPONED [clint-fewbar] setup rebuilds for extensions that build-dep on php5-dev: POSTPONED [clint-fewbar] setup backport for lucid to allow wider PHP 5.4 testing before the upgrade: POSTPONED Question: Does this require discussion or just rubber stamping? -- Daviey Answer: It is not entirely clear whether 5.4.0 will be sufficiently similar to 5.3.x to include in this release. The more conservative approach is just to ship 5.3.9 or 5.3.10 and leave 5.4.0 for 12.10, but the PHP community is interested in weighing in on the issue and I'd also like to hear the security team's take on the matter. * provide packages for both precise and lucid in the ppa (or lucid-backports) so people can test before upgrade * provide rebuilt extensions against the new ABI Question: With both PHP 5.4.0 final and Ubuntu 12.04 Beta 1 released today, is it correct to assume that the chances of PHP 5.4 being shipped with Ubuntu 12.04 are basically non existant? -Clemens -- PHP 5.4 for Ubuntu 12.04 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-php54 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 881464] Re: [MIR] keystone
For info, keystone packages after 2012.1~e4-0ubuntu1 (after the prior review), is based on whole new upstream code. Upstream rewrote this project from scratch. Apologies for the doubling of work. Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/881464 Title: [MIR] keystone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/881464/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 924337] Re: lxc on precise is not working with lucid containers (container does not reach runlevel 2)
This bug was fixed in the package lxc - 0.7.5-0ubuntu8.5 --- lxc (0.7.5-0ubuntu8.5) oneiric-proposed; urgency=low * lxcguest.lxcguest.upstart: emit the net-device-up IFACE=lo event, so that any upstart jobs waiting on it (esp rc-sysinit before oneiric) will proceed. (LP: #924337) * 0035-lxc-init-ignore-shm.patch: if lxc-init can't mount /dev/shm, don't fail on account of that. (LP: #927883) -- Serge Hallyn serge.hal...@ubuntu.com Mon, 06 Feb 2012 19:06:46 -0600 ** Changed in: lxc (Ubuntu Oneiric) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/924337 Title: lxc on precise is not working with lucid containers (container does not reach runlevel 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 927883] Re: lxc-execute fails due to missing /dev/shm
This bug was fixed in the package lxc - 0.7.5-0ubuntu8.5 --- lxc (0.7.5-0ubuntu8.5) oneiric-proposed; urgency=low * lxcguest.lxcguest.upstart: emit the net-device-up IFACE=lo event, so that any upstart jobs waiting on it (esp rc-sysinit before oneiric) will proceed. (LP: #924337) * 0035-lxc-init-ignore-shm.patch: if lxc-init can't mount /dev/shm, don't fail on account of that. (LP: #927883) -- Serge Hallyn serge.hal...@ubuntu.com Mon, 06 Feb 2012 19:06:46 -0600 ** Changed in: lxc (Ubuntu Oneiric) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/927883 Title: lxc-execute fails due to missing /dev/shm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/927883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 925028] Re: apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns -EINVAL)
This bug was fixed in the package linux - 3.2.0-18.28 --- linux (3.2.0-18.28) precise; urgency=low [ Andy Whitcroft ] * ubuntu: AUFS -- adapt to the new changelog handling * ubuntu: AUFS -- sort out the relative header paths * ubuntu: AUFS -- update to d266b0c5d0693d6383976ee54b9e2c0fa9a3f5b0 [ Chase Douglas ] * SAUCE: (drop after 3.3) HID: hid-magicmouse: Add pointer and buttonpad properties for Magic Trackpad * SAUCE: Input: synaptics - add second variant of two-button clickpad * SAUCE: Input: synapticss - Set buttonpad property for all clickpads [ Johannes Berg ] * SAUCE: iwlwifi: fix key removal - LP: #911059 [ John Johansen ] * Revert SAUCE: AppArmor: Fix unpack of network tables. * Revert SAUCE: AppArmor: Allow dfa backward compatibility with broken userspace * SAUCE: AppArmor: Add mising end of structure test to caps unpacking * SAUCE: AppArmor: Fix dropping of allowed operations that are force audited * SAUCE: AppArmor: Fix underflow in xindex calculation * SAUCE: AppArmor: fix mapping of META_READ to audit and quiet flags * SAUCE: AppArmor: Fix the error case for chroot relative path name lookup - LP: #925028 * SAUCE: AppArmor: Retrieve the dentry_path for error reporting when path lookup fails - LP: #925028 * SAUCE: AppArmor: Minor cleanup of d_namespace_path to consolidate error handling * SAUCE: AppArmor: Update dfa matching routines. * SAUCE: AppArmor: Move path failure information into aa_get_name and rename * SAUCE: AppArmor: Make chroot relative the default path lookup type * SAUCE: AppArmor: Add ability to load extended policy * SAUCE: AppArmor: basic networking rules * SAUCE: AppArmor: Add profile introspection file to interface * SAUCE: AppArmor: Add the ability to mediate mount * SAUCE: AppArmor: Add mount information to apparmorfs [ Kees Cook ] * SAUCE: AppArmor: refactor securityfs to use structures * SAUCE: AppArmor: add initial features directory to securityfs * SAUCE: AppArmor: add file details to securityfs * SAUCE: AppArmor: export known rlimit names/value mappings in securityfs [ Leann Ogasawara ] * Revert [Config] Enable CONFIG_NVRAM=m - LP: #942193 * Rebase to v3.2.7 * [Config] Enable CONFIG_USB_SERIAL_QUATECH2=m on arm and powerpc * [Config] Enable CONFIG_USB_SERIAL_QUATECH_USB2=m on arm and powerpc * [Config] Add CONFIG_NVRAM to config enforcer - LP: #942193 * [Config] Enable CONFIG_SCSI_IBMVSCSI=m for powerpc - LP: #943090 * [Config] Enable CONFIG_SCSI_IPR=m for powerpc - LP: #943090 * provide ipmi udeb - LP: #942926 * Rebase to v3.2.9 * Add ibmveth to d-i/modules-powerpc/nic-modules - LP: #712188 * [Config] Enable CONFIG_SCSI_IBMVFC=m for powerpc - LP: #712188 * Add ibmvfc and ibmvscsic to d-i/modules-powerpc/nic-modules - LP: #712188 [ Seth Heasley ] * SAUCE: ALSA: hda - Add Lynx Point HD Audio Controller DeviceIDs - LP: #900119 * SAUCE: ahci: AHCI-mode SATA patch for Intel Lynx Point DeviceIDs - LP: #900119 * SAUCE: ata_piix: IDE-mode SATA patch for Intel Lynx Point DeviceIDs - LP: #900119 * SAUCE: i2c-i801: Add device IDs for Intel Lynx Point - LP: #900119 [ Tim Gardner ] * [Config] updateconfigs after apparmor patches * [Config] Added hv_netvsc and hv_storvsc to -virtual - LP: #942256 * [Config] Enable aufs - LP: #943119 [ Upstream Kernel Changes ] * Revert Revert ath9k_hw: fix interpretation of the rx KeyMiss flag * Revert AppArmor: compatibility patch for v5 interface * Revert AppArmor: compatibility patch for v5 network controll * ACPI / PM: Do not save/restore NVS on Asus K54C/K54HR - LP: #898503 * rebase to v3.2.9 - LP: #900802 * rebase to v3.2.8 * rebase to v3.2.7 - LP: #930842 -- Leann Ogasawara leann.ogasaw...@canonical.com Fri, 02 Mar 2012 07:30:45 -0800 ** Changed in: linux (Ubuntu Precise) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/925028 Title: apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns -EINVAL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945117] [NEW] can't edit files in my public guest allow rw folder
Public bug reported: Precise 3D 32-Bit up-to-date What you expected to happen: When right clicking a folder and selecting these sharing options: * Share this folder * Allow others to create and delete... * Guest access + Modify Share + Adding the needed permissions by conforming that option in the upcoming dialog it should be possible to copy any file from an other computer through the network to mine. The received files should be accessible to me as any other file in my home directory. What happened instead: I was able to see, mount and send a couple of images from my laptop to my precise machine. Then I tried to edit an image in my shared local folder. This wasn't possible → 'permission denied' error. Rights of all received files inside the share: -rwxr--r-- 1 nobody nogroup When removing the folder from samba by unchecking the 'Share this folder' box and clicking the approval button the files inside the folder belong still to 'nobody' and 'nogroup'. This is a show stopper, no average user would know what to do, my parents would be lost. Suggestion: Change file during this kind of open world samba share (everybody has rw access) to $USER:nogroup. When removing the share, the permissions should be changed to $User:$User. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: samba 2:3.6.3-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.94-0ubuntu1 Architecture: i386 Date: Fri Mar 2 20:53:34 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120227) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: samba UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/945117 Title: can't edit files in my public guest allow rw folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/945117/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945117] Re: can't edit files in my public guest allow rw folder
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/945117 Title: can't edit files in my public guest allow rw folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/945117/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945177] [NEW] not lintian clean
Public bug reported: $ lintian nova-ajax-console-proxy_2012.1~e4-0ubuntu1_all.deb: W: nova-ajax-console-proxy: syntax-error-in-debian-changelog line 77 badly formatted trailer line W: nova-ajax-console-proxy: spelling-error-in-changelog dont don't W: nova-ajax-console-proxy: transitional-package-should-be-oldlibs-extra net/extra $ lintian nova-compute-kvm_2012.1~e4-0ubuntu1_all.deb: W: nova-compute-kvm: maintainer-script-needs-depends-on-adduser postinst $ lintian nova-compute-lxc_2012.1~e4-0ubuntu1_all.deb: W: nova-compute-lxc: maintainer-script-needs-depends-on-adduser postinst $ lintian nova-compute-qemu_2012.1~e4-0ubuntu1_all.deb: W: nova-compute-qemu: maintainer-script-needs-depends-on-adduser postinst $ lintian nova-compute-uml_2012.1~e4-0ubuntu1_all.deb: W: nova-compute-uml: maintainer-script-needs-depends-on-adduser postinst $ lintian nova-compute-xcp_2012.1~e4-0ubuntu1_all.deb: W: nova-compute-xcp: empty-binary-package $ lintian nova-compute-xen_2012.1~e4-0ubuntu1_all.deb: W: nova-compute-xen: maintainer-script-needs-depends-on-adduser postinst $ lintian nova-compute_2012.1~e4-0ubuntu1_all.deb: W: nova-compute: executable-not-elf-or-script usr/share/pyshared/nova/rootwrap/compute.py W: nova-compute: maintainer-script-needs-depends-on-adduser postinst $ lintian nova-doc_2012.1~e4-0ubuntu1_all.deb: W: nova-doc: syntax-error-in-debian-changelog line 77 badly formatted trailer line W: nova-doc: spelling-error-in-changelog dont don't $ lintian nova-network_2012.1~e4-0ubuntu1_all.deb: W: nova-network: executable-not-elf-or-script usr/share/pyshared/nova/rootwrap/network.py $ lintian nova-volume_2012.1~e4-0ubuntu1_all.deb: W: nova-volume: executable-not-elf-or-script usr/share/pyshared/nova/rootwrap/volume.py $ lintian nova-xcp-plugins_2012.1~e4-0ubuntu1_all.deb: W: nova-xcp-plugins: syntax-error-in-debian-changelog line 77 badly formatted trailer line W: nova-xcp-plugins: spelling-error-in-changelog dont don't W: nova-xcp-plugins: script-not-executable usr/lib/xcp/plugins/xenhost $ lintian python-nova_2012.1~e4-0ubuntu1_all.deb: W: python-nova: syntax-error-in-debian-changelog line 77 badly formatted trailer line W: python-nova: spelling-error-in-changelog dont don't ** Affects: nova (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/945177 Title: not lintian clean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/945177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945183] [NEW] lxc-start-ephemeral is difficult to use with non-ubuntu accounts
Public bug reported: Because of the current ssh approach used in lxc-start-ephemeral in lieu of lxc-attach, you need a password or key in the ubuntu account to connect. If you want to do this with automation, you can use a key. If you want to use this with another user and that user's key, you do not have an option at this time. http://paste.ubuntu.com/865767/ adds support for this scenario. We will switch -k for -S to match the ubuntu template, per Serge's suggestion ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/945183 Title: lxc-start-ephemeral is difficult to use with non-ubuntu accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/945183/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945183] Re: lxc-start-ephemeral is difficult to use with non-ubuntu accounts
** Branch linked: lp:~benji/ubuntu/precise/lxc/bug-945183 -- 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/945183 Title: lxc-start-ephemeral is difficult to use with non-ubuntu accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/945183/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945183] Re: lxc-start-ephemeral is difficult to use with non-ubuntu accounts
** Changed in: lxc (Ubuntu) Status: New = Confirmed ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/945183 Title: lxc-start-ephemeral is difficult to use with non-ubuntu accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/945183/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945183] Re: lxc-start-ephemeral is difficult to use with non-ubuntu accounts
This bug was fixed in the package lxc - 0.7.5-3ubuntu32 --- lxc (0.7.5-3ubuntu32) precise; urgency=low * add user (-u) and key (-S) to lxc-start-ephemeral. (LP: #945183) -- benji benji.y...@canonical.com Fri, 02 Mar 2012 17:20:46 -0500 ** Changed in: lxc (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/945183 Title: lxc-start-ephemeral is difficult to use with non-ubuntu accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/945183/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 902339] Re: samba(7) references missing programs
Maarten - thanks for submitting this patch. As I mentioned in the merge review, I believe this should go through debian (see http://www.debian.org/Bugs/Reporting). If you do so, you can mark this bug as 'also affecting' the debian bug # you opened. If you prefer, please let me know and I'll forward it for you. Thanks again! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/902339 Title: samba(7) references missing programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/902339/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 27463] Re: [needs-packaging] 389 Directory Server for Ubuntu
** Branch linked: lp:ubuntu/389-ds-base -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/27463 Title: [needs-packaging] 389 Directory Server for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/27463/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 913883] Re: [MIR] zookeeper, netty, log4cxx
mterry, thanks for the review. I fixed the test suite, it now runs on build, and added a -V to dh_makeshlibs. ** Changed in: log4cxx (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to netty in Ubuntu. https://bugs.launchpad.net/bugs/913883 Title: [MIR] zookeeper, netty, log4cxx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/log4cxx/+bug/913883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945264] [NEW] NTP not receiving PPS signal
Public bug reported: I am using GPSD to connect to my GPS receiever (Garmin 18 LVC). /etc/default/gpsd: START_DAEMON=true GPSD_OPTIONS=-n -b BAUDRATE=4800 DEVICES=/dev/ttyS5 USBAUTO=false GPSD_SOCKET=/var/run/gpsd.sock The daemon works and i get data using: gpsd -n -b -N -D2 /dev/ttyS5 /etc/ntp.conf: server 127.127.28.1 minpoll 4 prefer fudge 127.127.28.1 refid PPS server 127.127.28.0 minpoll 4 fudge 127.127.28.0 time1 0.535 refid GPS Output of ntpq -p: SHM(1) .PPS.0 l- 1600.0000.000 0.000 *SHM(0) .GPS.0 l4 16 3770.0008.359 18.780 As you can see NTP is only seeing the GPS NMEA input and not the PPS signal. I just upgraded from debian queeze and this exact setup worked there. GPS receiver is working, tested the PPS signal with multi-meter. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- 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/945264 Title: NTP not receiving PPS signal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/945264/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945264] Re: NTP not receiving PPS signal
This is on 12.04 server Beta 1 :-) -- 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/945264 Title: NTP not receiving PPS signal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/945264/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 756499] Re: cgroup-bin breaks suspend to RAM
*** This bug is a duplicate of bug 693594 ***
https://bugs.launchpad.net/bugs/693594
I'm marking this a duplicate of #693594 but if you come across this here
are some Workarounds/Fixes:
1)do not move all tasks into a default cgroup
comment CREATE_DEFAULT=yes out and uncomment CREATE_DEFAULT=no in
/etc/default/cgconfig
2)putting the following in /etc/cgconfig.conf fixed (a better value as this is
kernels default anyway)
group sysdefault {
cpu {
cpu.rt_runtime_us = 95;
}
}
3) Add a rule so that [kthreadd] is never put in the default group
In case anybody was wondering what is going on:
Suspend fails because it cannot shutdown your extra CPUs ( you can test this
with echo 0 /sys/devices/system/cpu/cpu$x/online ).
The kernel can't shutdown the extra CPUs because some it spawns some threads
(ksoftirqd and migration) that need realtime scheduling and because they are in
the sysdefault subgroup it will not allow it (you can fix this with echo PID of
the stuck thread to /sys/fs/cgroup/cpu/tasks (the thread will show up as state
D (Uninterruptible sleep))).
Note that on some kernels: (e.g 3.0.0 that is shipped with 11.10) you
can shutdown the CPUs once each before the problem occurs (e.g one
suspend) but on others ( e.g 3.3.0-rc4) you cant.
** This bug has been marked a duplicate of bug 693594
cgroup-bin should not move kthreadd into a default cgroup
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubuntu.
https://bugs.launchpad.net/bugs/756499
Title:
cgroup-bin breaks suspend to RAM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/756499/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 858102] Re: cgroup service prevents VMWare services stopping
Hi I've been looking at cgroup bugs and I suspect that you have a multicore/hypterthreaded system which is experiencing a symptom of https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/693594 could you try giving the default group some realtime priority (e.g echo 95 | sudo tee /sys/fs/cgroup/cpu/sysdefault/cpu.rt_runtime_us ) and then seeing if you still have the problem? Thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/858102 Title: cgroup service prevents VMWare services stopping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/858102/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945299] [NEW] keystone_2012.1~e4-0ubuntu1_all fails to install
Public bug reported: Error in preinst: Selecting previously unselected package keystone. Unpacking keystone (from .../keystone_2012.1~e4-0ubuntu1_all.deb) ... adduser: The group `keystone' does not exist. id: keystone: No such user chown: invalid user: `keystone:keystone' dpkg: error processing /var/cache/apt/archives/keystone_2012.1~e4-0ubuntu1_all.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/keystone_2012.1~e4-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ubuntu@ip-10-252-25-139:~$ ** Affects: keystone (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/945299 Title: keystone_2012.1~e4-0ubuntu1_all fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/945299/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 945299] Re: keystone_2012.1~e4-0ubuntu1_all fails to install
** Branch linked: lp:~gandelman-a/ubuntu/precise/keystone/lp945299 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/945299 Title: keystone_2012.1~e4-0ubuntu1_all fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/945299/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 894804] Re: 255 cannot create tmp file
[Expired for samba (Ubuntu) because there has been no activity for 60 days.] ** Changed in: samba (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/894804 Title: 255 cannot create tmp file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/894804/+subscriptions -- Ubuntu-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-p-freeipa-tech-preview] FreeIPA Tech Preview
Blueprint changed by Timo Aaltonen: Whiteboard changed: Rather fine-grained task list below. Uploading full 389ds stack is not necessary (hence status isn't BLOCKED), though not a whole lot of work after the prereqs are already done. Work items (precise-alpha-2): [tjaalton] package python-nss: DONE [tjaalton] upload python-nss: DONE [tjaalton] package python-krbv: DONE [tjaalton] upload python-krbv: DONE [tjaalton] package certmonger: DONE [tjaalton] upload certmonger: DONE [tjaalton] add gssapi delegation support for curl (merge from Debian): DONE [tjaalton] add gssapi delegation support for xmlrpc-c (patch from RHEL): DONE [tjaalton] package svrcore: DONE [tjaalton] upload svrcore: DONE [tjaalton] package libmozilla-ldap-perl: DONE [tjaalton] package 389-ds-base: DONE [tjaalton] test /usr/sbin/setup-ds: DONE [vorlon] Include ldif.h in libldap2-dev by updating openldap to =2.4.26: DONE [tjaalton] upload libmozilla-ldap-perl (needs new openldap): DONE [tjaalton] package ldapjdk: DONE [tjaalton] upload ldapjdk: DONE [tjaalton] package jss: DONE [tjaalton] upload jss: DONE [tjaalton] package idm-console-framework: DONE [tjaalton] package libapache2-mod-nss: DONE [tjaalton] package tomcatjss: DONE [tjaalton] package osutil: DONE [tjaalton] upload osutil: DONE [tjaalton] package dogtag-pki-theme: DONE [tjaalton] package 389-adminutil: DONE [tjaalton] package 389-admin: DONE [tjaalton] package 389-admin-console: DONE [tjaalton] package 389-console: DONE [tjaalton] package 389-ds-console: DONE Work items (ubuntu-12.04-beta-1): - [tjaalton] upload 389-ds-base: INPROGRESS + [tjaalton] upload 389-ds-base: DONE [tjaalton] upload idm-console-framework: DONE [tjaalton] upload libapache2-mod-nss: DONE [tjaalton] upload tomcatjss: DONE [tjaalton] package freeipa-client: DONE - [tjaalton] upload freeipa-client: INPROGRESS [tjaalton] package 389-dsgw: DONE [tjaalton] upload 389-adminutil: DONE Work items: [tjaalton] package 389-ds meta package: DONE - [tjaalton] upload 389-admin: INPROGRESS - [tjaalton] upload 389-dsgw: INPROGRESS - [tjaalton] upload 389-admin-console: INPROGRESS + [tjaalton] upload 389-admin: DONE + [tjaalton] upload 389-dsgw: DONE + [tjaalton] upload 389-admin-console: DONE + [tjaalton] upload freeipa-client: INPROGRESS [tjaalton] package pki: INPROGRESS [tjaalton] upload pki: TODO [tjaalton] package freeipa-server: INPROGRESS [tjaalton] upload freeipa-server: BLOCKED [tjaalton] test /usr/sbin/ipa-client-install: INPROGRESS [tjaalton] test /usr/sbin/ipa-server-install: TODO [tjaalton] package slapi-nis, or drop NIS support from freeipa (if possible): TODO [tjaalton] upload slapi-nis: TODO [tjaalton] upload 389-console: TODO [tjaalton] upload 389-ds-console: TODO [tjaalton] upload 389-ds: TODO tjaalton -- 2012-02-16: FF today, so pushing everything that's verified to be finished. Splitting freeipa-client apart from the server, that can be worked on separately. Client got uploaded to precise. tjaalton -- 2012-02-21: Upstream has PKI in one big git repo, it is now packaged using that as a base (builds 34 binary packages), renamed the task here to reflect that -- FreeIPA Tech Preview https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-freeipa-tech-preview -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 930916] Re: amavis start-stop script fails to stop amavisd
I have verified the patch again. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/930916 Title: amavis start-stop script fails to stop amavisd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/930916/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
