[Bug 1363832] Re: [utopic] fails to build containers

2014-09-01 Thread Martin Pitt
** Attachment added: cloud-init-output.log
   
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1363832/+attachment/4192081/+files/cloud-init-output.log

** Description changed:

  I tried the local provider again on current utopic, and today it fails
  on creating containers:
  
  - Start from a clean slate: no *juju* containers (I do have some
  containers for other work, though), no ~/.juju, etc. I follow
  https://juju.ubuntu.com/docs/getting-started.html and
  https://juju.ubuntu.com/docs/config-local.html
  
  - sudo apt install juju-core juju-local
-   juju generate-config
-   juju switch local
+   juju generate-config
+   juju switch local
  
  - As I have $HOME on ecryptfs, I follow the documentation and use a
  separate juju root:
  
-   sudo mkdir /scratch/juju
-   sudo chown martin:martin /scratch/juju/
+   sudo mkdir /scratch/juju
+   sudo chown martin:martin /scratch/juju/
  
-   Now I edit ~/.juju/environments.yaml in the local section to have
+   Now I edit ~/.juju/environments.yaml in the local section to have
  root-dir: /scratch/juju and default-series: trusty.
  
-   I also apply a workaround for bug 1290920: 
-   lrwxrwxrwx 1 root root 12 Jun 11 21:55 /var/lib/lxc - /scratch/lxc
+   I also apply a workaround for bug 1290920:
+   lrwxrwxrwx 1 root root 12 Jun 11 21:55 /var/lib/lxc - /scratch/lxc
  
  - Now bootstrap, this apparently works well:
  
  $ juju bootstrap
  uploading tools for series [precise trusty utopic]
- [sudo] password for martin: 
+ [sudo] password for martin:
  Logging to /scratch/juju/cloud-init-output.log on remote host
  Bootstrapping Juju machine agent
  Starting Juju machine agent (juju-agent-martin-local)
  
  This took maybe 10 seconds. /scratch/juju/cloud-init-output.log contains
  no ERROR, and ends with juju-agent-martin-local start/running,
  process 3997, so this seems fine. But I'll attach the log anyway. Note
  that this did *not* create any extra container; sudo lxc-ls --fancy
  does not show me anything new.
  
  $ juju status
  environment: local
  machines:
-   0:
- agent-state: started
- agent-version: 1.20.5.1
- dns-name: localhost
- instance-id: localhost
- series: utopic
- state-server-member-status: has-vote
+   0:
+ agent-state: started
+ agent-version: 1.20.5.1
+ dns-name: localhost
+ instance-id: localhost
+ series: utopic
+ state-server-member-status: has-vote
  services: {}
- 
  
  - Now I try to deploy the GUI:
  
  $ juju deploy juju-gui
  Added charm cs:trusty/juju-gui-5 to the environment.
  
  (Returned after ~ 5 s)
  
  $ juju status
  environment: local
  machines:
-   0:
- agent-state: started
- agent-version: 1.20.5.1
- dns-name: localhost
- instance-id: localhost
- series: utopic
- state-server-member-status: has-vote
-   1:
- agent-state-info: container failed to start
- instance-id: pending
- series: trusty
+   0:
+ agent-state: started
+ agent-version: 1.20.5.1
+ dns-name: localhost
+ instance-id: localhost
+ series: utopic
+ state-server-member-status: has-vote
+   1:
+ agent-state-info: container failed to start
+ instance-id: pending
+ series: trusty
  services:
-   juju-gui:
- charm: cs:trusty/juju-gui-5
- exposed: false
- units:
-   juju-gui/0:
- agent-state: pending
- machine: 1
+   juju-gui:
+ charm: cs:trusty/juju-gui-5
+ exposed: false
+ units:
+   juju-gui/0:
+ agent-state: pending
+ machine: 1
  
  This created a new container:
- juju-trusty-lxc-template  STOPPED  - - -   NO 
+ juju-trusty-lxc-template  STOPPED  - - -   NO
  
  But it is basically empty, except for a new log dir:
  
  $ find /scratch/lxc/juju-trusty-lxc-template/
  /scratch/lxc/juju-trusty-lxc-template/
  /scratch/lxc/juju-trusty-lxc-template/config
  /scratch/lxc/juju-trusty-lxc-template/rootfs
  /scratch/lxc/juju-trusty-lxc-template/rootfs/var
  /scratch/lxc/juju-trusty-lxc-template/rootfs/var/log
  /scratch/lxc/juju-trusty-lxc-template/rootfs/var/log/juju
  
  The first error in /scratch/juju/log/machine-0.log is
  
  2014-09-01 06:36:47 ERROR juju.worker runner.go:218 exited api: unable
  to connect to wss://localhost:17070/
  
  but it seems to retry and succeed a bit later:
  
  2014-09-01 06:36:50 INFO juju.state.api apiclient.go:176 connection
  established to wss://localhost:17070/
  
  then it just ends with
  
  2014-09-01 06:39:19 ERROR juju.container.lxc clonetemplate.go:167 container 
failed to start: container failed to start
  2014-09-01 06:39:19 ERROR juju.provisioner provisioner_task.go:418 cannot 
start instance for machine 1: container failed to start
  
  I'll also attach the full file. So it seems it fails very early on to
  create containers, this doesn't seem very charm specific. But just to
  make sure, I destroyed the juju service and machine (which didn't
  destroy the container, I did that manually) 

[Bug 1363832] [NEW] [utopic] fails to build containers

2014-09-01 Thread Martin Pitt
Public bug reported:

I tried the local provider again on current utopic, and today it fails
on creating containers:

- Start from a clean slate: no *juju* containers (I do have some
containers for other work, though), no ~/.juju, etc. I follow
https://juju.ubuntu.com/docs/getting-started.html and
https://juju.ubuntu.com/docs/config-local.html

- sudo apt install juju-core juju-local
  juju generate-config
  juju switch local

- As I have $HOME on ecryptfs, I follow the documentation and use a
separate juju root:

  sudo mkdir /scratch/juju
  sudo chown martin:martin /scratch/juju/

  Now I edit ~/.juju/environments.yaml in the local section to have
root-dir: /scratch/juju and default-series: trusty.

  I also apply a workaround for bug 1290920:
  lrwxrwxrwx 1 root root 12 Jun 11 21:55 /var/lib/lxc - /scratch/lxc

- Now bootstrap, this apparently works well:

$ juju bootstrap
uploading tools for series [precise trusty utopic]
[sudo] password for martin:
Logging to /scratch/juju/cloud-init-output.log on remote host
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-martin-local)

This took maybe 10 seconds. /scratch/juju/cloud-init-output.log contains
no ERROR, and ends with juju-agent-martin-local start/running,
process 3997, so this seems fine. But I'll attach the log anyway. Note
that this did *not* create any extra container; sudo lxc-ls --fancy
does not show me anything new.

$ juju status
environment: local
machines:
  0:
agent-state: started
agent-version: 1.20.5.1
dns-name: localhost
instance-id: localhost
series: utopic
state-server-member-status: has-vote
services: {}

- Now I try to deploy the GUI:

$ juju deploy juju-gui
Added charm cs:trusty/juju-gui-5 to the environment.

(Returned after ~ 5 s)

$ juju status
environment: local
machines:
  0:
agent-state: started
agent-version: 1.20.5.1
dns-name: localhost
instance-id: localhost
series: utopic
state-server-member-status: has-vote
  1:
agent-state-info: container failed to start
instance-id: pending
series: trusty
services:
  juju-gui:
charm: cs:trusty/juju-gui-5
exposed: false
units:
  juju-gui/0:
agent-state: pending
machine: 1

This created a new container:
juju-trusty-lxc-template  STOPPED  - - -   NO

But it is basically empty, except for a new log dir:

$ find /scratch/lxc/juju-trusty-lxc-template/
/scratch/lxc/juju-trusty-lxc-template/
/scratch/lxc/juju-trusty-lxc-template/config
/scratch/lxc/juju-trusty-lxc-template/rootfs
/scratch/lxc/juju-trusty-lxc-template/rootfs/var
/scratch/lxc/juju-trusty-lxc-template/rootfs/var/log
/scratch/lxc/juju-trusty-lxc-template/rootfs/var/log/juju

The first error in /scratch/juju/log/machine-0.log is

2014-09-01 06:36:47 ERROR juju.worker runner.go:218 exited api: unable
to connect to wss://localhost:17070/

but it seems to retry and succeed a bit later:

2014-09-01 06:36:50 INFO juju.state.api apiclient.go:176 connection
established to wss://localhost:17070/

then it just ends with

2014-09-01 06:39:19 ERROR juju.container.lxc clonetemplate.go:167 container 
failed to start: container failed to start
2014-09-01 06:39:19 ERROR juju.provisioner provisioner_task.go:418 cannot start 
instance for machine 1: container failed to start

I'll also attach the full file. So it seems it fails very early on to
create containers, this doesn't seem very charm specific. But just to
make sure, I destroyed the juju service and machine (which didn't
destroy the container, I did that manually) and service, and tried to
juju deploy mysql, but with the exact same result.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: juju-local 1.20.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
Uname: Linux 3.16.0-11-generic x86_64
ApportVersion: 2.14.7-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep  1 08:23:10 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-27 (185 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
PackageArchitecture: all
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

** Attachment added: machine-0.log
   
https://bugs.launchpad.net/bugs/1363832/+attachment/4192077/+files/machine-0.log

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

Title:
  [utopic] fails to build containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1363832/+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 1363832] Re: [utopic] fails to build containers

2014-09-01 Thread Martin Pitt
I tried this again without setting default-series: trusty, thus
defaulting to precise (ugh, shouldn't we switch to trusty now? precise
is certainly not the currently preferred deployment target any more).

Running juju deploy juju-gui still showed Added charm cs:trusty
/juju-gui-5 to the environment., so perhaps the comment in the yaml is
wrong and the default is indeed trusty these days?

Behaves exactly the same, i. e. creates an empty (except the log dir)
container and then fails.

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

Title:
  [utopic] fails to build containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1363832/+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 1363617] Re: Sync python-webob 1.4-2 (main) from Debian unstable (main)

2014-09-01 Thread Daniel Holbach
This bug was fixed in the package python-webob - 1.4-2
Sponsored for Artur Rona (ari-tczew)

---
python-webob (1.4-2) unstable; urgency=medium

  * Removed debian/python3-webob.pyremove: we really need the egg-info file.
Thanks to doko for the bug report. (Closes: #757928)
  * Added myself as uploader.

 -- Thomas Goirand z...@debian.org  Sat, 30 Aug 2014 18:25:25 +

** Changed in: python-webob (Ubuntu)
   Status: New = Fix Released

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

Title:
  Sync python-webob 1.4-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-webob/+bug/1363617/+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 1363620] Re: Sync popt 1.16-10 (main) from Debian unstable (main)

2014-09-01 Thread Daniel Holbach
This bug was fixed in the package popt - 1.16-10
Sponsored for Artur Rona (ari-tczew)

---
popt (1.16-10) unstable; urgency=low

  * debian/rules: move dependency on target autoreconf-stamp from 
configure (which isn't called) to configure-deb-stamp and 
configure-udeb-stamp.
  * Patches: 757935-autoreconf.patch: add change to Makefile.am of 
testit.sh path.
  * That'll teach me to try to be too clever! (Closes: #757935)

 -- Paul Martin p...@debian.org  Mon, 25 Aug 2014 16:15:25 +0100

popt (1.16-9) unstable; urgency=low

  * Patches:
+ 728596-secure-getenv.patch: update to change #elseif (not recognised
  by gcc) to #elif.
+ 757935-autoreconf.patch: remove AM_C_PROTOTYPES from configure.ac
  * Add dependency on dh-autoreconf, and use that in debian/rules instead
of directly using the rules from autotools-dev. (Closes: #757935)
  * Update to standards version 3.9.5 (no changes)

 -- Paul Martin p...@debian.org  Mon, 25 Aug 2014 13:46:30 +0100

** Changed in: popt (Ubuntu)
   Status: New = Fix Released

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

Title:
  Sync popt 1.16-10 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/popt/+bug/1363620/+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 1320144] Re: kvm crashes with malloc.c assertion failed and other errors

2014-09-01 Thread f3a97
Hi,

FYI, I upgraded to Ubuntu 14.04 and the bug vanished!

Thanks


On 13 August 2014 06:17, Launchpad Bug Tracker 1320...@bugs.launchpad.net
wrote:

 [Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
 days.]

 ** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1320144

 Title:
   kvm crashes with malloc.c assertion failed and other errors

 Status in “qemu-kvm” package in Ubuntu:
   Expired

 Bug description:
   My Win7 VM running on KVM keeps crashing lately.

   I cannot say when it started to do so but I can say that this was not
   happening at all some weeks ago.

   From the qemu-kvm log file related to this VM just after the crash I
   have found what follows:

   2014-05-16 08:37:14.597+: starting up
   LC_ALL=C
 PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
 QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -cpu
 core2duo,+lahf_lm,+popcnt,+sse4.2,+sse4.1,+cx16,-monitor,-vme -enable-kvm
 -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name win7-32 -uuid
 9c5a2a97-7657-add4-2c4a-b9f1f8c076bd -nodefconfig -nodefaults -chardev
 socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7-32.monitor,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
 -no-shutdown -drive
 file=/host/Users/ste/Desktop/KVM/win7-32.img,if=none,id=drive-ide0-0-0,format=raw
 -device
 ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device
 ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev
 tap,fd=18,id=hostnet0 -device
 rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:20:0b:dd,bus=pci.0,addr=0x3
 -netdev tap,fd=19,id=hostnet1 -device
 rtl8139,netdev=hostnet1,id=net1,mac=52:54:00:c7:05:c9,bus=pci.0,addr=0x6
 -chardev pty,id=charserial0 -device
 isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:0 -vga std
 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
 hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
 virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
   char device redirected to /dev/pts/2
   kvm: malloc.c:2451: sYSMALLOc: Assertion `(old_top == (((mbinptr)
 (((char *) ((av)-bins[((1) - 1) * 2])) - __builtin_offsetof (struct
 malloc_chunk, fd  old_size == 0) || ((unsigned long) (old_size) =
 (unsigned long)__builtin_offsetof (struct malloc_chunk,
 fd_nextsize))+((2 * (sizeof(size_t))) - 1))  ~((2 * (sizeof(size_t))) -
 1)))  ((old_top)-size  0x1)  ((unsigned long)old_end  pagemask) ==
 0)' failed.
   2014-05-16 08:38:32.952+: shutting down

   And also:

   *** glibc detected *** /usr/bin/kvm: double free or corruption
   (fasttop): 0x7f6530001c40 ***

   ProblemType: Bug
   DistroRelease: Ubuntu 12.04
   Package: qemu-kvm 1.0+noroms-0ubuntu14.14
   ProcVersionSignature: Ubuntu 3.2.0-61.93-generic 3.2.55
   Uname: Linux 3.2.0-61-generic x86_64
   ApportVersion: 2.0.1-0ubuntu17.6
   Architecture: amd64
   Date: Fri May 16 10:40:47 2014
   KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit
 code 1: UIDPID  PPID  CSZ   RSS PSR STIME TTY  TIME CMD
   MachineType: Hewlett-Packard HP ProBook 4520s
   MarkForUpload: True
   ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-61-generic
 root=UUID=D2E20BC3E20BAAB5 loop=/hostname/disks/root.disk ro quiet splash
 vt.handoff=7
   SourcePackage: qemu-kvm
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 08/26/2010
   dmi.bios.vendor: Hewlett-Packard
   dmi.bios.version: 68AZZ Ver. F.0A
   dmi.board.name: 1411
   dmi.board.vendor: Hewlett-Packard
   dmi.board.version: KBC Version 57.30
   dmi.chassis.type: 10
   dmi.chassis.vendor: Hewlett-Packard
   dmi.modalias:
 dmi:bvnHewlett-Packard:bvr68AZZVer.F.0A:bd08/26/2010:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.30:cvnHewlett-Packard:ct10:cvr:
   dmi.product.name: HP ProBook 4520s
   dmi.sys.vendor: Hewlett-Packard

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1320144/+subscriptions


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

Title:
  kvm crashes with malloc.c assertion failed and other errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1320144/+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 1361069] Re: openvswitch-datapath-dkms 2.0.1+git20140120-0ubuntu2: openvswitch kernel module failed to build

2014-09-01 Thread James Page
*** This bug is a duplicate of bug 1266749 ***
https://bugs.launchpad.net/bugs/1266749

** This bug has been marked a duplicate of bug 1266749
   openvswitch-datapath-dkms fails to build with 3.13 kernel

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

Title:
  openvswitch-datapath-dkms 2.0.1+git20140120-0ubuntu2: openvswitch
  kernel module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1361069/+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 1357229] Re: [SRU] 2.0.2 stable update

2014-09-01 Thread James Page
Smoking OK on serverstack after a few weeks of use; marking verification
done.

** 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 openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1357229

Title:
  [SRU] 2.0.2 stable update

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

2014-09-01 Thread James Page
*** This bug is a duplicate of bug 1266749 ***
https://bugs.launchpad.net/bugs/1266749

** This bug has been marked a duplicate of bug 1266749
   openvswitch-datapath-dkms fails to build with 3.13 kernel

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

Title:
  openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel
  module failed to build

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

2014-09-01 Thread James Page
*** This bug is a duplicate of bug 1266749 ***
https://bugs.launchpad.net/bugs/1266749

** This bug has been marked a duplicate of bug 1266749
   openvswitch-datapath-dkms fails to build with 3.13 kernel

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1357019/+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 1352570] Re: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()

2014-09-01 Thread James Page
We've not seen any problems since upgrading to the version in trusty-
proposed; marking verification done.

** 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 openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1352570

Title:
  ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1352570/+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 1363897] [NEW] kdb5_ldap_util can not create krbContainer

2014-09-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Following instructions on
https://help.ubuntu.com/10.04/serverguide/kerberos-ldap.html
creating the initial database with kdb5_ldap_util 
(sudo kdb5_ldap_util -D cn=admin,dc=app,dc=tsn create -subtrees dc=app,dc=tsn 
-r APP.TSN -s -H ldap:///ldap01.app.tsn)
fails with error message:
kdb5_ldap_util: Kerberos Container create FAILED: Object class violation 
while creating realm 'APP.TSN'

after reading these mails
http://comments.gmane.org/gmane.comp.encryption.kerberos.general/18509
setting up loglevel for slapd in syslog, following error message can be found:
--
Sep  1 09:52:19 ldap01 slapd[1165]: == hdb_add: dc=app,dc=tsn
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_required entry (dc=app,dc=tsn), 
objectClass krbContainer
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type objectClass
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type cn
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type 
structuralObjectClass
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type dc
Sep  1 09:52:19 ldap01 slapd[1165]: Entry (dc=app,dc=tsn), attribute 'dc' not 
allowed
Sep  1 09:52:19 ldap01 slapd[1165]: hdb_add: entry failed schema check: 
attribute 'dc' not allowed (65)
---

System: 
Ubuntu 14.04 LTS
slapd  2.4.31-1+nmu amd64
krb5-config2.3
krb5-kdc   1.12+dfsg-2u amd64
krb5-kdc-ldap  1.12+dfsg-2u amd64
krb5-locales   1.12+dfsg-2u 
krb5-user  1.12+dfsg-2u amd64

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

-- 
kdb5_ldap_util  can not create krbContainer
https://bugs.launchpad.net/bugs/1363897
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to krb5 in Ubuntu.

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


[Bug 1363897] [NEW] kdb5_ldap_util can not create krbContainer

2014-09-01 Thread Reinhard
Public bug reported:

Following instructions on
https://help.ubuntu.com/10.04/serverguide/kerberos-ldap.html
creating the initial database with kdb5_ldap_util 
(sudo kdb5_ldap_util -D cn=admin,dc=app,dc=tsn create -subtrees dc=app,dc=tsn 
-r APP.TSN -s -H ldap:///ldap01.app.tsn)
fails with error message:
kdb5_ldap_util: Kerberos Container create FAILED: Object class violation 
while creating realm 'APP.TSN'

after reading these mails
http://comments.gmane.org/gmane.comp.encryption.kerberos.general/18509
setting up loglevel for slapd in syslog, following error message can be found:
--
Sep  1 09:52:19 ldap01 slapd[1165]: == hdb_add: dc=app,dc=tsn
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_required entry (dc=app,dc=tsn), 
objectClass krbContainer
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type objectClass
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type cn
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type 
structuralObjectClass
Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type dc
Sep  1 09:52:19 ldap01 slapd[1165]: Entry (dc=app,dc=tsn), attribute 'dc' not 
allowed
Sep  1 09:52:19 ldap01 slapd[1165]: hdb_add: entry failed schema check: 
attribute 'dc' not allowed (65)
---

System: 
Ubuntu 14.04 LTS
slapd  2.4.31-1+nmu amd64
krb5-config2.3
krb5-kdc   1.12+dfsg-2u amd64
krb5-kdc-ldap  1.12+dfsg-2u amd64
krb5-locales   1.12+dfsg-2u 
krb5-user  1.12+dfsg-2u amd64

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

** Attachment added: krb5.conf
   https://bugs.launchpad.net/bugs/1363897/+attachment/4192162/+files/krb5.conf

** Package changed: nfs-utils (Ubuntu) = krb5 (Ubuntu)

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

Title:
  kdb5_ldap_util  can not create krbContainer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1363897/+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 1363366] Re: DNSSEC for dnsmasq

2014-09-01 Thread Thomas Hood
** Description changed:

  This is a wishlist item.
  
- I'd like to use DNSSEC for dnsmasq out of the box. Currently support for
- DNSSEC appears to be disabled at compile time: if I add dnssec options
- to the dnsmasq.conf, it doesn't accept the configuration. I'm using
- Ubuntu Trusty.
+ I'd like to turn on dnsmasq's DNSSEC validation. However, it appears
+ that support for DNSSEC is disabled at compile time: if I add the
+ dnssec option to the dnsmasq.conf, dnsmasq doesn't accept the
+ configuration. I'm using Ubuntu Trusty.
  
- As a workaround, I currently configured DNSSEC to proxy via upstream DNS
- with the proxy-dnssec option -- but this is insecure.
+ As a workaround, I currently configure dnsmasq to rely on the DNSSEC
+ validation of upstream DNS servers (i.e., I use the proxy-dnssec
+ option) but this is not entirely secure.

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

Title:
  DNSSEC for dnsmasq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1363366/+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 1363366] Re: DNSSEC for dnsmasq

2014-09-01 Thread Thomas Hood
Trusty has dnsmasq 2.68-1. Looking at the buildlog I don't see
HAVE_DNSSEC being defined on the compiler command line.

gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -W -DHAVE_DBUS
-DHAVE_CONNTRACK -DLOCALEDIR='/usr/share/locale' -DVERSION='2.68'
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include
-c dnsmasq.c

However, in the build log of dnsmasq 2.71-1, which is in Utopic, I do
see HAVE_DNSSEC being defined on the compiler command line.

gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -W -DNO_NETTLE_ECC
-DHAVE_DBUS -DHAVE_CONNTRACK -DHAVE_DNSSEC
-DLOCALEDIR='/usr/share/locale' -DVERSION='2.71'
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include
-c dnsmasq.c

I surmise, therefore, that this wish is fulfilled in Utopic.

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

Title:
  DNSSEC for dnsmasq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1363366/+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 1363980] [NEW] kadmin.local in wrong package

2014-09-01 Thread Hadmut Danisch
Public bug reported:

Hi,

in contrast to /usr/bin/kadmin,  /usr/bin/kadmin.local does not use the
server, but accesses the database directly. It does not use the krb5
-admin-server.

It therefore should not be packed into the krb5-admin-server, but in the
krb5-kdc package, to allow using it without/before installing the admin
server.

Doesn't make sense to put a program designed to be independent from
admin-server in the package with admin-server.

regards
Hadmut

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: krb5-admin-server 1.12+dfsg-2ubuntu4.2
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Sep  1 14:18:26 2014
SourcePackage: krb5
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  kadmin.local in wrong package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1363980/+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 1358284] Re: apache 2.4.7 does not respect valid-user

2014-09-01 Thread jaf@id
We have exactly the same problem here using apache 2.4.7 on Ubuntu 14.04. 
The following configuration does not work i.e. i could not access the 
restricted ressource:

AuthType Basic
AuthName Restricted Files
AuthBasicProvider file
AuthUserFile /path/to/file/.htpasswd
require valid-user

If I use require user jfoe I can access the ressource:

AuthType Basic
AuthName Restricted Files
AuthBasicProvider file
AuthUserFile /path/to/file/.htpasswd
require user jdoe

The same is true if I use AuthBasicProvider ldap instead of file.

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

Title:
  apache 2.4.7 does not respect valid-user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1358284/+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 1363063] Re: ACPI BIOS Error with 3.13.0-32-generic and qemu 2.1.0~rc5ubuntu1

2014-09-01 Thread Vermut
We used old bios with new qemu. Close it.

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

Title:
  ACPI BIOS Error with 3.13.0-32-generic and qemu 2.1.0~rc5ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1363063/+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 1363063] Re: ACPI BIOS Error with 3.13.0-32-generic and qemu 2.1.0~rc5ubuntu1

2014-09-01 Thread Serge Hallyn
** Changed in: qemu-kvm (Ubuntu)
   Status: New = Invalid

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

Title:
  ACPI BIOS Error with 3.13.0-32-generic and qemu 2.1.0~rc5ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1363063/+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 1364037] [NEW] Juju expects a public address for all machines maybe insecure

2014-09-01 Thread pootow
Public bug reported:

Why [Juju expects a public address for all machines][1]? I think this is
unnecessary and insecure.

[1]: http://juju-docs.readthedocs.org/en/latest/provider-configuration-
openstack.html#openstack-configuration

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Juju expects a public address for all machines maybe insecure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1364037/+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 1286209] Re: unhandled trace if no namespaces in metering agent

2014-09-01 Thread Ilya Shakhat
** Changed in: neutron
   Status: Confirmed = In Progress

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

Title:
  unhandled trace if no namespaces in metering agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1286209/+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 1363832] Re: [utopic] fails to build containers

2014-09-01 Thread Martin Pitt
On IRC I was asked to try and create the template container manually:

$ sudo lxc-create -n mytrusty -t ubuntu-cloud -- -r trusty -S ~/.ssh/id_rsa.pub 
ubuntu-cloudimg-query ist /usr/bin/ubuntu-cloudimg-query
wget ist /usr/bin/wget
failed to get 
https://cloud-images.ubuntu.com/query/trusty/server/daily-dl.current.txt
There is no download available for release=trusty, stream=daily, arch=amd64

It should not use the daily channel for this, but the stable ones?

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

Title:
  [utopic] fails to build template container -- ubuntu-cloudimg-query
  fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1363832/+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 1363832] Re: [utopic] fails to build containers

2014-09-01 Thread Martin Pitt
Reading /usr/share/lxc/templates/lxc-ubuntu-cloud it seems to default to
tryreleased, which fails:

$ ubuntu-cloudimg-query trusty released amd64
failed to get 
https://cloud-images.ubuntu.com/query/trusty/server/released-dl.current.txt

and then it falls back to daily (which doesn't exist). I can open the
link above just fine, I see some 5 images. But ubuntu-cloudimg-query
apparently is unhappy about it somehow?

** Summary changed:

- [utopic] fails to build containers
+ [utopic] fails to build template container -- ubuntu-cloudimg-query fails

** Also affects: cloud-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [utopic] fails to build template container -- ubuntu-cloudimg-query
  fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1363832/+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 1363832] Re: [utopic] fails to build template container -- ubuntu-cloudimg-query fails

2014-09-01 Thread Martin Pitt
One step further: ubuntu-cloudimg-query uses wget, but that fails to
check the cert:

$ LC_ALL=C wget -O- 
https://cloud-images.ubuntu.com/query/trusty/server/released-dl.current.txt
--2014-09-01 17:19:54--  
https://cloud-images.ubuntu.com/query/trusty/server/released-dl.current.txt
Resolving cloud-images.ubuntu.com (cloud-images.ubuntu.com)... 91.189.88.141
Connecting to cloud-images.ubuntu.com 
(cloud-images.ubuntu.com)|91.189.88.141|:443... connected.
ERROR: cannot verify cloud-images.ubuntu.com's certificate, issued by 
'/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, 
Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate 
Authority - G2':
  Unable to locally verify the issuer's authority.
To connect to cloud-images.ubuntu.com insecurely, use `--no-check-certificate'.


** Changed in: juju-core (Ubuntu)
   Status: New = Invalid

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

Title:
  [utopic] fails to build template container -- ubuntu-cloudimg-query
  fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1363832/+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 1363832] Re: [utopic] fails to build template container -- ubuntu-cloudimg-query fails

2014-09-01 Thread Martin Pitt
I added --no-check-certificate to the wget calls in /usr/bin/ubuntu-
cloudimg-query and /usr/share/lxc/templates/lxc-ubuntu-cloud and  now
the juju-trusty-lxc-template is created properly, the martin-local-
machine-1 one cloned off that. lxc deploy juju-gui still fails (agent-
state-info: 'hook failed: install'), but that's now another bug
report.

So the essence of this is: Utopic's ca-certificates don't cover the cert
we are using to sign our cloud images and their catalogs.

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

Title:
  [utopic] fails to build template container -- ubuntu-cloudimg-query
  fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1363832/+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 1361030] Re: new dnsmasq requirement exceeds available version on ubuntu 12.04

2014-09-01 Thread Eugene Nikanorov
** Changed in: neutron
   Status: New = Confirmed

** Changed in: neutron
   Importance: Undecided = Medium

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

Title:
  new dnsmasq requirement exceeds available version on ubuntu 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1361030/+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 1364069] Re: [utopic] deploy juju-gui fails on apt-get install error (with local provider)

2014-09-01 Thread Martin Pitt
$ juju debug-hooks juju-gui/0
root@martin-local-machine-1:~# apt-get -y install libapt-pkg-dev python-apt 
python-launchpadlib python-tempita python-yaml
[...]
E: Failed to fetch 
http://archive.ubuntu.com/ubuntu/pool/main/z/zlib/zlib1g-dev_1.2.8.dfsg-1ubuntu1_amd64.deb
  Unable to connect to 127.0.0.1:3142:

And indeed:

# cat /etc/apt/apt.conf.d/42-juju-proxy-settings 
Acquire::http::Proxy http://127.0.0.1:3142;;

That's wrong -- juju can't blindly copy the host's apt proxy (in this
case, apt-cacher-ng). Doing so is great, but it needs to rewrite
localhost and 127.0.0.1 to 10.0.3.1 (or more generally, the host in the
default route, or lxcbr0's IP). I do something similar in autopkgtest:

 http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/tree/tools
/adt-build-lxc#n51

that might be something to steal?

** Summary changed:

- [utopic] deploy juju-gui fails on apt-get install error (with local provider)
+ local provider must transform localhost in apt proxy address

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

Title:
  local provider must transform localhost in apt proxy address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1364069/+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 1364069] Re: [utopic] deploy juju-gui fails on apt-get install error (with local provider)

2014-09-01 Thread Martin Pitt
** Attachment added: unit-juju-gui-0.log
   
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1364069/+attachment/4192530/+files/unit-juju-gui-0.log

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

Title:
  local provider must transform localhost in apt proxy address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1364069/+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 1364069] [NEW] local provider must transform localhost in apt proxy address

2014-09-01 Thread Martin Pitt
Public bug reported:

After debugging and working around various earlier failures (bug 1290920
and bug 1363832) I'm at a point where juju bootstrap and juju deploy
juju-gui on utopic created a juju-trusty-lxc-template container and
cloned this into a running martin-local-machine-1:

juju-trusty-lxc-template  STOPPED  -  - -   NO 
martin-local-machine-1RUNNING  10.0.3.57  - -   YES

but the deploy still failed:

$ juju status
environment: local
machines:
  0:
agent-state: started
agent-version: 1.20.5.1
dns-name: localhost
instance-id: localhost
series: utopic
state-server-member-status: has-vote
  1:
agent-state: started
agent-version: 1.20.5.1
dns-name: 10.0.3.57
instance-id: martin-local-machine-1
series: trusty
hardware: arch=amd64
services:
  juju-gui:
charm: cs:trusty/juju-gui-5
exposed: false
units:
  juju-gui/0:
agent-state: error
agent-state-info: 'hook failed: install'
agent-version: 1.20.5.1
machine: 1
public-address: 10.0.3.57


log/unit-juju-gui-0.log says:

2014-09-01 15:34:44 INFO install subprocess.CalledProcessError: Command
'['apt-get', '-y', 'install', 'libapt-pkg-dev', 'python-apt', 'python-
launchpadlib', 'python-tempita', 'python-yaml']' returned non-zero exit
status 100

Unfortunately it doesn't have apt's stdout/err, so the log/unit-juju-
gui-0.log is fairly useless I'll attach it anyway for completeness.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: juju-local 1.20.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
Uname: Linux 3.16.0-11-generic x86_64
ApportVersion: 2.14.7-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep  1 17:38:12 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-27 (186 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
PackageArchitecture: all
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

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

Title:
  local provider must transform localhost in apt proxy address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1364069/+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 1360471] Re: [SRU] update walinuxagent to 2.0.8

2014-09-01 Thread Ben Howard
v2.0.8 is in Utopic now. Daily builds have passed automated testing.

** Changed in: walinuxagent (Ubuntu Utopic)
   Status: Confirmed = Fix Released

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

Title:
  [SRU] update walinuxagent to 2.0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1360471/+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 1360471] Re: [SRU] update walinuxagent to 2.0.8

2014-09-01 Thread Ben Howard
** Description changed:

+ SRU justification
+ 
+ Impact : Microsoft has released an update to the 2.0.x series for 
WALinuxagent. There are several notable fixes:
+   - reporting of SSH host keys for Ubuntu to the fabric
+   - fix extension handling bugs
+ 
+ Fix : Updating to v2.0.8 fixes these bugs.
+ 
+ Test Case :
+  * First boot
+- build new images from -proposed
+- confirm that instance boots
+- run against extension
+- confirm that portal captures SSH host keys
+  * Capture (VM Snapshot)
+- boot instance on Azure
+- upgrade from -proposed
+- shut instances down
+- capture instance
+- boot capture instance
+- confirm that portal capture SSH host keys
+- confirm instance has new identity
+- check /var/log/{cloud-init,waagent}.log for errors
+ 
+ Regression : regression potential is low, as these changes tighten up
+ the code and fix a broken feature.
+ 
+ 
+ [ORIGINAL REPORT] 
+ 
  We have tagged a new release for WALinuxAgent (2.0.7):
  https://github.com/Azure/WALinuxAgent/releases/tag/WALinuxAgent-2.0.7.
  Ubuntu's walinuxagent package is currently based on 2.0.5, so there are
  several fixes in 2.0.6 and 2.0.7 that are important to pick up.
  
  Specifically, there are a number of fixes for extension handling,
  provisioning and the new feature for adding a readme warning to the
  resource disk. For 12.04, here are the relevant fixes to look at.
  
  Fixes to extension handling
  
https://github.com/Azure/WALinuxAgent/commit/fd0aa07e0a08eaf285c4d4ce2b2aaf7698d3fd9d
  
https://github.com/Azure/WALinuxAgent/commit/f445aff063aa8aa59c1dca7e065e68f64904ae43
  
https://github.com/Azure/WALinuxAgent/commit/3f93680589116d28acdfdd594fe6942b52c139e4
  
  Add README warning to resource disk
  
https://github.com/Azure/WALinuxAgent/commit/78f97d9885725d6ca5fc749d3f9708f496920e97#diff-d41d8cd98f00b204e9800998ecf8427e
  
https://github.com/Azure/WALinuxAgent/commit/2321b9cd92988843ebea4f031d99b09c0054ee13
  
https://github.com/Azure/WALinuxAgent/commit/f574932748ec66eccca74e643e369b61eab81bf8
  
  Fixes for SSH server and host key handling (report host key to fabric)
  
https://github.com/Azure/WALinuxAgent/commit/62252f3f9162235aabc82f896efbab756935e141
  
https://github.com/Azure/WALinuxAgent/commit/71020f9913629bbe20fb76d424fb88e14a673dd3
  
  Please let us know if you have questions/concerns about any of these
  patches.

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

Title:
  [SRU] update walinuxagent to 2.0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1360471/+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 1360471] Re: [SRU] update walinuxagent to 2.0.8

2014-09-01 Thread Ben Howard
** Description changed:

  SRU justification
  
  Impact : Microsoft has released an update to the 2.0.x series for 
WALinuxagent. There are several notable fixes:
-   - reporting of SSH host keys for Ubuntu to the fabric
-   - fix extension handling bugs
+   - reporting of SSH host keys for Ubuntu to the fabric
+   - fix for extension timeout handling
+   - fultiple fixes for extension handler in status report and heartbeat
  
  Fix : Updating to v2.0.8 fixes these bugs.
  
  Test Case :
-  * First boot
-- build new images from -proposed
-- confirm that instance boots
-- run against extension
-- confirm that portal captures SSH host keys
-  * Capture (VM Snapshot)
-- boot instance on Azure
-- upgrade from -proposed
-- shut instances down
-- capture instance
-- boot capture instance
-- confirm that portal capture SSH host keys
-- confirm instance has new identity
-- check /var/log/{cloud-init,waagent}.log for errors
+  * First boot
+    - build new images from -proposed
+    - confirm that instance boots
+    - run against extension
+    - confirm that portal captures SSH host keys
+  * Capture (VM Snapshot)
+    - boot instance on Azure
+    - upgrade from -proposed
+    - shut instances down
+    - capture instance
+    - boot capture instance
+    - confirm that portal capture SSH host keys
+    - confirm instance has new identity
+    - check /var/log/{cloud-init,waagent}.log for errors
  
  Regression : regression potential is low, as these changes tighten up
  the code and fix a broken feature.
  
- 
- [ORIGINAL REPORT] 
+ [ORIGINAL REPORT]
  
  We have tagged a new release for WALinuxAgent (2.0.7):
  https://github.com/Azure/WALinuxAgent/releases/tag/WALinuxAgent-2.0.7.
  Ubuntu's walinuxagent package is currently based on 2.0.5, so there are
  several fixes in 2.0.6 and 2.0.7 that are important to pick up.
  
  Specifically, there are a number of fixes for extension handling,
  provisioning and the new feature for adding a readme warning to the
  resource disk. For 12.04, here are the relevant fixes to look at.
  
  Fixes to extension handling
  
https://github.com/Azure/WALinuxAgent/commit/fd0aa07e0a08eaf285c4d4ce2b2aaf7698d3fd9d
  
https://github.com/Azure/WALinuxAgent/commit/f445aff063aa8aa59c1dca7e065e68f64904ae43
  
https://github.com/Azure/WALinuxAgent/commit/3f93680589116d28acdfdd594fe6942b52c139e4
  
  Add README warning to resource disk
  
https://github.com/Azure/WALinuxAgent/commit/78f97d9885725d6ca5fc749d3f9708f496920e97#diff-d41d8cd98f00b204e9800998ecf8427e
  
https://github.com/Azure/WALinuxAgent/commit/2321b9cd92988843ebea4f031d99b09c0054ee13
  
https://github.com/Azure/WALinuxAgent/commit/f574932748ec66eccca74e643e369b61eab81bf8
  
  Fixes for SSH server and host key handling (report host key to fabric)
  
https://github.com/Azure/WALinuxAgent/commit/62252f3f9162235aabc82f896efbab756935e141
  
https://github.com/Azure/WALinuxAgent/commit/71020f9913629bbe20fb76d424fb88e14a673dd3
  
  Please let us know if you have questions/concerns about any of these
  patches.

** Description changed:

  SRU justification
  
  Impact : Microsoft has released an update to the 2.0.x series for 
WALinuxagent. There are several notable fixes:
    - reporting of SSH host keys for Ubuntu to the fabric
-   - fix for extension timeout handling
-   - fultiple fixes for extension handler in status report and heartbeat
+   - fix for extension timeout handling
+   - multiple fixes for extension handler in status report and heartbeat
  
  Fix : Updating to v2.0.8 fixes these bugs.
  
  Test Case :
   * First boot
     - build new images from -proposed
     - confirm that instance boots
     - run against extension
     - confirm that portal captures SSH host keys
   * Capture (VM Snapshot)
     - boot instance on Azure
     - upgrade from -proposed
     - shut instances down
     - capture instance
     - boot capture instance
     - confirm that portal capture SSH host keys
     - confirm instance has new identity
     - check /var/log/{cloud-init,waagent}.log for errors
  
  Regression : regression potential is low, as these changes tighten up
  the code and fix a broken feature.
  
  [ORIGINAL REPORT]
  
  We have tagged a new release for WALinuxAgent (2.0.7):
  https://github.com/Azure/WALinuxAgent/releases/tag/WALinuxAgent-2.0.7.
  Ubuntu's walinuxagent package is currently based on 2.0.5, so there are
  several fixes in 2.0.6 and 2.0.7 that are important to pick up.
  
  Specifically, there are a number of fixes for extension handling,
  provisioning and the new feature for adding a readme warning to the
  resource disk. For 12.04, here are the relevant fixes to look at.
  
  Fixes to extension handling
  
https://github.com/Azure/WALinuxAgent/commit/fd0aa07e0a08eaf285c4d4ce2b2aaf7698d3fd9d
  
https://github.com/Azure/WALinuxAgent/commit/f445aff063aa8aa59c1dca7e065e68f64904ae43
  

[Bug 1363260] Re: add cloud-init datasource for Cloud Sigma to 12.04

2014-09-01 Thread Ben Howard
Build package to PPA for testing:
https://launchpad.net/~utlemming/+archive/ubuntu/lp1363260

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

Title:
  add cloud-init datasource for Cloud Sigma to 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1363260/+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 1360471] Re: [SRU] update walinuxagent to 2.0.8

2014-09-01 Thread Ben Howard
Uploaded 12.04 and 14.04 versions; pending acceptance into -proposed.

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

Title:
  [SRU] update walinuxagent to 2.0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1360471/+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 1364069] Re: local provider must transform localhost in apt proxy address

2014-09-01 Thread Ian Booth
*** This bug is a duplicate of bug 1329051 ***
https://bugs.launchpad.net/bugs/1329051

** This bug has been marked a duplicate of bug 1329051
   local charm deployment fails on git not found due to wrong apt proxy

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

Title:
  local provider must transform localhost in apt proxy address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1364069/+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 1336364] Re: network.filters should be included when installing nova-compute

2014-09-01 Thread Itzik Brown
One Example:

# nova/virt/libvirt/vif.py: 'ebrctl', ...
ebrctl: CommandFilter, ebrctl, root

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

Title:
  network.filters should be included when installing nova-compute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1336364/+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 1081660] Re: If maas-enlist fails to reach a DNS server, the node will be named ; ; connection timed out; no servers could be reached

2014-09-01 Thread Julian Edwards
** Changed in: maas
   Status: Triaged = Fix Committed

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

Title:
  If maas-enlist fails to reach a DNS server, the node will be named ;;
  connection timed out; no servers could be reached

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1081660/+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 1315154] Re: [SRU] doesn't support booting ppc64el hardware

2014-09-01 Thread Greg Lutostanski
** Summary changed:

- doesn't support booting ppc64el hardware
+ [SRU] doesn't support booting ppc64el hardware

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

Title:
  [SRU] doesn't support booting ppc64el hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1315154/+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 1325640] Re: test_prepare_holds_startup_lock() still fails spuriously

2014-09-01 Thread Greg Lutostanski
** Description changed:

+ [Impact]
+  * Previously Django's aggressive connection closing policy would prevent 
session-level locks from being maintained.
+ 
+ [Testcase]
+  * Run included tests
+ 
+ [Regression Potential]
+  * Minimal, potentially an issue as it deals with releasing a lock (it could 
throw an exception) but most is just fixing up testcases.
+ 
  See bug 1308069.

** Summary changed:

- test_prepare_holds_startup_lock() still fails spuriously
+ [SRU] test_prepare_holds_startup_lock() still fails spuriously

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

Title:
  [SRU] test_prepare_holds_startup_lock() still fails spuriously

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1325640/+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 1325759] Re: start_up uses database lock outside of transaction

2014-09-01 Thread Greg Lutostanski
** Description changed:

+ [Impact]
+  * When using new locking code, this is used to prevent an error on maas 
server startup when asking for a lock when not in a transaction
+ 
+ [Testcase]
+  * Run included tests in test_start_up.py
+ 
+ [Regression Potential]
+  * Minimal
+ 
  mod_wsgi (pid=26521): Exception occurred processing WSGI script 
'/usr/share/maas/wsgi.py'.
  Traceback (most recent call last):
-   File /usr/share/maas/wsgi.py, line 32, in module
- start_up()
-   File /usr/lib/python2.7/dist-packages/maasserver/start_up.py, line 54, in 
start_up
- with locks.startup:
-   File /usr/lib/python2.7/dist-packages/maasserver/utils/dblocks.py, line 
77, in __enter__
- raise DatabaseLockAttemptOutsideTransaction(self)
+   File /usr/share/maas/wsgi.py, line 32, in module
+ start_up()
+   File /usr/lib/python2.7/dist-packages/maasserver/start_up.py, line 54, in 
start_up
+ with locks.startup:
+   File /usr/lib/python2.7/dist-packages/maasserver/utils/dblocks.py, line 
77, in __enter__
+ raise DatabaseLockAttemptOutsideTransaction(self)
  DatabaseLockAttemptOutsideTransaction: DatabaseLock classid=20120116 objid=1
  mod_wsgi (pid=26522): Target WSGI script '/usr/share/maas/wsgi.py' cannot be 
loaded as Python module.
  mod_wsgi (pid=26522): Exception occurred processing WSGI script 
'/usr/share/maas/wsgi.py'.
  Traceback (most recent call last):
-   File /usr/share/maas/wsgi.py, line 32, in module
- start_up()
-   File /usr/lib/python2.7/dist-packages/maasserver/start_up.py, line 54, in 
start_up
- with locks.startup:
-   File /usr/lib/python2.7/dist-packages/maasserver/utils/dblocks.py, line 
77, in __enter__
- raise DatabaseLockAttemptOutsideTransaction(self)
+   File /usr/share/maas/wsgi.py, line 32, in module
+ start_up()
+   File /usr/lib/python2.7/dist-packages/maasserver/start_up.py, line 54, in 
start_up
+ with locks.startup:
+   File /usr/lib/python2.7/dist-packages/maasserver/utils/dblocks.py, line 
77, in __enter__
+ raise DatabaseLockAttemptOutsideTransaction(self)
  DatabaseLockAttemptOutsideTransaction: DatabaseLock classid=20120116 objid=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/1325759

Title:
  start_up uses database lock outside of transaction

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1325759/+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 1334401] Re: [SRU] Missing dependency on python-paramiko

2014-09-01 Thread Greg Lutostanski
** Summary changed:

- Missing dependency on python-paramiko
+ [SRU] Missing dependency on python-paramiko

** Description changed:

- As seen here: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-
- maas/131/console, maas package can't be installed on utopic due to a
- missing dependency on python-paramiko
+ [Impact]
+  * Add missing dependency for install
  
+ [Testcase]
+  * install maas-dns (will fail if 1.6.0)
+  * or using provisioning on mscm hardware (will fail if =1.5.4) -- when fix 
not included
+ 
+ [Regression Potential]
+  * Minimal, included in main for all supported releases.
+ 
+ 
+ As seen here: 
http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-maas/131/console, maas 
package can't be installed on utopic due to a missing dependency on 
python-paramiko
  
  Setting up maas-dns (1.6+bzr2367+2475+283-0ubuntu1) ...
  Traceback (most recent call last):
-   File /usr/bin/django-admin, line 5, in module
- management.execute_from_command_line()
-   File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py, 
line 399, in execute_from_command_line
- utility.execute()
-   File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py, 
line 392, in execute
- self.fetch_command(subcommand).run_from_argv(self.argv)
-   File /usr/lib/python2.7/dist-packages/django/core/management/base.py, 
line 242, in run_from_argv
- self.execute(*args, **options.__dict__)
-   File /usr/lib/python2.7/dist-packages/django/core/management/base.py, 
line 284, in execute
- self.validate()
-   File /usr/lib/python2.7/dist-packages/django/core/management/base.py, 
line 310, in validate
- num_errors = get_validation_errors(s, app)
-   File 
/usr/lib/python2.7/dist-packages/django/core/management/validation.py, line 
34, in get_validation_errors
- for (app_name, error) in get_app_errors().items():
-   File /usr/lib/python2.7/dist-packages/django/db/models/loading.py, line 
196, in get_app_errors
- self._populate()
-   File /usr/lib/python2.7/dist-packages/django/db/models/loading.py, line 
78, in _populate
- self.load_app(app_name)
-   File /usr/lib/python2.7/dist-packages/django/db/models/loading.py, line 
99, in load_app
- models = import_module('%s.models' % app_name)
-   File /usr/lib/python2.7/dist-packages/django/utils/importlib.py, line 40, 
in import_module
- __import__(name)
-   File /usr/lib/python2.7/dist-packages/maasserver/models/__init__.py, line 
47, in module
- from maasserver.models.bootimage import BootImage
-   File /usr/lib/python2.7/dist-packages/maasserver/models/bootimage.py, 
line 27, in module
- from maasserver.models.nodegroup import NodeGroup
-   File /usr/lib/python2.7/dist-packages/maasserver/models/nodegroup.py, 
line 37, in module
- from maasserver.refresh_worker import refresh_worker
-   File /usr/lib/python2.7/dist-packages/maasserver/refresh_worker.py, line 
21, in module
- from provisioningserver.tasks import refresh_secrets
-   File /usr/lib/python2.7/dist-packages/provisioningserver/tasks.py, line 
56, in module
- from provisioningserver.drivers.hardware.mscm import probe_and_enlist_mscm
-   File 
/usr/lib/python2.7/dist-packages/provisioningserver/drivers/hardware/mscm.py, 
line 26, in module
- from paramiko import (
+   File /usr/bin/django-admin, line 5, in module
+ management.execute_from_command_line()
+   File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py, 
line 399, in execute_from_command_line
+ utility.execute()
+   File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py, 
line 392, in execute
+ self.fetch_command(subcommand).run_from_argv(self.argv)
+   File /usr/lib/python2.7/dist-packages/django/core/management/base.py, 
line 242, in run_from_argv
+ self.execute(*args, **options.__dict__)
+   File /usr/lib/python2.7/dist-packages/django/core/management/base.py, 
line 284, in execute
+ self.validate()
+   File /usr/lib/python2.7/dist-packages/django/core/management/base.py, 
line 310, in validate
+ num_errors = get_validation_errors(s, app)
+   File 
/usr/lib/python2.7/dist-packages/django/core/management/validation.py, line 
34, in get_validation_errors
+ for (app_name, error) in get_app_errors().items():
+   File /usr/lib/python2.7/dist-packages/django/db/models/loading.py, line 
196, in get_app_errors
+ self._populate()
+   File /usr/lib/python2.7/dist-packages/django/db/models/loading.py, line 
78, in _populate
+ self.load_app(app_name)
+   File /usr/lib/python2.7/dist-packages/django/db/models/loading.py, line 
99, in load_app
+ models = import_module('%s.models' % app_name)
+   File /usr/lib/python2.7/dist-packages/django/utils/importlib.py, line 40, 
in import_module
+ __import__(name)
+   File /usr/lib/python2.7/dist-packages/maasserver/models/__init__.py, line 
47, in module
+ from maasserver.models.bootimage import BootImage
+   File 

[Bug 1352273] Re: [SRU] ImportError: No module named pexpect when setting up maas-region-controller

2014-09-01 Thread Greg Lutostanski
** Summary changed:

- ImportError: No module named pexpect when setting up maas-region-controller
+ [SRU] ImportError: No module named pexpect when setting up 
maas-region-controller

** Description changed:

+ [Impact]
+  * Install required deps for maas-provisioningserver (move from 
maas-region-controller) so it installs in correct order.
+ 
+ [Testcase]
+  * Install python-maas-provisioningserver without error (will throw No module 
named pexpect if not including fix)
+ 
+ [Regression Potential]
+  * Almost none
+ 
  Hi,
  
  We're upgrading our MAAS infrastructure from precise+MAAS 1.4 to
  trusty+MAAS 1.5. During a do-release-upgrade, we're seeing the following
  traceback when setting up maas-region-controller:
  
-  in load_app
- models = import_module('%s.models' % app_name)
-   File /usr/lib/python2.7/dist-packages/django/utils/importlib.py, line 40, 
in import_module
- __import__(name)
-   File /usr/lib/python2.7/dist-packages/maasserver/models/__init__.py, line 
44, in module
- from maasserver.models.bootimage import BootImage
-   File /usr/lib/python2.7/dist-packages/maasserver/models/bootimage.py, 
line 26, in module
- from maasserver.models.nodegroup import NodeGroup
-   File /usr/lib/python2.7/dist-packages/maasserver/models/nodegroup.py, 
line 35, in module
- from maasserver.refresh_worker import refresh_worker
-   File /usr/lib/python2.7/dist-packages/maasserver/refresh_worker.py, line 
21, in module
- from provisioningserver.tasks import refresh_secrets
-   File /usr/lib/python2.7/dist-packages/provisioningserver/tasks.py, line 
49, in module
- from provisioningserver.custom_hardware.virsh import 
probe_virsh_and_enlist
-   File 
/usr/lib/python2.7/dist-packages/provisioningserver/custom_hardware/virsh.py, 
line 18, in module
- import pexpect
+  in load_app
+ models = import_module('%s.models' % app_name)
+   File /usr/lib/python2.7/dist-packages/django/utils/importlib.py, line 40, 
in import_module
+ __import__(name)
+   File /usr/lib/python2.7/dist-packages/maasserver/models/__init__.py, line 
44, in module
+ from maasserver.models.bootimage import BootImage
+   File /usr/lib/python2.7/dist-packages/maasserver/models/bootimage.py, 
line 26, in module
+ from maasserver.models.nodegroup import NodeGroup
+   File /usr/lib/python2.7/dist-packages/maasserver/models/nodegroup.py, 
line 35, in module
+ from maasserver.refresh_worker import refresh_worker
+   File /usr/lib/python2.7/dist-packages/maasserver/refresh_worker.py, line 
21, in module
+ from provisioningserver.tasks import refresh_secrets
+   File /usr/lib/python2.7/dist-packages/provisioningserver/tasks.py, line 
49, in module
+ from provisioningserver.custom_hardware.virsh import 
probe_virsh_and_enlist
+   File 
/usr/lib/python2.7/dist-packages/provisioningserver/custom_hardware/virsh.py, 
line 18, in module
+ import pexpect
  ImportError: No module named pexpect
  
- 
- The python-pexpect package isn't installed because we have 
APT::Install-Recommends set to false.
+ The python-pexpect package isn't installed because we have APT
+ ::Install-Recommends set to false.
  
  iF  maas-region-controller  
1.5.2+bzr2282-0ubuntu0.2  all  MAAS server complete 
region controller
  ii  maas-region-controller-min  
1.5.2+bzr2282-0ubuntu0.2  all  MAAS Server minimum 
region controller
  
- 
  Regards,
  
  Haw

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

Title:
  [SRU] ImportError: No module named pexpect when setting up maas-
  region-controller

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1352273/+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 1364217] [NEW] smbd -F crashed on Samba server configured through caja-share

2014-09-01 Thread Eliah Kagan
Public bug reported:

I'm not sure what triggered this crash; I would not have known there was
one if Apport hadn't caught it.

smbd -F (which I did not run manually) crashed on a Utopic i386 system
running the MATE desktop environment, through which the Samba server had
been automatically configured via Caja (with caja-share).

I was also unable to make shares of external volumes accessible (tested
with both a Windows and an Ubuntu client), but I am unsure if that is a
bug and my intention here is to report the crash, and not that problem
(unless they turn out to be facets of the same problem).

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: samba 2:4.1.11+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic i686
ApportVersion: 2.14.7-0ubuntu1
Architecture: i386
BothFailedConnect: Yes
CrashCounter: 1
Date: Mon Sep  1 23:55:42 2014
ExecutablePath: /usr/sbin/smbd
InstallationDate: Installed on 2014-08-13 (19 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha i386 (20140812)
NmbdLog:
 
ProcCmdline: smbd -F
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SambaServerRegression: Yes
Signal: 6
SmbConfIncluded: Yes
SmbLog:
 
SourcePackage: samba
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: apport-crash i386 utopic

** Information type changed from Private to Public

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

Title:
  smbd -F crashed on Samba server configured through caja-share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1364217/+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 1329051] Re: local provider must transform localhost in apt proxy address

2014-09-01 Thread Martin Pitt
** Summary changed:

- local charm deployment fails on git not found due to wrong apt proxy
+ local provider must transform localhost in apt proxy address

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

Title:
  local provider must transform localhost in apt proxy address

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1329051/+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 1364217]

2014-09-01 Thread Apport retracing service
StacktraceSource:
 #0  0xb776cd7c in __kernel_vsyscall ()
 #1  0xb6ae0827 in __GI___open_catalog (cat_name=0x260019 error: Cannot access 
memory at address 0x260019, nlspath=0x0, env_var=0x0, catalog=0x0) at 
open_catalog.c:109
   [Error: open_catalog.c was not found in source tree]
StacktraceTop: __GI___open_catalog (cat_name=0x260019 error: Cannot access 
memory at address 0x260019, nlspath=0x0, env_var=0x0, catalog=0x0) at 
open_catalog.c:109

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

Title:
  smbd -F crashed on Samba server configured through caja-share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1364217/+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 1364217] ThreadStacktrace.txt

2014-09-01 Thread Apport retracing service
** Attachment added: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1364217/+attachment/4192963/+files/ThreadStacktrace.txt

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1364217/+attachment/4192955/+files/CoreDump.gz

** Changed in: samba (Ubuntu)
   Importance: Undecided = Medium

** Tags removed: need-i386-retrace

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

Title:
  smbd -F crashed on Samba server configured through caja-share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1364217/+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 1364217] Stacktrace.txt

2014-09-01 Thread Apport retracing service
** Attachment added: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1364217/+attachment/4192962/+files/Stacktrace.txt

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

Title:
  smbd -F crashed on Samba server configured through caja-share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1364217/+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: ubuntu 12.04 not running latest phomyadmin, even though installed.

2014-09-01 Thread Rajeev Prasad
when i run the application like this: http://mywebsite.com/phpMyAdmin/index.php

on the home page it shows i am using old version:
Version information: 3.4.3.1, latest stable version: 4.2.7.1

but i have latest phpmyadmin installed (see below) why is it not appearing?

MySQL client version is 5.5.38


$ cat /etc/phpmyadmin/apache.conf
# phpMyAdmin default Apache configuration

Alias /phpmyadmin /usr/share/phpmyadmin

Directory /usr/share/phpmyadmin
Options FollowSymLinks
DirectoryIndex index.php
AllowOverride All

IfModule mod_php5.c
AddType application/x-httpd-php .php

php_flag magic_quotes_gpc Off
php_flag track_vars On
php_flag register_globals Off
php_admin_flag allow_url_fopen Off
php_value include_path .
php_admin_value upload_tmp_dir /var/lib/phpmyadmin/tmp
php_admin_value open_basedir 
/usr/share/phpmyadmin/:/etc/phpmyadmin/:/var/lib/phpmyadmin/
/IfModule

/Directory

# Authorize for setup
Directory /usr/share/phpmyadmin/setup

IfModule mod_authn_file.c
AuthType Basic
AuthName phpMyAdmin Setup
AuthUserFile /etc/phpmyadmin/htpasswd.setup
/IfModule
Require valid-user
/Directory

# Disallow web access to directories that don't need it
Directory /usr/share/phpmyadmin/libraries
Order Deny,Allow
Deny from All
/Directory
Directory /usr/share/phpmyadmin/setup/lib
Order Deny,Allow
Deny from All
/Directory
$
$


$ dpkg -s phpmyadmin
Package: phpmyadmin
Status: install ok installed
Priority: extra
Section: web
Installed-Size: 15113
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
Architecture: all
Version: 4:3.4.10.1-1
Depends: libapache2-mod-php5 | libapache2-mod-php5filter | php5-cgi | php5-fpm 
| php5, php5-mysql | php5-mysqli, php5-mcrypt, perl, debconf (= 0.5) | 
debconf-2.0, dbconfig-common, ttf-dejavu-core, ucf (= 0.28)
Recommends: apache2 | lighttpd | httpd, php5-gd, mysql-client
Suggests: mysql-server, www-browser
Conffiles:
 /etc/phpmyadmin/apache.conf
840caa9c589c9a84213c2c6ef9fb5a39
 /etc/phpmyadmin/config.footer.inc.php f59a8fe4a05431392ad1ef4e0b36278f
 /etc/phpmyadmin/config.header.inc.php ff471619d3280ef72b7b0641bab4ba27
 /etc/phpmyadmin/config.inc.php f5201f1a5c501d2f0bacc551d9bfedce
 /etc/phpmyadmin/lighttpd.conf 72d500d79840a38eff5dca64bfe02198
 /etc/phpmyadmin/phpmyadmin.desktop 18948893751469fa6a6a910db9714909
 /etc/phpmyadmin/phpmyadmin.service f79a2a07e93b221f646a75e894496ef0
Description: MySQL web administration tool
 This package allows administering of MySQL with a web interface.
 .
 It allows administrators to:
  - browse through databases and tables;
  - create, copy, rename, alter
and drop databases;
  - create, copy, rename, alter and drop tables;
  - perform table maintenance;
  - add, edit and drop fields;
  - execute any SQL-statement, even multiple queries;
  - create, alter and drop indexes;
  - load text files into tables;
  - create and read dumps of tables or databases;
  - export data to SQL, CSV, XML, Word, Excel, PDF and LaTeX formats;
  - administer multiple servers;
  - manage MySQL users and privileges;
  - check server settings and runtime information with configuration hints;
  - check referential integrity in MyISAM tables;
  - create complex queries using Query-by-example (QBE),
automatically
connecting required tables;
  - create PDF graphics of database layout;
  - search globally in a database or a subset of it;
  - transform stored data into any format using a set of predefined
functions, such as displaying BLOB-data as image or download-link;
  - manage InnoDB tables and foreign keys;
 and is fully internationalized and localized in dozens of languages.
Original-Maintainer: Thijs Kinkhorst th...@debian.org
Homepage: phpMyAdmin


phpMyAdmin
Download 4.2.8 Try demo Donate GSoC 2014 Platinum sponsor Gold sponsor Silver 
sponsors Sponsorship See other sponsors and information for new sponsors. About 
  
View on www.phpmyadmin.net Preview by Yahoo  




under my web folder tree, under www, i have folder for phpmyadmin - everything 
is there - i think i have to do something to it??
mywebsite/www/phpmyadmin..
I even copied all of /usr/share/phpmyadmin to replace this, but it still shows 
old version :(( 


pl help.

ty.

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam