At least python-libvirt, which nova-compute uses, seems to leak memory
when handling XML data. Find the file d.py attached which reproduces a
similar problem.
ii python-libvirt 1.2.2-0ubuntu1 amd64 libvirt Python
bindings
valgrind can detect definitely lost.
# ps -ef|grep d.py
We are affected by (what seems) exactly the same issue on:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename: trusty
php5 5.5.9+dfsg-1ubuntu4.4
--
You received this bug notification because
** Changed in: maas (Ubuntu)
Status: In Progress = 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/1346703
Title:
/var/log/maas/rsyslog has incorrect permission
To
python-oslo.i18n was already in main
** Changed in: python-oslo.i18n (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-oslo.utils in Ubuntu.
This bug was fixed in the package oslo.messaging - 1.4.0.0~a3-0ubuntu2
---
oslo.messaging (1.4.0.0~a3-0ubuntu2) utopic; urgency=medium
* d/p/zmq-server-routing.patch: Cherry pick WIP to ensure that ZMQ
messages get routed correctly for call's (LP: #1301723).
-- James Page
There is an in-flight SRU for trusty that is near completion :
https://bugs.launchpad.net/maas/+bug/1337437
I will wait until it is done to SRU this one
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
This type of files should be also excluded but I'm not sure what would be the
best way to do:
http://archive.ubuntu.com/ubuntu/dists/precise-updates/main/dist-upgrader-all/current/precise.tar.gz
http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/dist-upgrader-all/current/trusty.tar.gz
and
Public bug reported:
Seguimos teniendo errores en la actualizacion de qemu, en los
repositorios de seguridad
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: qemu-system-misc 2.0.0+dfsg-2ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic
** Tags removed: need-duplicate-check
--
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/1368233
Title:
package qemu-system-misc 2.0.0+dfsg-2ubuntu1.2 failed to
install/upgrade: cannot
** Also affects: ntp (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: isc-dhcp (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ntp (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: isc-dhcp (Ubuntu Precise)
** Patch added: lp1257082_prefers_dhcp_ntp_servers_trusty.debdiff
https://bugs.launchpad.net/maas/+bug/1257082/+attachment/4201542/+files/lp1257082_prefers_dhcp_ntp_servers_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Hello,
Since there is no consensus on the definitive solution , I am proposing
a simple fix for prefers dhcp provided NTP servers if one is found as
also @elmo pointed here.
Please review the test-case and description for further details.
** Description changed:
[Impact]
MAAS-deployed
** Patch added: lp1257082_prefers_dhcp_ntp_servers_utopic.debdiff
https://bugs.launchpad.net/maas/+bug/1257082/+attachment/4201541/+files/lp1257082_prefers_dhcp_ntp_servers_utopic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Patch added: lp1257082_prefers_dhcp_ntp_servers_precise.debdiff
https://bugs.launchpad.net/maas/+bug/1257082/+attachment/4201543/+files/lp1257082_prefers_dhcp_ntp_servers_precise.debdiff
** Changed in: ntp (Ubuntu Precise)
Status: New = In Progress
** Changed in: ntp (Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Updated to Ubuntu 14.04 today. Installation baulked. Error ambiguous but
suggested it might be a 3rd party repository but none were enabled.
Alternatively it suggested that I run sudo apt install -f in terminal.
The following was the error...
~$ sudo apt-get install -f
Reading package lists...
Public bug reported:
I'm using the command 'maas maas nodes acquire system_id=node-
b0685f4e-3843-11e4-922e-00163e6ffb81' and maas is acquiring a random
node. The problem is that system_id is not a valid parameter to the
nodes acquire command.
1. If an invalid parameter is given then it should
Thanks. Meanwhile I've raised the issue on lxc-devel mailing list.
--
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/1367730
Title:
container root directory has broken permissions with
On the following page Nat Gew explains the bug and explains how to
resolve the upgrade.
http://askubuntu.com/questions/450109/when-attempting-upgrade-
from-13-10-to-14-04-upgrade-halted-at-aborting-samba-li
--
You received this bug notification because you are a member of Ubuntu
Server Team,
One catch with my approach is that setting NTPDATE_USE_NTP_CONF=yes
might mean use /var/lib/ntp/ntp.conf.dhcp, and that would break. But
maybe this file won't exist or is not useful if /etc/ntp.conf doesn't
exist?
--
You received this bug notification because you are a member of Ubuntu
Server
Thanks Jorge.
The way I imagined a fix going that might also be acceptable to Debian
would be to treat NTPDATE_USE_NTP_CONF as no if ntp.conf doesn't exist,
even if it says yes. Would this work for you?
Then I imagine addition of something like (untested):
if [ ! -f /etc/ntp.conf ]; then
Oh, one more thing. I get the impression the failure you're
experiencing, which is the case that you do have a working RTC, is a
slightly different issue with the same symptom. curtin should set the
RTC, and so on boot into the installed system you should already have a
good enough clock. I think
Michael,
Its a new build dependency for horizon. They have stripped out the
javascript that was included in horizon and split it out into new
dependencies.
chuck
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
I have built a package some time ago with the new patch posted on
bugs.samba.org for utopic
(https://launchpad.net/~saxl/+archive/ubuntu/ppa/+build/6263614),
The 4.1.11+dfsg-1ubuntu1saxl1 build works well on my site. The problem
is that I am also the bug reporter on bugs.samba.org, so maybe
It appears your local copy of the package is corrupted:
Unpacking qemu-system-misc (2.0.0+dfsg-2ubuntu1.3) over
(2.0.0+dfsg-2ubuntu1.2) ...
dpkg-deb (subprocess): decompressing archive member: lzma error: compressed
data is corrupt
Please try the following:
sudo apt-get clean
sudo apt-get
At some point, this started working again after a dist-upgrade, so
nss_initgroups_ignoreusers is working for me.
The only thing I've done on top of that for house keeping purposes, is
to modify the init script to remove the ignoreusers line on system start
(the configs are controlled vi puppet,
Set package task as invalid since this is an upstream issue.
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New = Invalid
** Tags added: api maas-cli
** Description changed:
I'm using the command 'maas maas nodes acquire
Thanks @msaxl, I'll add this patch to our package.
** Changed in: samba (Ubuntu Utopic)
Status: Incomplete = Triaged
--
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/1310919
I can't get this to happen. Can you? If so, how?
This is a year old. Perhaps it was fixed or that the code changed so
much that it takes some more effort.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to boost1.53 in Ubuntu.
Hello Serge, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package samba - 2:4.1.11+dfsg-1ubuntu2
---
samba (2:4.1.11+dfsg-1ubuntu2) utopic; urgency=medium
* d/p/krb_zero_cursor.patch - apply proposed-upstream fix for
pam_winbind krb5_ccache_type=FILE failure (LP: #1310919)
-- Serge Hallyn
Any update on that issue? Is there anybody who can suggest a work around?
Thank you!
--
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/1315501
Title:
cloud-init does not use
You have been subscribed to a public bug by Corey Bryant (corey.bryant):
I'm not sure that the deployment file matters but here's what I was
using:
$ cat deployment.yaml
# vim: set ts=2 et:
openstack-services:
services:
mysql:
branch: lp:charms/mysql
constraints: mem=1G
This occurs on version 0.4.0-3. 0.3.6-0ubuntu2 is working fine.
--
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/1368403
Title:
juju-deployer traceback AttributeError: 'NoneType'
FWIW, I ended up compiling the latest 3.6 version of Samba from the
official source and it works just fine. I also tried sss with AD auth
for a bit but it has its own set of issues in our environment.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
If running a box with multiple CPU sockets and Ubuntu 14.04 Server
64-bit qemu-kvm with KSM enabled as by default, random high latency
occurs on network connections for VMs, as high as 4000ms - 5000ms. The
host also reports high IO wait times.
Disabling KSM fixed this for
Removing horizon as it has its own bug and patch up for this bug 1335999
--
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/1310340
Title:
live migration fails when use long hostname
This isn't really a bug, changing to Wishlist.
** Changed in: nova
Importance: Medium = Wishlist
** Changed in: nova
Status: In Progress = Confirmed
** No longer affects: horizon
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I lack permission to remove horizon (Ubuntu), so moving back to New.
** Changed in: horizon (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
This might be a dupe but I can't find the original.
** Changed in: maas
Status: New = Triaged
** Summary changed:
- maas profile nodes acquire system_id=system_id acquires a random node
+ api ignores unknown parameters
** Changed in: maas
Importance: Undecided = Medium
--
You
Additionally, do we not also use juju, region and cluster on the same
NUC inside the Orange Box? So it seems like it would be important from
the OB perspective to fix this as well. Just an additional use case.
--
You received this bug notification because you are a member of Ubuntu
Server
Hrmmm... it just bit me while trying to test out the checkbox charm on
bare metal from my private maas server. and it's not just a matter of
juju.
for example, MAAS is successfully updating the zone files:
npdxh IN CNAME 10-0-0-123
and I can't ssh to my node by hostname:
Bear in mind that there is no region controller as a single entity, it
is comprised of many discrete components. So far people have been
installing them all in the same place using the convenience of the
maas meta package, so if installing that package it could update
resolv.conf as well, but in
** Changed in: nova
Status: New = Confirmed
** Changed in: nova
Importance: Undecided = Low
--
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/1316556
Title:
vmware: boot from
** Changed in: mir
Status: New = Incomplete
** Changed in: boost1.53 (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to boost1.53 in Ubuntu.
https://bugs.launchpad.net/bugs/1243564
Title:
Public bug reported:
The Intel AMT allows passwords with $ in them. I set a password of
1Pa$$word and could not control the power from MAAS. I changed the
password to 1Pa**word and MAAS could then control the power on the
Intel Nuc.
** Affects: maas (Ubuntu)
Importance: Undecided
** Changed in: systemd-shim (Debian)
Status: Fix Released = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1355966
Title:
[FFE] Implement AbandonScope (etc)
To manage
** Changed in: maas
Assignee: (unassigned) = Julian Edwards (julian-edwards)
** Changed in: maas
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
48 matches
Mail list logo
