[Bug 1321257] Re: The neutron-plugin-openvswitch-agent package no longer depends on neutron-plugin-openvswitch
I've updated the title to reflect the requested name change (otherwise this ticket can be closed). I agree with the name change as this is confusing and anyway, ml2 supports plugins, it isn't a plugin itself. ** Summary changed: - The neutron-plugin-openvswitch-agent package no longer depends on neutron-plugin-openvswitch + Rename neutron-plugin-ml2 to neutron-ml2 to avoid confusion -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1321257 Title: Rename neutron-plugin-ml2 to neutron-ml2 to avoid confusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1321257/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384109] [NEW] Mechanism driver 'l2population' failed in update_port_postcommit
Public bug reported: OpenStack Juno, Ubuntu 14.04, 3 x neutron-server's with 32 API workers each, rally/boot-and-delete with a concurrency level of 150: 2014-10-21 16:37:04.615 16312 ERROR neutron.plugins.ml2.managers [req-c4cdefd5-b2d9-46fa-a031-bddd03d981e6 None] Mechanism driver 'l2population' failed in update_port_postcommit 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers Traceback (most recent call last): 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py, line 291, in _call_on_drivers 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers getattr(driver.obj, method_name)(context) 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/l2pop/mech_driver.py, line 135, in update_port_postcommit 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers self._update_port_up(context) 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/l2pop/mech_driver.py, line 228, in _update_port_up 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers agent_ports += self._get_port_fdb_entries(binding.port) 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/l2pop/mech_driver.py, line 45, in _get_port_fdb_entries 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers ip['ip_address']] for ip in port['fixed_ips']] 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers TypeError: 'NoneType' object has no attribute '__getitem__' 2014-10-21 16:37:04.615 16312 TRACE neutron.plugins.ml2.managers 2014-10-21 16:37:04.618 16312 ERROR oslo.messaging.rpc.dispatcher [req-c4cdefd5-b2d9-46fa-a031-bddd03d981e6 ] Exception during message handling: update_port_postcommit failed. 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/rpc.py, line 161, in update_device_up 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher host) 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/plugin.py, line 1136, in update_port_status 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher self.mechanism_manager.update_port_postcommit(mech_context) 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py, line 527, in update_port_postcommit 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher continue_on_failure=True) 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py, line 302, in _call_on_drivers 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher method=method_name 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher MechanismDriverError: update_port_postcommit failed. 2014-10-21 16:37:04.618 16312 TRACE oslo.messaging.rpc.dispatcher 2014-10-21 16:37:04.620 16312 ERROR oslo.messaging._drivers.common [req-c4cdefd5-b2d9-46fa-a031-bddd03d981e6 ] Returning exception update_port_postcommit failed. to caller 2014-10-21 16:37:04.621 16312 ERROR oslo.messaging._drivers.common [req-c4cdefd5-b2d9-46fa-a031-bddd03d981e6 ] ['Traceback (most recent call last):\n', ' File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply\nincoming.message))\n', ' File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch\nreturn self._do_dispatch(endpoint, method, ctxt, args)\n', ' File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch\nresult = getattr(endpoint, method)(ctxt,
[Bug 1384108] Re: Exception during message handling: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 10
Environment was being exercises using the boot-and-delete task/rally -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1384108 Title: Exception during message handling: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 10 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384108/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384108] [NEW] Exception during message handling: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 10
Public bug reported: OpenStack Juno release, Ubuntu 14.04 using Cloud Archive; under relatively high instance creation concurrency (150), neutron starts to throw some errors: 2014-10-21 16:40:44.124 16312 ERROR oslo.messaging._drivers.common [req-8e3ebbdb-bc01-439d-af86-655176f206a6 ] ['Traceback (most recent call last):\n', ' File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply\nincoming.message))\n', ' File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch\nreturn self._do_dispatch(endpoint, method, ctxt, args)\n', ' File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch\nresult = getattr(endpoint, method)(ctxt, **new_args)\n', ' File /usr/lib/python2.7/dist-packages/neutron/api/rpc/handlers/securitygroups_rpc.py, line 74, in security_group_info_for_devices\nports = self._get_devices_info(devices_info)\n', ' File /usr/lib/python2.7/dist-packages/neutron/api/rpc/handlers/securitygroups_rpc.py, line 41, in _get_devices_info\nport = self.plugin.get_port_from_device(device)\n', ' File /us r/lib/python2.7/dist-packages/neutron/plugins/ml2/plugin.py, line 1161, in get_port_from_device\nport = db.get_port_and_sgs(port_id)\n', ' File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/db.py, line 222, in get_port_and_sgs\nport_and_sgs = query.all()\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py, line 2300, in all\n return list(self)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py, line 2412, in __iter__\nreturn self._execute_and_instances(context)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py, line 2425, in _execute_and_instances\nclose_with_result=True)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py, line 2416, in _connection_from_session\n**kw)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py, line 854, in connection\nclose_with_result=close_with_result)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/sessi on.py, line 858, in _connection_for_bind\nreturn self.transaction._connection_for_bind(engine)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py, line 322, in _connection_for_bind\nconn = bind.contextual_connect()\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1799, in contextual_connect\nself.pool.connect(),\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 338, in connect\n return _ConnectionFairy._checkout(self)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 641, in _checkout\n fairy = _ConnectionRecord.checkout(pool)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 440, in checkout\n rec = pool._do_get()\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 957, in _do_get\n (self.size(), self.overflow(), self._timeout))\n', 'TimeoutError: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeo ut 10\n'] 2014-10-21 16:40:44.126 16312 ERROR oslo.messaging.rpc.dispatcher [req-ea96dc85-dc0f-4ddc-a827-dbc25ab32a03 ] Exception during message handling: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 10 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/neutron/db/agents_db.py, line 237, in report_state 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher self.plugin.create_or_update_agent(context, agent_state) 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/neutron/db/agents_db.py, line 197, in create_or_update_agent 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher return self._create_or_update_agent(context, agent) 2014-10-21 16:40:44.126 16312 TRACE
[Bug 1381537] Re: Dovecot version in precise too old to switch off SSLv3 protocol for poodle fix
So basicaly the following commit has to be backported to the 2.0 Version. http://hg.dovecot.org/dovecot-2.1/rev/406a1d52390b I created a patch for 2.0.19 and tried it on our staging systems. This worked quite well for ous. ** Patch added: Backport of 406a1d52390b https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1381537/+attachment/4241680/+files/ssl_protocols.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1381537 Title: Dovecot version in precise too old to switch off SSLv3 protocol for poodle fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1381537/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1384108] [NEW] Exception during message handling: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 10
Can you try setting the max connections for SQL to the number of API workers? http://docs.openstack.org/trunk/config-reference/content/networking-options-db.html On Oct 22, 2014 4:31 AM, James Page james.p...@ubuntu.com wrote: Public bug reported: OpenStack Juno release, Ubuntu 14.04 using Cloud Archive; under relatively high instance creation concurrency (150), neutron starts to throw some errors: 2014-10-21 16:40:44.124 16312 ERROR oslo.messaging._drivers.common [req-8e3ebbdb-bc01-439d-af86-655176f206a6 ] ['Traceback (most recent call last):\n', ' File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply\nincoming.message))\n', ' File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch\nreturn self._do_dispatch(endpoint, method, ctxt, args)\n', ' File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch\nresult = getattr(endpoint, method)(ctxt, **new_args)\n', ' File /usr/lib/python2.7/dist-packages/neutron/api/rpc/handlers/securitygroups_rpc.py, line 74, in security_group_info_for_devices\nports = self._get_devices_info(devices_info)\n', ' File /usr/lib/python2.7/dist-packages/neutron/api/rpc/handlers/securitygroups_rpc.py, line 41, in _get_devices_info\nport = self.plugin.get_port_from_device(device)\n', ' File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/plugin.py, line 1161, in get_port_from_device\nport = db.get_port_and_sgs(port_id)\n', ' File /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/db.py, line 222, in get_port_and_sgs\nport_and_sgs = query.all()\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py, line 2300, in all\nreturn list(self)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py, line 2412, in __iter__\nreturn self._execute_and_instances(context)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py, line 2425, in _execute_and_instances\nclose_with_result=True)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py, line 2416, in _connection_from_session\n**kw)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py, line 854, in connection\nclose_with_result=close_with_result)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py, line 858, in _connection_for_bind\nreturn self.transaction._connection_for_bind(engine)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py, line 322, in _connection_for_bind\nconn = bind.contextual_connect()\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1799, in contextual_connect\nself.pool.connect(),\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 338, in connect\nreturn _ConnectionFairy._checkout(self)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 641, in _checkout\nfairy = _ConnectionRecord.checkout(pool)\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 440, in checkout\nrec = pool._do_get()\n', ' File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 957, in _do_get\n(self.size(), self.overflow(), self._timeout))\n', 'TimeoutError: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 10\n'] 2014-10-21 16:40:44.126 16312 ERROR oslo.messaging.rpc.dispatcher [req-ea96dc85-dc0f-4ddc-a827-dbc25ab32a03 ] Exception during message handling: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 10 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/neutron/db/agents_db.py, line 237, in report_state 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher self.plugin.create_or_update_agent(context, agent_state) 2014-10-21 16:40:44.126 16312 TRACE oslo.messaging.rpc.dispatcher File
[Bug 1384122] [NEW] SNMPD defaultmonitors not working
Public bug reported: i run ubuntu 14.04 LTS server 64 Bit snmpd: Installed: 5.7.2~dfsg-8.1ubuntu3 Candidate: 5.7.2~dfsg-8.1ubuntu3 Version table: *** 5.7.2~dfsg-8.1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status I have snmpd installed and can do a snmpwalk to read out all kinds of data but it just won't send a trap whenever i monitor something with the defaultmonitors ie. proc apache2 in /var/log/syslog i get the following error messages snmpd[1225]: /etc/snmp/snmpd.conf: line 179: Warning: Unknown token: defaultMonitors. snmpd[1225]: /etc/snmp/snmpd.conf: line 180: Warning: Unknown token: linkUpDownNotifications. this is similair to debian problem https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746399 please help! ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1384122 Title: SNMPD defaultmonitors not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1384122/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381967] Re: mongodb shell crash on arm64
The shell cannot work without js. It's a bug that binary is included in the package. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274947] Re: juju lxc instances deployed via MAAS don't have resolvable hostnames
** Changed in: maas Milestone: None = next -- 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/1274947 Title: juju lxc instances deployed via MAAS don't have resolvable hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1274947/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381967] Re: mongodb shell crash on arm64
Michael, many thanks for your comment. Could you confirm that we should be using juju-mongodb (https://launchpad.net/ubuntu/+source/juju-mongodb) on ARM64 for the time being? ISTR that juju-mongodb has omitted the libv8 engine, and associated functionality. Thanks again, Andy. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+subscriptions -- Ubuntu-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-u-server-core] General server work for Utopic
Blueprint changed by Robie Basak: Work items changed: Work items for ubuntu-14.06: [serge-hallyn] convert libvirt to cgmanager (4d): DONE [racb] Early cycle merge report: POSTPONED [serge-hallyn] merge qemu: DONE Work items for ubuntu-14.07: [serge-hallyn] cgmanager package into debian: DONE [serge-hallyn] systemd-shim integration for cgmanager: DONE [jamespage] (with raharper) docker 1.0 in 14.04: INPROGRESS Work items for ubuntu-14.08: - [racb] Late cycle merge report: TODO + [racb] Late cycle merge report: POSTPONED [smoser] add simplestreams data to ubuntu core images: TODO [serge-hallyn] triage qemu bugs: DONE [serge-hallyn] go over high prio qemu bugs: DONE [racb] bcache in universe: DONE [kick-d] validate bcache in archive: DONE [kick-d] write up and publish bcache test plan: TODO [racb] add scribe (https://github.com/facebook/scribe) to universe: POSTPONED [racb] add meteor (https://github.com/meteor/meteor) to universe: POSTPONED Work items for ubuntu-14.09: [smoser] write documentation on the process of how to do image customization in simplestreams: TODO [serge-hallyn] triage libvirt bugs: DONE [serge-hallyn] go over high prio libvirt bugs: DONE Work items for ubuntu-14.10: [serge-hallyn] discuss cgmanager features through systemd/cgfs (plumbers): POSTPONED determine ssd caching solution (bcache is it): DONE investigate support of ruby for puppet: POSTPONED -- General server work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-server-core -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381967] Re: mongodb shell crash on arm64
You shouldn't be using juju-mongodb for anything but Juju. AIUI, the security team don't support it for security updates for any other purpose. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381967] Re: mongodb shell crash on arm64
Although that was the plan, it occurs to me that juju-mongodb never entered main. So perhaps I am mistaken. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384108] Re: Exception during message handling: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 10
I've bumped the max connections to 4 x the worker configuration just to be on the safe side. Retesting now to see if this helps. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1384108 Title: Exception during message handling: QueuePool limit of size 10 overflow 20 reached, connection timed out, timeout 10 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384108/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384229] [NEW] When I turn on the laptop after suspend, it displays the boot loader instead of the operating system.
Public bug reported: When I turn on the laptop after suspend, it displays the boot loader instead of the operating system. This bug has been detected in Ubuntu Precise Pangolin (the first version which I installed) and it is not fixed still. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Wed Oct 22 16:07:40 2014 InstallationDate: Installed on 2014-03-25 (210 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140323) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug failed i386 suspend trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1384229 Title: When I turn on the laptop after suspend, it displays the boot loader instead of the operating system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1384229/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384229] Re: When I turn on the laptop after suspend, it displays the boot loader instead of the operating system.
** Description changed: When I turn on the laptop after suspend, it displays the boot loader instead of the operating system. This bug has been detected in Ubuntu Precise Pangolin (the first version which I installed) and it is not - fixed still. + fixed still. Sony Vaio vgn-sr19vrn ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Wed Oct 22 16:07:40 2014 InstallationDate: Installed on 2014-03-25 (210 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140323) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1384229 Title: When I turn on the laptop after suspend, it displays the boot loader instead of the operating system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1384229/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381967] Re: mongodb shell crash on arm64
Thanks Robie, so for ARM64 platforms we should be using MongoDb, but just avoiding the shell and any scripting functions (in order to avoid invoking libv8). Is that correct? Thanks again, Andy. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1382632] Re: Insecure key file permissions
** Tags added: openstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1382632 Title: Insecure key file permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1382632/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384232] Re: Certificate hostname verification fix
Do you know if a CVE has been assigned for this issue? Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/1384232 Title: Certificate hostname verification fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1384232/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
The problem is that I need to leave them triaged or I miss them in the milestone list. -- 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/1373261 Title: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1332120] Re: panic error while backup mailboxes with doveadm backup
Hi there! Is there someone reading this report? The fix is included already. It is a server critical bug, because it influences the imap backup functionality. Please give it a chance. I'm manually repairing the imap backup every time a user deletes an imap folder. Please. It is the LTS server release! Thanks Lars -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1332120 Title: panic error while backup mailboxes with doveadm backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1332120/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1361357] Re: metadata service performance regression ~8x
** Changed in: neutron Assignee: Oleg Bondarev (obondarev) = (unassigned) ** Changed in: neutron Milestone: kilo-1 = None -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1361357 Title: metadata service performance regression ~8x To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1361357/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1361357] Re: metadata service performance regression ~8x
As per a thread on the mailing list [1], this issue was already fixed [2] in Neutron in Juno and backported to Icehouse, so I'm going to remove Neutron as an affected project. 1: http://lists.openstack.org/pipermail/openstack-dev/2014-October/048916.html 2: https://bugs.launchpad.net/neutron/+bug/1276440 ** No longer affects: neutron -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1361357 Title: metadata service performance regression ~8x To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1361357/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384279] [NEW] Enhancement Request Version and program data About
Public bug reported: Request adding version and program information in the web interface. Foreman has a fantastic approach to this, which we should just mimic/copy. Reference the foreman about page and note system information in the bottom right. ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- 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/1384279 Title: Enhancement Request Version and program data About To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1384279/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381383] Re: Vm destroyed when created with virsh create without --autodestroy
I'm marking this low priority per guidelines since there is a workaround (use virsh define). However it most certainly looks like a bug, especially since --autodestroy is listed as an option in the help usage. ** Summary changed: - Vm destroyed when created virsh create without --autodestroy + Vm destroyed when created with virsh create without --autodestroy ** Changed in: libvirt (Ubuntu) Importance: Undecided = Low ** Changed in: libvirt (Ubuntu) Status: Invalid = Triaged -- 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/1381383 Title: Vm destroyed when created with virsh create without --autodestroy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1381383/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1363729] Re: pam_mount Broken with util-linux 2.25
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libpam-mount (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libpam-mount in Ubuntu. https://bugs.launchpad.net/bugs/1363729 Title: pam_mount Broken with util-linux 2.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/1363729/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1039420] Re: NTP security vulnerability because not using authentication by default
Unfortunately, ntp autokey is broken and insecure, it can't be used to provide any additional security. http://zero-entropy.de/autokey_analysis.pdf The only solution for the moment is for system administrators to set up their own symmetric keys with their own ntp server. -- 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/1039420 Title: NTP security vulnerability because not using authentication by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1039420/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383794] Re: GCE datasource should use the short hostname
** Attachment added: Precise debdiff of working patch https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+attachment/4241831/+files/precise-debdiff.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1383794 Title: GCE datasource should use the short hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383379] Re: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE
In discussion with mdeslaur on IRC, I'm attaching DebDiffs for Ubuntu in the off chance the release team wishes to push these changes. A few extra details as to why this is extremely relevant to being pushed and updated: A lot of newbie users that we see in the NGINX IRC channel for support end up using the default configuration file(s) as a template/law for their sites, and we end up seeing them just uncomment the SSL portion and use it. That opens them up to the POODLE vulnerability. Upstream, in Debian, this was revised per POODLE so newbies wouldn't be exposing themselves to vulnerability, hence the rationale for this perhaps being pushed/updated. Unfortunately, all versions of nginx (including Lucid, which is being ignored intentionally) are impacted by POODLE and SSLv3, so it's better to just remove the SSLv3 protocol from the ssl_protocols line, mainly to prevent newbies from making their systems open to attack. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1383379 Title: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1383379/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383379] Re: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE
** Patch added: Precise Debdiff for Ubuntu https://bugs.launchpad.net/nginx/+bug/1383379/+attachment/4241830/+files/nginx_sslv3_remove_debdiff_precise.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1383379 Title: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1383379/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381967] Re: mongodb shell crash on arm64
I believe the only *ARM64* MongoDB version that is reasonably expected to work (i.e. without server side scripting and at demo grade quality) is out of a PPA : https://launchpad.net/~mongodb- arm64/+archive/ubuntu/ppa . The mongoDB charm was recently enhanced (By Charles Butler) to add an option to speficy this PPA when installing MongoDB. So I thinkany ARM64 testing should be focused on this PPA. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383794] Re: GCE datasource should use the short hostname
** Attachment added: Utopic debdiff of working patch https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+attachment/4241834/+files/utopic-debdiff.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1383794 Title: GCE datasource should use the short hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383794] Re: GCE datasource should use the short hostname
** Attachment added: Trusty debdiff of working patch https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+attachment/4241833/+files/trusty-debdiff.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1383794 Title: GCE datasource should use the short hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383379] Re: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE
NOTE: I didn't know where to target this for Utopic, so I just targeted it to 'utopic'. Please change that if it is not valid. ** Patch added: Utopic Debdiff for Ubuntu https://bugs.launchpad.net/nginx/+bug/1383379/+attachment/4241835/+files/nginx_sslv3_remove_debdiff_utopic.debdiff ** Changed in: nginx Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1383379 Title: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1383379/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383379] Re: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE
** Patch added: Trusty Debdiff for Ubuntu https://bugs.launchpad.net/nginx/+bug/1383379/+attachment/4241832/+files/nginx_sslv3_remove_debdiff_trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1383379 Title: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1383379/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384327] [NEW] lxc-attach --clear-env results in a limited $PATH in the container
Public bug reported: Here is the problem in more details: # Clearing the env $ printf 'echo $PATH\n' | sudo lxc-attach --clear-env -n p1 /bin:/usr/bin # Keeping the env $ printf 'echo $PATH\n' | sudo lxc-attach --keep-env -n p1 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin While keeping the env seems like a good workaround it cause other undesirable effects like preserving $HOME that doesn't (always) exist in the container. Additional information: $ apt-cache policy lxc lxc: Installed: 1.0.6-0ubuntu0.1 Candidate: 1.0.6-0ubuntu0.1 Version table: *** 1.0.6-0ubuntu0.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.5-0ubuntu0.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 1.0.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Both host and container are: $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Summary changed: - lxc-attach --clear-env resulted in a limited $PATH in the container + lxc-attach --clear-env results in a limited $PATH in the container -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384327 Title: lxc-attach --clear-env results in a limited $PATH in the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384327/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383379] Re: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE
The attachment Precise Debdiff for Ubuntu seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the patch flag from the attachment, remove the patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1383379 Title: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1383379/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1378441] Re: add GCE support for cloud-init on 12.04
Marking this as verification done. I've confirmed that this works on multiple instances. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1378441 Title: add GCE support for cloud-init on 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1378441/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383794] Re: GCE datasource should use the short hostname
** Branch linked: lp:~utlemming/ubuntu/precise/precise/lp1383794 ** Branch linked: lp:~utlemming/ubuntu/trusty/cloud-init/lp1383794 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1383794 Title: GCE datasource should use the short hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1384327] [NEW] lxc-attach --clear-env results in a limited $PATH in the container
The minimal PATH comes from getconf -a | grep ^PATH (if confstr were not available then lxc would actually default to a longer PATH) status: invalid ** Changed in: lxc (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384327 Title: lxc-attach --clear-env results in a limited $PATH in the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384327/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1384327] [NEW] lxc-attach --clear-env results in a limited $PATH in the container
On 10/22/2014 12:54 PM, Serge Hallyn wrote: The minimal PATH comes from getconf -a | grep ^PATH (if confstr were not available then lxc would actually default to a longer PATH) I didn't mention but the guest in question was freshly created with sudo lxc-create -t ubuntu -n p1. status: invalid Are you saying my container is broken somehow or that it's not a bug? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384327 Title: lxc-attach --clear-env results in a limited $PATH in the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384327/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383379] Re: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE
(nginx project) Updated packages uploaded to the staging PPA, pending building. ** Changed in: nginx Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1383379 Title: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1383379/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1346538] Re: maas-dns fails to install due to missing config file for bind9
This bug was fixed in the package maas - 1.7.0~beta8+bzr3272-0ubuntu1 --- maas (1.7.0~beta8+bzr3272-0ubuntu1) utopic; urgency=medium * New Upstream Release, Beta 8 bzr 3272. - Maintain backward compatibility with status codes to not break client MAAS API users. (LP: #1383609) - Allow users to disable DHCP NIC scanning during commissioning otherwise this can lead machines not being able to commission (LP: #1383384) - Ensure that MAAS can correctly download, and install HWE Kernels, and not crash in the process. (LP: #1357532, LP: #1382281) - Add a lock to ensure we don't give the same 2 systems to two different users when acquiring a machine. (LP: #1382575) [ Michael McCracken ] * debian/maas-dns.postrm: ensure named.conf is cleaned of maas includes (LP: #1346538) -- Andres Rodriguez andres...@ubuntu.com Wed, 22 Oct 2014 12:55:08 -0400 ** Branch linked: lp:ubuntu/utopic-proposed/maas ** Changed in: maas (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1346538 Title: maas-dns fails to install due to missing config file for bind9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346538/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1382266] Re: maas-proxy fails to start on freshly installed MAAS
Hi Kiko, If you can reproduce this, can you please attach: /var/log/upstart/maas-proxy.log? -- 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/1382266 Title: maas-proxy fails to start on freshly installed MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382266/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
Jeroen, Can you please provide what ends up in pserv.yaml? -- 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/1373261 Title: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1384327] [NEW] lxc-attach --clear-env results in a limited $PATH in the container
I'm saying this is not a bug because the limited path is by design. Your system in fact is telling lxc which path to use as the default. If you think that rather than take the value from the system through sysconf, we should always use a longer PATH, then that could be discussed on the lxc-devel mailing list. Really to me the bug seems to be that sysconf(_SC_PATH) on ubuntu isn't giving the path that root gets by default. -- 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/1384327 Title: lxc-attach --clear-env results in a limited $PATH in the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384327/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383379] Re: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE
** Also affects: nginx (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: nginx (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nginx (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: nginx (Ubuntu Utopic) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1383379 Title: nginx default config has SSLv3 enabled, makes sites using default config options vulnerable to POODLE To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1383379/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Hi, I confirm this problem with 2 other computers. It seems to be link to Unity or Gnome keyring and ssh-agent. It does not happen with a KDE desktop. If you press ctrl+alt+F1 and test your ssh connexion, it should work due to environment variables where echo $SSL_AUTH_SOCK return an empty value. Into your session Unity/Gnome, you can bypass this problem by adding this line into your /home/user/.bashrc file : export SSH_AUTH_SOCK=0 reload your bash environment with this command : $ source /home/user/.bashrc It works for me. -- 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/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssh (Ubuntu) Status: New = Confirmed -- 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/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1384327] [NEW] lxc-attach --clear-env results in a limited $PATH in the container
On 10/22/2014 02:05 PM, Serge Hallyn wrote: Really to me the bug seems to be that sysconf(_SC_PATH) on ubuntu isn't giving the path that root gets by default. Thanks Serge, so I agree with you that's not LXC's fault. Though, with such a limited PATH, lxc-attach is much less convenient to work with, IMHO. I'm coming from OpenVZ where I used vzctl enter/exec frequently and now I'm trying to find an equivalent command for LXC so it's quite possible I'm looking at the wrong tool. In which case, a hint would be appreciated ;) If lxc-attach is the right tool for the job, would you mind, when you have time, moving the bug to the appropriate package as I can't find which one it should be. Regards, Simon -- 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/1384327 Title: lxc-attach --clear-env results in a limited $PATH in the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384327/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349868] Re: [MIR] new build dependencies for ceilometer
I reviewed libsmi version 0.4.8+dfsg2-9ubuntu2 as checked into utopic. This should not be considered a full security audit but rather a quick gauge of maintainability. CVE history: CVE-2010-2891 - libsmi provides bindings to manipulate OIDs stored in MIB files - Build-Depends: flex, bison, debhelper, dh-autoreconf - No cryptography - May call wget or similar via smicache mechanism; I believe this isn't enabled by default in our packages - Does not daemonize - No pre/post inst/rm scripts - No initscripts - No dbus - No setuid - No sudo fragments - No cronjobs - No udev rules - Binaries smistrip, smicache, smidump, smilint, smiquery, smixlate, smidiff - Test suite isn't run during build - Build logs are fairly messy - binaries not PIE - Subprocesses only spawned for smicache - Memory management is hectic - The individual tools will write to files designated by the user - The logging looked safe - The environment variable uses looked sane - No privileged operations - No cryptography - May call wget to download MIB files - No temporary files - No WebKit - No PolicyKit - A handful of errors from cppcheck, some common, some surprising Here are some notes I've collected while reviewing the code in the hopes someone finds them useful: - getOidString() very complicated, no protection against overflowing 's' buffer. I suspect bugs live in this function. - parseDH() very complicated, I suspect bugs live in this function. case '*' at least seems to hide memory leaks. - printClass() no protection against overflowing 'string' buffer - fprint() missing error return check on 'fputs()' - getValueString() no protection against overflowing 's' buffer - optString() may not nul-terminate the return string - getStringIndexList() insufficient allocation for strIdxLst, uses +4 but should use +5, one-byte buffer overflow overwrites space for nul. This function may work by accident. - getStringSubrange() memory leak minStr, maxStr - getStringRange() memory leak str, subRange - undefined behaviours (sprintf(dest, %s, dest)) - many warnings - smidiff.c:840:1: note: the ABI of passing union with long double has changed in GCC 4.4 This codebase is pretty messy; there's duplicated code in multiple files rather than using shared utility files; there's awkward uses of C string routines, there's extensive memory allocation and re-allocation when manipulating strings, there's extensive use of fixed-length buffers without visible bounds checking, etc. There are doubtless many bugs left in this library; cppcheck has reported some, gcc reports many warnings, and there is a lot of room for improvement. It really needs something like a StringBuffer-style datastructure to replace the extensive C-string operations. However, despite my large misgivings about this library, by and large it should process mostly-static data from trusted sources. In this role its flaws may not be a big deal. Please enable build-time tests. Please enable PIE for the binaries. Please ensure that ceilometer does not need the smicache functionality; this library should not be used on unauthenticated data. Security team ACK for promoting libsmi to main. -- 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/1349868 Title: [MIR] new build dependencies for ceilometer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmi/+bug/1349868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349868] Re: [MIR] new build dependencies for ceilometer
I reviewed python-pysnmp4-apps version 0.3.2-1 as checked into utopic. This should not be considered a full security audit, but rather a quick gauge of code maintainability. - This package provides snmp tools similar to the netsnmp tools. - Build-Depends: debhelper, cdbs, python-all, python-setuptools - Does not itself do cryptography - Does not itself do networking - Does not daemonize - No pre/post inst/rm - No initscripts - No dbus - No setuid - No sudo fragments - No udev rules - No cronjobs - No testsuite - Clean build logs - No spawned subprocesses - No memory management (Python) - No file manipulation - Logging looks sane - No environment variables - No privileged operations - No cryptography (user interface selects among authentication and privacy options to be used in snmp) - No privileged portions of code - No temporary files - No WebKit - No Javascript - No PolicyKit python-pysnmp4-apps is high-quality, high-density code -- while fixes might be difficult, I suspect there aren't many bugs to be found. Security team ACK for promoting python-pysnmp4-apps to main. ** Changed in: libsmi (Ubuntu) Assignee: Seth Arnold (seth-arnold) = (unassigned) ** Changed in: python-pysnmp4 (Ubuntu) Assignee: Seth Arnold (seth-arnold) = (unassigned) ** Changed in: python-pysnmp4-apps (Ubuntu) Assignee: Seth Arnold (seth-arnold) = (unassigned) -- 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/1349868 Title: [MIR] new build dependencies for ceilometer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmi/+bug/1349868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349868] Re: [MIR] new build dependencies for ceilometer
I reviewed python-pysnmp4 version 4.2.5-1 as checked into utopic. This should not be considered a full security audit, but rather a quick gauge of code maintainability. - python-pysnmp provides a pure-python implementation of snmp - Build-Depends: debhelper (= 5.0.37.2), cdbs, python-all, python3-all, python-setuptools, python3-setuptools, python-crypto, python3-crypto - Depends: smitools - Recommends: python-crypto, python-pysnmp4-mibs, python-pysnmp4-apps, python-twisted - Does use encryption - Does use networking - Uses smitools, thus libsmi - Can be added to other applications via twisted, asyncore - Does not itself daemonize - No pre/post inst/rm scripts - No initscripts - No dbus - No setuid - No sudo fragments - No udev rules - No cron jobs - Adds libsmi2pysnmp and build-pysnmp-mib binaries - Clean build logs - No subprocesses spawned - Python, no real memory management - Only file operation is read-only - Logging looked safe - No use of environment variables - No privileged operations - Does use cryptography, SNMP-standards-specified use of MD5, DES, 3DES, AES, SHA-1, etc. I didn't investigate further, mechanisms all standardized - Extensive networking, looked to be well-managed - No privileged portions of code - No temporary files - No WebKit - No JavaScript - No PolicyKit The code is complicated, though references to relevant RFC sections abound in much of the code. It all seemed straight-forward enough, considering the complexity of SNMP. Security team ACK for promoting python-pysnmp4 to main. -- 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/1349868 Title: [MIR] new build dependencies for ceilometer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmi/+bug/1349868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383794] Re: GCE datasource should use the short hostname
** Branch unlinked: lp:~utlemming/ubuntu/precise/precise/lp1383794 ** Branch linked: lp:~utlemming/ubuntu/utopic/cloud-init/lp1383794 ** Branch linked: lp:~utlemming/ubuntu/precise/cloud-init/lp1383794 ** Summary changed: - GCE datasource should use the short hostname + [SRU] GCE datasource should use the short hostname -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1383794 Title: [SRU] GCE datasource should use the short hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381967] Re: mongodb shell crash on arm64
Yes, please use that PPA for any mongodb on arm64 work. It's a couple of point release behind I see -- someone (i.e. me I guess?) should update it to 2.6.5. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383794] Re: [SRU] GCE datasource should use the short hostname
** Branch linked: lp:~utlemming/cloud-init/lp1383794 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1383794 Title: [SRU] GCE datasource should use the short hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
We've agreed that as a fix for the problem — since it's going to potentially break a lot of charms on customer deployments — we're going to put PTR records back in for dynamic-pool IP addresses. I'm going to investigate using the bind GENERATE directive to make this simpler [1]. [1] http://www.thedumbterminal.co.uk/?action=showArticlearticleId=116 ** Changed in: maas Status: Incomplete = Triaged ** Changed in: maas Assignee: Julian Edwards (julian-edwards) = Graham Binns (gmb) -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1380792] Fix proposed to nova (stable/juno)
Fix proposed to branch: stable/juno Review: https://review.openstack.org/130342 -- 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/1380792 Title: requests to EC2 metadata's '/2009-04-04/meta-data/security-groups' failing To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1380792/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383794] Re: [SRU] GCE datasource should use the short hostname
** Description changed: - The GCE datasource uses the long hostname. Hostnames longer than 64 - characters can break several tools. + [IMPACT] Since GCE FQDN are usually longer than 64-characters, several + hi-profile tools like Java and Hadoop may break. + + [FIX] Per GCE's recommendation, Linux instances should use the short + hostname over the FQDN. This change sets the system hostname to the + short name. + + [VERIFICATION] + 1. Install new cloud-init from proposed + 2. Re-run cloud-config: +* 14.04/14.10: cloud-init single -n set_hostname --frequency=always +* 12.04: + 3. Check to make sure that the short name is used for /etc/hostname + + [RISK] This is a very low risk change. The actual change is a single + line, and has test cases for 14.04 and 14.10. Further, since this change + is only in the GCE datasource, it only affects GCE instances. + + [ORIGINAL REPORT] + The GCE datasource uses the long hostname. Hostnames longer than 64 characters can break several tools. ** Description changed: [IMPACT] Since GCE FQDN are usually longer than 64-characters, several hi-profile tools like Java and Hadoop may break. [FIX] Per GCE's recommendation, Linux instances should use the short hostname over the FQDN. This change sets the system hostname to the short name. [VERIFICATION] 1. Install new cloud-init from proposed 2. Re-run cloud-config: -* 14.04/14.10: cloud-init single -n set_hostname --frequency=always -* 12.04: + * 14.04/14.10: cloud-init single -n set_hostname --frequency=always + * 12.04: cloud-init-cfg set_hostname always 3. Check to make sure that the short name is used for /etc/hostname [RISK] This is a very low risk change. The actual change is a single line, and has test cases for 14.04 and 14.10. Further, since this change is only in the GCE datasource, it only affects GCE instances. [ORIGINAL REPORT] The GCE datasource uses the long hostname. Hostnames longer than 64 characters can break several tools. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1383794 Title: [SRU] GCE datasource should use the short hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349868] Re: [MIR] new build dependencies for ceilometer
** Changed in: libsmi (Ubuntu) Status: New = In Progress -- 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/1349868 Title: [MIR] new build dependencies for ceilometer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmi/+bug/1349868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349868] Re: [MIR] new build dependencies for ceilometer
python-pysnmp4-apps packaging looks fine. There is no testsuite. Conditional ACK provided there is a bug subscriber. -- 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/1349868 Title: [MIR] new build dependencies for ceilometer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmi/+bug/1349868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349868] Re: [MIR] new build dependencies for ceilometer
libsmi packaging looks fine and ticks all the boxes except for the issues Seth mentioned. Needs a bug subscriber and to enable the testsuite. Considering the time, I would find it acceptable to enable the test suite in an SRU. ** Changed in: python-pysnmp4-apps (Ubuntu) Status: New = Fix Committed -- 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/1349868 Title: [MIR] new build dependencies for ceilometer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmi/+bug/1349868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349868] Re: [MIR] new build dependencies for ceilometer
python-pysnmp4 packaging looks fine too. There is no testsuite. Conditional ACK provided there is a bug subscriber, pending security review. -- 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/1349868 Title: [MIR] new build dependencies for ceilometer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmi/+bug/1349868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349868] Re: [MIR] new build dependencies for ceilometer
** Changed in: python-pysnmp4 (Ubuntu) Status: New = Fix Committed ** Changed in: libsmi (Ubuntu) Assignee: (unassigned) = Matthias Klose (doko) -- 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/1349868 Title: [MIR] new build dependencies for ceilometer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmi/+bug/1349868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381359] Re: [SRU] ship new public cert
This bug was fixed in the package pollinate - 4.7-0ubuntu1.2 --- pollinate (4.7-0ubuntu1.2) trusty-security; urgency=medium * debian/patches/1381359.patch: LP: #1381359 - update expiring SSL certificate -- Dustin Kirkland kirkl...@ubuntu.com Tue, 21 Oct 2014 16:12:43 -0700 ** Changed in: pollinate (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollinate in Ubuntu. https://bugs.launchpad.net/bugs/1381359 Title: [SRU] ship new public cert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1381359/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
I started out by poking the $GENERATE directive into my reverse zone file manually: ; Zone file modified: 2014-10-21 18:24:59.654931. ; Note that the modification time of this file doesn't reflect ; the actual modification time. MAAS controls the modification time ; of this file to be able to force the zone to be reloaded by BIND. $TTL300 @ INSOA maas. nobody.example.com. ( 000260 ; serial 600 ; Refresh 1800 ; Retry 604800 ; Expire 300 ; TTL ) IN NS maas. $GENERATE 1-100 $.0.0.10.in-addr.arpa. IN PTR no-name-yet-$.maas. 129.0.0.10.in-addr.arpa. IN PTR devoted-minute.maas. 128.0.0.10.in-addr.arpa. IN PTR dismayed-clown.maas. This works perfectly: graham@dodger:~⟫ dig +noall +answer -x 10.0.0.128 @10.0.0.1 128.0.0.10.in-addr.arpa. 300IN PTR dismayed-clown.maas. graham@dodger:~⟫ dig +noall +answer -x 10.0.0.129 @10.0.0.1 129.0.0.10.in-addr.arpa. 300IN PTR devoted-minute.maas. graham@dodger:~⟫ dig +noall +answer -x 10.0.0.100 @10.0.0.1 100.0.0.10.in-addr.arpa. 300IN PTR no-name-yet-100.maas. So, now all we need to do is have the DNSReverseZoneConfig add this for the dynamic range (I say all we need to do; obviously that's 1 task, but I'll divide it up in the morning). -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1377308] Re: booting cloud image without initramfs broken
** Attachment added: ppc64el console log without initramfs and with mountall debug https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4242046/+files/no-initrd-ppc64el.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1377308 Title: booting cloud image without initramfs broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1377308/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1377308] Re: booting cloud image without initramfs broken
** Attachment added: amd64 console log without initramfs and with mountall debug https://bugs.launchpad.net/cloud-init/+bug/1377308/+attachment/4242047/+files/no-initrd-amd64.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1377308 Title: booting cloud image without initramfs broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1377308/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349868] Re: [MIR] new build dependencies for ceilometer
PIE for libsmi enabled, and packages promoted. keeping the bug reports open, until the remaining issues are addressed ** Changed in: libsmi (Ubuntu) Status: In Progress = Fix Committed ** Changed in: libsmi (Ubuntu) Assignee: Matthias Klose (doko) = (unassigned) -- 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/1349868 Title: [MIR] new build dependencies for ceilometer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmi/+bug/1349868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
I think this will work for IPv6 too, but as Kiko pointed out on IRC so will wildcards — the main reason I'd like to stick with $GENERATE for both is that it's one less bit of code to write ;) -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
On 22 October 2014 22:03, Graham Binns graham.bi...@canonical.com wrote: This works perfectly: Awesome, that's great. Sort of brain-dump follows: How does this work for networks that don't line up with IPv4 octets? For example, for a dynamic range that covers 192.168.0.0/23, would we need to write the following? $GENERATE 1-254 $.0.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. $GENERATE 1-254 $.1.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. A /16 would need 256 lines. Is this expanded macro-like within BIND, or is it compiled into a rule? It may make a difference to performance. I assume we'll do this only for IPv4? If it's compiled to a rule, we /could/ do it for IPv6 too, but that may be a slope down which we don't want to slip. Ultimately we want to steer people towards reserving IP addresses via MAAS's API. Is this enough to satisfy RabbitMQ? Some services like to make sure that they can round-trip through DNS, i.e. that the PTR record resolves to a name that then resolves back to the starting address. We could choose the prefix to encourage people to reserve addresses. For example, dynamic-$, anon-$, temporary-$, or do-not-use-$, in order of severity. Unfortunately this is bikeshed territory, so I'm going to put myself out of the running by voting for do-not-rely-on-this-you-get-to-keep-the-pieces-and-give-me-one-million-dollars-$. -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384477] [NEW] install fails: insserv: ssh: Permission denied
Public bug reported: Setting up openssh-server (1:6.6p1-8) ... insserv: ssh: Permission denied update-rc.d: error: insserv rejected the script header dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1384477 Title: install fails: insserv: ssh: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1384477/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003854] Re: Database upgrade/migration fails with nested db directories (lucid to precise)
Fixed in Debian in 2.4.40-1. ** Changed in: openldap (Debian) Status: Fix Committed = Fix Released -- 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/1003854 Title: Database upgrade/migration fails with nested db directories (lucid to precise) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1003854/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
On 22 October 2014 23:19, Gavin Panella gavin.pane...@canonical.com wrote: On 22 October 2014 22:03, Graham Binns graham.bi...@canonical.com wrote: This works perfectly: Awesome, that's great. Sort of brain-dump follows: How does this work for networks that don't line up with IPv4 octets? For example, for a dynamic range that covers 192.168.0.0/23, would we need to write the following? $GENERATE 1-254 $.0.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. $GENERATE 1-254 $.1.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. A /16 would need 256 lines. If I'm reading [1] right (and I may not be; it's late), we could do something like this: $GENERATE 1-254 $.$.0.10.in-addr.arpa. IN PTR no-name-yet-$.$.maas. But a quick check of that on my local MAAS suggests it doesn't work. I'll dig further tomorrow. Is this expanded macro-like within BIND, or is it compiled into a rule? It may make a difference to performance. AFAICT, it's expanded rather than compiled into a rule. I assume we'll do this only for IPv4? If it's compiled to a rule, we /could/ do it for IPv6 too, but that may be a slope down which we don't want to slip. Ultimately we want to steer people towards reserving IP addresses via MAAS's API. True. That said, if we fix this for v6 too it means that some very nasty hacks in charms can be canned, and that's not a terrible thing for our users. If it's easy to do, I say we might as well be consistent. If v6 causes (as I suspect it will) considerable headaches here, then we'll stick with v4 and push for everyone to use APIs as they should be doing. Is this enough to satisfy RabbitMQ? Some services like to make sure that they can round-trip through DNS, i.e. that the PTR record resolves to a name that then resolves back to the starting address. I haven't checked that out yet, but it's a good point. We could always use $GENERATE to generate the forward zone too, though, if your first point doesn't make that entirely onerous. We could choose the prefix to encourage people to reserve addresses. For example, dynamic-$, anon-$, temporary-$, or do-not-use-$, in order of severity. Unfortunately this is bikeshed territory, so I'm going to put myself out of the running by voting for do-not-rely-on-this-you-get-to-keep-the-pieces-and-give-me-one-million-dollars-$. use-this-at-your-peril-$.maas. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
On 22 October 2014 23:56, Graham Binns graham.bi...@canonical.com wrote: $GENERATE 1-254 $.$.0.10.in-addr.arpa. IN PTR no-name-yet-$.$.maas. But a quick check of that on my local MAAS suggests it doesn't work. I'll dig further tomorrow. Nope, scratch that, it works fine. Well, named-checkzone generates a perfectly valid set of rules, but strangely the reverse lookup itself doesn't work. Definitely more poking to be done on the morrow. For a /23 (or some other such fun thing), yes, I think we'd have to write $GENERATE 1-254 $.0.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. $GENERATE 1-254 $.1.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. Again. More `dig`ing (geddit?) tomorrow. -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1368815] Re: qemu-img convert intermittently corrupts output images
FWIW the following 2 commits in qemu master resolve the issue for qemu- img. http://git.qemu.org/?p=qemu.git;a=commit;h=38c4d0aea3e1264c86e282d99560330adf2b6e25 http://git.qemu.org/?p=qemu.git;a=commit;h=7c15903789953ead14a417882657d52dc0c19a24 If possible they should be back ported to trusty and utopic. You'll also need something like: http://git.qemu.org/?p=qemu.git;a=commit;h=4f11aa8a40351b28c0e67c7276e0003b38cc46ac before my 2 patches. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1368815 Title: qemu-img convert intermittently corrupts output images To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1368815/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1377218] Re: [FFe] ceilometer 2014.2 rc2
This bug was fixed in the package ceilometer - 2014.2-0ubuntu1 --- ceilometer (2014.2-0ubuntu1) utopic; urgency=medium * New upstream release. -- Chuck Short zul...@ubuntu.com Thu, 16 Oct 2014 14:07:11 -0400 ** Changed in: ceilometer (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceilometer in Ubuntu. https://bugs.launchpad.net/bugs/1377218 Title: [FFe] ceilometer 2014.2 rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1377218/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1373617] Re: Still missing logrotate configuration files
This bug was fixed in the package ceilometer - 2014.2-0ubuntu1 --- ceilometer (2014.2-0ubuntu1) utopic; urgency=medium * New upstream release. -- Chuck Short zul...@ubuntu.com Thu, 16 Oct 2014 14:07:11 -0400 ** Changed in: ceilometer (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceilometer in Ubuntu. https://bugs.launchpad.net/bugs/1373617 Title: Still missing logrotate configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1373617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384503] [NEW] rsync fails on large files with compression
Public bug reported: Copying large (10GB) files with rsync -z (compression) leads to a long hang and eventual error after transferring part of the file. The error is consistent. The file copies at normal speed until it reaches its maximum size (1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for another). Then nothing happens for a while (many minutes). Finally, there is an error: [] jh/.VirtualBox/win7/win7.vbox jh/.VirtualBox/win7/win7.vbox-prev jh/.VirtualBox/win7/win7.vdi rsync: [sender] write error: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(837) [sender=3.1.0] In this case, 6.9 GB of 29 GB transferred. Without -z, it works. See the following upstream report, with a comment at the end from the rsync maintainer: https://bugzilla.samba.org/show_bug.cgi?id=10372 According to this report, version 3.1.0 (included in 14.04) uses a different compression package from prior versions. Prior versions did not have this problem for me using the same command on the same systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04 now, in each case with all updates applied, Intel hardware. Network connection between them is gigabit ethernet through one switch. A shell ssh between them in a terminal works and stays up during the failure, so it is not a network issue. There are no relevant entries in syslog on either machine. There is sufficient capacity on the receiving disk. All filesystems are ext4. rsync command: /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found --exclude=.gvfs --exclude=/nonlaptop /home/ backup.host.edu:/bu/host/home/ (yes, I changed the machine names) Current release (both hosts): Description:Ubuntu 14.04.1 LTS Release:14.04 Current package (both hosts): rsync: Installed: 3.1.0-2ubuntu0.1 Candidate: 3.1.0-2ubuntu0.1 Version table: *** 3.1.0-2ubuntu0.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.0-2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Thanks, --jh-- ** Affects: rsync (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1384503 Title: rsync fails on large files with compression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1377308] Re: booting cloud image without initramfs broken
bah. /etc/init/cloud-init-local.conf - start on mounted MOUNTPOINT=/ +start on mounted MOUNTPOINT=/ and mounted MOUNTPOINT=/run -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1377308 Title: booting cloud image without initramfs broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1377308/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1377308] Re: booting cloud image without initramfs broken
comment 3 above is ordered wrong. the change that caused this is: /etc/init/cloud-init-local.conf +start on mounted MOUNTPOINT=/ +start on mounted MOUNTPOINT=/ and mounted MOUNTPOINT=/run the reason was that cloud-init-local needs to write to / and to /run. previously it was using /run without declaring the need for it. also cloud-init generally wants 'mounted' to block things. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1377308 Title: booting cloud image without initramfs broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1377308/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
On Wednesday 22 Oct 2014 23:18:24 you wrote: On 22 October 2014 23:56, Graham Binns graham.bi...@canonical.com wrote: $GENERATE 1-254 $.$.0.10.in-addr.arpa. IN PTR no-name-yet-$.$.maas. But a quick check of that on my local MAAS suggests it doesn't work. I'll dig further tomorrow. Nope, scratch that, it works fine. Well, named-checkzone generates a perfectly valid set of rules, but strangely the reverse lookup itself doesn't work. Definitely more poking to be done on the morrow. For a /23 (or some other such fun thing), yes, I think we'd have to write $GENERATE 1-254 $.0.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. $GENERATE 1-254 $.1.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. Again. More `dig`ing (geddit?) tomorrow. See the related bug 1356012 about that. -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384232] Re: Certificate hostname verification fix
We sent email to cve-ass...@mitre.org and got the following response, but we don't agree that this is an intentionally made. This patch appears to be outside the scope of CVE. For issues of this type, the scope of CVE is limited to unintentional implementation mistakes. Here, the vendor intentionally did not do a hostname check because (quoting http://bugs.exim.org/show_bug.cgi?id=1479#c2) Exim is an MTA, there has been no sane approach to determining a hostname suitable for verification of certificate identity. The vendor went on to implement a useful security enhancement in response to your report. This is a very good outcome, but security enhancements are not assigned CVE-IDs. ** Bug watch added: bugs.exim.org/ #1479 http://bugs.exim.org/show_bug.cgi?id=1479 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/1384232 Title: Certificate hostname verification fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1384232/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384532] [NEW] libvirt-qemu apparmor profile missing kvm-spice
Public bug reported: /usr/bin/kvm-spice is a soft-link to /usr/bin/kvm in /etc/apparmor.d/abstractions/libvirt-qemu there is no line for kvm- spice. This leads rise to the error: libvirt: error : unable to set AppArmor profile 'libvirt-224075ba-a31a-48e9-98fe-337146e9f4f1' for '/usr/bin/kvm-spice': No such file or directory when using e.g. OpenStack $ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 $ dpkg -l|grep libvirt-bin ii libvirt-bin 1.2.8-0ubuntu11 amd64programs for the libvirt library ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- 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/1384532 Title: libvirt-qemu apparmor profile missing kvm-spice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384327] Re: lxc-attach --clear-env results in a limited $PATH in the container
Looks like the value actually comes straight from a #define in the glibc source code. As such, I think it would be pretty reasonable to change lxc to always use its own path. ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: Invalid = Triaged -- 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/1384327 Title: lxc-attach --clear-env results in a limited $PATH in the container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384327/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
I think this is a dupe of bug 1274947. -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
