** Changed in: nova
Importance: Undecided => High
--
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/1398999
Title:
Block migrate with attached volumes copies volumes to themselves
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: logcheck (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logcheck in Ubuntu.
Fix proposed to branch: stable/juno
Review: https://review.openstack.org/233546
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1501772
Title:
Metadata proxy process errors with
Just saw kernel version 3.2 mentioned. So this seems to be a mix of
older base OS (Precise) and a more recent qemu (maybe from Trusty). I am
trying to clarify how far this needs to be backported. So I think the
original qemu version in Precise is unaffected.
--
You received this bug notification
@Li Chengyuan, is your host OS really 12.04 (aka Precise)? Because in
12.04 the qemu version is 1.0 and the fix would not apply. I am not sure
that old qemu is even affected since the code is very different.
Backports of the fix seem only to make sense up (or back) to 14.04 (aka
Trusty) which
This bug was fixed in the package qemu - 1:2.3+dfsg-5ubuntu9
---
qemu (1:2.3+dfsg-5ubuntu9) wily; urgency=low
* debian/patches/upstream-fix-irq-route-entries.patch
Fix "kvm_irqchip_commit_routes: Assertion 'ret == 0' failed"
(LP: #1465935)
-- Stefan Bader
Public bug reported:
Steps to reproduce (using a docker container):
$ docker pull ubuntu:trusty
$ docker run --rm -it ubuntu:trusty /bin/bash
# lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
# apt-get update
# apt-get install python3.4
python3.4 is already the
I've been experiencing this irritation for the last year and a half and
I've finally diagnosed it.
The problem seems to be that the log line emitted by dhclient has
changed since the logcheck pattern was written. A sample log line is:
Oct 11 07:22:55 mythtv dhclient: DHCPREQUEST of 192.168.1.2
# cat /etc/issue.net
Ubuntu 14.04.3 LTS
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logcheck in Ubuntu.
https://bugs.launchpad.net/bugs/1134592
Title:
isc-dhcp 4.2.4-5's DHCPREQUEST messages no longer match ignore regex
To
If you can figure out how to get to this state from a fresh install, and
you can do it without editing the configuration file manually, then it
is probably a bug - please explain that, set the bug status back to New,
and I'll take another look.
--
You received this bug notification because you
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Public bug reported:
When set as follows
disk = [ 'script=block-drbd, vdev=xvda2, access=rw, target=domu-disk' ]
where domu-disk is drbd resource ( can be found as /dev/drbd_domu-disk).
xl create does start drbd-block script AFTER trying to attach disk and
launching bootloader, which results
You have been subscribed to a public bug by Robie Basak (racb):
After upgrading my raring VMs to the latest isc-dhcp:
isc-dhcp (4.2.4-5ubuntu1) raring; urgency=low
isc-dhcp (4.2.4-5) unstable; urgency=medium
logcheck's email now includes DHCPREQUEST messages. This is very
annoying when
You have been subscribed to a public bug by Robie Basak (racb):
initially sent to the ubuntu-users mailing list when reported by the user using
reportbug
-- Forwarded message --
From: Cip-Admin
To: Ubuntu Bug Tracking System
This was reported fixed in Debian 2.1.16-2, and Wily has 2.1.20-1, so
marked Fix Released in Ubuntu. Looks like Precise is still affected,
though.
** Changed in: mailman (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: mailman (Ubuntu Precise)
Importance: Undecided
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Which line should I comment, Specifically?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1477059
Title:
package mysql-server-5.6 5.6.25-0ubuntu0.15.04.1 failed to
** Package changed: python3.4 (Ubuntu) => python-urllib3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-urllib3 in Ubuntu.
https://bugs.launchpad.net/bugs/1500768
Title:
python3.4.3 SRU break requests
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
This still isn't fixed using the latest from the cloud archive today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1502363
Title:
Linux bridge agent should include ebtables
You have been subscribed to a public bug by Robie Basak (racb):
A bug in the Apache2 HTTP server results in invalid memory references
in the ap_server_config_defines array after a graceful restart. This
can result in server config variables defined by means of the Define
directive appearing to
Hi,
personally in 15.10 I have
# Tell any system-wide dnsmasq instance to make sure to bind to interfaces
# instead of listening on 0.0.0.0
# WARNING: changes to this file will get lost if lxc is removed.
bind-interfaces
except-interface=lxcbr0
server=/lxc/10.0.3.1
in /etc/dnsmaq.d/lxc
and it
** Patch removed: "lp1494141_fix_stop_failure.debdiff"
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+attachment/4473139/+files/lp1494141_fix_stop_failure.debdiff
** Patch added: "lp1481737_stop_multipid.debdiff"
I think the problem is a dangling symlink:
/etc/systemd/system/nut-client.service ->
/lib/systemd/system/nut-monitor.service
You can try this, but it doesn't fix the underlying problem it it just makes it
so the package scripts don't fail. I was able to remove nut-client by running
this
You have been subscribed to a public bug by Robie Basak (racb):
After upgrading Ubuntu from LTS to 15.04, spamassassin daemon does not
start anymore because it does not have a proper systemd configuration.
Attempts to enable it using `systemctl enable spamassassin` do also
fail.
** Tags added: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logcheck in Ubuntu.
https://bugs.launchpad.net/bugs/1134592
Title:
isc-dhcp 4.2.4-5's DHCPREQUEST messages no longer match ignore regex
To manage
The attachment "allow-crl-cache.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 user owned by
root@compute1:~# apt-cache showpkg neutron-plugin-linuxbridge-agent
Package: neutron-plugin-linuxbridge-agent
Versions:
2:7.0.0~rc1-0ubuntu2~cloud0
(/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_trusty-updates_liberty_main_binary-amd64_Packages)
(/var/lib/dpkg/status)
2015-10-12 23:43:41.881 1092 INFO
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
[req-404c3fdf-1abf-4d55-afe3-be56bfe38939 - - - - -] LinuxBridge Agent RPC
Daemon Started!
2015-10-12 23:43:41.888 1092 INFO oslo.messaging._drivers.impl_rabbit [-]
Connecting to AMQP
Public bug reported:
wily dist-upgrade caused this failure.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: nut-client 2.7.1-1ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu2
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1505288
Title:
package nut-client 2.7.1-1ubuntu5 failed to install/upgrade:
subprocess installed
% sudo apt-get install --reinstall nut-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk
Removing the bogus symlink lets me at least remove nut, nut-client, and
nut-server and reinstall those packages.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1505288
Title:
package
The attachment "amended-fix-for-1314887.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 user owned
More headscratchers:
% locate nut-client.service | xargs ls -l
lrwxrwxrwx 1 root root 39 Jan 10 2014 /etc/systemd/system/nut-client.service
-> /lib/systemd/system/nut-monitor.service
-rw-r--r-- 1 root root 0 Jan 10 2014
/var/lib/systemd/deb-systemd-helper-enabled/nut-client.service
% ls -l
You have been subscribed to a public bug:
Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using a
squid proxy:
It seems that I can't create a generic Ubuntu task since other Ubuntu
tasks already exist, so I'll leave this with the docker.io package for
now so we don't lose it.
I think we need a Launchpad project for cloud images if we don't already
have one.
** Also affects: docker.io (Ubuntu)
I also see this bu only on Windows guests.
--
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/1423631
Title:
tap interface drops many packets on highload systems
To manage notifications
I realize it's a poor reason but I mimicked the network_interfaces
function /etc/init.d/openvswitch-switch. Want me to switch it over to
use ifquery?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Confirmed - I have followed your reproduction steps and hit the same
issue.
The underlying reason however is not in the python3.4 nor mod-wsgi
packages. The issue is that the Docker "ubuntu:trusty" image seems to
Scratch comment #3.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/1505164
Title:
Ubuntu Docker images incorrectly include packages from trusty-proposed
To manage notifications
I was able to resolve this with the below udev rule:
# cat /etc/udev/rules.d/60-tap.rules
KERNEL=="tap*", RUN+="/sbin/ip link set %k txqueuelen 1"
#
I used the below to reload udev
udevadm control --reload-rules
I then used the below to apply the rules to already created interfaces:
Change abandoned by Ihar Hrachyshka (ihrac...@redhat.com) on branch: stable/juno
Review: https://review.openstack.org/233546
Reason: Actually, we don't use oslo.log, neither py34 in Juno, so no need for
the change.
--
You received this bug notification because you are a member of Ubuntu
Server
I'm experiencing this in 15.04. With the change to systemd, the pm-utils
scripts are no longer run when the system resumes after suspend.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Selective block device migration feature was backported to libvirt 1.2.16 for
ubuntu willy.
This patch provides block live migration of vm booted from image with attached
devices on libvirt 1.2.16.
** Patch added: "Patch for Ubuntu willy with libvirt 1.2.16"
Public bug reported:
There seems to be some issue with the udev triggers, either they do not
happen properly for partitions or they happen too early in the boot
process.
If I do a "ceph-disk activate /dev/sdXX" after the system has booted,
the OSD is starting just fine.
If I do a "udevadm
The attachment "Patch for Ubuntu willy with libvirt 1.2.16" 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
Public bug reported:
If configured to do so, strongSwan will cache CRLs to /etc/ipsec.d/crls
but AppArmor blocks the creation of the file. Here is the relevant
syslog line:
kernel: [400994.988829] audit: type=1400 audit(1444649911.842:37):
apparmor="DENIED" operation="mknod"
I am unable to repo this bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/1505164
Title:
Ubuntu Docker images incorrectly include packages from trusty-proposed
To manage
"Nice" thread about systemd + hdparm:
http://lists.freedesktop.org/archives/systemd-
devel/2012-June/005595.html
So it seems users should write their own udev rules to get this working
:-| or some custom distro specific stuff. Its really weird that this one
is still around after that many years
For avoidance of doubt, this problem was caused by the actions taken to
remedy bug 1500768. Workarounds to get an instance unstuck can be found
there.
Dan
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
Also:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725284
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779412
** Bug watch added: Debian Bug tracker #725284
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725284
** Bug watch added: Debian Bug tracker #779412
Hi Mark, all,
At some point, Python 3.4.3 was released to the trusty archive. However,
a (serious) regression was found, and it was removed from the archive.
This image was built after the release, but before the removal, which
means it has ended up in a state that apt-get doesn't understand.
I was hitting problems with lxc on just normal package upgrades in vivid
earlier, but I was able to dpkg --configure -a this problem away and
finish out the release upgrade by hand (apt-get dist-upgrade (noop),
apt-get autoremove, reboot)
--
You received this bug notification because you are a
This bug was fixed in the package net-snmp - 5.7.3+dfsg-1ubuntu2
---
net-snmp (5.7.3+dfsg-1ubuntu2) wily; urgency=medium
* debian/snmp.preinst:
It turns out that the original motivation why killall was added is gone.
So we can just remove the killall introduced by Ubuntu LP
Thank you @racb for taking the time to look into this and reassign it
correctly - apols for my clumsy assignment.
Dan @daniel-thewatkins - thanks dude.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
** Branch linked: lp:ubuntu/net-snmp
--
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/1245604
Title:
"killall -u snmp" in a pre-install step kills any running snmpd
To manage
** Summary changed:
- Ubuntu Docker images incorrectly include packages from trusty-proposed
+ Ubuntu Docker images include packages deleted from trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
Went ahead and created a new (and simpler) patch that uses ifquery. See
attached
** Patch added: "amended-fix-for-1314887.patch"
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+attachment/4492519/+files/amended-fix-for-1314887.patch
--
You received this bug notification
This was caused by Bug #1500768.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/1505164
Title:
Ubuntu Docker images include packages deleted from trusty-updates
To manage
** Changed in: docker.io (Ubuntu)
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
** Changed in: docker.io (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1502178
Title:
update squid from 3.3.8 to 3.3.14
To manage notifications about this bug go to:
Quoting Dadio (domini...@ramaekers-stassart.be):
> I've investigated this issue in Willy:
>
> Hugepages are now mounted on /dev/hugepages and not in /run/hugepages
Hi,
Note that /etc/init.d/qemu-kvm calls /usr/share/qemu/init/qemu-kvm-init
which mounts hugepages under /run/hugepages.
The
Public bug reported:
When I try to create a external snapshot, I get an apparmor related
error:
virsh snapshot-create-as --domain PCVIRT1 PCVIRT1-SN1 --diskspec
vda,file=/srv/poolVMS2/PCVIRT1-SN1.qcow2 --disk-only --atomic --quiesce
fout: internal error: kan AppArmor profiel
Thanks for the new info.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1504283
Title:
libvirt 1.2.2-0ubuntu13
--- Comment From apu...@us.ibm.com 2015-10-12 20:37 EDT---
This patch did not make it into today build.
I tried to reinstall pearlp5 at hit the initramfs issues still.
This is blocking debug of 130680
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
Hello,
I use minicom with an USB Adapter to communicate with a cisco switch.
Everything went fine but when I close the program with ctrl+a, z and j, the
lock at /dev/ttyUSB0 wasn't removed. :/
If I remove the file /var/lock/LCK..ttyUSB0, the device is unlocked.
Sorry for
Public bug reported:
Creating a stack via heat (Liberty, 5.0.0~rc1-0ubuntu1~cloud0) generates
the following error due to a missing file:
INFO heat.engine.stack [-] Stack CREATE IN_PROGRESS (testStack): Stack CREATE
started
INFO heat.engine.resource [-] creating Server "server" Stack "testStack"
@Stefan Bader,
The host OS is ubuntu 12.04, and we upgraded the QEMU to 2.0.0 from ubuntu
cloud-archive repo.
https://wiki.ubuntu.com/ServerTeam/CloudArchive
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
[Expired for mysql-5.6 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-5.6 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Public bug reported:
ubuntu@keeton:~$ lsb_release -rc
Release:14.04
Codename: trusty
ubuntu@keeton:~$ dpkg-query -W pollen
pollen 4.11-0ubuntu1
ubuntu@keeton:~$ _
pollen does not start on boot, due to an error in the upstart config:
ubuntu@keeton:~$ grep start
72 matches
Mail list logo