[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

I have installed qemu-slof from trusty and ran again:

qemu-slof:
  Installed: 20151103+dfsg-1ubuntu1
  Candidate: 20151103+dfsg-1ubuntu1
  Version table:
 *** 20151103+dfsg-1ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages
100 /var/lib/dpkg/status
 20131015+dfsg-1ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports trusty/universe ppc64el 
Packages
ubuntu@alpine01:~$ sudo apt-get install qemu-slof=20131015+dfsg-1ubuntu1

It froze on the exact same spot.

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

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1563887/+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 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

Same issue with -m 2048

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

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+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 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

Same issue. Stopped on the exact same spot.

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

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+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 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

Yes. I only mounted (a different file) to troubleshoot what was going
on. The issue was happening before and after mounting. I have since
unmounted it.

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

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+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 1563887] [NEW] qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

Public bug reported:

qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image
as part of the certification process. This on an IBM ppc64le in PowerVM
mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no
error output.

ubuntu@alpine01:~$ qemu-system-ppc64 -m 256 -display none -nographic -net nic 
-net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries 
-drive file=
xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
qemu-system-ppc64: -drive file=seed.iso,if=virtio: Could not open 'seed.iso': 
No such file or directory
ubuntu@alpine01:~$ cd kvm
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive f
ile=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
WARNING: Image format was not specified for 'seed.iso' and probing guessed raw.
 Automatically detecting the format is dangerous for raw images, write 
operations on block 0 will be restricted.
 Specify the 'raw' format explicitly to remove the restrictions.

SLOF **
QEMU Starting
 Build Date = Jan 29 2016 18:58:37
 FW Version = buildd@ release 20151103
 Press "s" to enter Open Firmware.

Populating /vdevice methods
Populating /vdevice/vty@7100
Populating /vdevice/nvram@7101
Populating /vdevice/l-lan@7102
Populating /vdevice/v-scsi@7103
   SCSI: Looking for devices
  8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
Populating /pci@8002000
 00 1800 (D) : 1af4 1001virtio [ block ]
 00 1000 (D) : 1af4 1001virtio [ block ]
 00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
 00  (D) : 1234 qemu vga
No NVRAM common partition, re-initializing...
Installing QEMU fb

Scanning USB
  OHCI: initializing
USB Keyboard
USB mouse
No console specified using screen & keyboard

  Welcome to Open Firmware

  Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
  This program and the accompanying materials are made available
  under the terms of the BSD License available at
  http://www.opensource.org/licenses/bsd-license.php

Trying to load:  from: /pci@8002000/scsi@3 ...
E3404: Not a bootable device!
Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
Linux ppc64le
#31-Ubuntu SMP F

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic ppc64le
ApportVersion: 2.20-0ubuntu3
Architecture: ppc64el
Date: Wed Mar 30 14:10:01 2016
KvmCmdLine:
 COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
 kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
 qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
 qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
ProcLocks:
 1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
 2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
 3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
 4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
 5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /swap.img   file   8388544 0   -1
ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
bootlist:
 /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
 
/pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
 
/pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
 
/pci@8002018/ethernet@0,2:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
 
/pci@8002018/ethernet@0,3:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
cpu_cores: Number of cores 

[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Mike Rushton]

In Ubuntu 14.04.4 running on the same hardware, the fix was to update
qemu-system-ppc from cloud-archive:kilo. This repository is only
supported on trusty and contains an earlier version of qemu-system-ppc
than what is available on xenial.


** Description changed:

  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image
  as part of the certification process. This on an IBM ppc64le in PowerVM
- mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1.
+ mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no
+ error output.
  
  ubuntu@alpine01:~$ qemu-system-ppc64 -m 256 -display none -nographic -net nic 
-net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries 
-drive file=
  xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  qemu-system-ppc64: -drive file=seed.iso,if=virtio: Could not open 'seed.iso': 
No such file or directory
  ubuntu@alpine01:~$ cd kvm
  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive f
  ile=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.
  
  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.
  
  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb
  
  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard
  
    Welcome to Open Firmware
  
    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php
  
  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   

[Bug 1379567] Re: maas-proxy is an open proxy with no ACLs; it should add networks automatically

[Mike Pontillo]

I agree with the concerns about documentation.

Currently, maas-proxy is an optional package which does not depend on
the MAAS region server (or any other MAAS component). It's analogous to
squid-deb-proxy.

The squid-deb-proxy approach to security is to ship (in an
autogenerated/ directory, which you are not supposed to edit) an
allowed-networks-src.acl file, which contains the RFC 1918 IPv4
addresses, and the link-local IPv6 addresses by default.

We could add an additional dependency on the MAAS region (or at least, a
URL to the MAAS region which allows us to figure out which networks are
attached to MAAS), and try to be smart about which networks to add. But
I'm not sure a solution that complex is worth the cost. For now, perhaps
it would be sufficient to take the same approach that squid-deb-proxy
uses, and then document how to ensure it's both secure, and able to
allow any additional desired networks.

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

Title:
  maas-proxy is an open proxy with no ACLs; it should add networks
  automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1379567/+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 1379567] Re: maas-proxy is an open proxy with no ACLs; it should add networks automatically

[Mike Pontillo]

I've seen users complain that when we change this file it gets
overwritten automatically. (I guess we should also move it to /var, if
we're going to be automatically generating the configuration.)

Should every network MAAS knows about be included in the allow list? Or
is finer control needed?

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

Title:
  maas-proxy is an open proxy with no ACLs; it should add networks
  automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1379567/+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 1379567] Re: maas-proxy is an open proxy with no ACLs; it should add networks automatically

[Mike Pontillo]

s/when we change this/when they change that/

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

Title:
  maas-proxy is an open proxy with no ACLs; it should add networks
  automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1379567/+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 1554720] [NEW] Winbind maxing out CPU when AD user logs in with expired password

[Mike]

Public bug reported:

Hi,

My systems are Ubuntu 14.04.3 LTS with samba/winbind 2:4.1.6+dfsg-
1ubuntu2.14.04.11

I am experiencing issues as described in this Samba bug:
https://bugzilla.samba.org/show_bug.cgi?id=11038 which is entitled
'Logging with an account which has the "User must change password on
next logon" flag cause winbindd to use 100% cpu and stop answering
request'.

Jeremy Allison marked this as a blocker bug with the comment "We must
not ship another Samba release with this bug unfixed".

The bug appears to have been fixed in Samba 4.2 and 4.3 releases, but
not in 4.1. Is there any plan to port this bug fix into releases
available on Ubuntu 14.04 LTS?

Mike

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

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

Title:
  Winbind maxing out CPU when AD user logs in with expired password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1554720/+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 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes

[Mike Pontillo]

** Changed in: maas
   Status: New => Triaged

** Changed in: maas
   Importance: Undecided => High

** Also affects: maas/1.10
   Importance: Undecided
   Status: New

** Also affects: maas/1.9
   Importance: Undecided
   Status: New

** Changed in: maas/1.10
   Status: New => Triaged

** Changed in: maas/1.9
   Status: New => Triaged

** Changed in: maas/1.10
   Importance: Undecided => High

** Changed in: maas/1.9
   Importance: Undecided => High

** Changed in: maas
Milestone: None => 2.0.0

** Changed in: maas/1.10
Milestone: None => 1.10.0

** Changed in: maas/1.9
Milestone: None => 1.9.1

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

Title:
  proxy tries ipv6 and gets 503 when no ipv6 routes

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1547640/+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 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup

[Mike Dunphy]

Thanks so much Brian, I tested it out of wily-proposed and it works great for 
me. 
Regards
-mjd

-- 
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 segfault on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1536395] Re: package maas-cluster-controller 1.8.3+bzr4053-0ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Mike Pontillo]

Ah, I just realized that you are running Xenial.

The best-supported way to run MAAS at this time is to run it on Trusty.
We won't have a Xenial compatible MAAS release until Xenial itself
releases.

** Changed in: maas
   Status: Incomplete => Invalid

** Changed in: maas (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package maas-cluster-controller 1.8.3+bzr4053-0ubuntu1 failed to
  install/upgrade: sub-processo script post-installation instalado
  retornou estado de saída de erro 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1536395/+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 1536395] Re: package maas-cluster-controller 1.8.3+bzr4053-0ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Mike Pontillo]

I found this in the dpkg terminal log:

8712 Configurando python-formencode (1.3.0-0ubuntu1) ...
8713 Configurando python-netifaces (0.10.4-0.1build2) ...
8714 Configurando python-crypto (2.6.1-6build1) ...
8715 Configurando python-ecdsa (0.13-2) ...
8716 Configurando python-paramiko (1.15.3-1) ...
8717 Configurando python-ptyprocess (0.5-1) ...
8718 Configurando python-pexpect (4.0.1-1) ...
8719 Configurando python-pyparsing (2.0.3+dfsg1-1) ...
8720 Configurando python-boto (2.38.0-1ubuntu1) ...
8721 Configurando python-simplestreams (0.1.0~bzr420-0ubuntu1) ...
8722 Configurando python-tempita (0.5.2-1build1) ...
8723 Configurando python-txtftp (0.1~bzr42-0ubuntu2) ...
8724 Configurando python-yaml (3.11-3build1) ...
8725 Configurando python-maas-provisioningserver (1.8.3+bzr4053-0ubuntu1) ...
8726 Configurando python-netaddr (0.7.18-1) ...
8727 Configurando pxelinux (3:6.03+dfsg-8ubuntu2) ...
8728 Configurando libibverbs1 (1.1.8-1.1ubuntu1) ...
8729 Configurando librdmacm1 (1.0.21-1) ...
8730 Configurando sg3-utils (1.40-0ubuntu1) ...
8731 Configurando tgt (1:1.0.62-1ubuntu1) ...
8732 Configurando maas-cluster-controller (1.8.3+bzr4053-0ubuntu1) ...
8733 Traceback (most recent call last):
8734   File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
8735 "__main__", fname, loader, pkg_name)
8736   File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
8737 exec code in run_globals
8738   File "/usr/lib/python2.7/dist-packages/provisioningserver/__main__.py", 
line 18, in 
8739 import provisioningserver.boot.install_bootloader
8740   File 
"/usr/lib/python2.7/dist-packages/provisioningserver/boot/__init__.py", line 
29, in 
8741 from provisioningserver.boot.tftppath import compose_image_path
8742   File 
"/usr/lib/python2.7/dist-packages/provisioningserver/boot/tftppath.py", line 
26, in 
8743 from provisioningserver import config
8744   File "/usr/lib/python2.7/dist-packages/provisioningserver/config.py", 
line 84, in 
8745 from formencode.validators import (
8746 ImportError: cannot import name is_validator

** Also affects: maas
   Importance: Undecided
   Status: New

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

Title:
  package maas-cluster-controller 1.8.3+bzr4053-0ubuntu1 failed to
  install/upgrade: sub-processo script post-installation instalado
  retornou estado de saída de erro 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1536395/+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 1536395] Re: package maas-cluster-controller 1.8.3+bzr4053-0ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Mike Pontillo]

It's strange that you would hit this error. We should be able to import
is_validator; I can see that formencode has been installed. Can you
paste the output of these commands into the bug (my example output shown
for comparison):

$ python -c "from formencode import validators"
$ python -c "import formencode; print(formencode.__file__)"
/usr/lib/python2.7/dist-packages/formencode/__init__.pyc
$ dpkg -S /usr/lib/python2.7/dist-packages/formencode/validators.py
python-formencode: /usr/lib/python2.7/dist-packages/formencode/validators.py
$ dpkg -S $(python -c "import formencode; 
print(formencode.__file__.replace('.pyc', '.py'))")
python-formencode: /usr/lib/python2.7/dist-packages/formencode/__init__.py

** Changed in: maas
   Status: New => Incomplete

** Changed in: maas (Ubuntu)
   Status: New => 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/1536395

Title:
  package maas-cluster-controller 1.8.3+bzr4053-0ubuntu1 failed to
  install/upgrade: sub-processo script post-installation instalado
  retornou estado de saída de erro 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1536395/+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 1522422] Re: PHP5 branch and PHP7 branch

[Mike O'Connell]

It has been added:

http://packages.ubuntu.com/xenial/php/php7.0

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

Title:
  PHP5 branch and PHP7 branch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1522422/+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

Re: [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Mike Gabriel]

Hi Serge,

On  Mo 04 Jan 2016 21:26:05 CET, Serge Hallyn wrote:

> Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):
>> Hi Serge,
>>
>> sorry for getting back to this so late.
>>
>> On  Di 08 Dez 2015 17:08:58 CET, Serge Hallyn wrote:
>>
>> > Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):
>>
>> >> today I worked on backporting available fixes for CVE-2015-1335 to LXC
>> >> 0.7.x (as found in Debian squeeze-lts).
>> >>
>> >> The patch is attached, I am still in the testing-for-regressions phase.
>> >> Can any of the LXC devs take a look at the patch and maybe see if it is
>> >> suitable for Ubuntu 12.04, as well?
>> >
>> > Hi,
>> >
>> > So the thing to look for is any unconverted "mount" calls.  It
>> > looks like the lxc_setup_fs() calls to mount_fs() are not being
>> > protected.  So the contianer admin could attack through a /proc
>> > symlink.
>>
>> Hmmm... ok...
>>
>> I just checked upstream Git and the location you refer to is not using
>> safe_mount either there [1]
>
> Huh, that's odd.  Yes those should be protected, since /proc etc in
> the container could be symlinks.  Do you mind sending a patch?

I will work on the squeeze-lts / precise patch first and test that. If  
that works well, I will forward-port the change to current HEAD.

>> Furthermore, it seems non-trivial to inform safe_mount about the root
>> path from within lxc_init.c.
>>
>> Do you have any input on the following questions?:
>>
>>o Why mount_fs() in latest HEAD still using the mount() call
>> instead of safe_mount()?
>>o How could one pipe the rootfs path into lxc_setup_fs() -> mount_fs()?
>
> You shouldn't need to - it's just '/' because you're already chrooted
> there.
>

Ok. That will make it very easy.

I get back to you with results within the month.

Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de

-- 
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 allow guest to read host
  filesystem, interfere with apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+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

Re: [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Mike Gabriel]

Hi Serge,

sorry for getting back to this so late.

On  Di 08 Dez 2015 17:08:58 CET, Serge Hallyn wrote:

> Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):

>> today I worked on backporting available fixes for CVE-2015-1335 to LXC
>> 0.7.x (as found in Debian squeeze-lts).
>>
>> The patch is attached, I am still in the testing-for-regressions phase.
>> Can any of the LXC devs take a look at the patch and maybe see if it is
>> suitable for Ubuntu 12.04, as well?
>
> Hi,
>
> So the thing to look for is any unconverted "mount" calls.  It
> looks like the lxc_setup_fs() calls to mount_fs() are not being
> protected.  So the contianer admin could attack through a /proc
> symlink.

Hmmm... ok...

I just checked upstream Git and the location you refer to is not using  
safe_mount either there [1]

Furthermore, it seems non-trivial to inform safe_mount about the root  
path from within lxc_init.c.

Do you have any input on the following questions?:

   o Why mount_fs() in latest HEAD still using the mount() call  
instead of safe_mount()?
   o How could one pipe the rootfs path into lxc_setup_fs() -> mount_fs()?

Thanks for any input.

Mike

[1] https://github.com/lxc/lxc/blob/master/src/lxc/initutils.c#L35
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de

-- 
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 allow guest to read host
  filesystem, interfere with apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+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 1331214] Re: MAAS (amttool) cannot control AMT version > 8

[Mike Pontillo]

Related is bug #1513198.

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

Title:
  MAAS (amttool) cannot control AMT version > 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1331214/+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 1524069] Re: [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes

[Mike Pontillo]

@Serge, A workaround for me is to use "hypervisor default" in  virt-
manager. I'm not sure what the equivalent is in virt-install, but maybe
using --cpu=host-model-only would be a workaround?

>From the man page:

   Expose the host CPUs configuration to the guest. This enables 
the guest to take advantage of many
   of the host CPUs features (better performance), but may cause 
issues if migrating the guest to a
   host without an identical CPU.

   --cpu host-model-only
   Expose the nearest host CPU model configuration to the guest.  
It is the best CPU which can be
   used for a guest on any of the hosts.

   Use --cpu=? to see a list of all available sub options. Complete 
details at
   

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

Title:
  [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in
  raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial
  KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel
  exception]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1524069/+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 1524069] Re: [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes

[Mike Pontillo]

On my Trusty VM with "[x] Copy host CPU configuration" checked in virt-
manager, running 'sudo modprobe -r raid6_pq && sudo modprobe raid6_pq'
is enough to reproduce the kernel exception in dmesg (though I didn't
see it print "Segmentation Fault", so that may be somewhat of a red
herring).

Here's /proc/cpuinfo on the guest:
http://paste.ubuntu.com/13868715/

And here's /proc/cpuinfo on the hypervisor host:
http://paste.ubuntu.com/13868744/

I have a separate issue (which I have not filed, because I haven't
triaged, and am not sure I can reproduce yet) that was blocking me from
creating a Xenial guest, but I can try again shortly.

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

Title:
  [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in
  raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial
  KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel
  exception]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1524069/+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 1524069] Re: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception

[Mike Pontillo]

I just tried again with two logical CPUs and the core set to "Westmere"
(I think that was the default), and didn't see the bug. So this seems
related specifically to "[x] Copy host CPU configuration" being checked.
Here's the /proc/cpuinfo from the "virtual Westmere" where it works:

http://paste.ubuntu.com/13836572/

** Also affects: kvm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes
  kernel exception

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1524069/+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 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Mike Gabriel]

Hi all,

today I worked on backporting available fixes for CVE-2015-1335 to LXC
0.7.x (as found in Debian squeeze-lts).

The patch is attached, I am still in the testing-for-regressions phase.
Can any of the LXC devs take a look at the patch and maybe see if it is
suitable for Ubuntu 12.04, as well?

Greets,
Mike (aka sunweaver at debian.org)

** Patch added: "Backport fix for CVE-2015-1335 to LXC 0.7.x (Ubuntu 12.04 / 
Debian squeeze-lts)"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+attachment/4529631/+files/CVE-2015-1335.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/1476662

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+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 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

[Mike Pontillo]

Getting closer:

http://paste.ubuntu.com/13595538/

I still don't know exactly why this is happening, but I think I can get
it fixed within a day.

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

Title:
  juju 1.25.1:  lxc units all have the same IP address - changed to
  claim_sticky_ip_address

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1519527/+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 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

[Mike Pontillo]

I can confirm that I have replicated the issue in my local MAAS test
bed.

I'm seeing behavior such as this:

$ maas admin device claim-sticky-ip-address 
node-ad58adcc-980a-11e5-a692-525400130e6f
Success.
Machine-readable output follows:
{
"macaddress_set": [
{
"mac_address": "01:02:03:04:05:07"
}
], 
"zone": {
"resource_uri": "/MAAS/api/1.0/zones/default/", 
"name": "default", 
"description": ""
}, 
"parent": "node-0f48bcc8-9263-11e5-9fc7-525400130e6f", 
"ip_addresses": [], 
"hostname": "cheap-coast.maas", 
"system_id": "node-ad58adcc-980a-11e5-a692-525400130e6f", 
"owner": "root", 
"tag_names": [], 
"resource_uri": 
"/MAAS/api/1.0/devices/node-ad58adcc-980a-11e5-a692-525400130e6f/"
}

I would expect to see some ip_addresses here, but we've got nothing.

I'm still working on the root cause.

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

Title:
  juju 1.25.1:  lxc units all have the same IP address - changed to
  claim_sticky_ip_address

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1519527/+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 1356012] Re: maas incorrectly overmanages DNS reverse zones

[Mike Pontillo]

** Also affects: maas/1.9
   Importance: Undecided
   Status: New

** Changed in: maas/1.9
   Status: New => Won't Fix

** Changed in: maas/1.9
   Importance: Undecided => Critical

** Changed in: maas/1.9
   Importance: Critical => Wishlist

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

Title:
  maas incorrectly overmanages DNS reverse zones

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1356012/+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 1356012] Re: maas incorrectly overmanages DNS reverse zones

[Mike Pontillo]

Thanks to LaMont's recent work on this for MAAS-next, we have the
opportunity to backport this fix to 1.9.0 before the codebase diverges
too much.

** Changed in: maas
Milestone: None => 1.9.0

** Also affects: maas/1.9
   Importance: Undecided
   Status: New

** Also affects: maas/trunk
   Importance: Medium
   Status: Triaged

** Changed in: maas/1.9
Milestone: None => 1.9.0

** Changed in: maas/trunk
Milestone: 1.9.0 => next

** Changed in: maas/1.9
   Status: New => Triaged

** Changed in: maas/1.9
   Importance: Undecided => High

** Changed in: maas/trunk
   Importance: Medium => High

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

Title:
  maas incorrectly overmanages DNS reverse zones

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1356012/+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 1266840] Re: maas-dns failed to install completely on Trusty

[Mike Pontillo]

As Jeff said, I believe this is fixed in MAAS 1.7.

I worked on a related race condition having to do with migrating MAAS-
managed BIND variables to the MAAS database.

If you are installing MAAS on a machine which will *not* host the MAAS
database, there is still somewhat of a race condition, in that we cannot
fully migrate the BIND configuration to the MAAS database unless the
database is up and running.

On MAAS 1.7, if you hit this situation, you can run:

sudo maas-region-admin edit_named_options --migrate-conflicting-options

This will rewrite the BIND configuration to ensure that MAAS does not
duplicate any BIND options (which would result in the symptom above:
BIND failing to start).

** Changed in: maas (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: maas
   Status: New => Fix Released

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

Title:
  maas-dns failed to install completely on Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1266840/+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 1510711] Re: if-pre-up.d/vlan should support brN.X interfaces

[Mike Pontillo]

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

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

Title:
  if-pre-up.d/vlan should support brN.X interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1510711/+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 1509414] [NEW] lxc postinst script checks available interfaces, can choose

[Mike McCracken]

Public bug reported:

The released wily image preinstalls lxc, which breaks the assumption
that lxc's preinst packaging script makes:

It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
10.0.3.0 when it was installed on whatever system was generating the
image. This conflicts with the network that eth0 gets attached to when
the image is brought up in a container, because it gets attached to the
host's lxcbr0, which is using 10.0.3.x.

This affects LXC, and should affect LXD but doesn't currently. (see #2)
The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a 
wily host:

sudo lxc-create -t ubuntu-cloud -n wily
sudo lxc-start -n wily
sudo lxc-attach -n wily
# inside container, test connectivity, eg:
apt-get update

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


** Tags: cloud-installer

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

Title:
  lxc postinst script checks available interfaces, can choose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup

[Mike Dunphy]

Unfortunately I just rolled 20 servers to 15.10 and this bug bit me big time. 
Is there a workaround or estimate when 
complete or do I need to roll back to 15.04. Is it possible to just install the 
autofs from the 15.04 distro ?

-- 
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 segfault on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+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 1468897] Re: multipath creates binding for Removable(USB) drives

[Mike Rushton]

** Tags removed: verification-done
** Tags added: verification-failed

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

Title:
  multipath creates binding for Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+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 1468897] Re: multipath creates binding for Removable(USB) drives

[Mike Rushton]

The following shows that the 0.4.9-3ubuntu7.6 version of multipath-tools
does in fact ignore USB when creating the bindings. Marking as
verification-done.

ubuntu@cameron:~$ cat /etc/multipath/bindings 
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0   5EC2A680
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC2A6E0
mpath2 1IBM IPR-0   5EC2A660
mpath3 1IBM IPR-0   5EC2A620
mpath4 1IBM IPR-0   5EC2A640
mpath5 1IBM IPR-0   5EC2A6C0
mpath6 1IBM IPR-0   5EC2A6A0
mpath7 1IBM IPR-0   5EC2A6000100
mpath8 3200049454505080f
ubuntu@cameron:~$ sudo sed -i '/^mpath8/d' /etc/multipath/bindings 
ubuntu@cameron:~$ cat /etc/multipath/bindings 
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0   5EC2A680
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC2A6E0
mpath2 1IBM IPR-0   5EC2A660
mpath3 1IBM IPR-0   5EC2A620
mpath4 1IBM IPR-0   5EC2A640
mpath5 1IBM IPR-0   5EC2A6C0
mpath6 1IBM IPR-0   5EC2A6A0
mpath7 1IBM IPR-0   5EC2A6000100
ubuntu@cameron:~$ sudo /etc/init.d/multipath-tools stop ; sudo 
/etc/init.d/multipath-tools start
 * Stopping multipath daemon multipathd
   ...done.
 * Starting multipath daemon multipathd
   ...done.
ubuntu@cameron:~$ cat /etc/multipath/bindings 
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0   5EC2A680
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC2A6E0
mpath2 1IBM IPR-0   5EC2A660
mpath3 1IBM IPR-0   5EC2A620
mpath4 1IBM IPR-0   5EC2A640
mpath5 1IBM IPR-0   5EC2A6C0
mpath6 1IBM IPR-0   5EC2A6A0
mpath7 1IBM IPR-0   5EC2A6000100

** Tags removed: verification-failed
** Tags added: verification-done

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

Title:
  multipath creates binding for Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+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 1468897] Re: multipath creates binding for Removable(USB) drives

[Mike Rushton]

Verification failed:

ubuntu@cameron:~$ apt-cache policy multipath-tools
multipath-tools:
  Installed: 0.4.9-3ubuntu7.6
  Candidate: 0.4.9-3ubuntu7.6
  Version table:
 *** 0.4.9-3ubuntu7.6 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el 
Packages
100 /var/lib/dpkg/status
 0.4.9-3ubuntu7.4 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main ppc64el 
Packages
 0.4.9-3ubuntu7 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages


sudo lsblk
NAME MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda8:01   7.5G  0 disk  
├─sda1 8:11   7.5G  0 part  
└─mpath8 (dm-10) 252:10   0   7.5G  0 mpath 
  └─mpath8-part1 (dm-12) 252:12   0   7.5G  0 part  


ubuntu@cameron:~$ cat /etc/multipath/bindings
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0   5EC2A680
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC2A6E0
mpath2 1IBM IPR-0   5EC2A660
mpath3 1IBM IPR-0   5EC2A620
mpath4 1IBM IPR-0   5EC2A640
mpath5 1IBM IPR-0   5EC2A6C0
mpath6 1IBM IPR-0   5EC2A6A0
mpath7 1IBM IPR-0   5EC2A6000100
mpath8 3200049454505080f

** Tags removed: verification-needed
** Tags added: verification-failed

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

Title:
  multipath creates binding for Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+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 1500683] Re: By default DNSSEC is enabled with automatic keys

[Mike Pontillo]

Yes, that seems to be the argument. I would like to understand why it
seems to be that many environments are set up with a forwarder that does
not support DNSSEC. (is this by choice? is it a particular vendor, or
old DNS server which does not forward the queries properly?
misconfigured firewall rules?)

There are three possible values for the BIND dnssec-validation option:
'yes', 'no', and 'auto'.

By saying "enabled with automatic keys", we just mean the default value
of "dnssec-validation auto;" in the BIND configuration file.

See also: http://users.isc.org/~jreed/dnssec-guide/dnssec-guide.html
#dnssec-validation-explained

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

Title:
  By default DNSSEC is enabled with automatic keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1500683/+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 1500683] Re: DNSSEC should be disabled in MAAS by default

[Mike Pontillo]

Adding the `bind` package. MAAS simply uses the value from the BIND
configuration files in order to determine what to configure in MAAS. So
this cannot change in MAAS unless a decision is made in BIND, or the
value is left out of the configuration file by default, allowing MAAS to
make its own decision.

** Also affects: bind (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: bind (Ubuntu)

** Also affects: bind9 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  DNSSEC should be disabled in MAAS by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1500683/+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 1319600] Re: maas-cli stack trace if .maascli.db unreadable

[Mike Pontillo]

I think the bug here is that we display an unwieldy stack trace rather
than a nice error message.

Running "sudo maas " may cause this bug to occur, since the
~/.maascli.db will be created by the root user, rather than the
currently-logged-in user.

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

Title:
  maas-cli stack trace if .maascli.db unreadable

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1319600/+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 1468897] Re: multipath creates binding for Removable(USB) drives

[Mike Rushton]

Tested multipath-tools version Installed: 0.4.9-3ubuntu7.5 from the
proposed repository in Trusty. The test shows the problem resolved.

** 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 multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1468897

Title:
  multipath creates binding for Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+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 1485785] [NEW] simplestreams in trusty ignores http 403 when downloading imag

[Mike McCracken]

Public bug reported:


a recent bug in the cloud-images service caused the metadata to have an 
incorrect path, which meant that simplestreams got a 403 when requesting an 
image. However it swallowed that error and apparently uploaded 384 bytes of 
something, possibly an error HTML page, as the new image to a user's glance 
store, when used as part of the glance-simplestreams-sync charm.

Here's an edited bit of log from http://paste.ubuntu.com/12112343/ (this
snippet starts at line 2303 in there)

First we see they have a real 20150810 image, size=258343424.

DEBUG * 08-15 06:41:20 [PID:2747] * glanceclient.common.http * curl -i -X 
GET -H 'X-Auth-Token: fe1ca44f89f24174a9ccf3418fddf9d3' -H 'Content-Type: 
application/json' -H 'User-Agent: python-glanceclient' 
http://10.16.100.108:9292/v1/images/detail?limit=20
DEBUG * 08-15 06:41:20 [PID:2747] * glanceclient.common.http * 
HTTP/1.1 200 OK
date: Sat, 15 Aug 2015 06:41:20 GMT
content-length: 3746
content-type: application/json; charset=UTF-8
x-openstack-request-id: req-req-1c273480-d084-46d9-b951-64ba5714d605

{images: [{status: active, deleted_at: null, name: 
auto-sync/ubuntu-trusty-14.04-amd64-server-20150810-disk1.img, deleted: 
false, container_format: bare, created_at: 2015-08-12T06:46:58.00, 
disk_format: qcow2, updated_at: 2015-08-12T06:47:00.00, min_disk: 
0, protected: false, id: 016346a7-8b29-4f2d-8391-e7ad85968ce0, min_ram: 
0, checksum: 9cf87eeb3c6595fc3965ccf7d9941360, owner: 
f011a026b2fc4165b99ae4740f467d1d, is_public: true, virtual_size: null, 
properties: {item_name: disk1.img, architecture: x86_64, 
version_name: 20150810, content_id: auto.sync, product_name: 
com.ubuntu.cloud:server:14.04:amd64, source_content_id: 
com.ubuntu.cloud:released:download}, size: 258343424}, 
 snip, edited out a bunch of non-ubuntu images in their glance
]}

## then we see that it got new metadata and decided to delete 0810 and
get 0813.

INFO  * 08-15 06:41:20 [PID:2747] * sstreams * 
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:15.04:arm64: 
to_add=[u'20150729'] to_remove=[]
INFO  * 08-15 06:41:20 [PID:2747] * sstreams * 
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:13.04:amd64: 
to_add=[u'20140111'] to_remove=[]
INFO  * 08-15 06:41:20 [PID:2747] * sstreams * 
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:15.04:ppc64el: 
to_add=[u'20150729'] to_remove=[]
INFO  * 08-15 06:41:20 [PID:2747] * sstreams * 
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:15.04:armhf: 
to_add=[u'20150729'] to_remove=[]
INFO  * 08-15 06:41:20 [PID:2747] * sstreams * 
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:15.04:amd64: 
to_add=[u'20150729'] to_remove=[]
INFO  * 08-15 06:41:20 [PID:2747] * sstreams * 
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:10.04:amd64: 
to_add=[u'20150427'] to_remove=[]
INFO  * 08-15 06:41:20 [PID:2747] * sstreams * 
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:14.10:arm64: 
to_add=[u'20150723'] to_remove=[]
INFO  * 08-15 06:41:20 [PID:2747] * sstreams * 
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:14.04:amd64: 
to_add=[u'20150813'] to_remove=[u'20150810']
DEBUG * 08-15 06:41:20 [PID:2747] * sstreams * getting local copy of 
http://cloud-images.ubuntu.com/releases/server/releases/trusty/release-20150813/ubuntu-14.04-server-cloudimg-amd64-disk1.img
INFO  * 08-15 06:41:20 [PID:2747] * urllib3.connectionpool * Starting new 
HTTP connection (1): cloud-images.ubuntu.com
DEBUG * 08-15 06:41:20 [PID:2747] * urllib3.connectionpool * Setting read 
timeout to object object at 0x7fc83ec93170
DEBUG * 08-15 06:41:20 [PID:2747] * urllib3.connectionpool * GET 
/releases/server/releases/trusty/release-20150813/ubuntu-14.04-server-cloudimg-amd64-disk1.img
 HTTP/1.1 403 289

## uh oh, that path is bad and we got a 403 with 289 bytes left. we
should bail here, but instead we upload to glance:


DEBUG * 08-15 06:41:20 [PID:2747] * glanceclient.common.http * curl -i -X 
POST -H 'x-image-meta-property-source_content_id: 
com.ubuntu.cloud:released:download' -H 'X-Auth-Token: 
fe1ca44f89f24174a9ccf3418fddf9d3' -H 'x-image-meta-property-version_name: 
20150813' -H 'x-image-meta-property-product_name: 
com.ubuntu.cloud:server:14.04:amd64' -H 'x-image-meta-checksum: 
f655dd7ce96dd5b76b663edcec931b8e' -H 'Transfer-Encoding: chunked' -H 
'x-image-meta-container_format: bare' -H 'x-image-meta-property-content_id: 
auto.sync' -H 'User-Agent: python-glanceclient' -H 
'x-image-meta-property-item_name: disk1.img' -H 
'x-image-meta-property-architecture: x86_64' -H 'x-image-meta-is_public: True' 
-H 'x-image-meta-size: 384' -H 'Content-Type: application/octet-stream' -H 
'x-image-meta-disk_format: qcow2' -H 'x-image-meta-name: 
auto-sync/ubuntu-trusty-14.04-amd64-server-20150813-disk1.img' -d 'open file 
'/tmp/tmpcb3szh', mode 'rb' at 0x7fc8390ac300' 
http://10.16.100.108:9292/v1/images

## note the 

[Bug 1485090] [NEW] package maas-dhcp 1.7.6+bzr3376-0ubuntu2~15.04.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100

[Mike McCracken]

Public bug reported:

package failed to install during do-release-upgrade from vivid to wily

happened immediately after https://bugs.launchpad.net/ubuntu/+source
/isc-dhcp/+bug/1485089

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: maas-dhcp 1.7.6+bzr3376-0ubuntu2~15.04.1
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.18-0ubuntu6
Architecture: amd64
Date: Fri Aug 14 12:11:32 2015
DuplicateSignature: package:maas-dhcp:1.7.6+bzr3376-0ubuntu2~15.04.1:subprocess 
new pre-removal script returned error exit status 100
ErrorMessage: subprocess new pre-removal script returned error exit status 100
InstallationDate: Installed on 2014-04-15 (485 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu1
SourcePackage: maas
Title: package maas-dhcp 1.7.6+bzr3376-0ubuntu2~15.04.1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
100
UpgradeStatus: Upgraded to wily on 2015-08-14 (0 days ago)

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


** Tags: amd64 apport-package dist-upgrade wily

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

Title:
  package maas-dhcp 1.7.6+bzr3376-0ubuntu2~15.04.1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1485090/+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 1468897] Re: multipath creates binding for Removable(USB) drives

[Mike Rushton]

Updated information. It seems the issue only comes about with USB 3.0
devices. USB 2.0 devices do not get lumped in with multipath upon
detection.

dmesg output from inserting a USB 3.0 device and then a USB 3.0 device.
Both into USB 3.0 ports:

[  223.050845] usb 4-4: new SuperSpeed USB device number 3 using xhci_hcd
[  223.069996] usb 4-4: New USB device found, idVendor=125f, idProduct=312b
[  223.07] usb 4-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  223.070004] usb 4-4: Product: ADATA USB Flash Drive
[  223.070006] usb 4-4: Manufacturer: ADATA
[  223.070009] usb 4-4: SerialNumber: 0454
[  223.070589] usb-storage 4-4:1.0: USB Mass Storage device detected
[  223.071125] scsi4 : usb-storage 4-4:1.0
[  224.071718] scsi 4:0:0:0: Direct-Access ADATAUSB Flash Drive  1.00 
PQ: 0 ANSI: 6
[  224.073117] sd 4:0:0:0: Attached scsi generic sg32 type 0
[  224.073458] sd 4:0:0:0: [sdi] 30869504 512-byte logical blocks: (15.8 
GB/14.7 GiB)
[  224.073729] sd 4:0:0:0: [sdi] Write Protect is off
[  224.073737] sd 4:0:0:0: [sdi] Mode Sense: 23 00 00 00
[  224.073992] sd 4:0:0:0: [sdi] Write cache: disabled, read cache: disabled, 
doesn't support DPO or FUA
[  224.079661]  sdi: sdi1
[  224.080909] sd 4:0:0:0: [sdi] Attached SCSI removable disk
[  224.675188] usb 3-3: new high-speed USB device number 3 using xhci_hcd
[  224.810797] usb 3-3: New USB device found, idVendor=13fe, idProduct=3600
[  224.810802] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  224.810805] usb 3-3: Product: MKNUFDPR2GB
[  224.810807] usb 3-3: Manufacturer: MUSHKIN
[  224.810810] usb 3-3: SerialNumber: 07C10403C8956553
[  224.811540] usb-storage 3-3:1.0: USB Mass Storage device detected
[  224.812218] usb-storage 3-3:1.0: Quirks match for vid 13fe pid 3600: 4000
[  224.812419] scsi5 : usb-storage 3-3:1.0
[  225.841184] scsi 5:0:0:0: Direct-Access MUSHKIN  MKNUFDPR2GB  PMAP 
PQ: 0 ANSI: 0 CCS
[  225.842314] sd 5:0:0:0: Attached scsi generic sg33 type 0
[  226.527048] sd 5:0:0:0: [sdj] 3911680 512-byte logical blocks: (2.00 GB/1.86 
GiB)
[  226.527209] sd 5:0:0:0: [sdj] Write Protect is off
[  226.527213] sd 5:0:0:0: [sdj] Mode Sense: 23 00 00 00
[  226.527363] sd 5:0:0:0: [sdj] No Caching mode page found
[  226.527442] sd 5:0:0:0: [sdj] Assuming drive cache: write through
[  226.560690]  sdj: sdj1
[  226.562590] sd 5:0:0:0: [sdj] Attached SCSI removable disk


lsblk for relevant devices:

sdi8:128  1  14.7G  0 disk  
├─sdi1 8:129  1  14.7G  0 part  
└─mpath4 (dm-8)  252:80  14.7G  0 mpath 
  └─mpath4-part1 (dm-10) 252:10   0  14.7G  0 part  
sdj8:144  1   1.9G  0 disk  
└─sdj1 8:145  1   1.9G  0 part

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

Title:
  multipath creates binding for Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+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 1413388] Re: [SRU] upgrade of MAAS removes local config for bind and breaks DNS

[Mike Pontillo]

I tested by installing bind9 on Trusty, then installing maas
1.7.6+bzr3376-0ubuntu2~14.04.1.

I verified that the forwarders were properly migrated to the MAAS
configuration, as long as at least one cluster interface was set to be
managing DNS.

The forwarders are migrated into the MAAS database, and values such as
allow-query, allow-recursion, and allow-query-cache (which MAAS had
previously always written into
/etc/bind/maas/named.conf.options.inside.maas) are now only written if
the values are not already present in /etc/bind/named.conf.options.

Hopefully this solves the issue for everyone.

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

Title:
  [SRU] upgrade of MAAS removes local config for bind and breaks DNS

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1413388/+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 1381537] Re: Dovecot version in precise too old to switch off SSLv3 protocol for poodle fix

[Mike Threesi]

OK, I hate to be so stupid, but I need some help and can't seem to
locate anyone knowledgeable so far:

In 10-ssl.conf I added:  ssl_protocols = !SSLv2 !SSLv3 (to no avail so i
think I am not patched)

Would appreciate some helpful comments / guidance please...

I did a fresh install of 12.04.5 on another machine, thinking that there
had been a patch for dovecot, but I am still getting this error, so I
assume it is not patched in 12.04.5 ?  Or how do I get the patch
installed?

This accepts the login:  `openssl s_client -connect localhost:993 -ssl3`

This gives an error:  `openssl s_client -connect localhost:465 -ssl3`
139852816377504:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl
handshake failure:s3_pkt.c:59

This too gives an error:  `openssl s_client -connect localhost:25 -ssl3`
140205816501920:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
version number:s3_pkt.c:339

So if I go to a poodle website and check, they return OK for Poodle
EXCEPT for 993 port, do you know what I am doing wrong?

BTW, these are the exact results from my long running 12.04.4 ubuntu,
and we need to stay on 12.04 for now.

Throw me a bone, please - give me some detailed instructions of how I
can fix this, thank you.  My goal is to have port 25, 587, 465, 993, etc
all !SSLv3 compliant.

Thank you

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

Title:
  Dovecot version in precise  too old to switch off SSLv3 protocol for
  poodle fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1381537/+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 1473369] Re: new mock release broke a bunch of unit tests

[Mike Fedosin]

** Also affects: python-glance-store (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: python-glance-store (Ubuntu)

** Also affects: glance-store
   Importance: Undecided
   Status: New

** Changed in: glance-store
 Assignee: (unassigned) = Mike Fedosin (mfedosin)

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

Title:
  new mock release broke a bunch of unit tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1473369/+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 1462139] Re: curtain fails with Device is busy error during unmount

[Mike Pontillo]

I tested the fix; looks good! Thanks.

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

Title:
  curtain fails with Device is busy error during unmount

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1462139/+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 1473229] [NEW] nagios-plugins-standard claims to have check_linux_raid in it, does not

[Mike Mattice]

Public bug reported:

The package description is incorrect.

Precise's version of the package had check_linux_raid in it.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nagios-plugins-standard 1.5-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
Uname: Linux 3.13.0-52-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul  9 17:02:55 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-03-14 (847 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
SourcePackage: nagios-plugins
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nagios-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  nagios-plugins-standard claims to have check_linux_raid in it, does
  not

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1473229/+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 1473228] [NEW] qemu-system-ppc requires openhackware package

[Mike Rushton]

Public bug reported:

Release: Ubuntu 14.04.2 installed on IBM Power 8 (Tuleta)
kernel: 3.16.0-43-generic
Arch: ppc64le

When trying to run qemu-system-ppc64 to create a new VM, we get the
following error:

qemu: hardware error: qemu: could not load bios image 'ppc_rom.bin'

ppc_rom.bin is located in /usr/share/qemu/ppc_rom.bin which is a link to
/usr/share/openhackware/ppc_rom.bin which gets installed from
openhackware.

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


** Tags: blocks-hwcert-server

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

Title:
  qemu-system-ppc requires openhackware package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1473228/+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 1425376] Re: Ubuntu Core provides no console login prompt if network is unavailable

[Mike Carifio]

Nevermind, it was pilot error on my part. I redid the directions and can
both log in directly and ssh via port 8022. Good to see my track record
of finding every possible way of failing remains intact...

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

Title:
  Ubuntu Core provides no console login prompt if network is unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1425376/+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 1425376] Re: Ubuntu Core provides no console login prompt if network is unavailable

[Mike Carifio]

Does the image http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-
amd64-generic.img.xz have this fix? Still can't login after spinning up
the image using kvm. Is there a workaround to login based on the kvm
directions at https://developer.ubuntu.com/en/snappy/start/? Please
advise. Thanks.

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

Title:
  Ubuntu Core provides no console login prompt if network is unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1425376/+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 1470149] [NEW] uvt-kvm wait --insecure fails on systemd-using guests

[Mike McCracken]

Public bug reported:

Using a 14.04.2 host, running a 15.04 guest, uvt-kvm wait waits forever
because systemd goes straight to runlevel 5

This is fixed in uvtool upstream by 
http://bazaar.launchpad.net/~uvtool-dev/uvtool/trunk/revision/94
and I'd like that fix to be SRU'd into Trusty.

** Affects: uvtool (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: uvtool (Ubuntu Trusty)
 Importance: Medium
 Status: Triaged

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

Title:
  uvt-kvm wait --insecure fails on systemd-using guests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1470149/+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 1037607] Re: vmbuilder completely fails on Quantal due to kernel pae detection failure

[Mike Neumann]

Bug still exists. I encountered it just now attempting to generate a
trusty image on a trusty host. Adding addpkg = linux-image-generic to
my /etc/vmbuilder.cfg file allowed the process to complete.

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

Title:
  vmbuilder completely fails on Quantal due to kernel pae detection
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1037607/+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 1468897] [NEW] multipath creates binding for Removable(USB) drives

[Mike Rushton]

Public bug reported:

On a system with a multipath configuration, multipath bindings are being
created for removable(USB) drives rendering them inaccessible as normal
removable drives.

in this case, the usb drive is detected as /dev/sdi:

# lsblk|grep -A2 sdi
sdi8:128  1  14.7G  0 disk  
├─sdi1 8:129  1  14.7G  0 part  
└─mpath4 (dm-9)  252:90  14.7G  0 mpath 
  └─mpath4-part1 (dm-10) 252:10   0  14.7G  0 part  

# cat /etc/multipath/bindings 
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0   5EC25980
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC25960
mpath2 1IBM IPR-0   5EC25940
mpath3 1IBM IPR-0   5EC25920
mpath4 1ADATA   USB Flash Drive 

Upon trying to format /dev/sdi1:

# mkfs.ext4 /dev/sdi1
mke2fs 1.42.9 (4-Feb-2014)
/dev/sdi1 is apparently in use by the system; will not make a filesystem here!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: multipath-tools 0.4.9-3ubuntu7.2
ProcVersionSignature: User Name 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11
Uname: Linux 3.16.0-41-generic ppc64le
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: ppc64el
Date: Thu Jun 25 20:44:13 2015
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: multipath-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: multipath-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug ppc64el trusty uec-images

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

Title:
  multipath creates binding for Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+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 1468897] Re: multipath creates binding for Removable(USB) drives

[Mike Rushton]

After following this post: https://www.redhat.com/archives/dm-
devel/2008-September/msg00235.html

I have prepended the following to /lib/udev/rules.d/95-multipath.rules:

#Weed out the linear map.
KERNEL==dm-*, PROGRAM==/sbin/dmsetup table -j %M -m %m, RESULT==*linear*, 
OPTIONS=last_rule

# And block devices that come from usb:
ACTION==add, KERNEL==sd*, SUBSYSTEM==usb, OPTIONS=last_rule


This prevents /dev/sdi from showing up under lsblk completely and is now 
missing as a block device completely:

$ ls /dev/sdi*
ls: cannot access /dev/sdi*: No such file or directory

I think this is some progress, but not working as intended yet.

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

Title:
  multipath creates binding for Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+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 1447167] Re: multipath-install: Installing with multipath enabled does not install multipath-tools

[Mike Rushton]

I have tried the latest curtin-common and python-curtin from the wily
repositories running on 14.04.2:

#leftyfb@maaster[0]:~$ apt-cache policy curtin-common
curtin-common:
  Installed: 0.1.0~bzr214-0ubuntu1
  Candidate: 0.1.0~bzr214-0ubuntu1
  Version table:
 *** 0.1.0~bzr214-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
 0.1.0~bzr201-0ubuntu1~14.04.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
 0.1.0~bzr126-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy python-curtin
python-curtin:
  Installed: 0.1.0~bzr214-0ubuntu1
  Candidate: 0.1.0~bzr214-0ubuntu1
  Version table:
 *** 0.1.0~bzr214-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
 0.1.0~bzr201-0ubuntu1~14.04.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
 0.1.0~bzr126-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy maas
maas:
  Installed: 1.7.5+bzr3369-0ubuntu1~trusty1
  Candidate: 1.7.5+bzr3369-0ubuntu1
  Version table:
 1.7.5+bzr3369-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
 *** 1.7.5+bzr3369-0ubuntu1~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
100 /var/lib/dpkg/status
 1.5.4+bzr2294-0ubuntu1.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1.5+bzr2252-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

The deployment never fully boots up. It never gets to a console or
allows an ssh connection. Attached is a log of the deployment and first
boot process to debug.

** Attachment added: multipath.log
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1447167/+attachment/4413932/+files/multipath.log

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

Title:
  multipath-install: Installing with multipath enabled does not install
  multipath-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1447167/+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 1371634] Re: block devices appear twice

[Mike Rushton]

I have tried the latest curtin-common and python-curtin from the wily
repositories running on 14.04.2:

#leftyfb@maaster[0]:~$ apt-cache policy curtin-common
curtin-common:
  Installed: 0.1.0~bzr214-0ubuntu1
  Candidate: 0.1.0~bzr214-0ubuntu1
  Version table:
 *** 0.1.0~bzr214-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
 0.1.0~bzr201-0ubuntu1~14.04.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
 0.1.0~bzr126-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy python-curtin
python-curtin:
  Installed: 0.1.0~bzr214-0ubuntu1
  Candidate: 0.1.0~bzr214-0ubuntu1
  Version table:
 *** 0.1.0~bzr214-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
 0.1.0~bzr201-0ubuntu1~14.04.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
 0.1.0~bzr126-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy maas
maas:
  Installed: 1.7.5+bzr3369-0ubuntu1~trusty1
  Candidate: 1.7.5+bzr3369-0ubuntu1
  Version table:
 1.7.5+bzr3369-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
 *** 1.7.5+bzr3369-0ubuntu1~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
100 /var/lib/dpkg/status
 1.5.4+bzr2294-0ubuntu1.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1.5+bzr2252-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

The deployment never fully boots up. It never gets to a console or
allows an ssh connection. Attached is a log of the deployment and first
boot process to debug.


** Attachment added: multipath.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4412768/+files/multipath.log

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

Title:
  block devices appear twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+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 1462383] [NEW] ceilometer-common with mongodb-autoreconnect.patch regression in vivid

[Mike Lloyd]

Public bug reported:

[Issue]
ceilometer 1.0.13 displays same error message as bug 1421663.

root@controller-1:~# ceilometer-dbsync
2015-06-05 07:53:55.970 8367 CRITICAL ceilometer [-] AttributeError: 'NoneType' 
object has no attribute 'find'
2015-06-05 07:53:55.970 8367 TRACE ceilometer Traceback (most recent call last):
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/bin/ceilometer-dbsync, line 10, in module
2015-06-05 07:53:55.970 8367 TRACE ceilometer sys.exit(dbsync())
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/dist-packages/ceilometer/cmd/storage.py, line 30, in dbsync
2015-06-05 07:53:55.970 8367 TRACE ceilometer 
storage.get_connection_from_config(cfg.CONF, 'metering').upgrade()
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/dist-packages/ceilometer/storage/__init__.py, line 116, in 
get_connection_from_config
2015-06-05 07:53:55.970 8367 TRACE ceilometer return _inner()
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/dist-packages/retrying.py, line 68, in wrapped_f
2015-06-05 07:53:55.970 8367 TRACE ceilometer return Retrying(*dargs, 
**dkw).call(f, *args, **kw)
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/dist-packages/retrying.py, line 229, in call
2015-06-05 07:53:55.970 8367 TRACE ceilometer raise attempt.get()
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/dist-packages/retrying.py, line 261, in get
2015-06-05 07:53:55.970 8367 TRACE ceilometer six.reraise(self.value[0], 
self.value[1], self.value[2])
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/dist-packages/retrying.py, line 217, in call
2015-06-05 07:53:55.970 8367 TRACE ceilometer attempt = Attempt(fn(*args, 
**kwargs), attempt_number, False)
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/dist-packages/ceilometer/storage/__init__.py, line 114, in 
_inner
2015-06-05 07:53:55.970 8367 TRACE ceilometer return get_connection(url, 
namespace)
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/dist-packages/ceilometer/storage/__init__.py, line 121, in 
get_connection
2015-06-05 07:53:55.970 8367 TRACE ceilometer connection_scheme = 
urlparse.urlparse(url).scheme
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/urlparse.py, line 143, in urlparse
2015-06-05 07:53:55.970 8367 TRACE ceilometer tuple = urlsplit(url, scheme, 
allow_fragments)
2015-06-05 07:53:55.970 8367 TRACE ceilometer   File 
/usr/lib/python2.7/urlparse.py, line 182, in urlsplit
2015-06-05 07:53:55.970 8367 TRACE ceilometer i = url.find(':')
2015-06-05 07:53:55.970 8367 TRACE ceilometer AttributeError: 'NoneType' object 
has no attribute 'find'
2015-06-05 07:53:55.970 8367 TRACE ceilometer

Tested against PostgreSQL 9.4.0 and MongoDB v2.6.3.

Connection string:
root@controller-1:~# cat /etc/ceilometer/ceilometer.conf |grep postgresql
backend = postgresql
connection = postgresql://ceilometer:ceilodb123@postgres-01/ceilometer

[Versioning]
root@controller-1:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=vivid
DISTRIB_DESCRIPTION=Ubuntu 15.04
root@controller-1:~# apt-cache policy ceilometer-common
ceilometer-common:
  Installed: 2015.1.0-0ubuntu1
  Candidate: 2015.1.0-0ubuntu1
  Version table:
 *** 2015.1.0-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2015.1~rc1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
root@controller-1:~# pip list | grep ceilometer
ceilometer (2015.1.0)

Bug 1421663 mentions this was fixed in ceilometer (2014.2.2-0ubuntu2)
utopic, however the issue is still present in 2015.1.0-0ubuntu1. Is this
potentially a regression?

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

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

Title:
  ceilometer-common with mongodb-autoreconnect.patch regression in vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1462383/+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 1371634] Re: block devices appear twice

[Mike Rushton]

I tried following the above workaround on the IBM Power 8 twice on new
deployments. Attached is the log.

** Attachment added: multipath.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4409977/+files/multipath.log

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

Title:
  block devices appear twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+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 1461170] [NEW] glance parses incorrectly when creating new images.

[Mike Lloyd]

Public bug reported:

This command fails:
root@controller-1:~# glance image-create --name cirros-0.3.4-x86_64 --file 
/tmp/images/cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format 
bare --visibility public --progress
usage: glance [--version] [-d] [-v] [--get-schema] [--timeout TIMEOUT]
  [--no-ssl-compression] [-f] [--os-image-url OS_IMAGE_URL]
  [--os-image-api-version OS_IMAGE_API_VERSION]
  [--profile HMAC_KEY] [-k] [--os-cert OS_CERT]
  [--cert-file OS_CERT] [--os-key OS_KEY] [--key-file OS_KEY]
  [--os-cacert ca-certificate-file] [--ca-file OS_CACERT]
  [--os-username OS_USERNAME] [--os-user-id OS_USER_ID]
  [--os-user-domain-id OS_USER_DOMAIN_ID]
  [--os-user-domain-name OS_USER_DOMAIN_NAME]
  [--os-project-id OS_PROJECT_ID]
  [--os-project-name OS_PROJECT_NAME]
  [--os-project-domain-id OS_PROJECT_DOMAIN_ID]
  [--os-project-domain-name OS_PROJECT_DOMAIN_NAME]
  [--os-password OS_PASSWORD] [--os-tenant-id OS_TENANT_ID]
  [--os-tenant-name OS_TENANT_NAME] [--os-auth-url OS_AUTH_URL]
  [--os-region-name OS_REGION_NAME]
  [--os-auth-token OS_AUTH_TOKEN]
  [--os-service-type OS_SERVICE_TYPE]
  [--os-endpoint-type OS_ENDPOINT_TYPE]
  subcommand ...
glance: error: unrecognized arguments: --name --disk-format qcow2 
--container-format bare --visibility public

This command succeeds:
root@controller-1:~# glance image-create --name cirros-0.3.4-x86_64 --file 
/tmp/images/cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format 
bare --visibility public --progress
[=] 100%
+--+--+
| Property | Value|
+--+--+
| checksum | ee1eca47dc88f4879d8a229cc70a07c6 |
| container_format | bare |
| created_at   | 2015-06-02T16:56:45Z |
| disk_format  | qcow2|
| id   | c6d64ec3-c2cc-43d0-bcfb-b1e1afd02793 |
| min_disk | 0|
| min_ram  | 0|
| name | cirros-0.3.4-x86_64  |
| owner| 8dd1052ce0204770ad22cc4e38df88cc |
| protected| False|
| size | 13287936 |
| status   | active   |
| tags | []   |
| updated_at   | 2015-06-02T16:56:47Z |
| virtual_size | None |
| visibility   | public   |
+--+--+

Glance version:
root@controller-1:~# glance --version
0.15.0

root@controller-1:~# bash --version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)

Ubuntu Version:
root@controller-1:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION=Ubuntu 14.04.2 LTS

The documentation uses  around cirros-0.3.4-x86_64 and that is causing
the command to fail.

---
Built: 2015-06-02T07:28:13 00:00
git SHA: ec9656cef3faba478bc2796034515fa60c14773d
URL: 
http://docs.openstack.org/kilo/install-guide/install/apt/content/glance-verify.html
source File: 
file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_glance-verify.xml
xml:id: glance-verify

** Affects: openstack-manuals
 Importance: Undecided
 Status: New

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


** Tags: glance

** Also affects: python-glanceclient (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  This command fails:
- glance image-create --name cirros-0.3.4-x86_64 --file 
/tmp/images/cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format 
bare --visibility public --progress
+ root@controller-1:~# glance image-create --name cirros-0.3.4-x86_64 --file 
/tmp/images/cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format 
bare --visibility public --progress
+ usage: glance [--version] [-d] [-v] [--get-schema] [--timeout TIMEOUT]
+   [--no-ssl-compression] [-f] [--os-image-url OS_IMAGE_URL]
+   [--os-image-api-version OS_IMAGE_API_VERSION]
+   [--profile HMAC_KEY] [-k] [--os-cert OS_CERT]
+   [--cert-file OS_CERT] [--os-key OS_KEY] [--key-file OS_KEY]
+   [--os-cacert ca-certificate-file] [--ca-file OS_CACERT]
+   [--os-username OS_USERNAME] [--os-user-id OS_USER_ID]
+   [--os-user-domain-id OS_USER_DOMAIN_ID]
+ 

[Bug 1450091] Re: tgt does not auto-start on Vivid

[Mike Pontillo]

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

** Changed in: tgt (Ubuntu)
 Assignee: ubuntudotcom1 (ubuntudotcom1) = (unassigned)

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

Title:
  tgt does not auto-start on Vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1450091/+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 1446878] Re: maas django app won't start ImportError: No module named apt_pkg

[Mike Pontillo]

This should have been fixed with the following commit to the packaging
branch:

https://code.launchpad.net/~mpontillo/maas/packaging-python-apt-
fix/+merge/255265

** Branch linked: lp:~mpontillo/maas/packaging-python-apt-fix

** Changed in: maas (Ubuntu)
   Status: New = Fix Committed

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

Title:
  maas django app won't start ImportError: No module named apt_pkg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1446878/+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 1446878] Re: maas django app won't start ImportError: No module named apt_pkg

[Mike Pontillo]

I thought we recently fixed this. Either the version under test doesn't
have the fix yet, or we missed the fix for some subset of MAAS packages.
I will check tomorrow.

** Changed in: maas (Ubuntu)
 Assignee: (unassigned) = Mike Pontillo (mpontillo)

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

Title:
  maas django app won't start ImportError: No module named apt_pkg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1446878/+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 823096] Re: package freeradius-mysql 2.1.8 dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Mike Bryant]

This also affects freeradius-postgresql

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

Title:
  package freeradius-mysql 2.1.8 dfsg-1ubuntu1 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/freeradius/+bug/823096/+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 1246236] Re: pxe boot from maas fails due to time out

[Mike Pontillo]

I hit this problem today, and it turned out to be a non-MAAS bug.

I was trying to configure a Trusty host with VMware Workstation *and*
LXCs sharing the same network.

It turns out that the combination of VMware plus Linux bridge interfaces
have a bug: if I set up the VM network to be bridged to br0, I can ping
hosts on the local network, and I can ping the Linux hypervisor, and I
can ping any of the LXCs. I can even DHCP from the LXCs. But I *can't*
establish any TCP connections to the LXCs from the VMware guest.

My current theory is that somehow the bridge interface is causing
packets sentto the LXC from the VMware guest to be discarded at a low
level, rather than sent up the stack. I couldn't find any IP Because
when I configure VMware to bridge to a physical interface rather than a
virtual bridge, it works. Until I disconnect the physical interface.

So the bottom line for me was:
(1) Have VMware bridge to the physical interface (in my case, it was eth0.100, 
a VLAN interface) if you want to use bridged mode
(2) Use a host-only network (without DHCP, so MAAS can do its thing!) if you 
want to develop in isolation, without sharing the network with the local LAN
 - Do NOT bridge VMware to a bridge created with 'brctl' or similar!

I added the VMware bridge interface (vmnet1) to the br0 interface I'm
using for my MAAS LXC, which may get me the best of both. I'll continue
to test this configuration.

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

Title:
  pxe boot from maas fails due to time out

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1246236/+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 1044559] Re: apt-get remove maas --purge while maas is running prevents full database purge

[Mike Pontillo]

I attempted to fix this, but haven't gotten anywhere. I am seeing the
following errors:

Removing maas-region-controller (1.8.0~beta2+bzr3777-0ubuntu1) ...
 * Stopping web server apache2  
 * 
dbconfig-common: dumping pgsql database maasdb to 
/var/tmp/maas-region-controller.maasdb.2015-04-06-23.29.pgsql.AhZK0m.
dbconfig-common: dropping pgsql database maasdb.
dropping database maasdb: does not exist.
dbconfig-common: revoking privileges for user maas on maasdb.
revoking access to database maasdb from maas@localhost: failed.

However, I found a workaround:

$ sudo -u postgres dropdb maasdb

You can verify that the maasdb database has been dropped by executing:

$ sudo -u postgres psql

I tried adding sudo -u postgres dropdb maasdb to the postrm packaging
script for maas-region-controller, but that didn't make a difference.

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

Title:
  apt-get remove maas --purge while maas is running prevents full
  database purge

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1044559/+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 1044559] Re: apt-get remove maas --purge while maas is running prevents full database purge

[Mike Pontillo]

I think this is a bug with dbconfig-common. It looks like Zbbix is still
having this issue:

https://support.zabbix.com/browse/ZBXNEXT-2587

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

Title:
  apt-get remove maas --purge while maas is running prevents full
  database purge

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1044559/+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 1044559] Re: apt-get remove maas --purge while maas is running prevents full database purge

[Mike Pontillo]

** Branch linked: lp:~mpontillo/maas/packaging-fix-db-purge

** Changed in: maas
   Importance: Medium = High

** Changed in: maas
 Assignee: (unassigned) = Mike Pontillo (mpontillo)

** Changed in: maas
Milestone: None = 1.8.0

** Changed in: maas
   Status: New = Triaged

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

Title:
  apt-get remove maas --purge while maas is running prevents full
  database purge

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1044559/+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 1044559] Re: apt-get remove maas --purge while maas is running prevents full database purge

[Mike Pontillo]

I just saw this one again. I found a relevant discussion here:

https://lists.alioth.debian.org/pipermail/dbconfig-common-
devel/2006-September/000627.html

Here's the relevant quote from Sean Finney (the maintainer of dbconfig-
common):


i can reproduce your problem... looking in my postgres logs i see:

ERROR:  database zabbix is being accessed by other users
ERROR:  role zabbix cannot be dropped because some objects depend on
it

i think this is because the zabbix server has the datbase open while the
removal code is running in the prerm script.   if you manually stop the
zabbix server before purging i think you'll see what i'm talking about.

as for how to workaround this... you could manually stop the server
before calling dbc_go when $1 is set to remove, or you could call the
dbconfig hooks after the #DEBHELPER# macro.

since this could be a general problem with other pgsql+daemon packages,
i'd appreciate suggestions for how to mention this in documentation,
assuming this solves your problem :)


Reply from Michael Ablassmeier:


yes, moving the stanza in prerm above the dbconfig-common call works
nicely and the package successfully purges its database setup. Thanks
for your time! (having a short note somewhere in the Docs might be
helpful since i've discovered the same problem for the mysql part of the
package, even tho mysql doesnt care about it that much)


** Changed in: maas
   Importance: Undecided = Medium

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

Title:
  apt-get remove maas --purge while maas is running prevents full
  database purge

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1044559/+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 1252768] Re: removing (including with --purge) fails on pg script

[Mike Pontillo]

*** This bug is a duplicate of bug 1044559 ***
https://bugs.launchpad.net/bugs/1044559

Note: If you try to purge the database, it actually fails in this case,
and the database is left intact.

See comments on bug #1044559.

** Also affects: maas
   Importance: Undecided
   Status: New

** Changed in: maas
   Importance: Undecided = High

** This bug has been marked a duplicate of bug 1044559
   apt-get remove maas --purge while maas is running prevents full database 
purge

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

Title:
  removing (including with --purge) fails on pg script

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1252768/+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 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer

[Mike]

Thank you for the suggestions Gary. I realized that my problem is caused
by the router firmware. Basically, they introduced loopback blocking and
I couldn't connect from the same network even using the external IP.

-- 
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/bugs/708493

Title:
  Can't login anymore: Read from socket failed: Connection reset by peer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/708493/+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 1044559] Re: apt-get remove maas --purge while maas is running prevents full database purge

[Mike Pontillo]

I just saw this exact behavior while using a 1.8.0 development package
on Trusty. Not sure what the correct process to reopen a bug is, but I
think this either wasn't fully fixed, or there has been a regression.

** Also affects: maas
   Importance: Undecided
   Status: New

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

Title:
  apt-get remove maas --purge while maas is running prevents full
  database purge

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1044559/+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 1431766] [NEW] package cinder-volume 1:2014.2.1-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

[Mike Stotko]

Public bug reported:

got this error while installing packages through software updater

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: cinder-volume 1:2014.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
Date: Fri Mar 13 10:43:53 2015
DuplicateSignature: package:cinder-volume:1:2014.2.1-0ubuntu1:subprocess new 
pre-removal script returned error exit status 5
ErrorMessage: subprocess new pre-removal script returned error exit status 5
InstallationDate: Installed on 2015-01-24 (48 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: cinder
Title: package cinder-volume 1:2014.2.1-0ubuntu1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 5
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: cinder (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 cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1431766

Title:
  package cinder-volume 1:2014.2.1-0ubuntu1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1431766/+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 1421377] Re: MAAS failed to start recurs if postgresql is stopped

[Mike Pontillo]

*** This bug is a duplicate of bug 1428647 ***
https://bugs.launchpad.net/bugs/1428647

** This bug has been marked a duplicate of bug 1428647
   regiond service crashes with the database system is starting up

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

Title:
  MAAS failed to start recurs if postgresql is stopped

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1421377/+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 1028718] Re: nova volumes are inappropriately clingy for ceph and similar drivers

[Mike Perez]

** Tags removed: canonistack rbd volume
** Tags added: drivers

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

Title:
  nova volumes are inappropriately clingy for ceph and similar drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1028718/+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 1423613] Re: maas needs to support systemd for Ubuntu = 15.04

[Mike Pontillo]

** Changed in: maas
 Assignee: (unassigned) = Mike Pontillo (mpontillo)

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

Title:
  maas needs to support systemd for Ubuntu = 15.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1423613/+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 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer

[Mike]

Hello,
Not sure it is the same problem here, but I cannot connect to my machine if go 
through NAT.
If I connect directly from LAN everything works, but if I use the external IP, 
then I get connection reset after debug1: SSH2_MSG_KEXINIT sent.

Client and server is the same machine. I tried to set MTU to 1400 and
400 with no effect, also changed the net.ipv4.tcp_rmem setting and tried
different cipher algorithms with no luck.

Linux 3.16.0-31-generic #41-Ubuntu
Ubuntu 14.10

-- 
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/bugs/708493

Title:
  Can't login anymore: Read from socket failed: Connection reset by peer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/708493/+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

Re: [Bug 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer

[Mike]

Thanks, but a specific client is not an option. I need to connect with any
client from different systems. The flow I described is for problem
isolation only. Putty cannot connect either.

On Fri Feb 20 2015 at 18:31:15 Gary Salisbury 708...@bugs.launchpad.net
wrote:

 Use dbclient ...

 On 20 February 2015 at 19:07, Mike smart...@gmail.com wrote:

  Hello,
  Not sure it is the same problem here, but I cannot connect to my machine
  if go through NAT.
 ...

-- 
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/bugs/708493

Title:
  Can't login anymore: Read from socket failed: Connection reset by peer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/708493/+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 1421377] [NEW] MAAS failed to start recurs if postgresql is stopped

[Mike Pontillo]

Public bug reported:

This is using the MAAS 1.8 experimental branch.

A race condition is possible in which a persistent exception is thrown
when hitting http://server/MAAS, if maas-regiond starts before
postgresql. (that is, even if you start postgresql, the MAAS web
interface never recovers.)

== Exception seen on the web page ==

MAAS failed to start

Traceback (most recent call last):
  File /usr/lib/python2.7/threading.py, line 783, in __bootstrap
self.__bootstrap_inner()
  File /usr/lib/python2.7/threading.py, line 810, in __bootstrap_inner
self.run()
  File /usr/lib/python2.7/threading.py, line 763, in run
self.__target(*self.__args, **self.__kwargs)
--- exception caught here ---
  File /usr/lib/python2.7/dist-packages/twisted/python/threadpool.py, line 
191, in _worker
result = context.call(ctx, function, *args, **kwargs)
  File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 118, 
in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 81, 
in callWithContext
return func(*args,**kw)
  File /usr/lib/python2.7/dist-packages/maasserver/webapp.py, line 83, in 
prepareApplication
start_up.start_up()
  File /usr/lib/python2.7/dist-packages/maasserver/start_up.py, line 48, in 
start_up
security.get_shared_secret()
  File /usr/lib/python2.7/dist-packages/provisioningserver/utils/twisted.py, 
line 113, in wrapper
return func_in_reactor(*args, **kwargs).wait(timeout)
  File /usr/lib/python2.7/dist-packages/crochet/_eventloop.py, line 219, in 
wait
result.raiseException()
  File /usr/lib/python2.7/dist-packages/twisted/python/threadpool.py, line 
191, in _worker
result = context.call(ctx, function, *args, **kwargs)
  File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 118, 
in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 81, 
in callWithContext
return func(*args,**kw)
  File /usr/lib/python2.7/dist-packages/provisioningserver/utils/twisted.py, 
line 148, in wrapper
return func(*args, **kwargs)
  File /usr/lib/python2.7/dist-packages/maasserver/utils/async.py, line 164, 
in call_within_transaction
return func_outside_txn(*args, **kwargs)
  File /usr/lib/python2.7/dist-packages/maasserver/utils/orm.py, line 216, in 
retrier
return func(*args, **kwargs)
  File /usr/lib/python2.7/dist-packages/django/db/transaction.py, line 338, 
in inner
with self:
  File /usr/lib/python2.7/dist-packages/django/db/transaction.py, line 237, 
in __enter__
if not connection.get_autocommit():
  File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, line 
324, in get_autocommit
self.ensure_connection()
  File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, line 
124, in ensure_connection
self.connect()
  File /usr/lib/python2.7/dist-packages/django/db/utils.py, line 99, in 
__exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
  File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, line 
124, in ensure_connection
self.connect()
  File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, line 
112, in connect
self.connection = self.get_new_connection(conn_params)
  File 
/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py,
 line 116, in get_new_connection
return Database.connect(**conn_params)
  File /usr/lib/python2.7/dist-packages/psycopg2/__init__.py, line 179, in 
connect
connection_factory=connection_factory, async=async)
django.db.utils.OperationalError: could not connect to server: Connection 
refused
Is the server running on host localhost (127.0.0.1) and accepting
TCP/IP connections on port 5432?


== Steps to Reproduce ==

$ sudo service postgresql stop
 * Stopping PostgreSQL 9.3 database server  
[ OK ] 

$ sudo service maas-clusterd stop
maas-clusterd stop/waiting

$ sudo service maas-regiond stop
maas-regiond stop/waiting

$ sudo service maas-regiond start
maas-regiond start/running, process 10964

(then hit the MAAS web page)

(Note: this was seen upon system boot.)

== Workaround ==

$ sudo service maas-clusterd restart

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

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

Title:
  MAAS failed to start recurs if postgresql is stopped

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

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

[Bug 1421377] Re: MAAS failed to start recurs if postgresql is stopped

[Mike Pontillo]

** Description changed:

  This is using the MAAS 1.8 experimental branch.
  
  A race condition is possible in which a persistent exception is thrown
  when hitting http://server/MAAS, if maas-regiond starts before
  postgresql. (that is, even if you start postgresql, the MAAS web
  interface never recovers.)
  
  == Exception seen on the web page ==
  
  MAAS failed to start
  
  Traceback (most recent call last):
-   File /usr/lib/python2.7/threading.py, line 783, in __bootstrap
- self.__bootstrap_inner()
-   File /usr/lib/python2.7/threading.py, line 810, in __bootstrap_inner
- self.run()
-   File /usr/lib/python2.7/threading.py, line 763, in run
- self.__target(*self.__args, **self.__kwargs)
+   File /usr/lib/python2.7/threading.py, line 783, in __bootstrap
+ self.__bootstrap_inner()
+   File /usr/lib/python2.7/threading.py, line 810, in __bootstrap_inner
+ self.run()
+   File /usr/lib/python2.7/threading.py, line 763, in run
+ self.__target(*self.__args, **self.__kwargs)
  --- exception caught here ---
-   File /usr/lib/python2.7/dist-packages/twisted/python/threadpool.py, line 
191, in _worker
- result = context.call(ctx, function, *args, **kwargs)
-   File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 
118, in callWithContext
- return self.currentContext().callWithContext(ctx, func, *args, **kw)
-   File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 81, 
in callWithContext
- return func(*args,**kw)
-   File /usr/lib/python2.7/dist-packages/maasserver/webapp.py, line 83, in 
prepareApplication
- start_up.start_up()
-   File /usr/lib/python2.7/dist-packages/maasserver/start_up.py, line 48, in 
start_up
- security.get_shared_secret()
-   File 
/usr/lib/python2.7/dist-packages/provisioningserver/utils/twisted.py, line 
113, in wrapper
- return func_in_reactor(*args, **kwargs).wait(timeout)
-   File /usr/lib/python2.7/dist-packages/crochet/_eventloop.py, line 219, in 
wait
- result.raiseException()
-   File /usr/lib/python2.7/dist-packages/twisted/python/threadpool.py, line 
191, in _worker
- result = context.call(ctx, function, *args, **kwargs)
-   File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 
118, in callWithContext
- return self.currentContext().callWithContext(ctx, func, *args, **kw)
-   File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 81, 
in callWithContext
- return func(*args,**kw)
-   File 
/usr/lib/python2.7/dist-packages/provisioningserver/utils/twisted.py, line 
148, in wrapper
- return func(*args, **kwargs)
-   File /usr/lib/python2.7/dist-packages/maasserver/utils/async.py, line 
164, in call_within_transaction
- return func_outside_txn(*args, **kwargs)
-   File /usr/lib/python2.7/dist-packages/maasserver/utils/orm.py, line 216, 
in retrier
- return func(*args, **kwargs)
-   File /usr/lib/python2.7/dist-packages/django/db/transaction.py, line 338, 
in inner
- with self:
-   File /usr/lib/python2.7/dist-packages/django/db/transaction.py, line 237, 
in __enter__
- if not connection.get_autocommit():
-   File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, 
line 324, in get_autocommit
- self.ensure_connection()
-   File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, 
line 124, in ensure_connection
- self.connect()
-   File /usr/lib/python2.7/dist-packages/django/db/utils.py, line 99, in 
__exit__
- six.reraise(dj_exc_type, dj_exc_value, traceback)
-   File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, 
line 124, in ensure_connection
- self.connect()
-   File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, 
line 112, in connect
- self.connection = self.get_new_connection(conn_params)
-   File 
/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py,
 line 116, in get_new_connection
- return Database.connect(**conn_params)
-   File /usr/lib/python2.7/dist-packages/psycopg2/__init__.py, line 179, in 
connect
- connection_factory=connection_factory, async=async)
+   File /usr/lib/python2.7/dist-packages/twisted/python/threadpool.py, line 
191, in _worker
+ result = context.call(ctx, function, *args, **kwargs)
+   File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 
118, in callWithContext
+ return self.currentContext().callWithContext(ctx, func, *args, **kw)
+   File /usr/lib/python2.7/dist-packages/twisted/python/context.py, line 81, 
in callWithContext
+ return func(*args,**kw)
+   File /usr/lib/python2.7/dist-packages/maasserver/webapp.py, line 83, in 
prepareApplication
+ start_up.start_up()
+   File /usr/lib/python2.7/dist-packages/maasserver/start_up.py, line 48, in 
start_up
+ security.get_shared_secret()
+   File 
/usr/lib/python2.7/dist-packages/provisioningserver/utils/twisted.py, line 
113, in wrapper
+ return func_in_reactor(*args, **kwargs).wait(timeout)
+  

[Bug 1368815] Re: qemu-img convert intermittently corrupts output images

[Mike Perez]

** Changed in: cinder
   Status: In Progress = Triaged

** Changed in: cinder
 Assignee: Tony Breeds (o-tony) = (unassigned)

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

Title:
  qemu-img convert intermittently corrupts output images

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1368815/+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 1313935] Re: tenant is required for quota-update but not for quota-show

[Mike Perez]

** Changed in: cinder
Milestone: kilo-2 = None

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

Title:
  tenant is required for quota-update but not for quota-show

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1313935/+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 1313935] Re: tenant is required for quota-update but not for quota-show

[Mike Perez]

** Tags added: low-hanging-fruit

** Changed in: cinder
 Assignee: Thang Pham (thang-pham) = (unassigned)

** Changed in: cinder
Milestone: kilo-1 = kilo-2

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

Title:
  tenant is required for quota-update but not for quota-show

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1313935/+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 1381768] Re: AttributeError: 'module' object has no attribute 'LDAP_CONTROL_PAGE_OID' with python-ldap 2.4

[Mike Dorman]

The above patch is what I'm running locally against Icehouse.  It does
not seem that complicated, unless I am missing something major.  I did
briefly look at the cherry-pick, and that is quite a bit different.  The
the above is working well for us.

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

Title:
  AttributeError: 'module' object has no attribute
  'LDAP_CONTROL_PAGE_OID' with python-ldap 2.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1381768/+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 1313935] Re: tenant is required for quota-update but not for quota-show

[Mike Perez]

** Changed in: cinder
Milestone: None = kilo-1

** Changed in: cinder
   Status: New = Triaged

** Changed in: cinder
   Importance: Undecided = Medium

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

Title:
  tenant is required for quota-update but not for quota-show

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1313935/+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 1252467] Re: /etc/cron.d/awstats: wrong user for cron job

[Mike Robinson]

Either running the cron job as root or allowing www-data to read the
apache log files are bad ideas. Instead you want to create a new user
and add it to the www-data and adm groups and make the cron job execute
as that user. I called mine awstats:

useradd awstats  usermod -a -G www-data awstats  usermod -a -G adm
awstats

Seems to work like a charm.

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

Title:
  /etc/cron.d/awstats: wrong user for cron job

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1252467/+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 451314] Re: [SRU] PHP 5.2.10 zlib bug remains for 32bit

[Mike]

This bug still remains 6 months later. I just wasted 2 days trying to
figure out why this package I was using wasn't working. Please fix this
for 32-bit users.

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

Title:
  [SRU] PHP 5.2.10 zlib bug remains for 32bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/451314/+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 1381768] Re: AttributeError: 'module' object has no attribute 'LDAP_CONTROL_PAGE_OID' with python-ldap 2.4

[Mike Dorman]

+1 on would like this backported to Icehouse.

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

Title:
  AttributeError: 'module' object has no attribute
  'LDAP_CONTROL_PAGE_OID' with python-ldap 2.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1381768/+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 1387002] [NEW] typo in maas-region-controller.postrm stops remove/purge from correctly calling dbconfig

[Mike McCracken]

Public bug reported:

line 9 of maas-region-controller.postrm tests for the existence of '/etc
/dbconfig-common/maas.conf', which will not exist. the file that gets
created is instead maas-region-controller.conf. since that test is never
true, the call to dbc_go to do the postrm.pgsql stuff never happens.

This appears to contribute to some flakiness involving purging and
reinstalling maas.

On one server that I'm currently having difficulty with, I had a /etc
/dbconfig-common/maas-region-controller.conf that was two months (and
several maas versions) old, despite having purged several times.

I think this is related to the error messages I was seeing when purging,
including errors about wrong password for user maas. The
local_settings.py I saw had a password of 'maas', but that .conf file
had a different password.

Unfortunately, while this appears to be a legitimate typo bug, manually
fixing it and re-running the purge did not fix my problems:

Setting up maas-region-controller (1.7.0~beta8+bzr3273-0ubuntu1~trusty1) ...
dpkg: error processing package maas-region-controller (--configure):
 subprocess installed post-installation script returned error exit status 10

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


** Tags: cloud-installer

** Description changed:

- 
- line 9 of maas-region-controller.postrm tests for the existence of 
'/etc/dbconfig-common/maas.conf', which will not exist. the file that gets 
created is instead maas-region-controller.conf. since that test is never true, 
the call to dbc_go to do the postrm.pgsql stuff never happens.
+ line 9 of maas-region-controller.postrm tests for the existence of '/etc
+ /dbconfig-common/maas.conf', which will not exist. the file that gets
+ created is instead maas-region-controller.conf. since that test is never
+ true, the call to dbc_go to do the postrm.pgsql stuff never happens.
  
  This appears to contribute to some flakiness involving purging and
  reinstalling maas.
  
  On one server that I'm currently having difficulty with, I had a /etc
  /dbconfig-common/maas-region-controller.conf that was two months (and
  several maas versions) old, despite having purged several times.
  
  I think this is related to the error messages I was seeing when purging,
  including errors about wrong password for user maas. The
  local_settings.py I saw had a password of 'maas', but that .conf file
  had a different password.
+ 
+ Unfortunately, while this appears to be a legitimate typo bug, manually
+ fixing it and re-running the purge did not fix my problems.

** Description changed:

  line 9 of maas-region-controller.postrm tests for the existence of '/etc
  /dbconfig-common/maas.conf', which will not exist. the file that gets
  created is instead maas-region-controller.conf. since that test is never
  true, the call to dbc_go to do the postrm.pgsql stuff never happens.
  
  This appears to contribute to some flakiness involving purging and
  reinstalling maas.
  
  On one server that I'm currently having difficulty with, I had a /etc
  /dbconfig-common/maas-region-controller.conf that was two months (and
  several maas versions) old, despite having purged several times.
  
  I think this is related to the error messages I was seeing when purging,
  including errors about wrong password for user maas. The
  local_settings.py I saw had a password of 'maas', but that .conf file
  had a different password.
  
  Unfortunately, while this appears to be a legitimate typo bug, manually
- fixing it and re-running the purge did not fix my problems.
+ fixing it and re-running the purge did not fix my problems:
+ 
+ Setting up maas-region-controller (1.7.0~beta8+bzr3273-0ubuntu1~trusty1) ...
+ dpkg: error processing package maas-region-controller (--configure):
+  subprocess installed post-installation script returned error exit status 10

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

Title:
  typo in maas-region-controller.postrm stops remove/purge from
  correctly calling dbconfig

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1387002/+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 1379201] Re: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build

[Mike Heald]

Same error here, seemed to be fine on -69, but doesn't build on -70.

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

Title:
  openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1379201/+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 1379201] Re: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build

[Mike Heald]

he signature of ip_select_ident changed from -69 to -70.

It went from (struct sk_buff *skb, struct dst_entry *dst, struct sock
*sk) to (struct sk_buff *skb, struct sock *sk, int segs).

Unfortunately I don't know enough about openvswitch internals to change
the call, but the calls are made in datapath/tunnel.c starting line
1303.

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

Title:
  openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1379201/+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 1379201] Re: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build

[Mike Heald]

The backported patch that caused this was
https://lkml.org/lkml/2014/8/8/861

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

Title:
  openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1379201/+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 1371657] [NEW] package spamassassin 3.4.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Mike Greaves]

Public bug reported:

Our configuration files may be obsolete.
Also there is a warning about file permissions in /var/lib/spamassassin (?) 
that I haven't checked yet.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: spamassassin 3.4.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
Date: Fri Sep 19 11:03:40 2014
DuplicateSignature: package:spamassassin:3.4.0-1ubuntu1:subprocess installed 
post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2012-12-11 (647 days ago)
InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 
(20121017.2)
PackageArchitecture: all
SourcePackage: spamassassin
Title: package spamassassin 3.4.0-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
UpgradeStatus: Upgraded to trusty on 2014-09-19 (0 days ago)
mtime.conffile..etc.default.spamassassin: 2014-02-27T15:00:48.388069
mtime.conffile..etc.spamassassin.init.pre: 2014-05-16T14:53:54.726876
mtime.conffile..etc.spamassassin.local.cf: 2014-05-16T14:53:54.742876

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


** Tags: amd64 apport-package dist-upgrade trusty

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

Title:
  package spamassassin 3.4.0-1ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1371657/+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 1346528] Re: maas-dhcp fails to install if isc-dhcp-server is not yet fully installed

[Mike McCracken]

FWIW, this happened again just now with an earlier (non PPA I guess)
version of maas-dhcp:

Setting up isc-dhcp-server (4.2.4-7ubuntu12) ...
isc-dhcp-server start/running, process 11190
isc-dhcp-server6 stop/pre-start, process 11233
Setting up maas-dhcp (1.5.2+bzr2282-0ubuntu0.2) ...
stop: Unknown instance: 
invoke-rc.d: initscript isc-dhcp-server, action stop failed.
dpkg: error processing package maas-dhcp (--configure):
 subprocess installed post-installation script returned error exit status 1

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

Title:
  maas-dhcp fails to install if isc-dhcp-server is not yet fully
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346528/+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 1307473] Re: guest hang due to missing clock interrupt

[Mike Lowe]

I need to amend comment #39, moving from 3.13.0-30  to 3.13.0-27 did not
eliminate the problem.  It would seem that it takes a couple of hours
following a reboot for the symptoms to manifest with 3.13.0-27.

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

Title:
  guest hang due to missing clock interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1307473/+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 1307473] Re: guest hang due to missing clock interrupt

[Mike Lowe]

I believe I have the same problem, place a guest under any amount of
load, let's say 'yum upgrade' and the network stack goes out to lunch
for 1-5 seconds.  Here is a sample of the ping statistics (host to
guest) from doing such an operation on a 3.13.0-30.55 kernel:

213 packets transmitted, 213 received, 0% packet loss, time 211998ms
rtt min/avg/max/mdev = 0.136/106.283/2651.359/428.403 ms, pipe 3

And a 3.11.0-19.33 kernel:

62 packets transmitted, 62 received, 0% packet loss, time 61074ms
rtt min/avg/max/mdev = 0.189/0.434/1.987/0.228 ms

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

Title:
  guest hang due to missing clock interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1307473/+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 1307473] Re: guest hang due to missing clock interrupt

[Mike Lowe]

I can confirm that rolling back to 3.13.0-27 from 3.13.0-30 alleviated
my symptoms.

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

Title:
  guest hang due to missing clock interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1307473/+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 1340983] [NEW] GlanceMirror class does not expose progress update callbacks

[Mike McCracken]

Public bug reported:


The GlanceMirror class has no callback to provide progress updates on
image downloads. OS images are often large enough (and you may be
syncing several images) that this presents a serious UX problem during
which a user (or client program) of simplestreams will not be able to
tell that anything is happening.

The attached diff exposes progress update callbacks with a minimum of
changes to existing program logic. The GlanceMirror class gets a basic
callback, and calling code is expected to handle figuring out what
images will be downloaded and their size before calling
GlanceMirror.sync(). In order to help with this, a separate class
ItemInfoDryRunMirror is added, to make use of the same filter logic
that GlanceMirror will use but instead just collect a list of images
to download and their size.

Since this is provided as optional keyword arguments, existing users
will not be affected.

[Test Case]

From the source tree top directory,

PYTHONPATH=. tools/sstream-mirror-glance --max=1 -v -v -v --output-dir \
images/ --cloud-name test_cloud --content-id test_content \
--keyring /usr/share/keyrings/ubuntu-cloudimage-keyring.gpg \
http://cloud-images.ubuntu.com/releases/ streams/v1/index.json

And verify that it prints status updates to stdout. The
sstream-mirror-glance tool has been updated to use the new api in
GlanceMirror.

[Regression Potential]

This has limited regression potential, because the new functionality
is provided as optional arguments. If anything is running the
sstream-mirror-glance script and parsing its output, that may break,
but that seems very unlikely because that script does not currently
produce anything useful to parse.

** Affects: simplestreams
 Importance: Undecided
 Status: New

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

** Also affects: simplestreams (Ubuntu)
   Importance: Undecided
   Status: New

** Branch linked: lp:~mikemc/simplestreams/glance-extra-progress

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

Title:
  GlanceMirror class does not expose progress update callbacks

To manage notifications about this bug go to:
https://bugs.launchpad.net/simplestreams/+bug/1340983/+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 1339842] [NEW] GlanceMirror item filters are hardcoded

[Mike McCracken]

Public bug reported:


The GlanceMirror class has a hard-coded filter for items to be
downloaded. 

Anyone using it directly or via the script in
tools/sstream-mirror-glance to load images into an openstack cloud
will end up with a large number of images, at least one for each of
the available release series, and only x86_64 or amd64.

It is likely that users will want to be able to limit the images they
download to just one release, and may want to be able to download
images for other architectures, such as arm*.

The uploaded package simply exposes the existing filter mechanism as a
config option, using the previous hardcoded values as defaults.

This config option is used (currently it is just ignored by the
published simplestreams code) in an charm that is released on the
charm store for trusty, 'glance-simplestreams-sync'. Users of
OpenStack on Trusty are likely to want the option to control image
downloads via that charm.

[Test Case]

In an openstack cloud, with proper openstack env vars (OS_USERNAME,
OS_PASSWORD, OS_REGION etc), run the sstream-mirror-glance tool to
download images locally:

from the source tree top directory,

PYTHONPATH=. tools/sstream-mirror-glance --max=1 -v -v -v --output-dir \
images/ --cloud-name test_cloud --content-id test_content \
--keyring /usr/share/keyrings/ubuntu-cloudimage-keyring.gpg \
http://cloud-images.ubuntu.com/releases/ streams/v1/index.json

verify that it downloads many images. This may take a while.  If you
like, you can just check that it will download an image for an old
series like raring or quantal.

Clean up after it by removing the images/ directory.

Then with the update applied, from the source tree top dir:

PYTHONPATH=. tools/sstream-mirror-glance --max=1 -v -v -v --output-dir \
images/ --cloud-name test_cloud --content-id test_content \
--keyring /usr/share/keyrings/ubuntu-cloudimage-keyring.gpg \
--item-filter=release=trusty --item-filter=arch=arm64 \
http://cloud-images.ubuntu.com/releases/ streams/v1/index.json

and verify that it downloads only one matching image, trusty on arm64.

[Regression Potential]

This has very limited regression potential, because anyone relying on
the existing behavior will still get it because the previous behavior
is retained via defaults.

** Affects: simplestreams
 Importance: Undecided
 Status: Fix Committed

** Affects: simplestreams (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: cloud-installer

** Also affects: simplestreams
   Importance: Undecided
   Status: New

** Changed in: simplestreams
   Status: New = Fix Committed

** Branch linked: lp:~mikemc/simplestreams/add-filters-glance

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

Title:
  GlanceMirror item filters are hardcoded

To manage notifications about this bug go to:
https://bugs.launchpad.net/simplestreams/+bug/1339842/+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 281882] Re: ssh hangs in initial handshaking when using IPv6

[Mike Bordignon]

Update: it works if I change the cipher (to blowfish, in this instance).
Doesn't work using aes128.

-- 
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/bugs/281882

Title:
  ssh hangs in initial handshaking when using IPv6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/281882/+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 281882] Re: ssh hangs in initial handshaking when using IPv6

[Mike Bordignon]

I'm seeing this same issue on Ubuntu 14.04 LTS using OpenSSH 1.0.1f.

mab@source:~$ ssh -v mtaxxx
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to mtaxxx [ip address hidden] port 22.
debug1: Connection established.
debug1: identity file /home/mab/.ssh/id_rsa type -1
debug1: identity file /home/mab/.ssh/id_rsa-cert type -1
debug1: identity file /home/mab/.ssh/id_dsa type 2
debug1: identity file /home/mab/.ssh/id_dsa-cert type -1
debug1: identity file /home/mab/.ssh/id_ecdsa type -1
debug1: identity file /home/mab/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/mab/.ssh/id_ed25519 type -1
debug1: identity file /home/mab/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 
Ubuntu-2ubuntu2
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH_6.6.1* compat 
0x0400
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server-client aes128-ctr hmac-md5-...@openssh.com none
debug1: kex: client-server aes128-ctr hmac-md5-...@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
Connection closed by ip6 address

I can ping6 the host, see the traffic getting there in tcpdump, but SSH
won't connect (over v6).

-- 
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/bugs/281882

Title:
  ssh hangs in initial handshaking when using IPv6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/281882/+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 1328166] Re: /etc/cron.d/maas_remote_syslog_compress not removed on package uninstall

[Mike McCracken]

Thanks for testing. I had thought I'd used purge via a separate script,
but now that I look back I'm not sure.

My apologies for the bug spam

** Changed in: maas (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  /etc/cron.d/maas_remote_syslog_compress not removed on package
  uninstall

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1328166/+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