Public bug reported:
squid-deb-proxy fails to startup under normal boot on a systemd managed
machine.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: squid-deb-proxy 0.8.9
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion:
Presumably this is related to the DHCP client via dhclient and dhclient-
script, so presumably should be a task on isc-dhcp?
I see code in dhclient-script that sets the MTU based on the DHCP
option, but it doesn't have any special behaviour for br0. So I'm
wondering if this code is being used at
** Tags added: cts openstack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1405588
Title:
database connection failed (Protocol error)
To manage notifications about this bug
** Attachment added: syslog-tftp-hpa-net-device-up.txt
https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1342580/+attachment/4292436/+files/syslog-tftp-hpa-net-device-up.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The proposed fix (from #1 as well as the corrected version from #5) does
not solve the problem for me. Actually, when I look at what time the
system tries to start the tftp-hpa process, it makes it even worse: The
process gets started earlier (around ~11s vs ~13s)! Also, the relevant
errors look
** Tags removed: need-duplicate-check
--
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/1407670
Title:
package php5-fpm 5.5.12+dfsg-2ubuntu4.1 failed to install/upgrade:
subprocess
Public bug reported:
According to `ps faux` the process stopped (and then failed) during
`stop php5-fpm`
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: php5-fpm 5.5.12+dfsg-2ubuntu4.1
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
** Changed in: juju-core
Assignee: (unassigned) = Dimiter Naydenov (dimitern)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: bind9 (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1405075
Title:
Sync bind9 1:9.9.5.dfsg-7 (main) from Debian unstable
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
Interface MTU management across MAAS/juju
To manage notifications about this bug
This bug was fixed in the package bind9 - 1:9.9.5.dfsg-8
Sponsored for Artur Rona (ari-tczew)
---
bind9 (1:9.9.5.dfsg-8) unstable; urgency=medium
* Launch rndc command in the background in networking scripts to avoid a
hang in named from bringing down the entire network
You have been subscribed to a public bug:
I created NameVirtualHost, dev.conf in /etc/apache2/sites-available/, and
also symbolic link, dev.conf in /etc/apache2/sites-enabled/. The configure is
right, works with test.
But when restart Buntu 14.04 LTS, the link file missing - I have NOT any
** Tags added: trusty
** Package changed: ubuntu = apache2 (Ubuntu)
--
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/1407099
Title:
lost link file in sites-enabled
To manage
This bug was fixed in the package docker.io - 1.3.3~dfsg1-2ubuntu1
---
docker.io (1.3.3~dfsg1-2ubuntu1) vivid; urgency=low
* Merge from Debian unstable (LP: #1407408). Remaining changes:
- d/p/sync-apparmor-with-lxc.patch: Update AppArmor policy to be
in sync with LXC.
Ahh, you forgot to close bug in debian/changelog. I've added that, as
well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1407409
Title:
please merge golang from debian
To manage
Not bad, but the same issue like on the docker.io. I've deleted blank
line at the end of debian/changelog.
@@ -593,3 +623,4 @@
* Remove codereview directory - some python code to deal with mercurial
-- Ondřej Surý ond...@debian.org Mon, 14 Feb 2011 17:42:39 +0100
+
Thanks!
** Changed
This has been discussed before. I definately want to make things work
as cleanly as possible out of the box. There are a few problems with
doing htis though, 1) networkmanager isn't the only place we'd need to
do this (most serious lxc hosts probably don't run networkmanager), 2)
if we do this
** Branch linked: lp:ubuntu/vivid-proposed/golang
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1407409
Title:
please merge golang from debian
To manage notifications about this
Public bug reported:
On a desktop system, on AC power, pm-utils reset the vm.dirty_ratio and
vm.dirty_background_ratio at boot time.
When setting these variables using sysctl.conf, they are silently reset
by the /usr/lib/pm-utils/power.d/laptop-mode script shipped with pm-
utils.
The only way
If this could be fixed in seabios that would be ideal. Discussion of a
second-best solution should probably wait unti lwe're certain that is
not possible.
Since with respect to this issue we should be in sync with Debian, I'm curious
whether Debian also has this issue.
--
You received this bug
** 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/1380965
Title:
Floating IPs don't have instance ids in Juno
To manage notifications
Public bug reported:
When installing the docker.io package, it fails during installation with
a message akin to the following:
stderr: addgroup: The group `docker' already exists and is not a system group.
Exiting.
dpkg: error processing package docker.io (--configure):
subprocess installed
** Patch added: debian-ubuntu.debdiff
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1407826/+attachment/4292607/+files/debian-ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
** Patch added: ubuntu-ubuntu.debdiff
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1407826/+attachment/4292608/+files/ubuntu-ubuntu.debdiff
** Changed in: nss (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: nss (Ubuntu)
Status: New = Confirmed
--
You received this
Public bug reported:
nss (2:3.17.2-1.1) unstable; urgency=medium
* Non-maintainer upload.
* Fix CVE-2014-1569. Closes: #773625.
-- Matt Kraai kr...@debian.org Sun, 21 Dec 2014 19:46:52 -0800
** Affects: nss (Ubuntu)
Importance: Wishlist
Status: Confirmed
** CVE added:
This bug was fixed in the package golang - 2:1.3.3-1ubuntu1
---
golang (2:1.3.3-1ubuntu1) vivid; urgency=low
* Merge from Debian unstable. (LP: #1407409) Remaining changes:
- 016-armhf-elf-header.patch: Use correct ELF header for armhf binaries.
- Support co-installability
Thanks for taking an interest in the issue.
Since I filed this specifically against lxc in Ubuntu, wouldn't it make
sense to start by documenting the necessary config changes (including
NetworkManager's dnsmasq config, since it is part of Ubuntu by default)
in /usr/share/doc/lxc/README?
--
You
I'm marking this as Opinion.
Here's why:
The local sysadmin may have created a Docker group, but *not* intended
to give the rights to use Docker to those users. Remember, the Docker
group is root equivelent.
[tag@cassiel:~][⌚ 09:02 PM] ♥ docker run -it --rm -v /./:/mnt
debian:unstable
As per the cloud init output log in comment #2, on a precise system, if
you do:
apt-get install cloud-image-utils
apt-decides it needs to remove the cloud-init package (amongst others).
Suggested fix along the lines of:
smoser we can fix that with a packaging change to cloud-init in precise.
Would you care to upload a patch to edit README.Debian with that
information?
Note that the non-network-manager version of this is currently commented
in https://help.ubuntu.com/14.04/serverguide/lxc.html .
--
You received this bug notification because you are a member of Ubuntu
Server Team,
For now, I've worked around in Juju by not explicitly installing cloud-
image-utils. Where tis matter, in local providers, I've added a check to
ensure that cloud-image-utils is installed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr195-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- hardware enablement: ppc64 support (LP: #1386394)
- hardware enablement: know kernel mapping for
This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.8
---
libvirt (1.2.2-0ubuntu13.1.8) trusty-proposed; urgency=medium
* complete the 9p support: (LP: #1378434)
- libvirt-qemu: add fowner and fsetid
- virt-aa-helper: add 'l' to 9p file options
* libvirt-qemu
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr195-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- hardware enablement: ppc64 support (LP: #1386394)
- hardware enablement: know kernel mapping for
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr195-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- hardware enablement: ppc64 support (LP: #1386394)
- hardware enablement: know kernel mapping for
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr195-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- hardware enablement: ppc64 support (LP: #1386394)
- hardware enablement: know kernel mapping for
The verification of the Stable Release Update for curtin has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for curtin has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for curtin has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for curtin has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
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 and corosync to latest: TODO
+ MySQL cleanup in Debian and 5.6 transition: TODO
--
General server work for Vivid
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr195-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- hardware enablement: ppc64 support (LP: #1386394)
- hardware enablement: know kernel mapping for
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr195-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- hardware enablement: ppc64 support (LP: #1386394)
- hardware enablement: know kernel mapping for
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr195-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- hardware enablement: ppc64 support (LP: #1386394)
- hardware enablement: know kernel mapping for
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr195-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- hardware enablement: ppc64 support (LP: #1386394)
- hardware enablement: know kernel mapping for
This bug was fixed in the package libvirt - 1.2.8-0ubuntu11.2
---
libvirt (1.2.8-0ubuntu11.2) utopic-proposed; urgency=medium
* complete the 9p support: (LP: #1378434)
- libvirt-qemu: add fowner and fsetid
- virt-aa-helper: add 'l' to 9p file options
* add mising apparmor
This bug was fixed in the package libvirt - 1.2.8-0ubuntu11.2
---
libvirt (1.2.8-0ubuntu11.2) utopic-proposed; urgency=medium
* complete the 9p support: (LP: #1378434)
- libvirt-qemu: add fowner and fsetid
- virt-aa-helper: add 'l' to 9p file options
* add mising apparmor
This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.8
---
libvirt (1.2.2-0ubuntu13.1.8) trusty-proposed; urgency=medium
* complete the 9p support: (LP: #1378434)
- libvirt-qemu: add fowner and fsetid
- virt-aa-helper: add 'l' to 9p file options
* libvirt-qemu
This worked for me:
ssh -v admin@172.16.3.253 -o KexAlgorithms=diffie-hellman-group14-sha1
source:
http://stackoverflow.com/questions/25341773/cisco-ssh-key-exchange-
fails-from-ubuntu-14-04-client-dh-key-range-mismatch
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package xen - 4.4.1-0ubuntu0.14.04.3
---
xen (4.4.1-0ubuntu0.14.04.3) trusty; urgency=low
* d/xen-utils-common.xen.init: Update script to start a QEMU process for
dom0. (LP: #1396068)
-- Stefan Bader stefan.ba...@canonical.com Thu, 11 Dec 2014
This bug was fixed in the package xen - 4.4.1-0ubuntu0.14.10.3
---
xen (4.4.1-0ubuntu0.14.10.3) utopic; urgency=low
* d/xen-utils-common.xen.init: Update script to start a QEMU process for
dom0. (LP: #1396068)
-- Stefan Bader stefan.ba...@canonical.com Thu, 11 Dec 2014
This bug was fixed in the package qemu - 2.0.0+dfsg-2ubuntu1.10
---
qemu (2.0.0+dfsg-2ubuntu1.10) trusty; urgency=low
* Apply an upstream qemu patch to fix issues with persistent grants
on qcow images accessed by dom0 (LP: #1394327).
-- Stefan Bader stefan.ba...@canonical.com
Canonical,
Do you agree on this patch? We sent it upstream but didn't received any
comment so far.
** Changed in: numactl (Ubuntu)
Assignee: (unassigned) = Taco Screen team (taco-screen-team)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
The verification of the Stable Release Update for xen has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package qemu - 2.1+dfsg-4ubuntu6.4
---
qemu (2.1+dfsg-4ubuntu6.4) utopic; urgency=low
* Apply an upstream qemu patch to fix issues with persistent grants
on qcow images accessed by dom0 (LP: #1394327).
-- Stefan Bader stefan.ba...@canonical.com Mon,
--- Comment (attachment only) From thierry.fa...@fr.ibm.com 2014-11-19
14:45 EDT---
** Attachment added: libnuma.so.1 sum 55709
https://bugs.launchpad.net/bugs/1358835/+attachment/4292524/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb
--
You received this bug notification
--- Comment on attachment From thierry.fa...@fr.ibm.com 2014-11-18 15:55
EDT---
Please have a test
** Attachment added: new libnuma.so with fix
https://bugs.launchpad.net/bugs/1358835/+attachment/4292523/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb
--
You received this bug
Proposing class C2
https://wiki.openstack.org/wiki/Vulnerability_Management#Incident_report_taxonomy
--
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/832507
Title:
console.log grows
I'm running Ubuntu 14.04 with Asterisk 11.7.0~dfsg-1ubuntu1 and FreePBX
12.0.25.
app_stack.so will not load at boot, either autoloading or with a
specific load directive in the startup scripts.
I can load it manually by connecting to the asterisk console (sudo
asterisk -r) and then manually
60 matches
Mail list logo
