[Bug 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts

2015-02-21 Thread Brendan McGrath
Please note that the installation scripts I meant to refer to are
postinst and postrm (not postinst and preinst).

-- 
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/1052449

Title:
  corosync hangs due to missing pacemaker shutdown scripts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts

2015-02-21 Thread Brendan McGrath
I got a bit confused reading through this bug and the comments so I'm
writing this in the hope it'll help future visitors.

Some of the comments are relevant to a work-around for this bug. But the
bug itself is about the missing update-rc.d command in the postinst (and
preinst) scripts of the install package.

The suggestion in the original bug report is to follow a pattern similar
to corosync where the update-rc.d is in the postinst and preinst scripts
but you still need to edit /etc/default/corosync to enable corosync to
start on boot.

The workaround in the meantime requires one to manually run update-rc.d.
When doing this - it's important that corosync starts before pacemaker
and shuts down after.

To do this, we can run:
sudo update-rc.d pacemaker defaults 99 00

I'm running 14.04.02 LTS - so:
#2 is no longer the case ('Required-Stop: corosync' is now in the 
/etc/init.d/pacemaker script)
#5 won't be a problem as insserv has been disabled (by .legacy-bootordering in 
/etc/init.d)

-- 
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/1052449

Title:
  corosync hangs due to missing pacemaker shutdown scripts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1395098] Re: [Utopic] OpenLDAP version is outdated

2015-02-21 Thread Ryan Tandy
** Attachment added: "openldap_2.4.40-4ubuntu1.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1395098/+attachment/4324360/+files/openldap_2.4.40-4ubuntu1.dsc

-- 
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/1395098

Title:
  Please merge openldap 2.4.40-4 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1395098/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1395098] Re: [Utopic] OpenLDAP version is outdated

2015-02-21 Thread Ryan Tandy
** Patch added: "openldap_2.4.40-4ubuntu1.diff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1395098/+attachment/4324361/+files/openldap_2.4.40-4ubuntu1.diff.gz

-- 
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/1395098

Title:
  Please merge openldap 2.4.40-4 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1395098/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1395098] Re: [Utopic] OpenLDAP version is outdated

2015-02-21 Thread Ryan Tandy
Rebased, sorry it took me a while to get to this.

I guess this has missed freeze for 15.04 now, but I'd still welcome
reviews in case changes are needed before getting it merged next cycle.

Packages for testing are in ppa:rtandy/lp1395098.

** Patch added: "debdiff against debian testing"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1395098/+attachment/4324362/+files/openldap_2.4.40-4ubuntu1.debdiff

** Summary changed:

- [Utopic] OpenLDAP version is outdated
+ Please merge openldap 2.4.40-4 (main) from Debian unstable (main)

** Changed in: openldap (Ubuntu)
 Assignee: Ryan Tandy (rtandy) => (unassigned)

** Changed in: openldap (Ubuntu)
   Status: In Progress => Confirmed

-- 
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/1395098

Title:
  Please merge openldap 2.4.40-4 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1395098/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1389954] Re: Make .lxc domain name resolution easier to discover and enable

2015-02-21 Thread Forest
Sure. Is this the right place?
https://github.com/lxc/lxc-pkg-ubuntu

-- 
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/1389954

Title:
  Make .lxc domain name resolution easier to discover and enable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389954/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424253] [NEW] RFE: procps tools should support lxc

2015-02-21 Thread Jens Elkner
Public bug reported:

Container management/monitoring is currently a pain, because procps do
not support container, i.e. there is no way to tell the tools to
"filter" the output wrt. a certain zone or to add a column, which shows
the zone name a process belongs to.

E.g. for what is needed:
{ps|pgrep|pkill|top} ... -z $myzone 
# show zone name as well
{ps|top} -Z

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1424253

Title:
  RFE: procps tools should support lxc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424253/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424233] Re: RFE lxc: lxc should do a better jon of housekeeping containers

2015-02-21 Thread Jens Elkner
** Package changed: upstart (Ubuntu) => lxc (Ubuntu)

-- 
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/1424233

Title:
  RFE lxc: lxc should do a better jon of housekeeping containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424233/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424233] [NEW] RFE lxc: lxc should do a better jon of housekeeping containers

2015-02-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Right now lxc does a pretty poor job wrt. managing containers, i.e. one
needs to know, where containers have been installed to be able to
access/use/manage them (option -P dir) unless they've been installed in
the default location. Even if one knows the install path, it is still a
pain to work with corresponding lxc commands, because one always needs
to specify -P ...

This really sucks (especially if one needs to service foreign machines).

So the proposal is, that if a zone gets created, lxc puts a symlink to
the related config under /etc/lxc/cfg/ or something like that and all
lxc tools like lxc-ls first check this directory, and if the link
destination exists, it has all information it needs to know., i.e. all
"-P idontknow" madness is not required anymore.

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New

-- 
RFE lxc: lxc should do a better jon of housekeeping containers
https://bugs.launchpad.net/bugs/1424233
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424237] [NEW] missing manpage for bridge.conf

2015-02-21 Thread Karl-Philipp Richter
Public bug reported:

There's currently no (easy) way to figure out the form of content of
`/etc/qemu/bridge.conf`. Some howtos (e.g.
https://wiki.archlinux.org/index.php/QEMU#Bridged_networking_using_qemu-
bridge-helper) mention `bridge.conf.sample` which is not available
according to `apt-file` and the official wiki at wiki.qemu.org doesn't
mention the file at all, it seems necessary, though, because
specification of `-net nic -net bridge,br=bridge0` fails with `failed to
get mtu of bridge `bridge0': No such device` (can't be investigated
further because setup is completely unclear).

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: qemu 2.1+dfsg-4ubuntu6.4
Uname: Linux 3.19.0-031900-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 21 19:39:07 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-26 (25 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
KvmCmdLine:
 COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
 kvm-irqfd-clean S<   0 0  1026 2  0.0 [kvm-irqfd-clean]
 qemu-system-x86 Sl+  0 0 25905 25904 11.9 qemu-system-x86_64 -boot c 
-hda ubuntu.img -m 2048 -smp 16 -enable-kvm -vnc :0,abc -k de -drive 
file=/dev/sda14,if=ide -net nic -net bridge,br=bridge0
 kvm-pit/25905   S0 0 25948 2  0.0 [kvm-pit/25905]
MachineType: LENOVO 20221
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-031900-generic 
root=UUID=ac20c93a-0ec5-445a-98cd-941f0fbc0e50 ro rootflags=subvol=@
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 71CN51WW(V1.21)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 3193WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Z500 Touch
dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
dmi.product.name: 20221
dmi.product.version: Lenovo IdeaPad Z500 Touch
dmi.sys.vendor: LENOVO

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages utopic

-- 
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/1424237

Title:
  missing manpage for bridge.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1424237/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424170] Re: package python-markdown 2.5.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2015-02-21 Thread Dmitry Shachnev
This looks like a random segfault somewhere in postinst code, not really
informative without a stack trace.

** Changed in: python-markdown (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-markdown in Ubuntu.
https://bugs.launchpad.net/bugs/1424170

Title:
  package python-markdown 2.5.1-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 139

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-markdown/+bug/1424170/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1423539] Re: package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-02-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: php5 (Ubuntu)
   Status: New => Confirmed

-- 
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/1423539

Title:
  package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1423539/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424192] [NEW] [python3] /usr/bin/pep8 is missing

2015-02-21 Thread exsudat
Public bug reported:

Attention: Am I correct that this launchpad is for "pep8" AND the 
"python3-pep8" package together?
This report depends on "python3-pep8", the pep8-version for Python3.

There is no /usr/bin/pep8 for this package. It could be a
/usr/bin/python3-pep8 or whatever do avoid conflicts with the Python2
version. The package "pep8" create a /usr/bin/pep8.

The Python3 version doesn't run without "tricks" (concrete path or load
as a module).

btw: I produtcivly testes this on trusty. But the package directory told
me that there is no such file in this package for vivid, too.

Please see the package info:


** Affects: pep8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: pep8 python3

** Description changed:

  Attention: Am I correct that this launchpad is for "pep8" AND the 
"python3-pep8" package together?
  This report depends on "python3-pep8", the pep8-version for Python3.
  
  There is no /usr/bin/pep8 for this package. It could be a
  /usr/bin/python3-pep8 or whatever do avoid conflicts with the Python2
  version. The package "pep8" create a /usr/bin/pep8.
  
  The Python3 version doesn't run without "tricks" (concrete path or load
  as a module).
  
  btw: I produtcivly testes this on trusty. But the package directory told
- me that there is no such file in this package for unicorn, too.
+ me that there is no such file in this package for vivid, too.
+ 
+ Please see the package info:
+ 

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pep8 in Ubuntu.
https://bugs.launchpad.net/bugs/1424192

Title:
  [python3] /usr/bin/pep8 is missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pep8/+bug/1424192/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424143] Re: lxc-net should attempt to use ip before ifconfig, not vice-versa

2015-02-21 Thread Ubuntu Foundations Team Bug Bot
The attachment "lxc-net-prefer_ip.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
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
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/1424143

Title:
  lxc-net should attempt to use ip before ifconfig, not vice-versa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424143/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424170] Re: package python-markdown 2.5.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2015-02-21 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-markdown in Ubuntu.
https://bugs.launchpad.net/bugs/1424170

Title:
  package python-markdown 2.5.1-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 139

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-markdown/+bug/1424170/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424170] [NEW] package python-markdown 2.5.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2015-02-21 Thread Ashish Deharia
Public bug reported:

don't know what happened, but the pc is still running fine.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: python-markdown 2.5.1-1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
Date: Sat Feb 21 17:26:38 2015
DuplicateSignature: package:python-markdown:2.5.1-1:subprocess installed 
post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2015-02-16 (4 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: python-markdown
Title: package python-markdown 2.5.1-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-markdown (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package utopic

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-markdown in Ubuntu.
https://bugs.launchpad.net/bugs/1424170

Title:
  package python-markdown 2.5.1-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 139

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-markdown/+bug/1424170/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424154] Re: apparmor sysfs remount rejection on lxc-start

2015-02-21 Thread Steve Beattie
So the only difference that I can see is that  so *without* the added
remount rule, /proc/mounts contains the following entries for
sysfs+/sys/ within the container:

  sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
  sysfs /sys sysfs ro,nosuid,nodev,noexec,relatime 0 0

with the added rule, /proc/mounts contains:

  sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
  sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0

(note the 'rw' for the second line of the latter.)

I'm guessing the first entry is the mount entry from the container host
and the second one is the actual container mount?

-- 
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/1424154

Title:
  apparmor sysfs remount rejection on lxc-start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424154/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424154] [NEW] apparmor sysfs remount rejection on lxc-start

2015-02-21 Thread Steve Beattie
Public bug reported:

When starting up an ubuntu lxc container in vivid, I'm seeing the
following apparmor rejection:

Feb 21 01:30:41 vivid-i386 kernel: [ 2121.606513] audit: type=1400
audit(1424511041.643:125): apparmor="DENIED" operation="mount"
info="failed flags match" error=-13 profile="lxc-container-default"
name="/sys/" pid=20698 comm="mount" flags="rw, nosuid, nodev, noexec,
remount"

The container still started up,and I couldn't see anything problematic
within it related to sysfs.

Adding the following remount apparmor rule to
/etc/apparmor.d/abstractions/lxc/container-base allows the remount
operatoin to succeed:

  remount options=(rw, nosuid, nodev, noexec) /sys/,

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lxc 1.1.0-0ubuntu1 [modified: usr/lib/i386-linux-gnu/lxc/lxc-net]
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic i686
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
Date: Sat Feb 21 01:43:55 2015
InstallationDate: Installed on 2014-12-12 (70 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141212)
ProcEnviron:
 TERM=screen
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx
modified.conffile..etc.apparmor.d.abstractions.lxc.container.base: [modified]
modified.conffile..etc.default.lxc: [modified]
mtime.conffile..etc.apparmor.d.abstractions.lxc.container.base: 
2015-02-21T01:34:23.031703
mtime.conffile..etc.default.lxc: 2015-02-20T18:15:56.552501

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apparmor apport-bug i386 third-party-packages vivid

-- 
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/1424154

Title:
  apparmor sysfs remount rejection on lxc-start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424154/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424143] Re: lxc-net should attempt to use ip before ifconfig, not vice-versa

2015-02-21 Thread Steve Beattie
And here's the patch to the lxc-net script to prefer ip(8) over
ifconfig.

** Patch added: "lxc-net-prefer_ip.patch"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424143/+attachment/4323815/+files/lxc-net-prefer_ip.patch

-- 
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/1424143

Title:
  lxc-net should attempt to use ip before ifconfig, not vice-versa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424143/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424143] Re: lxc-net should attempt to use ip before ifconfig, not vice-versa

2015-02-21 Thread Steve Beattie
Here's the complete sh -xe output from running lxc-net start:

ubuntu@vivid-i386:~$ sudo sh -xe /usr/lib/i386-linux-gnu/lxc/lxc-net start
+ distrosysconfdir=/etc/default
+ localstatedir=/var
+ varrun=/run/lxc
+ USE_LXC_BRIDGE=true
+ LXC_BRIDGE=lxcbr0
+ LXC_ADDR=10.0.3.1
+ LXC_NETMASK=255.255.255.0
+ LXC_NETWORK=10.0.3.0/24
+ LXC_DHCP_RANGE=10.0.3.2,10.0.3.254
+ LXC_DHCP_MAX=253
+ LXC_DHCP_CONFILE=
+ LXC_DOMAIN=
+ [ ! -f /etc/default/lxc ]
+ . /etc/default/lxc
+ MIRROR=http://ubuntu-mirror.nxnw.org/ubuntu
+ LXC_AUTO=true
+ USE_LXC_BRIDGE=false
+ [ -f /etc/default/lxc-net ]
+ . /etc/default/lxc-net
+ USE_LXC_BRIDGE=true
+ LXC_BRIDGE=lxcbr0
+ LXC_ADDR=10.0.3.1
+ LXC_NETMASK=255.255.255.0
+ LXC_NETWORK=10.0.3.0/24
+ LXC_DHCP_RANGE=10.0.3.2,10.0.3.254
+ LXC_DHCP_MAX=253
+ LXC_SHUTDOWN_TIMEOUT=120
+ [ -d /var/lock/subsys ]
+ lockdir=/var/lock/subsys
+ start
+ [ ! -f /var/lock/subsys/lxc-net ]
+ [ xtrue = xtrue ]
+ use_iptables_lock=-w
+ iptables -w -L -n
+ [ -d /sys/class/net/lxcbr0 ]
+ brctl addbr lxcbr0
+ echo 1
+ [ ! -d /run/lxc ]
+ ifup lxcbr0 10.0.3.1 255.255.255.0
+ which ifconfig
+ [ 0 = 0 ]
+ ifconfig lxcbr0 10.0.3.1 netmask 255.255.255.0 up
+ return
+ iptables -w -I INPUT -i lxcbr0 -p udp --dport 67 -j ACCEPT
+ iptables -w -I INPUT -i lxcbr0 -p tcp --dport 67 -j ACCEPT
+ iptables -w -I INPUT -i lxcbr0 -p udp --dport 53 -j ACCEPT
+ iptables -w -I INPUT -i lxcbr0 -p tcp --dport 53 -j ACCEPT
+ iptables -w -I FORWARD -i lxcbr0 -j ACCEPT
+ iptables -w -I FORWARD -o lxcbr0 -j ACCEPT
+ iptables -w -t nat -A POSTROUTING -s 10.0.3.0/24 ! -d 10.0.3.0/24 -j 
MASQUERADE
+ iptables -w -t mangle -A POSTROUTING -o lxcbr0 -p udp -m udp --dport 68 -j 
CHECKSUM --checksum-fill
+ LXC_DOMAIN_ARG=
+ [ -n  ]
+ getent passwd lxc-dnsmasq
+ break
+ dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces 
--pid-file=/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
+ touch /run/lxc/network_up
+ touch /var/lock/subsys/lxc-net
+ exit 0

-- 
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/1424143

Title:
  lxc-net should attempt to use ip before ifconfig, not vice-versa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424143/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424143] [NEW] lxc-net should attempt to use ip before ifconfig, not vice-versa

2015-02-21 Thread Steve Beattie
Public bug reported:

The lxc-net script in /usr/lib/$archtriplet/lxc/lxc-net attempts to use
ifconfig first and then falls back to trying to use ip(8) in the ifup()
and ifdown() shell functions. This behavior should be reversed, as ip
has been preferred over ifconfig for several years now.

As an example of why, lxc-net breaks the network setup within virtualbox
guests. After starting lxc-net, the route table looks like:

  ubuntu@vivid-i386:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 10.0.2.20.0.0.0 UG1024   00 eth0
  10.0.0.00.0.0.0 255.0.0.0   U 0  00 lxcbr0
  10.0.2.00.0.0.0 255.255.255.0   U 0  00 eth0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 eth0

This is despite the following settings in /etc/default/lxc-net:

  LXC_BRIDGE="lxcbr0"
  LXC_ADDR="10.0.3.1"
  LXC_NETMASK="255.255.255.0"
  LXC_NETWORK="10.0.3.0/24"

Switching the order in ifup and ifdown to try using ip first results in
the correct netmask being applied:

  ubuntu@vivid-i386:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 10.0.2.20.0.0.0 UG1024   00 eth0
  10.0.2.00.0.0.0 255.255.255.0   U 0  00 eth0
  10.0.3.00.0.0.0 255.255.255.0   U 0  00 lxcbr0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 eth0

Looking at sh -x output when running lxc-net manually, it *looks* like
ifconfig is being invoked correctly, so I don't know why it's getting
the netmask wrong:

+ use_iptables_lock=-w
+ iptables -w -L -n
+ [ -d /sys/class/net/lxcbr0 ]
+ brctl addbr lxcbr0
+ echo 1
+ [ ! -d /run/lxc ]
+ ifup lxcbr0 10.0.3.1 255.255.255.0
+ which ifconfig
+ [ 0 = 0 ]
+ ifconfig lxcbr0 10.0.3.1 netmask 255.255.255.0 up
+ return

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lxc 1.1.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic i686
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
Date: Sat Feb 21 00:13:27 2015
InstallationDate: Installed on 2014-12-12 (70 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141212)
ProcEnviron:
 TERM=screen
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx
modified.conffile..etc.default.lxc: [modified]
mtime.conffile..etc.default.lxc: 2015-02-20T18:15:56.552501

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apparmor apport-bug i386 third-party-packages vivid

-- 
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/1424143

Title:
  lxc-net should attempt to use ip before ifconfig, not vice-versa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424143/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1424140] Re: package sa-compile 3.4.0-3ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 25

2015-02-21 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: spamassassin (Ubuntu)
   Importance: Undecided => Low

** Changed in: spamassassin (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1424140

Title:
  package sa-compile 3.4.0-3ubuntu2.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 25

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1424140/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs