Had the same hang. Client is Ubuntu 15.10 and server is 14.04, both up
to date as of today. Fix was to change client MTU from 9000 to 1500.
--
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/bu
[Expired for openldap (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openldap (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.laun
(Note I cannot reproduce this here)
--
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/1516203
Title:
qemu-system-x86_64 crashed with SIGSEGV in SDL_BlitCopy()
To manage notifications abo
Pavaman - thanks for verifying. The latter issue sounds like a BMC
problem, which we're following-up separately.
** 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 ipmi
Your bug report includes an attached /etc/init/rpcbind.conf which is
radically different than the one shipped in the package. Do you recall
why you changed this file?
Since the only thing that the rpcbind postinst does that might block is
to start the rpcbind service, it's likely that the hang is
Which apparmor version do you use?
I can't reproduce the problem using the latest version from the 2.9
branch and bzr trunk. (I tested with abstractions/base instead of
abstractions/lxc/start-container in the profile, but that shouldn't
matter.)
--
You received this bug notification because you
** 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 the bug report.
https://bugs.launchpad.net/bugs/1481388
Title:
NTP : Use-after-free in routing socket code after dr
I've been using the -proposed package on 15 Trusty machines since it was
published. Again, I never was able to reproduce the original problem but
I saw no regression either.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report
I rebuilt autofs with the patch from comment 8. That seems to work well
for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1503034
Title:
Autofs 5.1.1-1ubuntu2 crashes with segfa
Thanks. (I thought I had upgraded my test system to xenial, but I
hadn't, so virtio-vga was not supported)
How far into the boot do you see this happening?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.l
Ah, interesting. So this may be a bug in aa-complain, as it did not
retain (iiuc) the attach_disconnected flags.
--
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/1516037
Title:
lxc-start
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
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/15160
Adding an apparmor task as the apparmor tools really shouldn't mangle
our profiles in a way that can't be reverted...
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subs
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
debsums: changed file /etc/default/lxc (from lxc package)
debsums: changed file /etc/apparmor.d/usr.bin.lxc-start (from lxc package)
So I restored the /etc/apparmor.d/usr.bin.lxc-start file to:
#include
/usr/bin/lxc-start flags=(attach_disconnected) {
#include
}
The only thing I remember I
That most definitely is not our default profile, so you or some script
you ran modified it.
You may want to install "debsums" and run "debsums -sa lxc" to get a
list of configuration files which have been modified on your system.
--
You received this bug notification because you are a member of
Mmm I'm having the same problem with lxc 1.1.5 on ubuntu 12.04 (using
the ppa). I had to downgrade to 1.1.4 to make my containers bootable
again.
I don't think I manually modified the file /etc/apparmor.d/usr.bin.lxc-
start. It contains:
#include
/usr/bin/lxc-start flags=(complain) {
#inclu
--- Comment From amda...@us.ibm.com 2015-11-16 18:17 EDT---
Because this is a security, we request this fix be included in 14.04 SRU please.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchp
bcache-tools_1.0.7-1~12.04.1 (in my ppa) has been tested and is known to
work. I'll be uploading that to precise-proposed shortly.
lamont
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.n
ProcCmdline: qemu-system-x86_64 -machine ubuntu,accel=kvm -m 1024
-device virtio-vga -cdrom ubuntu-15.10-desktop-amd64.iso
--
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/1516203
Title:
Hi. Squid3 not accept subdomains (only squid2x), and get ERROR:
'ppa.launchpad.net' is a subdomain of 'ppa.launchpad.net'
We have released a project to correct this:
http://www.maravento.com/p/blacklist.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
Could you please give the full command you used so that I can reproduce
this?
** Also affects: qemu
Importance: Undecided
Status: New
--
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/
** No longer affects: cloud-archive
--
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/1429739
Title:
neutron-server does not start: OperationalError: (OperationalError) no
such table
i have had this confiquration problem, or ubuntu bug for six months, if
i recollect correctly. I wish i could simply stop this from coming up
and taking 20 minutes of my time every time i UPDATE SOFTWARE !!
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
Fix proposed to branch: master
Review: https://review.openstack.org/245811
** Changed in: nova
Status: New => In Progress
--
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/1516652
T
** 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/1516652
Title:
'lxd' is an unsupported hypervisor type
To manage notifications about
Public bug reported:
I'm trying to boot glance images which have the hypervisor_type property
set on them to 'lxd' to target specific hypervisors within a mixed
hypervisor cloud; instance boot fails with:
{"message": "Hypervisor virtualization type 'lxd' is not recognised",
"code": 400, "created"
Does this bug affects 1.7
** Changed in: maas (Ubuntu)
Status: Confirmed => 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/1274944
Title:
maas-dhcp-server should be
You have been subscribed to a public bug:
I'm trying to boot glance images which have the hypervisor_type property
set on them to 'lxd' to target specific hypervisors within a mixed
hypervisor cloud; instance boot fails with:
{"message": "Hypervisor virtualization type 'lxd' is not recognised",
"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openstack-trove (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-trove in Ubuntu.
https://bugs.launc
Public bug reported:
Upgrade hung; needed to kill rpcbind and clear the postinst script to
get it to finish.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: rpcbind 0.2.1-2ubuntu2.2
ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
Uname: Linux 3.13.0-68-generic x86_64
Ap
hello, I've fixed simply getting the network_request class file from the
controller and copying on the compute node and editing the __init__.py
with the import of that file, but is still a bug :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
Public bug reported:
I am using nova ( version 2.17.0 ) on a compute node and there is a
server running the controller node
when i try to launch an instance when the nova compute is up, this is
stuck on scheduling state (building task) and i see this error on the
nova-comute.log on the compute no
I just test the proposed package version 1.0.8-0ubuntu0.2 and it fix my
issue.
Thanks a lot.
** 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 lxc in Ubuntu.
https:/
But when I follow the same steps on updating the OPAL 810 Firmware on
Firestone Hardware, I am getting error as shown.
root@ltc-fire8:~# uname -a
Linux ltc-fire8 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 10:11:54
UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
root@ltc-fire8:~# cat /etc/os-r
Could you paste the full stacktrace from your error logs so we can see
where the call is being made from please.
** Changed in: neutron (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: neutron (Ubuntu Wily)
Status: New => Incomplete
--
You received this bug notification be
Looking at the filters for neutron:
neutron/rootwrap.d/l3.filters
has the only reference to conntrack; neutron-l3-agent has the correct
depends on conntrack but I'm guessing that the linuxbridge configuration
you're using is not trying todo l3 routing.
So I'm a bit puzzled as to why this is ne
>From the Debian people I got a hint:
After adding
utf8_filesystem=YES
to the vsftpd.conf I got the UTF8 in response to the FEAT command! So, problem
solved!
I consider it to be a kind of 'undocumented feature' since the setting
is missing in the man-page.
Also I assume the default of this
** Also affects: neutron (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu Wily)
Importance: Undecided => High
** Changed in: neutron (Ubuntu Xenial)
Importance: Unde
I have installed the ipmitool_1.8.13-1ubuntu0.6_ppc64el.deb package on
Ubuntu 14.04.3 OS and tried to update the OPAL 810 latest Firmware on a
Habanero LC Hardware.
root@ltchabanero002:~# wget
https://launchpad.net/ubuntu/+source/ipmitool/1.8.13-1ubuntu0.6/+build/8288800/+files/ipmitool_1.8.13-1u
vivid build now ships the neon optimized jerasure backend:
drwxr-xr-x root/root 0 2015-11-12 14:48
./usr/lib/aarch64-linux-gnu/ceph/erasure-code/
-rw-r--r-- root/root432144 2015-11-12 14:48
./usr/lib/aarch64-linux-gnu/ceph/erasure-code/libec_jerasure.so
-rw-r--r-- root/root62
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apache2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/14
This bug has been discussed on the apache bug tracker :
https://bz.apache.org/bugzilla/show_bug.cgi?id=53555
There seems to be no movement to fix this that I can see. there is a
patch which seems to fix it for users up to a higher usage level.
https://bz.apache.org/bugzilla/attachment.cgi?id=331
Hi Rushikesh,
This doesn't appear to belong in this tracker, which is about problems
in documentation, so I've tagged it up with Ubuntu's neutron package for
you.
** Also affects: ubuntu
Importance: Undecided
Status: New
** No longer affects: ubuntu
** Also affects: neutron (Ubuntu)
44 matches
Mail list logo
