This still exists in current dev-version of Ubuntu 15.10. Is this a bug
caused by the (quite old, current Puppet-version is 4.2.2) Ubuntu
package or by puppet itself?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https
Debdiffs for squid3 fixes and libecap2 transition were provided in LP:
#1496223
Let me know if I should move or copy them here.
--
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/1496924
The squid3_3.3.8-1ubuntu16.debdiff patch requires gcc5 transition of
libecap2. I kept the lib soname and added a Conflicts: as per
https://wiki.debian.org/TransitionBestPractices
libecap2 and squid3 have been build at
https://launchpad.net/~tdaitx/+archive/ubuntu/testing/+sourcepub/5445490/+listin
** Patch added: "fixes for this bug as well as LP: #1501566 and LP: #1496924"
https://bugs.launchpad.net/squid/+bug/1496223/+attachment/4480476/+files/squid3_3.3.8-1ubuntu16.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sq
** Patch added: "patch with fixes for this bug as well as LP: #1496223 and LP:
#1496924"
https://bugs.launchpad.net/squid/+bug/1501566/+attachment/4480475/+files/squid3_3.3.8-1ubuntu16.debdiff
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Serv
FYI: The libecap older than 1.0.0 and Squid older than 3.5 are in a
lock-step dependency due to the libecap API and ABI being unstable in
those versions. Even if you can get it to build the call sequence to the
API is wrong at run-time. You get to pick libecap2 (0.2) + squid (3.3,
3.4) or libecap3
** Description changed:
squid3 fails with:
- dh_install -psquid3 --sourcedir=/«PKGBUILDDIR»/debian/tmp
+ dh_install -psquid3 --sourcedir=/«PKGBUILDDIR»/debian/tmp
cp: cannot stat
'/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8': No such file or
directory
dh_install: cp --
Public bug reported:
squid3 fails with:
dh_install -psquid3 --sourcedir=/«PKGBUILDDIR»/debian/tmp
cp: cannot stat '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8':
No such file or directory
dh_install: cp --reflink=auto -a
/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_aut
** Tags removed: need-duplicate-check
--
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/1501552
Title:
package apache2 2.4.7-1ubuntu4.7 [origin: Ubuntu] failed to
install/upgrade: pa
Public bug reported:
i just reinstalled badly, so it doesn't works very well
ProblemType: Package
DistroRelease: elementary OS 0.3.1
Package: apache2 2.4.7-1ubuntu4.7 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
Uname: Linux 3.16.0-50-generic x86_64
Nonf
The attachment "0001-vmhgfs-support-linux-4.2.x-kernel.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 Launchpa
** Changed in: open-vm-tools (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1500581
Title:
open-vm-tools-dkms fails to build on kernel 4
@gz: I got this at our staging environment, where we re-deploy
HA'd juju + openstacks several times a week (or day), 1st time
I positively observe this behavior, so I'd guess it's unfortunately
a subtle race condition or alike.
I did save /var/lib/juju/db/, /var/log/syslog and /var/log/juju/machin
This bug discussing here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322
https://aur.archlinux.org/packages/open-vm-tools-dkms/
https://github.com/vmware/open-vm-tools/issues/44
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed t
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to Vivid
base on change betwen
https://github.com/torvalds/linux/commit/1f55a6ec940fb45e3edaa52b6e9fc40cf8e18dcb
and
https://github.com/torvalds/linux/commit/680baacbca69d18a6d7315374ad83d05ac9c0977
a write patch 0001-vmhgfs-support-linux-4.2.x-kernel.patch
** Patch added: "0001-vmhgfs-support-linux-4.2.
** Bug watch added: Debian Bug tracker #800322
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322
** Also affects: open-vm-tools (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
** Attachment added: "proposed debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1501491/+attachment/4480272/+files/debdiff
--
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/150
--
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/1501491
Title:
Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty
To manage notifications about this bug go to:
https:
I cannot simply remove those characters as this is fstab generated by
our deployment S/W. I would think that a patch (assuming last digit in
a version is a patch level) should not break existing code.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Quoting Stephen (sajames1...@gmail.com):
> /home/ubuntu/nzos/volumes/1.0.0/common/shared
> /var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0
Plesae get rid of the "./" in the path.
We could check for this in the paths, but I start to become
concerned at that point that we're begging for
I opened 1501491
--
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/1501310
Title:
Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty
To manage notifications about this
Public bug reported:
A partial fix was made for 1501310 - this case still fails.
/home/ubuntu/nzos/volumes/1.0.0/common/shared
/var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0
This line is giving the same error. With 1.0.7-0ubuntu0.6 installed.
lxc-start: utils.c: ensure_not_symlink:
/home/ubuntu/nzos/volumes/1.0.0/common/shared
/var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0
This line is giving the same error. With 1.0.7-0ubuntu0.6 installed.
lxc-start: utils.c: ensure_not_symlink: 1398 Mount onto /usr/lib/x86_64
-linux-gnu/lxc//nzos/./__shared__ resulted in /usr
In reference to above comment - should I open a new bug?
--
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/1501310
Title:
Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on tr
The regression should be fixed with lxc 1.0.7-0ubuntu0.6. See
http://www.ubuntu.com/usn/usn-2753-2/ for more details.
--
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/1476662
Title:
lxc-s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: awscli (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to awscli in Ubuntu.
https://bugs.launchpad.net/bugs/1501
*** This bug is a duplicate of bug 1501042 ***
https://bugs.launchpad.net/bugs/1501042
** This bug has been marked a duplicate of bug 1501042
Hosted version for 14.04 is incompatible with python 3.4.1+
--
You received this bug notification because you are a member of Ubuntu
Server Team, w
Reviewed: https://review.openstack.org/225206
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=3aefdf4de76fdcdc02093bc631e339f9ecd4c707
Submitter: Jenkins
Branch:master
commit 3aefdf4de76fdcdc02093bc631e339f9ecd4c707
Author: James Page
Date: Fri Sep 18 16:38:47 2015
This bug was fixed in the package lxc - 1.0.7-0ubuntu0.6
---
lxc (1.0.7-0ubuntu0.6) trusty-security; urgency=medium
* Fix breakage of some configurations where // ends up in the mount
target. (LP: #1501310) (LP: #1476662)
-- Serge Hallyn Wed, 30 Sep 2015 10:38:14
-0500
**
> Will the juju team be asking for an MRE? Is it anticipated that new series
> (e.g., the 1.18 to 1.22 change) would be included as an MRE? What
> processes are in place to test updates before including updates into the
> archive? What processes are available to the security team to test
> updates
I reported https://bugs.launchpad.net/ubuntu/+source/juju-
core/+bug/1500916 to address bug 1497087. While the Juju team has always
provided backports for its community, we don't have the privileges to
provide backports quickly. The Juju QA team has dedicated staff for
release and backport, and in
@seth
I reported https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916 to
address bug 1497087. While the Juju team has always provided backports for its
community, we don't have the privileges to provide backports quickly. The Juju
QA team has dedicated staff for release and backport,
Sponsored for T/U/V.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1498697
Title:
Targets are not consistently shown with large numbers of targets
To manage notifications about this b
I'm aware of this behavior happening in earlier versions of Horizon - I
do need to double check that it happens on the latest code.
As an ugly workaround this panel can be disabled in a large environment.
** Changed in: horizon
Status: New => Confirmed
** Changed in: horizon
Importance
No pagination in the current code; I'm sure this is still an issue
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/nova.py#L734
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.la
I have found a work-around for 14.04 LTS. It's not the prettiest one but it
works. When I started a vpn connection and then ran
ps -efwww | grep vpn
I could see that the openvpn is already called with flags "--script-security 2
--up /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper". So t
2nd debdiff for Vivid (Fixing the unmet depencies of "libibverbs-dev")
** Patch added: "2nd debdiff for Vivid"
https://bugs.launchpad.net/ubuntu/trusty/+source/tgt/+bug/1498697/+attachment/4480119/+files/lp1498697_vivid2.debdiff
--
You received this bug notification because you are a member
** Changed in: lxc (Ubuntu)
Status: New => In Progress
** Changed in: lxc (Ubuntu)
Importance: Undecided => Critical
--
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/1501310
Titl
The bug report title makes it pretty clear that this is the security fix
on trusty.
--
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/1501310
Title:
Unable to start containers after upgrad
After applying the patch mentioned in comment #4 the build carries on
further, but fails with a new error. This is when building against the
new libecap3 library (that's in -proposed), so this might be actually
some problem regarding the changes there. But I also tried this patch
when building agai
@breno
You noted that these patches came from another comment. I'm not sure
which upstream commits these changes correspond to. Can you find this
out, and I can amend the debdiff to show patch origin. Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
I checked and Debian made squid3 building against libecap3 with version
3.5.6-1 [1]. This is a big upstream release and I'm not sure if it's a
good idea to merge it to Ubuntu wily so late in the cycle. I also
experimented and tried to fix the configure scripts to just pick up the
new libecap3 and s
Do you have any date when we will see this in trusty-backports?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1493597
Title:
[backport] open-vm-tools from 15.10 to 14.04/15.0
** Changed in: freeipmi (Ubuntu Wily)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1499838
Title:
ipmi-locate causes synchronous external
Hi Tobias - Can you share what Ubuntu release you're using?
--
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/1501310
Title:
Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on
Relative paths are definately recommended over absolute paths, but the
breaking of absolute paths will be fixed.
Can anyone who's having trouble who is not on trusty please comment?
I'd like to make sure that is the only problem.
--
You received this bug notification because you are a member of
Hello - Is anyone seeing this regression on a release other than 14.04
LTS (Trusty)?
--
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/1476662
Title:
lxc-start symlink vulnerabilities may
Thanks for reporting this bug.
As a workaround, please update the entry to read:
lxc.mount.entry=/media/array/backup/blixten var/backup none bind 0 0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpa
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to Vivid
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1498697
Title:
Targets are not consistently shown with large numbers of targets
To manage notifications about this bug
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to Vivid
** Changed in: open-vm-tools (Ubuntu)
Importance: Undecided => High
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New => Confirmed
** Changed in: hundredpapercuts
Importance: Undecided => High
--
You received
I prepared a backport of 1.24.6 from wily to vivid. The changelog is the only
difference between the wily and vivid versions. I made the diff like this:
diff -r -u -x *.bzr juju-core/ vivid-1.24.6/
where juju-core came from lp:ubuntu/juju-core and vivid-1.24.6 is a branch from
lp:ubuntu/juju
** Branch linked: lp:~sinzui/ubuntu/vivid/juju-core/vivid-1.24.6
--
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/1500916
Title:
[needs-packaging] 1.24.6 is not packaged in Vivid
T
I'm not so deep in LXC to know how the design/specification is done for
that. Discussion of "features" might therefore suite the lxc-users
mailing list better.
The other thing is, if Ubuntu would treat that part of new behaviour of
LXC affecting some users as "regression" and hence might act on th
I might be wrong, but I don't think changing the dependency back to
libecap2 (0.2.0) is the right way to go. The new libecap library
(libecap3) is currently in transition and the squid3 build problem is
blocking its migration. If we re-introduce the libecap2 dependency, then
libecap3 won't be able
@Stephen Gaito and @Roman Fiedler:
Thanks for your hints! Using **relative** paths definitely helps also within
the container fstab file.
However it would be very helpful if lxc would accept the absolute paths again:
fstab that fails with 1.0.7-0ubuntu0.5:
/home/MYUSER/somemountpoint
/var/lib/
Public bug reported:
I got this entry in the config file to mount a folder on the hosts
filesystem:
lxc.mount.entry=/media/array/backup/blixten
/var/lib/lxc/blixten/rootfs/var/backup none bind 0 0
this is the lxc root: lxc.rootfs = /var/lib/lxc/blixten/rootfs
Nither /media/array/backup/blixten
Public bug reported:
1)System
Release :
Description:Ubuntu 14.04.3 LTS
Release:14.04
Kernel:
Linux 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:21:34 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
2) Package:
vsftpd 3.0.2-1ubuntu2.14.04.1
3) Expected:
Being able to authenticate vsf
Public bug reported:
Não sei bem o que ocorreu durante a instalação
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: mysql-server-5.6 5.6.25-0ubuntu0.15.04.1
ProcVersionSignature: Error: [Errno 2] Arquivo ou diretório não encontrado:
'/proc/version_signature'
Uname: Linux 4.2.1-040201-g
** Tags removed: need-duplicate-check
--
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/1501286
Title:
package mysql-server-5.6 5.6.25-0ubuntu0.15.04.1 failed to
install/upgrade: s
Looking through the top Google results on how to bind-mount a directory
from the host-server into the lxc-server I notice that:
* Stéphane Graber's "LXC 1.0: Advanced container usage [3/10]" post (
https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/ )
makes use of the **relative*
@roman-fiedler
We're using absolute mount targets here, so that might help. Will try this out.
--
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/1476662
Title:
lxc-start symlink vulnerabil
@roman-fiedler
Might point to the same, but we already have relative mount targets:
lxc.mount.entry = proc /var/lib/our_containers/123/rootfs/proc proc
nosuid,nodev,noexec 0 0
So that won't help as suggested in the mail.
--
You received this bug notification because you are a member of Ubuntu
I have a similar problem (but not with /proc).
***Roman Fielder's link (above) suggests the correct work around.***
My lxc configuration file has the following line:
> lxc.mount.entry = /data/references
/var/lib/lxc/noteServer/rootfs/data/references none ro,bind 0 0
(Note that the mount direct
This happens to me, too. Blacklisting the module does nothing.
Reinstalling with a clean config does nothing.
I have had no choice but to roll back the whole system upgrade to a
previous backup.
It is a shame that probably the most important PBX is broken on probably
the most important Linux dist
Does https://lists.linuxcontainers.org/pipermail/lxc-
users/2015-September/010131.html point to the same problem?
--
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/1476662
Title:
lxc-star
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: open-vm-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad
The problem lies in the ubuntu patch
http://archive.ubuntu.com/ubuntu/pool/main/l/lxc/lxc_1.0.7-0ubuntu0.5.debian.tar.gz
where this code
+ size_t start = croot ? strlen(croot) : 0;
+ if (strcmp(ws + start, target + start) != 0) {
+ ERROR("Mount onto %s resulted in %s\n"
Public bug reported:
If I apt-get remove squid-deb-proxy-client, every apt-get
install/update/upgrade operation produces this error message:
0% [Working]Failed to exec method /usr/share/squid-deb-proxy-client
/apt-avahi-discover
The workaround is to apt-get purge squid-deb-proxy-client.
**
We're getting
lxc-start: utils.c: safe_mount: 1409 Mount of 'proc' onto
'/usr/lib/x86_64-linux-gnu/lxc//proc' was onto a symlink!
on all containers since we upgraded to 1.0.7-0ubuntu0.5 and they don't
start. No container has /proc as a symlink. Plese tell me what
information is required from me.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu Trusty)
Status: New => Confirmed
--
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/1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
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/1501135
** Changed in: landscape/cisco-odl
Status: Fix Committed => Fix Released
--
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/1490727
Title:
"Invalid IPC credentials" after coros
75 matches
Mail list logo
