[Bug 1078177] Re: typo in /etc/default/nagios3
Thank you for taking the time to report this bug and helping to make Ubuntu better. This typo is present in Debian too, and Ubuntu currently doesn't make any changes over the Debian package. So this bug would be best fixed directly in Debian, and then Ubuntu will pick up the fix automatically. Would you mind filing a bug with Debian please? ** Tags added: needs-upstream-report ** Changed in: nagios3 (Ubuntu) Status: New = Triaged ** Changed in: nagios3 (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1078177 Title: typo in /etc/default/nagios3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1078177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
To some extent it is a bug in the upstream kernel, which doesn't reset state properly. However, the qemu patch is also good. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078213] [NEW] juju-machine-agent.log is not logrotated
Public bug reported: I've been running a small juju cluster for a week now. There were some connection issues in the data center I'm using and juju had issues connecting to zookeeper. As a result /var/log/juju/juju- machine-agent.log quickly grew to 200M Overall on the four machines that make up my installation all of juju logs, combined, were over 2GB in size. With the size of the instances this is quickly becoming an issue. I don't imagine how I would manage a large juju cluster without scripting around this issue. I think that juju must support logrotate automatically out of the box. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:09:01 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise ** Description changed: - I'm running a small juju cluster for a week now. + I've been running a small juju cluster for a week now. There were some connection issues in the data center I'm using and juju had issues connecting to zookeeper. As a result /var/log/juju/juju- machine-agent.log quickly grew to 200M Overall on the four machines that make up my installation all of juju logs, combined, were over 2GB in size. With the size of the instances this is quickly becoming an issue. I don't imagine how I would manage a large juju cluster without scripting around this issue. I think that juju must support logrotate automatically out of the box. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:09:01 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: juju 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 juju in Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: juju-machine-agent.log is not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078213/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078214] [NEW] /var/lib/juju/units/*/charm.log is not logrotated
Public bug reported: I've deployed jenkins and jenkins-slave units in my juju cluster. On one of the jenkins-slave instances the /var/lib/juju/units/jenkins- slave-*/charm.log was over 700M in size (uncompressed) before I spotted the issue. This instance is very lightly used and it was running for a few days at most (having been added later in the week) With the size of disk instances this is a major issue. I think this file must be automatically logrotated out of the box. It should be also, perhaps, moved to /var/log/juju for consistency. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:15:34 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078214 Title: /var/lib/juju/units/*/charm.log is not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078214/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078217] [NEW] zookeeper connection is not using exponential backoff
Public bug reported: My juju cluster had some connection issues to zookeeper. While I was reading the charm.log of my jenkins-slave unit I noticed that juju had logged many thousands of exceptions such as this one: 2012-11-09 06:51:07,514: twisted@ERROR: Traceback (most recent call last): 2012-11-09 06:51:07,514: twisted@ERROR: File /usr/lib/python2.7/dist-packages/txzookeeper/managed.py, line 319, in _cb_created 2012-11-09 06:51:07,514: twisted@ERROR: if self._check_result(result_code, d): 2012-11-09 06:51:07,514: twisted@ERROR: File /usr/lib/python2.7/dist-packages/txzookeeper/client.py, line 219, in _check_result 2012-11-09 06:51:07,514: twisted@ERROR: self, error) 2012-11-09 06:51:07,515: twisted@ERROR: File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 134, in maybeDeferred 2012-11-09 06:51:07,515: twisted@ERROR: result = f(*args, **kw) 2012-11-09 06:51:07,515: twisted@ERROR: File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1181, in unwindGenerator 2012-11-09 06:51:07,515: twisted@ERROR: return _inlineCallbacks(None, gen, Deferred()) 2012-11-09 06:51:07,516: twisted@ERROR: --- exception caught here --- 2012-11-09 06:51:07,516: twisted@ERROR: File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1039, in _inlineCallbacks 2012-11-09 06:51:07,516: twisted@ERROR: result = g.send(result) 2012-11-09 06:51:07,516: twisted@ERROR: File /usr/lib/python2.7/dist-packages/txzookeeper/managed.py, line 257, in _cb_connection_error 2012-11-09 06:51:07,517: twisted@ERROR: raise error 2012-11-09 06:51:07,517: twisted@ERROR: zookeeper.ConnectionLossException: connection loss I can see about 300 such exceptions _every second_. This is very bad on two levels: 1) It quickly fills the log with pointless exceptions, using disk space, saturating slow virtual IO 2) It is against proven network practice of using exponential backoff when retrying failed communication ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:26:31 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078217 Title: zookeeper connection is not using exponential backoff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078217/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078216] [NEW] exceptions.AttributeError: 'UnitAgent' object has no attribute 'lifecycle'
Public bug reported: I was analyzing why my juju cluster was down. The particular instance I was analyzing had the jenkins-slave charm deployed. Reading /var/lib/juju/units/jenkins-slave-*/charm.log I found the following unhandled exception: 2012-11-13 09:04:23,261: twisted@ERROR: Unhandled error in Deferred: 2012-11-13 09:04:23,262: twisted@ERROR: Unhandled Error Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1181, in unwindGenerator return _inlineCallbacks(None, gen, Deferred()) File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1039, in _inlineCallbacks result = g.send(result) File /usr/lib/python2.7/dist-packages/juju/agents/base.py, line 250, in stopService yield self.stop() File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1181, in unwindGenerator return _inlineCallbacks(None, gen, Deferred()) --- exception caught here --- File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1039, in _inlineCallbacks result = g.send(result) File /usr/lib/python2.7/dist-packages/juju/agents/unit.py, line 127, in stop if self.lifecycle.running: exceptions.AttributeError: 'UnitAgent' object has no attribute 'lifecycle' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:23:43 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078216 Title: exceptions.AttributeError: 'UnitAgent' object has no attribute 'lifecycle' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078216/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078102] Re: /etc/ldap/ldap.conf missing
Thank you for taking the time to report this bug and helping to make Ubuntu better. It is certainly confusing that PAM uses /etc/ldap.conf whereas openldap uses /etc/ldap/ldap.conf. But it isn't clear to me that these two files are actually of the same format, or that it is guaranteed that one is a superset of the other. The pam_ldap(5) manpage says: pam_ldap stores its configuration in the ldap.conf file. (It should be noted that some LDAP client libraries, such as OpenLDAP, also use a configuration file of the same name. pam_ldap supports many of the same configuration file options as OpenLDAP, but it adds several that are specific to the functionality it provides. It is not guaranteed that pam_ldap will continue to match the configura‐ tion file semantics of OpenLDAP. You may wish to use different files.) I think that doing something such as your symlink would have unintended consequences, so I'm not sure that a fix for the general case is trivial. And any change would best be coordinated with Debian. ** Package changed: openldap (Ubuntu) = libpam-ldap (Ubuntu) ** Changed in: libpam-ldap (Ubuntu) Importance: Undecided = Medium ** Changed in: libpam-ldap (Ubuntu) Status: New = Triaged ** Summary changed: - /etc/ldap/ldap.conf missing + libpam-ldap should share openldap's configuration file ** Summary changed: - libpam-ldap should share openldap's configuration file + libpam-ldap should share openldap's configuration mechanism ** Also affects: openldap (Ubuntu) Importance: Undecided Status: New ** Changed in: openldap (Ubuntu) Importance: Undecided = Medium ** Changed in: openldap (Ubuntu) Status: New = Triaged -- 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/1078102 Title: libpam-ldap should share openldap's configuration mechanism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-ldap/+bug/1078102/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
** Changed in: qemu Status: New = In Progress ** Changed in: qemu Assignee: (unassigned) = Paolo Bonzini (bonzini) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074659] Re: ssh hangs if pm-hibernate ran on server
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please could you confirm how long you've waited for the client to time out, and whether you have tried to send any data from the client or if you are expecting it to time out on its own? ssh_config(5) indicates that by default TCP keepalives are enabled, and on my system it looks like Linux won't default to timing out on TCP keepalives for at least two hours and eleven minutes (tcp_keepalive_time=7200, tcp_keepalive_intvl=75, tcp_keepalive_probes=9). Have you waited this long? Additionally, are you aware of the ServerAliveInterval (and/or ClientAliveInterval on the server side) option? Please could you also clarify if the bug that you are reporting is that you want the default timeout options changed, the timeout tuning options don't work, or something else? ** Changed in: openssh (Ubuntu) Status: New = Incomplete -- 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/1074659 Title: ssh hangs if pm-hibernate ran on server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1074659/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078177] Re: typo in /etc/default/nagios3
ok sure,thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1078177 Title: typo in /etc/default/nagios3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1078177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1070519] Re: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: juju (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1070519 Title: zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1070519/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078242] [NEW] juju cannot connect to zookeeper - too many connections (max 10)
Public bug reported: My juju cluster running on precise had severe connection issues to zookeeper. Looking at zookeeper logs I can see that my juju nodes cannot connect as they already have pending connections. Zookeeper log is full of lines like (quick count gives me around 30,000) 2012-11-08 06:46:48,777 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /10.55.60.51 - max is 10 There are also session expiration messages (around 1000) 2012-11-08 06:46:58,000 - INFO [SessionTracker:ZooKeeperServer@316] - Expiring session 0x13ad043e9460400, timeout of 1ms exceeded And exceptions (about 4000) 2012-11-08 06:47:05,663 - ERROR [SyncThread:0:NIOServerCnxn@445] - Unexpected Exception: java.nio.channels.CancelledKeyException at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:73) at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:77) at org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:418) at org.apache.zookeeper.server.NIOServerCnxn.sendResponse(NIOServerCnxn.java:1509) at org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:162) at org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:135) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 11:11:30 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078242 Title: juju cannot connect to zookeeper - too many connections (max 10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078242/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074777] Re: package libldap-2.4-2 2.4.31-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:i3
Bug in dpkg; fixed in the version of dpkg in raring. SRU needed. ** Bug watch added: Debian Bug tracker #684776 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684776 ** Also affects: openldap (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684776 Importance: Unknown Status: Unknown ** Changed in: openldap (Ubuntu) Status: New = Fix Released ** Also affects: openldap (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Quantal) Importance: Undecided Status: New ** Changed in: openldap (Ubuntu Precise) Status: New = Triaged ** Changed in: openldap (Ubuntu Precise) Importance: Undecided = High ** Changed in: openldap (Ubuntu Quantal) Status: New = Triaged ** Changed in: openldap (Ubuntu Quantal) Importance: Undecided = High ** Changed in: openldap (Ubuntu Precise) Milestone: None = ubuntu-12.04.2 ** Changed in: openldap (Ubuntu Quantal) Milestone: None = quantal-updates -- 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/1074777 Title: package libldap-2.4-2 2.4.31-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1074777/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 876387] Re: fuser forking uncontrollably in cron job
Me too. a lot of fuser get over 20% of my CPU all time. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/876387 Title: fuser forking uncontrollably in cron job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/876387/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074777] Re: package libldap-2.4-2 2.4.31-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:i3
Looks like we need to cherry-pick this: http://anonscm.debian.org/gitweb/?p=dpkg/dpkg.git;a=commitdiff;h=05a8ddb -- 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/1074777 Title: package libldap-2.4-2 2.4.31-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1074777/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 876387] Re: fuser forking uncontrollably in cron job
Me too. If you really feel the urge to write Me too. (instead of just clicking at the top of the page), please at least provide some useful information. The version of Ubuntu, it's architecture, version of PHP 5 packages (php5-common should suffice) and version of psmisc package. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/876387 Title: fuser forking uncontrollably in cron job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/876387/+subscriptions -- Ubuntu-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 1078177] Re: typo in /etc/default/nagios3
On 11/13/2012 10:08 AM, Robie Basak wrote: Thank you for taking the time to report this bug and helping to make Ubuntu better. This typo is present in Debian too, and Ubuntu currently doesn't make any changes over the Debian package. So this bug would be best fixed directly in Debian, and then Ubuntu will pick up the fix automatically. Would you mind filing a bug with Debian please? not needed ... this is fixed in debian packaging vcs (77c9d0ef43ca87e6439abc4d035a71e4f66bfd0d) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1078177 Title: typo in /etc/default/nagios3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1078177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078177] Re: typo in /etc/default/nagios3
** Bug watch added: Debian Bug tracker #693124 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693124 ** Also affects: nagios3 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693124 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1078177 Title: typo in /etc/default/nagios3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1078177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073289] Re: nova-common has an incorrect dep on python-nova (= 2012.1-0ubuntu2)
** Changed in: nova (Ubuntu) Importance: Undecided = Medium ** Changed in: nova (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1073289 Title: nova-common has an incorrect dep on python-nova (= 2012.1-0ubuntu2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1073289/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1036093] Re: nova volume-attach with high device name keeps volume in state attaching
Marking as invalid as per upstream bug ** Changed in: nova (Ubuntu) Status: New = Invalid -- 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/1036093 Title: nova volume-attach with high device name keeps volume in state attaching To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1036093/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074359] Re: [SRU] Meta bug for tracking Nova stable update
** Changed in: nova (Ubuntu) Importance: Undecided = Medium ** Changed in: nova (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1074359 Title: [SRU] Meta bug for tracking Nova stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1074359/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077003] Re: ntp ignores config option interface ignore all
Hi, my expectation was that the ntp process does not open a port on any interface but localhost. The use case is to use the ntp daemon to permanently synchronize the time with a central time server, but not to serve the time to any other host. The interface option is defined in the nat.conf man page. However, when I double checked it today to add a link to this bug I saw that this was the manpage for precise (where ntpd works as I expected it). In the man page for lucid there is no sign of the interface option. So I guess this option was added somewhere between lucid and precise by the ntp developers. Sorry for not double checking this before opening a bug... I marked the bug as invalid. Regards, Michael ** Changed in: ntp (Ubuntu) Status: Incomplete = Invalid -- 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/1077003 Title: ntp ignores config option interface ignore all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1077003/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1029817] Re: Please enable bash completion
Done ** Changed in: python-novaclient (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/1029817 Title: Please enable bash completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/1029817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1075189] Re: python-glance client breaks on package upgrade
Closing ** Changed in: python-glanceclient (Ubuntu) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-glanceclient in Ubuntu. https://bugs.launchpad.net/bugs/1075189 Title: python-glance client breaks on package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-glanceclient/+bug/1075189/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020238] Re: nova client keeps asking for a keyring password
Work around according to the last comment. ** Changed in: python-novaclient (Ubuntu) Importance: Undecided = Low ** Changed in: python-novaclient (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/1020238 Title: nova client keeps asking for a keyring password To manage notifications about this bug go to: https://bugs.launchpad.net/python-novaclient/+bug/1020238/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1070630] Re: glance-manage does not read configuration correctly
** Changed in: glance (Ubuntu) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1070630 Title: glance-manage does not read configuration correctly To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1070630/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-openstack-ha] OpenStack Infrastructure HA
Blueprint changed by Andres Rodriguez: Definition Status: Drafting = Review -- OpenStack Infrastructure HA https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-ha -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-maas-next-steps] MAAS next steps
Blueprint changed by Andres Rodriguez: Definition Status: Drafting = Review -- MAAS next steps https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas-next-steps -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065255] Re: Installing glance client after keystone results in error
** Changed in: glance (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1065255 Title: Installing glance client after keystone results in error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glance/+bug/1065255/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667935] Re: Add etc/swift.conf-sample to base swift package
** Changed in: swift (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/667935 Title: Add etc/swift.conf-sample to base swift package To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/667935/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1035878] Re: man page useless
This looks like it has been fixed in a recent version of swift. ** Changed in: swift (Ubuntu) Status: Confirmed = Fix Committed ** Changed in: swift (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/1035878 Title: man page useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1035878/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073289] Re: nova-common has an incorrect dep on python-nova (= 2012.1-0ubuntu2)
** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: cloud-archive Importance: Undecided = Medium ** Changed in: cloud-archive Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1073289 Title: nova-common has an incorrect dep on python-nova (= 2012.1-0ubuntu2) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1073289/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cloud-archive Importance: Undecided = High ** Changed in: cloud-archive Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master
Puppet sources additional directories for facts, (hence facter -p). If I understand this report correctly, it sounds to me that the problem is that puppet is not sourcing /var/lib/puppet/lib/facter for facts, which is where factsync is writing them. Setting FACTERLIB in /etc/default/puppet is a workaround for the daemon, but will not work when calling puppet agent --test from the commandline, which should work too (but presumably doesn't). Is this an accurate interpretation? Have I understood your description wrong? What is upstream's behaviour here? ** Changed in: puppet (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1076286 Title: Puppet agent not correcly configuring facts synch'd from master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078177] Re: typo in /etc/default/nagios3
** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1078177 Title: typo in /etc/default/nagios3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1078177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078177] Re: typo in /etc/default/nagios3
Just realised that you've filed in Debian and linked it. Thanks! ** Tags removed: bitesize needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1078177 Title: typo in /etc/default/nagios3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1078177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master
Robie, yes the problem is exactly the one you described. The puppet daemon does not source /var/lib/puppet/lib/facter for facts and my proposed modification is a workaround to have it properly running. Also the command puppet agent --test does not source the facts in /var/lib/puppet/lib/facter and this is not solved by the modification I proposed. My proposal is a very quick fix to have the daemon properly running. I thought that when running the puppet command from commandline the user could define FACTERLIB in his environment somehow. Of course if you can find better solutions, they're very welcome. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1076286 Title: Puppet agent not correcly configuring facts synch'd from master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1061665] Re: Filter scheduler not respecting the force_hosts hint
** Changed in: openstack-manuals Status: Triaged = Fix Committed -- 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/1061665 Title: Filter scheduler not respecting the force_hosts hint To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1061665/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-maas-next-steps] MAAS next steps
Blueprint changed by Andres Rodriguez: Work items changed: Work items: [andreserl] SRU django 1.4 GenericIpAddressField to 1.3 for 12.04: TODO [andreserl] SRU 12.10-stabilization to Quantal: TODO [andreserl] SRU 12.10-stabilization to Precise: TODO [andreserl] SRU python-tx-tftp to Precise: TODO [andreserl] SRU yui3 to Precise: TODO [andreserl] SRU Raring features to Quantal: TODO [andreserl] SRU Raring features to Precise: TODO [andreserl] Bug #1073462 fence_cdu power type is missing: TODO - [andreserl] Bug #1064224 IPMI detection ends up with power_address of 0.0.0.0: TODO + [andreserl] Bug #1064224 IPMI detection ends up with power_address of 0.0.0.0: INPROGRESS [andreserl] Bug #1064527 detect_ipmi needs improvement. detects non-existant device in nested kvm: TODO + [andreserl] maas-ipmi-autodetect and maas-signal should be shipped with MAAS: TODO [maas-maintainers] Bug #975454complete documentation and man pages: TODO [maas-maintainers] Bug #1044503 kernel command line is not easily customizable: TODO [maas-maintainers] Bug #1066775 Main page slow to load with many nodes: DONE [maas-maintainers] Bug #1068843 maas-cluster-controller doesn't have images for provisioning: DONE [maas-maintainers] Bug #1069734 Filestorage is unique to each appserver instance: DONE [maas-maintainers] Bug #1069850 import_pxe_files does not include quantal: DONE [maas-maintainers] Bug #1070522 maas-cli nodes new incomplete documentation: DONE [maas-maintainers] Bug #1070765 DNS forward zone ends up with nonsensical entries: DONE [maas-maintainers] Bug #1070774 The hostname of a node can still be changed once the node is in use: DONE [maas-maintainers] Bug #1070775 The zone name (attached to a cluster controller) can still be changed when it contains in-use nodes and DNS is managed.: DONE [maas-maintainers] Bug #1075597 Duplicated prefix in the url used by the CLI: DONE [maas-maintainers] Bug #1034318 API calls that return a node leak private data: DONE [maas-maintainers] Bug #1059645 URI in API description wrong when accessing machine via alternative interface: DONE [maas-maintainers] Bug #1069603 Error in log when using 'Start node' button: MAASAPINotFound: No user data available for this node.: DONE [maas-maintainers] define supported release combination matrix: TODO -- MAAS next steps https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas-next-steps -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1075456] Re: wrong path given in README
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug is present in Debian too. So it would be best fixed in Debian, and then Ubuntu will pick it up on the next merge. Would you mind filing a bug with Debian please? ** Changed in: dovecot (Ubuntu) Status: New = Triaged ** Changed in: dovecot (Ubuntu) Importance: Undecided = Medium ** Tags added: bitesize needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1075456 Title: wrong path given in README To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1075456/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064224] Re: IPMI detection ends up with power_address of 0.0.0.0
** Changed in: maas Status: Triaged = In Progress ** Changed in: maas/1.2 Status: Triaged = In Progress -- 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/1064224 Title: IPMI detection ends up with power_address of 0.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1064224/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064224] Re: IPMI detection ends up with power_address of 0.0.0.0
** Branch linked: lp:~andreserl/maas/maas_ipmi_lp1064224 -- 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/1064224 Title: IPMI detection ends up with power_address of 0.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1064224/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master
Thanks Andrea. I'm not sure about fixing /etc/default/puppet in Ubuntu as in my judgement changing puppet agent --test to behave differently from the daemon would be worse for users. For the time being, users can find this bug and the associated workaround. For a proper fix, the next step is to identify whether this bug is present in the upstream project, introduced in the Debian packaging or introduced in Ubuntu's modifications. If Ubuntu hasn't introduced the problem, we should get a bug filed in the appropriate bug tracker. Are you able to help with this, please? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1076286 Title: Puppet agent not correcly configuring facts synch'd from master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 921489] Re: Segmentation fault in slapd (related to GSSAPI?)
I have several installation of slave slapd segfaulting. (gdb) run -h 'ldap://MYIP/ ldapi:///' -g openldap -u openldap -f /etc/ldap/slapd.conf -d 0 Starting program: /usr/sbin/slapd -h 'ldap://MYIP/ ldapi:///' -g openldap -u openldap -f /etc/ldap/slapd.conf -d 0 [Thread debugging using libthread_db enabled] [New Thread 0x7f2bdb7b5700 (LWP 7623)] [New Thread 0x7f2bdafb4700 (LWP 7624)] [New Thread 0x7f2bda7b3700 (LWP 7625)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2bdafb4700 (LWP 7624)] 0x7f2be16a4592 in ?? () (gdb) where #0 0x7f2be16a4592 in ?? () #1 0x7f2be16a5fd4 in ?? () #2 0x7f2be16a8cd7 in ?? () #3 0x7f2be11a22d8 in ldap_int_thread_pool_wrapper (xpool=value optimized out) at /build/buildd/openldap-2.4.21/libraries/libldap_r/tpool.c:685 #4 0x7f2bdf6439ca in start_thread () from /lib/libpthread.so.0 #5 0x7f2bdf3a016d in clone () from /lib/libc.so.6 #6 0x in ?? () i don't use gssapi and the error is in a different place but it might be related. Too bad the dbg packages are brocken. -- 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/921489 Title: Segmentation fault in slapd (related to GSSAPI?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/921489/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 921489] Re: Segmentation fault in slapd (related to GSSAPI?)
I instaled slapd-dbg and i have more informations: #0 syncrepl_entry (si=0x7fbe0206c4c0, op=0x7fbdfb537470, entry=0x7fbe020dab78, modlist=value optimized out, syncstate=value optimized out, syncUUID=value optimized out, syncCSN=0x0) at /build/buildd/openldap-2.4.21/servers/slapd/syncrepl.c:2428 #1 0x7fbe01c29fd4 in do_syncrep2 (op=0x7fbdfb537470, si=0x7fbe0206c4c0) at /build/buildd/openldap-2.4.21/servers/slapd/syncrepl.c:939 #2 0x7fbe01c2ccd7 in do_syncrepl (ctx=value optimized out, arg=0x7fbe0206b470) at /build/buildd/openldap-2.4.21/servers/slapd/syncrepl.c:1432 #3 0x7fbe017262d8 in ldap_int_thread_pool_wrapper (xpool=value optimized out) at /build/buildd/openldap-2.4.21/libraries/libldap_r/tpool.c:685 #4 0x7fbdffbc79ca in start_thread () from /lib/libpthread.so.0 #5 0x7fbdff92416d in clone () from /lib/libc.so.6 #6 0x in ?? () -- 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/921489 Title: Segmentation fault in slapd (related to GSSAPI?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/921489/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078364] [NEW] package lxc-templates (not installed) failed to install/upgrade: trying to overwrite '/usr/share/lxc/templates/lxc-opensuse', which is also in package lxc 0.8.0~rc1-4ubuntu42
Public bug reported: simple apt-get dselect-upgrade ProblemType: Package DistroRelease: Ubuntu 13.04 Package: lxc-templates (not installed) ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.2-0ubuntu3 AptOrdering: lxc-templates: Install lxc-templates: Configure Architecture: amd64 Date: Tue Nov 13 10:30:24 2012 ErrorMessage: trying to overwrite '/usr/share/lxc/templates/lxc-opensuse', which is also in package lxc 0.8.0~rc1-4ubuntu42 InstallationDate: Installed on 2011-12-22 (326 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=4c95009a-cfb3-44f5-9d2c-5fdc9fde26d4 ro SourcePackage: lxc Title: package lxc-templates (not installed) failed to install/upgrade: trying to overwrite '/usr/share/lxc/templates/lxc-opensuse', which is also in package lxc 0.8.0~rc1-4ubuntu42 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package raring -- 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/1078364 Title: package lxc-templates (not installed) failed to install/upgrade: trying to overwrite '/usr/share/lxc/templates/lxc-opensuse', which is also in package lxc 0.8.0~rc1-4ubuntu42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1078364/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078364] Re: package lxc-templates (not installed) failed to install/upgrade: trying to overwrite '/usr/share/lxc/templates/lxc-opensuse', which is also in package lxc 0.8.0~rc1-4ubuntu42
A fix has been uploaded 2 minutes before you filed this bug :) I expect the new fixed version to be available in the next hour or so. ** Changed in: lxc (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1078364 Title: package lxc-templates (not installed) failed to install/upgrade: trying to overwrite '/usr/share/lxc/templates/lxc-opensuse', which is also in package lxc 0.8.0~rc1-4ubuntu42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1078364/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-ceph] Ceph Activities for Raring
Blueprint changed by James Page: Work items changed: Work items: Backport argonaut to precise-folsom cloud archive: TODO Upgrade packaging to bobtail release: TODO MIR for additional dependencies for upstart integration: TODO Enable upstart configurations in packaging: TODO Enable XFS recommends in packaging: TODO Test upgrade paths from 12.10 with upstart and init scripts: TODO Upstream support for XFS in ceph-disk-*: TODO Review upstream patches for mod_fastcgi: TODO Review/test ceph RADOS with mod_fcgid: TODO Write dep8 tests for ceph and get automated: TODO Write UTAH tests for ceph and get automated: TODO Identify use-cases for ceph performance scenarios: TODO Upload bobtail to the grizzly cloud archive: TODO Multi-node ceph testing in the lab: TODO Ceph testing in the Openstack CI Lab: TODO - Enable rbd storage pool support in libvirt: TODO + Enable rbd storage pool support in libvirt: DONE -- Ceph Activities for Raring https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-ceph -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-ceph] Ceph Activities for Raring
Blueprint changed by James Page: Work items changed: Work items: - Backport argonaut to precise-folsom cloud archive: TODO + Backport argonaut to precise-folsom cloud archive: INPROGRESS Upgrade packaging to bobtail release: TODO MIR for additional dependencies for upstart integration: TODO Enable upstart configurations in packaging: TODO Enable XFS recommends in packaging: TODO Test upgrade paths from 12.10 with upstart and init scripts: TODO Upstream support for XFS in ceph-disk-*: TODO Review upstream patches for mod_fastcgi: TODO Review/test ceph RADOS with mod_fcgid: TODO Write dep8 tests for ceph and get automated: TODO Write UTAH tests for ceph and get automated: TODO Identify use-cases for ceph performance scenarios: TODO Upload bobtail to the grizzly cloud archive: TODO Multi-node ceph testing in the lab: TODO - Ceph testing in the Openstack CI Lab: TODO + Ceph testing in the Openstack CI Lab: INPROGRESS Enable rbd storage pool support in libvirt: DONE -- Ceph Activities for Raring https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-ceph -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076277] Re: package rrdcached 1.4.7-1 failed to install: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 139
Thank's a lot. That's solved the problem.. Best regards -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rrdtool in Ubuntu. https://bugs.launchpad.net/bugs/1076277 Title: package rrdcached 1.4.7-1 failed to install: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rrdtool/+bug/1076277/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1072772] Re: Package upgrade breaks rabbitmq communication.
I was unable to reproduce this bug report after many attempts. I'll mark it as incomplete for now and try to reproduce again when we are ready to SRU. ** Changed in: maas (Ubuntu) Status: Triaged = Incomplete -- 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/1072772 Title: Package upgrade breaks rabbitmq communication. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1072772/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-maas-next-steps] MAAS next steps
Blueprint changed by Andres Rodriguez: Work items changed: Work items: [andreserl] SRU django 1.4 GenericIpAddressField to 1.3 for 12.04: TODO [andreserl] SRU 12.10-stabilization to Quantal: TODO [andreserl] SRU 12.10-stabilization to Precise: TODO + [andreserl] SRU python-tx-tftp (0.1~bzr31-0ubuntu7) to Quantal: TODO [andreserl] SRU python-tx-tftp to Precise: TODO [andreserl] SRU yui3 to Precise: TODO [andreserl] SRU Raring features to Quantal: TODO [andreserl] SRU Raring features to Precise: TODO [andreserl] Bug #1073462 fence_cdu power type is missing: TODO [andreserl] Bug #1064224 IPMI detection ends up with power_address of 0.0.0.0: INPROGRESS [andreserl] Bug #1064527 detect_ipmi needs improvement. detects non-existant device in nested kvm: TODO [andreserl] maas-ipmi-autodetect and maas-signal should be shipped with MAAS: TODO [maas-maintainers] Bug #975454complete documentation and man pages: TODO [maas-maintainers] Bug #1044503 kernel command line is not easily customizable: TODO [maas-maintainers] Bug #1066775 Main page slow to load with many nodes: DONE [maas-maintainers] Bug #1068843 maas-cluster-controller doesn't have images for provisioning: DONE [maas-maintainers] Bug #1069734 Filestorage is unique to each appserver instance: DONE [maas-maintainers] Bug #1069850 import_pxe_files does not include quantal: DONE [maas-maintainers] Bug #1070522 maas-cli nodes new incomplete documentation: DONE [maas-maintainers] Bug #1070765 DNS forward zone ends up with nonsensical entries: DONE [maas-maintainers] Bug #1070774 The hostname of a node can still be changed once the node is in use: DONE [maas-maintainers] Bug #1070775 The zone name (attached to a cluster controller) can still be changed when it contains in-use nodes and DNS is managed.: DONE [maas-maintainers] Bug #1075597 Duplicated prefix in the url used by the CLI: DONE [maas-maintainers] Bug #1034318 API calls that return a node leak private data: DONE [maas-maintainers] Bug #1059645 URI in API description wrong when accessing machine via alternative interface: DONE [maas-maintainers] Bug #1069603 Error in log when using 'Start node' button: MAASAPINotFound: No user data available for this node.: DONE [maas-maintainers] define supported release combination matrix: TODO -- MAAS next steps https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas-next-steps -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076075] Re: maas_cluster.conf ends up with the wrong URL after upgrade.
** Also affects: maas (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Quantal) 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/1076075 Title: maas_cluster.conf ends up with the wrong URL after upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1076075/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076028] Re: maas-cluster-controller should conflict with tftpd-hpa
** Also affects: maas (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Quantal) 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/1076028 Title: maas-cluster-controller should conflict with tftpd-hpa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1076028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078444] [NEW] python-boto should verify SSL certificates and should use the systems certificate repository
Public bug reported: Currently python-boto does not verify SSL certificates by default. This is unacceptable as this exposes users to man in the middle attacks. This can be worked around by the user (see below). Unfortunately after enabling verification, python-boto uses it's own cacerts.txt file to verify certificates and does not use the system provided certificates. If a valid certificate is not included in the python-boto shipped cacerts.txt file and certificate validation is tuned on, then verification will fail. I presume that this behaviour exists to enable cross platform compatibility. Python-boto should enable SSL certificate verification by default and use the system installed certificates (perhaps falling back to it's shipped certs file if necessary). The method to override verification should be included in the package documentation (or a README). = Workaround to enable verification = Create a ~/.boto file with the following: [Boto] https_validate_certificates = true = System Information = $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.10 DISTRIB_CODENAME=quantal DISTRIB_DESCRIPTION=Ubuntu 12.10 $ dpkg-query --show python-boto ca-certificates ca-certificates 20120623 python-boto 2.3.0-1 ** Affects: python-boto (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1078444 Title: python-boto should verify SSL certificates and should use the systems certificate repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto/+bug/1078444/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078444] Re: python-boto should verify SSL certificates and should use the systems certificate repository
** Changed in: python-boto (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1078444 Title: python-boto should verify SSL certificates and should use the systems certificate repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto/+bug/1078444/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076028] Re: maas-cluster-controller should conflict with tftpd-hpa
** Branch linked: lp:~andreserl/maas/packaging.raring-updates ** Branch linked: lp:~andreserl/maas/packaging.quantal-updates -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1076028 Title: maas-cluster-controller should conflict with tftpd-hpa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1076028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1072744] Re: maas-cluster-controller depends on rabbitmq-server.
** Branch linked: lp:~andreserl/maas/packaging.quantal-updates -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1072744 Title: maas-cluster-controller depends on rabbitmq-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1072744/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078444] Re: python-boto should verify SSL certificates and should use the systems certificate repository
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1078444 Title: python-boto should verify SSL certificates and should use the systems certificate repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto/+bug/1078444/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] Re: Please upgrade ipmitool to 1.8.12 for 13.04
I could get the source package from the URL in the description to build by making the following modifications: http://bazaar.launchpad.net/~kentb/+junk/ipmitool-1.8.12/revision/2 This package also installed / updated cleanly on a server running the current version of ipmitool for precise. The ipmi dell oem commands (which is a new feature with this update) also seem to work without issue so far on a PowerEdge R420. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-maas-next-steps] MAAS next steps
Blueprint changed by Andres Rodriguez: Work items changed: Work items: [andreserl] SRU django 1.4 GenericIpAddressField to 1.3 for 12.04: TODO [andreserl] SRU 12.10-stabilization to Quantal: TODO [andreserl] SRU 12.10-stabilization to Precise: TODO [andreserl] SRU python-tx-tftp (0.1~bzr31-0ubuntu7) to Quantal: TODO [andreserl] SRU python-tx-tftp to Precise: TODO [andreserl] SRU yui3 to Precise: TODO [andreserl] SRU Raring features to Quantal: TODO [andreserl] SRU Raring features to Precise: TODO [andreserl] Bug #1073462 fence_cdu power type is missing: TODO - [andreserl] Bug #1064224 IPMI detection ends up with power_address of 0.0.0.0: INPROGRESS + [andreserl] Bug #1064224 IPMI detection ends up with power_address of 0.0.0.0: DONE [andreserl] Bug #1064527 detect_ipmi needs improvement. detects non-existant device in nested kvm: TODO [andreserl] maas-ipmi-autodetect and maas-signal should be shipped with MAAS: TODO [maas-maintainers] Bug #975454complete documentation and man pages: TODO [maas-maintainers] Bug #1044503 kernel command line is not easily customizable: TODO [maas-maintainers] Bug #1066775 Main page slow to load with many nodes: DONE [maas-maintainers] Bug #1068843 maas-cluster-controller doesn't have images for provisioning: DONE [maas-maintainers] Bug #1069734 Filestorage is unique to each appserver instance: DONE [maas-maintainers] Bug #1069850 import_pxe_files does not include quantal: DONE [maas-maintainers] Bug #1070522 maas-cli nodes new incomplete documentation: DONE [maas-maintainers] Bug #1070765 DNS forward zone ends up with nonsensical entries: DONE [maas-maintainers] Bug #1070774 The hostname of a node can still be changed once the node is in use: DONE [maas-maintainers] Bug #1070775 The zone name (attached to a cluster controller) can still be changed when it contains in-use nodes and DNS is managed.: DONE [maas-maintainers] Bug #1075597 Duplicated prefix in the url used by the CLI: DONE [maas-maintainers] Bug #1034318 API calls that return a node leak private data: DONE [maas-maintainers] Bug #1059645 URI in API description wrong when accessing machine via alternative interface: DONE [maas-maintainers] Bug #1069603 Error in log when using 'Start node' button: MAASAPINotFound: No user data available for this node.: DONE [maas-maintainers] define supported release combination matrix: TODO -- MAAS next steps https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas-next-steps -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064224] Re: IPMI detection ends up with power_address of 0.0.0.0
** Changed in: maas Status: In Progress = Fix Committed -- 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/1064224 Title: IPMI detection ends up with power_address of 0.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1064224/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064224] Re: IPMI detection ends up with power_address of 0.0.0.0
** Branch linked: lp:~andreserl/maas/maas.quantal_ipmi_lp1064224 -- 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/1064224 Title: IPMI detection ends up with power_address of 0.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1064224/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078530] [NEW] upstart job fails to start under lxc
Public bug reported: The KSM_ENABLED setting (on by default) for the qemu-kvm job fails under lxc but the kernel files still appear writable. Thats likely an lxc bug (either in defaults or device mapping), but there is no need for qemu- kvm's job to fail if those settings can't be written to IMNSHO. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078530] Re: upstart job fails to start under lxc
http://paste.ubuntu.com/1356944/ has a debdiff of the (trivial) fix, adjusted to not version conflict with my nbd patch. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1075010] Re: lm-sensors package out of date
** Branch linked: lp:ubuntu/raring-proposed/lm-sensors -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1075010 Title: lm-sensors package out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1075010/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1075010] Re: lm-sensors package out of date
This bug was fixed in the package lm-sensors - 1:3.3.2-2ubuntu1 --- lm-sensors (1:3.3.2-2ubuntu1) raring-proposed; urgency=low * Merge from Debian unstable (LP: #1075010). Remaining changes: - Add 100_recommend_using_upstart.patch: Recommend use of upstart rather than init-script. * Update 100_recommend_using_upstart.patch to reflect kmod transition. lm-sensors (1:3.3.2-2) unstable; urgency=low * Tell user to restart kmod instead of modules-init-tools (closes: #670213). * Install a systemd service file for lm-sensors (closes: #674778). * Correctly pass CPPFLAGS and LDFLAGS to build with hardening support. lm-sensors (1:3.3.2-1) unstable; urgency=low * New upstream version: * Bumped Standards-version to 3.9.3 (no changes). * Drop useless dependency on makedev | udev (closes: #666510). -- Logan Rosen logatron...@gmail.com Mon, 05 Nov 2012 13:18:21 -0500 ** Changed in: lm-sensors (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1075010 Title: lm-sensors package out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1075010/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064224] Re: IPMI detection ends up with power_address of 0.0.0.0
** Changed in: maas/1.2 Status: In Progress = Fix Committed -- 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/1064224 Title: IPMI detection ends up with power_address of 0.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1064224/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1043010] Re: Update to 3.6.9
** Summary changed: - Update to 3.6.7 + Update to 3.6.9 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1043010 Title: Update to 3.6.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1043010/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 991484] Re: package mcollective 1.2.1+dfsg-2ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
[Expired for mcollective (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mcollective (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mcollective in Ubuntu. https://bugs.launchpad.net/bugs/991484 Title: package mcollective 1.2.1+dfsg-2ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mcollective/+bug/991484/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
