** Branch linked: lp:ubuntu/trusty-proposed/ipxe
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipxe in Ubuntu.
https://bugs.launchpad.net/bugs/1409057
Title:
ipxe does not take into account nic boot order specified in libvirt
Sponsored for Trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cinderclient in Ubuntu.
https://bugs.launchpad.net/bugs/1404110
Title:
[SRU] Wrong hint key in volume create function
To manage notifications about this
** Changed in: vsftpd (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/1065714
Title:
vsftpd 2.3.5 needs allow_writeable_chroot option
To
Please don't change the bug status without an explanation. I marked this
bug as Invalid and I explained why. Leaving it as Confirmed just sets
false expectations to other readers that this bug might be fixed some
day, when it won't be.
--
You received this bug notification because you are a
FWIW, just re-reproduced this with latest upstream kernel / qemu / fresh
qcow2 image.
--
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/1292234
Title:
qcow2 image corruption in trusty
Yes, I also have a few error messages containing amavis[1533]: nss-
ldap: do_open: do_start_tls failed:stat=-1.
Removing ssl start_tls from /etc/ldap.conf allows amavis to start. So
the problem looks to be when amavis checking libnss when it is set to
use LDAP with STARTTLS.
The TLS
Hi:
Perhaps Launchpas /UBuntu policy should be to tag these cases as
won'tfix?
** Changed in: vsftpd (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
+1 :)
The [ sdb, mount point ] syntax is a bug as well. Device names are
not persistent in Linux and could change, so it is not guaranteed that
the ephemeral disk will be called /dev/sdb. Ideally this should be
auto-detected in cloud-init at runtime (for example, see
DeviceForIdePort() in the
It's now (UTC) Thursday.
** Changed in: ossa
Status: Incomplete = Won't Fix
** Tags added: security
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Released
Does it also fail with the qemu from
https://launchpad.net/~ubuntu-virt/+archive/ubuntu/virt-daily-upstream ?
(This isn't quite git head, but it is qemu v2.2)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Went ahead and tested - it is in fact fixed in the v2.2 version.
** Changed in: qemu (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
No, the mount location cannot be modified on Ubuntu via the
waagent.conf, that is the issue. I would like a way to modify the mount
point post-provisioning.
The only way to change the mount point on Azure is to use CustomData
(like user data on other clouds) to send a cloud-config to modify the
Public bug reported:
Background: Ceph's RADOS Gateway (RGW) is a web application that
provides an S3- and Swift-compatible interface to Ceph. RGW uses
mod_proxy_fcgi in Apache 2.4.
In the Ceph team's testing, the RGW application performs much better
when using Unix Domain Sockets with
*** This bug is a duplicate of bug 1312855 ***
https://bugs.launchpad.net/bugs/1312855
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1312855, so it is being marked as such. Please
maas 1.5.4+bzr2294-0ubuntu1.3 works for me. The permission is correctly
setup on install now.
** 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 maas in Ubuntu.
James, I don't follow your second paragraph. Can you explain like I'm
5? :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-sysv-ipc in Ubuntu.
https://bugs.launchpad.net/bugs/1399581
Title:
[MIR] python-sysv-ipc
To manage
** Patch added: 12.04 debdiff
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+attachment/4298428/+files/precise.deb.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Patch added: 14.10 debdiff
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+attachment/4298430/+files/utopic.deb.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
You have been subscribed to a public bug:
== Comment: #0 - Chanh H. Nguyen chngu...@us.ibm.com - 2015-01-09 17:30:08 ==
We use DVD to install Ubuntu 15.04 kernel 3.18.0-8-generic version on our
PowerVM system. After install, I am seeing this error
Setting to package init on LP side, as it appears to be an init issue
rather than a kernel issue.
** Package changed: ubuntu = init-system-helpers (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
Original set of patches is nearly three months old. Rebased the patch
for the latest Cloud-init. Checked to make sure that the debdiff and
patches still apply cleanly.
Requested MP on the upstream bits.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1410604
Title:
ISST-LTE: unable to open rtc device
To manage notifications about this bug go to:
--- Comment From helle...@us.ibm.com 2015-01-14 15:15 EDT---
The same problem is seen on 14.10 as well:
root@cellc10:~# uname -a
Linux cellc10 3.16.0-23-powerpc64-smp #31-Ubuntu SMP Tue Oct 21 18:12:52 UTC
2014 ppc64 ppc64 ppc64 GNU/Linux
root@cellc10:~# dmesg | grep rtc
[0.692983]
Public bug reported:
The cloud config settings
# swap can also be set up by the 'mounts' module
# default is to not create any swap files, because 'size' is set to 0
swap:
filename: /swap.img
size: auto or size in bytes
maxsize: size in bytes
will not result in a swap space.
Some big
Public bug reported:
The creation of custom mount points with cloud-config, when creating a
(linux) VM in Azure, is fairly simple, with some caveats.
However, the format
[ ephemeralX, mount point ]
is not working properly, even when explicitly declaring device aliases.
The format
[ sdb,
Problem should not occur on Ubuntu Trusty 14.04.1 LTS
--
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/1311463
Title:
disk-setup unable to partition disks
To manage notifications
Public bug reported:
Samba is intermittently throws a panic. However user are still able to
get to shares.
Here is the email message received with the trace.
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 23392 (/usr/sbin/smbd).
This means there was a
This bug was fixed in the package cgmanager - 0.24-0ubuntu7.2
---
cgmanager (0.24-0ubuntu7.2) trusty-proposed; urgency=medium
* 0009-chown-stop-cgmanager-crash-on-chown-of-bad-file.patch - prevent
cgmanager crashing on unhandled dbus error (LP: #1407787)
-- Serge Hallyn
This bug was fixed in the package cgmanager - 0.32-4ubuntu1.2
---
cgmanager (0.32-4ubuntu1.2) utopic-proposed; urgency=medium
* 0008-chown-stop-cgmanager-crash-on-chown-of-bad-file.patch and
0009-prevent-some-cgmanager-asserts.patch: prevent cgmanager
crashing on unhandled
We have experienced this issue too. He had to do some black magic with
monit to fix this behavior
--
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/1230917
Title:
php5-fpm logrotate
Gosh, why monit blackmagic when there's a simple fix in #5
(https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1230917/comments/5)?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
** Tags added: patch
--
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
Blueprint changed by Patricia Gaughen:
Work items changed:
Work items:
NTP on by default (from elmo): TODO
evaluate dpdk (http://dpdk.org/) for inclusion: TODO
update haproxy to latest: DONE
update corosync to latest: TODO
MySQL cleanup in Debian and 5.6 transition: INPROGRESS
+ Move
** Also affects: python-cinderclient (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python-cinderclient (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: python-cinderclient (Ubuntu)
Status: New = Fix Released
--
You received this bug
** No longer affects: python-cinderclient (Ubuntu)
** No longer affects: python-cinderclient (Ubuntu Trusty)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cinderclient in Ubuntu.
https://bugs.launchpad.net/bugs/1276088
The attachment samba-3.6.3-missing-gss-buffer-desc-init.patch seems to
be a patch. If it isn't, please remove the patch flag from the
attachment, remove the patch tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad
** Also affects: cloud-init (Ubuntu Utopic)
Importance: Undecided
Status: New
--
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
I have meet this problem with email servers that have been upgraded from
Ubuntu 12.04 (precise) to Ubuntu 14.04 (trusty). Amavis starts at
boot and with the debug option, but fails to start via the init script
or the command line ('sudo -u amavis strace /usr/sbin/amavisd-new
start').
I have done
** Description changed:
+
+ Impact: unable to specify nic boot order
+ Test Case: use the xml below to create a VM, and check that the 'boot order'
is ignored.
+ Regression potential: This cherrypicks 4 patches from
New version of the patch with the correct bug number in the
debian/changelog.
** Patch removed: lp_1404110_trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/python-cinderclient/+bug/1404110/+attachment/4283947/+files/lp_1404110_trusty.debdiff
** Patch added: lp_1404110_trusty.debdiff
I'm guessing that the issue here is that tools use hostname(7) to get
the hostname on the system and then are confused / broken when that is
more than 64 chars.
It really seems like its more important to have consitent behavior
across the board then change behavior somewhat randomly.
--
You
Thank you for the quick fix. I tested the released package on Ubuntu
14.04 (trusty) and it works fine :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipxe in Ubuntu.
https://bugs.launchpad.net/bugs/1409057
Title:
ipxe does not
Hello Nobuto, or anyone else affected,
Accepted maas into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/maas/1.5.4+bzr2294-0ubuntu1.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: libvirt (Ubuntu Trusty)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: libvirt (Ubuntu Utopic)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: ceph (Juju Charms
I'm also running slapd on the affected box. Similar setup:
- amavis user and group are local
- only end user users and groups in ldap
Checking back a bit further in the logs, I did also find this in syslog:
Jan 11 21:59:06 bamboo amavis[2820]: nss-ldap: do_open: do_start_tls
failed:stat=-1
I'm
** Branch linked: lp:ubuntu/trusty-proposed/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/1346703
Title:
/var/log/maas/rsyslog has incorrect permission
To manage notifications
Hello Pasquale, or anyone else affected,
Accepted ipxe into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/ipxe/1.0.0+git-2013.c3d1e78-2ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Changed in: walinuxagent (Ubuntu)
Assignee: (unassigned) = Ben Howard (utlemming)
** Changed in: walinuxagent (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
I set up a testing environment with 2 VMs, trusty-proposed enabled, all
updates installed and the following minimal cluster configuration:
node $id=168427521 kjpnode1 \
attributes standby=off
node $id=168427522 kjpnode2 \
attributes standby=on
primitive st_kjpnode1
** Attachment added: dpkg-versions
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4298137/+files/dpkg-versions
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
Okay,
I'm revisiting this today. Tks for the crash, I'll try to reproduce what
you are getting also.
Tinoco
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
I tracked my crash to what appears to be missing structure
initialization, resulting in invalid pointers being free()d
Added two initializations, seems to fix the problem. Not being familiar
with samba, please confirm if I'm doing the right thing.
** Patch added:
Public bug reported:
..
.
.
Setting up libtomcat7-java (7.0.52-1ubuntu0.1) ...
Setting up tomcat7-common (7.0.52-1ubuntu0.1) ...
Setting up tomcat7 (7.0.52-1ubuntu0.1) ...
chmod: cannot access ‘/etc/tomcat7/tomcat-users.xml’: No such file or directory
dpkg: error processing package tomcat7
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1410734
Title:
package tomcat7 7.0.52-1ubuntu0.1 failed to install/upgrade:
subprocess
Public bug reported:
lxc is configured for limited user usage, i.e. the backing store is
always dir. Let's create a container, and snapshot it in its pristine
state:
% lxc-create -n restorebug -t download -- -d ubuntu -r utopic -a amd64
lxc-snapshot -n restorebug
[...]
lxc_container:
If I configure the test environment like my production system (with the
exception of the stonith agent, of course) I get additional core dumps
of lrmd.
Peter
** Attachment added: _usr_lib_pacemaker_lrmd.0.crash
Public bug reported:
During a dist-upgrade I got the new version of python-oslo-config which
failed to install.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: python-oslo-config (not installed)
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux
Could it be that this is cause by conflict between System V and upstart?
Both of these files are installed by the freeradius deb:
/etc/init.d/freeradius
/etc/init/freeradius.conf
When I experienced this issue while installing freeradius-ldap, it
seemed that the post-install script of
** Attachment removed: Precise debdiff of working patch
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1383794/+attachment/4241831/+files/precise-debdiff.txt
** Attachment removed: Trusty debdiff of working patch
60 matches
Mail list logo
