[Bug 1545749] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From helmut.gra...@de.ibm.com 2016-03-08 02:21 EDT---
Hi
the problem is fixed. s390 support   libibverbs1 is implemented.
Thanks
Helmut

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

Title:
  libibverbs1: add s390x support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1545749/+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 1554031] Re: error: internal error: unable to execute QEMU command ‘block-commit’: Could not reopen file: Permission denied

[Jignasha]

PFB outputs

$ cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"
NAME="Ubuntu"
VERSION="14.04.4 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.4 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;

$ ls -l /etc/apt/sources.list.d
total 4
-rw-r--r-- 1 root root 78 Feb 23 05:51 cloudarchive-kilo.list

$ cat /etc/apt/sources.list.d/*
deb http://ubuntu-cloud.archive.canonical.com/ubuntu trusty-updates/kilo main

$ dpkg -l | egrep -e '(libvirt|qemu)'
ii  ipxe-qemu   1.0.0+git-2013.c3d1e78-2ubuntu1.1 
all  PXE boot firmware - ROM images for qemu
ii  libvirt-bin 1.2.12-0ubuntu14.2~cloud0 
amd64programs for the libvirt library
ii  libvirt01.2.12-0ubuntu14.2~cloud0 
amd64library for interfacing with different virtualization systems
ii  nova-compute-libvirt1:2015.1.2-0ubuntu2~cloud0
all  OpenStack Compute - compute node libvirt support
ii  python-libvirt  1.2.2-0ubuntu2
amd64libvirt Python bindings
ii  qemu1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64fast processor emulator
ii  qemu-slof   20140630+dfsg-1ubuntu1~14.04  
all  Slimline Open Firmware -- QEMU PowerPC version
ii  qemu-system 1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU full system emulation binaries
ii  qemu-system-arm 1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU full system emulation binaries (arm)
ii  qemu-system-common  1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU full system emulation binaries (common files)
ii  qemu-system-mips1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU full system emulation binaries (mips)
ii  qemu-system-misc1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU full system emulation binaries (miscelaneous)
ii  qemu-system-ppc 1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU full system emulation binaries (ppc)
ii  qemu-system-sparc   1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU full system emulation binaries (sparc)
ii  qemu-system-x86 1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU full system emulation binaries (x86)
ii  qemu-user   1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU user mode emulation binaries
ii  qemu-user-binfmt1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU user mode binfmt registration for qemu-user
ii  qemu-utils  1:2.2+dfsg-5expubuntu9.6~cloud0   
amd64QEMU utilities


Getting below DENIED stat in syslog

Mar  7 07:41:19 ubuntu-kilo kernel: [604860.586630] audit: type=1400 
audit(1457354479.040:171): apparmor="DENIED" operation="open" 
profile="libvirt-4aba5887-882f-494f-ae4b-26e2bdc8a25a" 
name="/sys/devices/system/node/" pid=22024 comm="qemu-system-x86" 
requested_mask="r" denied_mask="r" fsuid=106 ouid=0
Mar  7 07:41:19 ubuntu-kilo kernel: [604860.586652] audit: type=1400 
audit(1457354479.040:172): apparmor="DENIED" operation="open" 
profile="libvirt-4aba5887-882f-494f-ae4b-26e2bdc8a25a" 
name="/sys/devices/system/cpu/" pid=22024 comm="qemu-system-x86" 
requested_mask="r" denied_mask="r" fsuid=106 ouid=0

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

Title:
  error: internal error: unable to execute QEMU command ‘block-commit’:
  Could not reopen file: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1554031/+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 1554214] Re: Usege of vfio-pci module via /etc/dpdk/interfaces doesn't work

[ChristianEhrhardt]

Thanks for reporting.
As I'm currently testing and fixing all kind of this it matches what I do this 
week.
I just came not yet by vfio-pci, by that I have to thank you to make me aware.

I'll have a look at it and let you know.

** Changed in: dpdk (Ubuntu)
   Status: New => Triaged

** Changed in: dpdk (Ubuntu)
   Importance: Undecided => Medium

** Changed in: dpdk (Ubuntu)
 Assignee: (unassigned) => ChristianEhrhardt (paelzer)

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

Title:
  Usege of vfio-pci module via /etc/dpdk/interfaces doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1554214/+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 1546556] Re: Dropping privileges in openvswitch-switch via --user is incompatible with --dpdk

[ChristianEhrhardt]

Hi Thiago,
when running into the issue the bug is referring to it looked way different.
So I'd say the issue you are currently facing has nothing to do with the bug.

I've seen your mail on the List and will reply there with some
suggestions and by that keep the bug to the related things.

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

Title:
  Dropping privileges in openvswitch-switch via --user is incompatible
  with --dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1546556/+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 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values

[Tore Anderson]

Okay, sorry about the irrelevant verification on Vivid then. But I'd
like to point out that Trusty behaves exactly the same, i.e., the bug is
*not* fixed. Using the exact same multipath.conf as I mentioned in
comment #31 with multipath-tools on 0.4.9-3ubuntu7.9, I get the exact
same behaviour. That is, it is apparent that multipathd does read the
settings from the config file (as they're visible in output from
"multipathd -k'show config'"), but they're not being applied/written to
sysfs.

If I run use the command line utility in verbose mode to create the map,
it does claim that it opens the sysfs files in question, but strace
shows no sign of that actually happening:

root@ucstest:~# /etc/init.d/multipath-tools stop
 * Stopping multipath daemon multipathd 

[ OK ]
root@ucstest:~# multipath -F
root@ucstest:~# strace -ff -eopen multipath -v4 |& egrep 'create:|_tmo'
Mar 08 07:48:38 | 3600c0ff0001204a9d12b75510100: fast_io_fail_tmo = 16 
(controller default)
Mar 08 07:48:38 | 3600c0ff0001204a9d12b75510100: dev_loss_tmo = 2048 
(controller default)
Mar 08 07:48:38 | open 
'/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:01.0/:07:00.0/host1/rport-1:0-1/fc_remote_ports/rport-1:0-1'/'dev_loss_tmo'
ort-1:0-1'/'fast_io_fail_tmo'
Mar 08 07:48:38 | open 
'/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:01.0/:07:00.0/host1/rport-1:0-2/fc_remote_ports/rport-1:0-2'/'dev_loss_tmo'
Mar 08 07:48:38 | open 
'/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:01.0/:07:00.0/host1/rport-1:0-2/fc_remote_ports/rport-1:0-2'/'fast_io_fail_tmo'
Mar 08 07:48:38 | open 
'/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-1/fc_remote_ports/rport-2:0-1'/'dev_loss_tmo'
Mar 08 07:48:38 | open 
'/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-1/fc_remote_ports/rport-2:0-1'/'fast_io_fail_tmo'
Mar 08 07:48:38 | open 
'/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-2/fc_remote_ports/rport-2:0-2'/'dev_loss_tmo'
Mar 08 07:48:38 | open 
'/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-2/fc_remote_ports/rport-2:0-2'/'fast_io_fail_tmo'
create: 3600c0ff0001204a9d12b75510100 undef HP  ,P2000G3 FC/iSCSI

Note that this is a lab system, so if you'd like, you can have a look
yourself, Mathieu. Just send me a SSH pubkey on IRC and I'll set up a
user account for you.

Tore

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

Title:
  DevLossTO, FastIoFailTO settings do not match multipath.conf expected
  values

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+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 1546550] Re: openvswitch-switch-dpdk links against libdpdk statically

[ChristianEhrhardt]

Yeah we changed the dpdk piece to properly be linkable in bug 1547517.
And James did some great work on updating openvswitch to 2.5.
We just have forgot to update this one, I'll talk to James later if he agrees 
that we can close it.

Thanks already Thiago for making me aware!

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

Title:
  openvswitch-switch-dpdk links against libdpdk statically

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1546550/+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 1330408] Re: ucfr fails if smb.conf is not owned by samba

[Bug Watch Updater]

** Changed in: samba (Debian)
   Status: New => Incomplete

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

Title:
  ucfr fails if smb.conf is not owned by samba

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1330408/+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 1554343] Re: smbd crashed with SIGABRT in strlen()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1514766, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1554343/+attachment/4592224/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1554343/+attachment/4592226/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1554343/+attachment/4592228/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1554343/+attachment/4592229/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1554343/+attachment/4592230/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1554343/+attachment/4592233/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1554343/+attachment/4592234/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1514766
   smbd crashed with SIGABRT in strlen() while accessing a share from a W7 
client

** Information type changed from Private to Public

** Tags removed: need-amd64-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/1554343

Title:
  smbd crashed with SIGABRT in strlen()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1554343/+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 1546556] Re: Dropping privileges in openvswitch-switch via --user is incompatible with --dpdk

[Thiago Martins]

Guys,

I'm trying to use OVS with DPDK to create a bridge between 2 x 10G NIC
cards, however, it is not working, the log shows:

---
root@xenial-1:~# ovs-vswitchd log
2016-03-08T04:19:19Z|1|ovs_numa|INFO|Discovered 24 CPU cores on NUMA node 0
2016-03-08T04:19:19Z|2|ovs_numa|INFO|Discovered 24 CPU cores on NUMA node 1
2016-03-08T04:19:19Z|3|ovs_numa|INFO|Discovered 2 NUMA nodes and 48 CPU 
cores
2016-03-08T04:19:19Z|4|reconnect|INFO|log: connecting...
2016-03-08T04:19:19Z|5|reconnect|INFO|log: connection attempt failed 
(Address family not supported by protocol)
2016-03-08T04:19:19Z|6|reconnect|INFO|log: waiting 1 seconds before 
reconnect
2016-03-08T04:19:20Z|7|reconnect|INFO|log: connecting...
2016-03-08T04:19:20Z|8|reconnect|INFO|log: connection attempt failed 
(Address family not supported by protocol)
2016-03-08T04:19:20Z|9|reconnect|INFO|log: waiting 2 seconds before 
reconnect
2016-03-08T04:19:22Z|00010|reconnect|INFO|log: connecting...
2016-03-08T04:19:22Z|00011|reconnect|INFO|log: connection attempt failed 
(Address family not supported by protocol)
2016-03-08T04:19:22Z|00012|reconnect|INFO|log: waiting 4 seconds before 
reconnect
2016-03-08T04:19:23Z|00013|fatal_signal|WARN|terminating with signal 2 
(Interrupt)
---

After a bit of research on the Internet, I'm thinking that it might be
related to this problem... Or not?

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

Title:
  Dropping privileges in openvswitch-switch via --user is incompatible
  with --dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1546556/+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 1515791] Re: apparmor for qemu is too restrictive for USB passthrough

[Serge Hallyn]

Hi,

could you please show the contents of
/etc/apparmor.d/libvirt/libvirt-99917005-9251-4ea3-9e72-946b42061df1 ?

virt-aa-helper *is* supposed to be adding an rw entry for each usb file
for hostdevs being added (through file_iterate_hostdev_cb()), so I'm
wondering which file isn't being handled and why.

** Changed in: libvirt (Ubuntu)
   Status: Expired => Incomplete

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

Title:
  apparmor for qemu is too restrictive for USB passthrough

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1515791/+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 1554031] Re: error: internal error: unable to execute QEMU command ‘block-commit’: Could not reopen file: Permission denied

[Serge Hallyn]

The default security driver in Ubuntu is apparmor.

Could you please show the output of

cat /etc/*-release
ls -l /etc/apt/sources.list.d
cat /etc/apt/sources.list.d/*
dpkg -l | egrep -e '(libvirt|qemu)'

and show any relevant DENIED messages in syslog (grep DENIED
/var/log/syslog)

Your libvirt version, 1.2.12, is not in any support release of Ubuntu.

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

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

Title:
  error: internal error: unable to execute QEMU command ‘block-commit’:
  Could not reopen file: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1554031/+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 1532460] Re: Please upgrade to allow virsh blockcommit in Ubuntu 14. libvirt-1.2.9 (and above)

[Serge Hallyn]

Fix for that one is building in xenial-proposed as well.

** Changed in: libvirt (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Please upgrade to allow virsh blockcommit in Ubuntu 14.
  libvirt-1.2.9 (and above)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1532460/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or director

[Andres Rodriguez]

Hi Paul

Sorry for the delay and thanks for looking into it. Good catch on the
postrm. At least I know that's my fault. That being said, I wonder if
unregistering the file actually explains why it doesn't get re-created. The
funny thing here is that this is the first time it actually does something
similar (not creating the file), and the packaging hasn;'t really change in
that area.

I'm gonna try to reproduce what you suggest with touching the file and see
whether things get resolved with the fix to postrm..

Thanks!

On Mon, Mar 7, 2016 at 4:02 PM, Paul Gevers <1553...@bugs.launchpad.net>
wrote:

> Andres,
>
> This (in maas-region-controller.postrm) prevents dbconfig-common from
> unregistring the file with ucf (so the fact that you see the ucf prompt
> after purging and installing is at least caused by maas itself):
> if [ -f /etc/dbconfig-common/maas.conf ]; then
> if [ -f /usr/share/dbconfig-common/dpkg/postrm ]; then
> . /usr/share/dbconfig-common/dpkg/postrm.pgsql
> dbc_go maas-region-controller $@
> fi
> fi
>
> Paul
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1553757
>
> Title:
>   dbconfig-common: writing config to /etc/dbconfig-common/maas-region-
>   controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-
>   controller.conf': No such file or directory
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+subscriptions
>


-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

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

Title:
  dbconfig-common: writing config to /etc/dbconfig-common/maas-region-
  controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-
  controller.conf': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or director

[Andres Rodriguez]

So the reason we did this is because we wanted MAAS to be installed and we
didn't want any question to be asked, so we decided to do the preseeding.
The registration piece is something that I found in another package, but
allowed MAAS to register the preseed options, otherwise this would have
failed!

On Mon, Mar 7, 2016 at 3:59 PM, Paul Gevers <1553...@bugs.launchpad.net>
wrote:

> Hi Andres,
>
> Maybe unrelated and I may not understand your intentions, but I see the
> following in your maas-region-controller.config:
> set_question() {
> if ! db_fget "$1" seen; then
> db_register dbconfig-common/dbconfig-install "$1"
> db_subst "$1" ID "$1"
> db_fget "$1" seen
> fi
>
>
> Which gets called by:
> set_question maas-region-controller/dbconfig-install true
> set_question maas-region-controller/pgsql/app-pass ""
> set_question maas-region-controller/remote/host "localhost"
>
> But isn't the question from the second set, the $1 in the first
> function? So shouldn't that "db_register" line also register the other
> questions and use the value provided as argument?
>
> Paul
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1553757
>
> Title:
>   dbconfig-common: writing config to /etc/dbconfig-common/maas-region-
>   controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-
>   controller.conf': No such file or directory
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+subscriptions
>


-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

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

Title:
  dbconfig-common: writing config to /etc/dbconfig-common/maas-region-
  controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-
  controller.conf': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Launchpad Bug Tracker]

** Branch linked: lp:~smoser/cloud-init/trunk.disable_pollinate

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Scott Moser]

** Changed in: cloud-init
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1533728] Re: libvirt unable to create more than one snapshot

[Serge Hallyn]

Thanks, @Dadio, I'll cherrypick the patch unless #qemu points to
objections.

** Package changed: libvirt (Ubuntu) => qemu (Ubuntu)

** Changed in: qemu (Ubuntu)
   Importance: Undecided => High

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

Title:
  libvirt unable to create more than one snapshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1533728/+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 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

[Serge Hallyn]

this should be fixed by the fix to bug 1554269.

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

Title:
  Unprivileged nested Xenial container will not start inside a
  privileged Xenial container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+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 1554195] Re: Nova (juno) ignores logging_*_format_string in syslog output

[Wenzhi Yu]

** Changed in: nova
   Status: New => In Progress

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

Title:
  Nova (juno) ignores logging_*_format_string in syslog output

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1554195/+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 1553251] Re: USN-2915-1 introduced a regression in is_safe_url()

[Mathew Hodson]

** No longer affects: python-django (Ubuntu Precise)

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

Title:
  USN-2915-1 introduced a regression in is_safe_url()

To manage notifications about this bug go to:
https://bugs.launchpad.net/django/+bug/1553251/+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 1554195] Re: Nova (juno) ignores logging_*_format_string in syslog output

[Wenzhi Yu]

** Changed in: nova
 Assignee: (unassigned) => Wenzhi Yu (yuywz)

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

Title:
  Nova (juno) ignores logging_*_format_string in syslog output

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1554195/+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 1554214] Re: Usege of vfio-pci module via /etc/dpdk/interfaces doesn't work

[Thiago Martins]

I also added:

--
default_hugepagesz=1GB hugepagesz=1G hugepages=1
--

To Grub Linux options, still doesn't work.

I think I am following
"https://github.com/openvswitch/ovs/blob/master/INSTALL.DPDK.md; but no
luck.

BTW, this isn't working on Ubuntu:

--
chmod a+x /dev/vfio
--

It just ignored it.

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

Title:
  Usege of vfio-pci module via /etc/dpdk/interfaces doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1554214/+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 1549789] Re: Updated walinuxagent to 2.0.16

[Ben Howard]

** Description changed:

+ [IMPACT] Microsoft has released a bug fix release for walinuxagent that
+ fixes several bugs. Microsoft has asked that the 2.0.14 version for
+ Ubuntu 12.04 and 14.04 be updated to 2.0.16.
+ 
+ [Test Case 1]
+ 1. Boot instance
+ 2. Update walinuxagent from -proposed
+ 3. Reboot
+ 4. Confirm that /var/log/waagent.log is clean
+ 5. Capture instance; boot new instance from captured instance
+ 6. Confirm that instance provisions, /var/log/waagent.log is clean of errors 
and that /var/log/cloud-init.log is clean
+ 
+ [Test Case 2]
+ 1. Create new image built from -proposed
+ 2. Boot instance from new image
+ 3. Confirm instance is accessable via SSH
+ 4. Confirm /var/log/waagnet.log is clean
+ 5. Confirm /var/log/cloud-init.log is clean of errors
+ 
+ [Common for both test cases]
+ 1. Make that dataloss warning is in /mnt
+ 2. Follow instructions on disabling the dataloss warning, reboot
+ 3. Make sure that dataloss warning file is not present on reboot
+ 4. Enable boot diagnostics for the instance in the Azure console
+ 5. Make sure that SSH logging appears on the boot console.
+ 
+ [ORIGINAL REPORT]
+ 
  WALinuxAgent has a new up release for 2.0.16.
  
  Github Release: https://github.com/Azure/WALinuxAgent/releases/tag/v2.0.16
  Changelog:
- Add timeout for http request
- Handle http 410 when reporting health
- Fix plugin version comparison
- Change swap file permission to 0600
- Add retry on restarting network interface
- Add retry on environment detection
- Add log for status report
- Copy status files from old plugin dir to new during upgrade
- Remove old plugin dir after upgrade
+ Add timeout for http request
+ Handle http 410 when reporting health
+ Fix plugin version comparison
+ Change swap file permission to 0600
+ Add retry on restarting network interface
+ Add retry on environment detection
+ Add log for status report
+ Copy status files from old plugin dir to new during upgrade
+ Remove old plugin dir after upgrade

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

Title:
  Updated walinuxagent to 2.0.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1549789/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Ryan Harper]

On Mon, Mar 7, 2016 at 5:40 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> Hi Ryan,
>
> This appears to have fixed the nvme partition problem but, I'm sure
> there are nicer ways to do it.
>
>
Hi Rob!

Thanks for confirming a workaround.


> root@maas1:~# diff -u
> /usr/lib/python3/dist-packages/curtin/commands/block_meta.py
> /usr/lib/python3/dist-packages/curtin/commands/block_meta.py.orig
> --- /usr/lib/python3/dist-packages/curtin/commands/block_meta.py
> 2016-03-07 23:37:34.137946135 +
> +++ /usr/lib/python3/dist-packages/curtin/commands/block_meta.py.orig
>  2016-03-07 23:37:28.565864667 +
> @@ -368,13 +368,7 @@
>  partnumber = determine_partition_number(vol.get('id'),
> storage_config)
>  disk_block_path = get_path_to_storage_volume(vol.get('device'),
>   storage_config)
> -
> -if disk_block_path == '/dev/nvme0n1':
> -volume_path = disk_block_path + 'p' + str(partnumber)
> -else
> -volume_path = disk_block_path +  str(partnumber)
> -
> +volume_path = disk_block_path + str(partnumber)
>  devsync_vol = os.path.join(disk_block_path)
>
>  elif vol.get('type') == "disk":
>
> --
> You received this bug notification because you are subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> https://bugs.launchpad.net/bugs/1401190
>
> Title:
>   curtin makes assumptions about partition names on all devices
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions
>

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+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 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

[Serge Hallyn]

Hi - there should be a way, we just need to get sudo running the pam
module.

Perhaps libpam-cgfs should be added to /etc/pam.d/common-session-
noninteractive.

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

Title:
  Unprivileged nested Xenial container will not start inside a
  privileged Xenial container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Rob Sanderson]

Hi Ryan,

This appears to have fixed the nvme partition problem but, I'm sure
there are nicer ways to do it.

root@maas1:~# diff -u 
/usr/lib/python3/dist-packages/curtin/commands/block_meta.py 
/usr/lib/python3/dist-packages/curtin/commands/block_meta.py.orig
--- /usr/lib/python3/dist-packages/curtin/commands/block_meta.py
2016-03-07 23:37:34.137946135 +
+++ /usr/lib/python3/dist-packages/curtin/commands/block_meta.py.orig   
2016-03-07 23:37:28.565864667 +
@@ -368,13 +368,7 @@
 partnumber = determine_partition_number(vol.get('id'), storage_config)
 disk_block_path = get_path_to_storage_volume(vol.get('device'),
  storage_config)
-
-if disk_block_path == '/dev/nvme0n1':
-volume_path = disk_block_path + 'p' + str(partnumber)
-else
-volume_path = disk_block_path +  str(partnumber)
-
+volume_path = disk_block_path + str(partnumber)
 devsync_vol = os.path.join(disk_block_path)

 elif vol.get('type') == "disk":

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+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 1554266] [NEW] sshd does not start on newly installed desktop system

[Max Brustkern]

Public bug reported:

When I preseed a desktop install using utah for daily iso testing, the
ssh service is not running when it starts up. journalctl -u ssh shows no
entries. If I manually start the ssh service, it seems to work. If I
reboot, sshd is running. On the first boot, however, it is not. This
problem appears to have started on the March 5 image.

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

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

Title:
  sshd does not start on newly installed desktop system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+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 1546550] Re: openvswitch-switch-dpdk links against libdpdk statically

[Thiago Martins]

On Xenial, it is dynamically linked:

---
root@xenial-1:~# ldd /usr/lib/openvswitch-switch-dpdk/ovs-vswitchd-dpdk | grep 
-i dpdk
libdpdk.so.0 => /usr/lib/x86_64-linux-gnu/libdpdk.so.0 
(0x7f89a3b8d000)
---

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

Title:
  openvswitch-switch-dpdk links against libdpdk statically

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1546550/+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 1554214] Re: Usege of vfio-pci module via /etc/dpdk/interfaces doesn't work

[Thiago Martins]

I forgot to mention that, to make it work manually, I also enabled IOMMU
at boot, by appending the following option to Linux via GRUB2:

---
intel_iommu=on
---

Otherwise, the command `dpdk_nic_bind --bind=vfio-pci em1|em2` fails.

Best,
Thiago

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

Title:
  Usege of vfio-pci module via /etc/dpdk/interfaces doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1554214/+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 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Launchpad Bug Tracker]

This bug was fixed in the package pollinate - 4.14-0ubuntu1

---
pollinate (4.14-0ubuntu1) xenial; urgency=medium

  * pollinate, pollinate.1: LP: #1554152
- change the failure mode of pollinate, so as to more cleanly
  tolerate network failures
- add a --strict option to re-enable the previous behavior,
  ie, strictly exit non-zero if pollinate fails for any reason
- we've always promised that pollinate would operate on a best-effort
  basis, improving the prng seeding when possible, but failing
  gracefully when not possible; as such, we've made good on the first
  half of that promise, however, the latter half has proven
  troublesome;  this is due to the fact that if pollinate exits
  non-zero, then its callers (cloud-init, maas, etc.) may well
  interpret the behavior strictly as a failure to boot the system,
  when in fact that's not the case;  instead, we'll clearly print
  a warning to syslog, and we'll retry the seeding on next pollinate
  service start (e.g. a reboot);  moreover, we'll carry a --strict
  flag in the case that users want to opt into the previous behavior

 -- Dustin Kirkland   Tue, 13 Oct 2015 10:16:12
-0700

** Changed in: pollinate (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

[Christopher Townsend]

Hi Serge,

Thanks for working with me on this.

So it does work when I ssh into the privileged container as user ubuntu
and then start the unprivileged container.

I'm guessing there may be no way to start the unprivileged container
from lxc-attach like I want to, right?

Here is the output you requested:

$ sudo lxc-attach -n test-libertine -- sudo -u ubuntu -H cat /proc/self/cgroup
11:cpuset:/
10:pids:/
9:memory:/
8:blkio:/
7:perf_event:/
6:freezer:/
5:hugetlb:/
4:devices:/
3:cpu,cpuacct:/
2:net_cls,net_prio:/
1:name=systemd:/

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

Title:
  Unprivileged nested Xenial container will not start inside a
  privileged Xenial container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+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 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

[Serge Hallyn]

Quoting Christopher Townsend (christopher.towns...@canonical.com):
> I tried adding "lxc.include = /usr/share/lxc/config/nesting.conf" as I
> didn't know this existed.  However, it didn't help.
> 
> As you say, I can create unprivileged containers as user ubuntu, I just
> can't start them.  Are you able to start unprivileged containers as user
> ubuntu?  If so, how are you starting them?  I need to start them from

Yes.  I start them by ssh'ing in as user ubuntu and doing lxc-start.
Does that work for you?

> the host's shell, so I'm doing something like this:
> 
> $ sudo lxc-attach -n test-libertine -- sudo -u ubuntu -H lxc-start -n
> test

This may not be enough to trigger pam-cgfs to create cgroups for you,
so that may be the reason it fails.  What does

sudo lxc-attach -n test-libertine -- sudo -u ubuntu -H cat
/proc/self/cgroup

show?

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

Title:
  Unprivileged nested Xenial container will not start inside a
  privileged Xenial container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+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 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Launchpad Bug Tracker]

** Branch linked: lp:pollinate

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Dustin Kirkland ]

** Changed in: pollinate (Ubuntu)
   Status: New => In Progress

** Changed in: pollinate (Ubuntu)
   Importance: Undecided => Critical

** Changed in: pollinate (Ubuntu)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Dustin Kirkland ]

bzr commit -m '* pollinate, pollinate.1: LP: #1554152
  - change the failure mode of pollinate, so as to more cleanly
tolerate network failures
  - add a --strict option to re-enable the previous behavior,
ie, strictly exit non-zero if pollinate fails for any reason
  - we've always promised that pollinate would operate on a best-effort
basis, improving the prng seeding when possible, but failing
gracefully when not possible; as such, we've made good on the first
half of that promise, however, the latter half has proven
troublesome;  this is due to the fact that if pollinate exits
non-zero, then its callers (cloud-init, maas, etc.) may well
interpret the behavior strictly as a failure to boot the system,
when in fact that's not the case;  instead, we'll clearly print
a warning to syslog, and we'll retry the seeding on next pollinate
service start (e.g. a reboot);  moreover, we'll carry a --strict
flag in the case that users want to opt into the previous behavior' --fixes 
'lp:1554152'
Committing to: /srv/media/src/pollinate/pollinate/  

 
modified pollinate
modified pollinate.1
modified debian/changelog
Committed revision 293.


** Changed in: pollinate (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or director

[Paul Gevers]

Andres,

This (in maas-region-controller.postrm) prevents dbconfig-common from
unregistring the file with ucf (so the fact that you see the ucf prompt
after purging and installing is at least caused by maas itself):
if [ -f /etc/dbconfig-common/maas.conf ]; then
if [ -f /usr/share/dbconfig-common/dpkg/postrm ]; then
. /usr/share/dbconfig-common/dpkg/postrm.pgsql
dbc_go maas-region-controller $@
fi
fi

Paul

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

Title:
  dbconfig-common: writing config to /etc/dbconfig-common/maas-region-
  controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-
  controller.conf': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1554214] [NEW] Usege of vfio-pci module via /etc/dpdk/interfaces doesn't work

[Thiago Martins]

Public bug reported:

Guys,

 I'm trying to use the "vfio-pci" with DPDK under Xenial but, it does
not work.

 When with "uio-pci-generic", it works, like this:

---
pci :01:00.0uio-pci-generic
pci :01:00.1uio-pci-generic
---

 After reboot, I can see that devices and bounded to DPDK-compatible
driver "dpdk_nic_bind --status", as expected.

 However, when I change it to "vfio-pci", it does not work anymore, like
this:

---
pci:01:00.0vfio-pci
pci:01:00.1vfio-pci
---

 I tried to add "vfio-pci" to the "/etc/modules" but, it also doesn't
work after reboot.

 So, I disabled all entries under "/etc/dpdk/interfaces", to try it
manually, like this:

---
dpdk_nic_bind --bind=vfio-pci em1
dpdk_nic_bind --bind=vfio-pci em2
---

 Then, it worked! Look the output of "dpdk_nic_bind --status":

---
Network devices using DPDK-compatible driver

:01:00.0 'NetXtreme II BCM57800 1/10 Gigabit Ethernet' drv=vfio-pci 
unused=bnx2x
:01:00.1 'NetXtreme II BCM57800 1/10 Gigabit Ethernet' drv=vfio-pci 
unused=bnx2x
---

 So, it is not working via "/etc/dpdk/interfaces" but works manually!

 NOTE: To make it work manually, the module "vfio-pci" must be declared
at "/etc/modules" as well.

Cheers!
Thiago

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

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

Title:
  Usege of vfio-pci module via /etc/dpdk/interfaces doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1554214/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or director

[Paul Gevers]

Hi Andres,

Maybe unrelated and I may not understand your intentions, but I see the
following in your maas-region-controller.config:
set_question() {
if ! db_fget "$1" seen; then
db_register dbconfig-common/dbconfig-install "$1"
db_subst "$1" ID "$1"
db_fget "$1" seen
fi


Which gets called by:
set_question maas-region-controller/dbconfig-install true
set_question maas-region-controller/pgsql/app-pass ""
set_question maas-region-controller/remote/host "localhost"

But isn't the question from the second set, the $1 in the first
function? So shouldn't that "db_register" line also register the other
questions and use the value provided as argument?

Paul

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

Title:
  dbconfig-common: writing config to /etc/dbconfig-common/maas-region-
  controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-
  controller.conf': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Rob Sanderson]

Hi Ryan,

I'm more than happy to let maas supply the data, I'm only trying to
override the default behaviour by adding to
/etc/maas/preseeds/curtin_userdata to get around the nvme bug.

Here's the output:

root@maas1:~# maas admin node get-curtin-config 
node-4c4aecf2-e332-11e5-a740-00163e1ca9db
Success.
Machine-readable output follows:
apt_mirrors:
  ubuntu_archive: http://archive.ubuntu.com//ubuntu
  ubuntu_security: http://archive.ubuntu.com//ubuntu
apt_proxy: http://10.10.4.221:8000/
debconf_selections:
  maas: 'cloud-init   cloud-init/datasources  multiselect MAAS

cloud-init   cloud-init/maas-metadata-url  string
http://10.10.4.221/MAAS/metadata/

cloud-init   cloud-init/maas-metadata-credentials  string 
oauth_token_key=
   
install:
  log_file: /tmp/install.log
  post_files:
  - /tmp/install.log
kernel:
  mapping: {}
  package: linux-generic
late_commands:
  maas:
  - wget
  - --no-proxy
  - 
http://10.10.4.221/MAAS/metadata/latest/by-id/node-4c4aecf2-e332-11e5-a740-00163e1ca9db/
  - --post-data
  - op=netboot_off
  - -O
  - /dev/null
network:
  config:
  - id: eth0
mac_address 
mtu: 1500
name: eth0
subnets:
- address: 10.10.4.11/22
  dns_nameservers: []
  gateway: 10.10.4.1
  type: static
type: physical
  - id: eth1
mac_address: 
mtu: 1500
name: eth1
subnets:
- type: manual
type: physical
  - bond_interfaces:
- eth0
- eth1
id: bond0
mac_address: 
mtu: 1500
name: bond0
params:
  bond-downdelay: 0
  bond-lacp_rate: fast
  bond-miimon: 100
  bond-mode: 802.3ad
  bond-updelay: 0
  bond-xmit_hash_policy: layer2
subnets:
- type: manual
type: bond
  - address: 10.10.4.221
search:
- 
type: nameserver
  version: 1
network_commands:
  builtin:
  - curtin
  - net-meta
  - custom
partitioning_commands:
  builtin:
  - curtin
  - block-meta
  - custom
power_state:
  mode: reboot
reporting:
  maas:
consumer_key: 
endpoint: 
http://10.10.4.221/MAAS/metadata/status/node-4c4aecf2-e332-11e5-a740-00163e1ca9db
token_key: 
token_secret: 
type: webhook
storage:
  config:
  - id: sdc
model: Samsung SSD 840
name: sdc
serial: 
type: disk
wipe: superblock
  - id: sda
model: ST2000DM001-1CH1
name: sda
serial: 
type: disk
wipe: superblock
  - id: sdb
model: ST2000DM001-1CH1
name: sdb
serial: 
type: disk
wipe: superblock
  - grub_device: true
id: nvme0n1
name: nvme0n1
path: /dev/nvme0n1
ptable: msdos
type: disk
wipe: superblock
  - device: nvme0n1
id: nvme0n1-part1
name: nvme0n1-part1
number: 1
offset: 4194304B
size: 128026935296B
type: partition
uuid: edf17540-d929-41cc-85de-c4df78802b8d
wipe: superblock
  - fstype: ext4
id: nvme0n1-part1_format
label: ''
type: format
uuid: ce3b35c2-48ee-4d6f-9b20-0ff9642b2961
volume: nvme0n1-part1
  - device: nvme0n1-part1_format
id: nvme0n1-part1_mount
path: /
type: mount
  version: 1

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+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 1553460] Re: named crashed with SIGABRT in isc_assertion_failed()

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  named crashed with SIGABRT in isc_assertion_failed()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1553460/+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 1554186] Re: walinuxagent ephemeral warning lacks full command for removal of file

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.1.3-0ubuntu4

---
walinuxagent (2.1.3-0ubuntu4) xenial; urgency=medium

  * Correct ephemeral warning to include the full command for removal
(LP: #1554186).

 -- Ben Howard   Mon, 07 Mar 2016 12:10:21 -0700

** Changed in: walinuxagent (Ubuntu)
   Status: In Progress => 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/1554186

Title:
  walinuxagent ephemeral warning lacks full command for removal of file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1554186/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Ryan Harper]

On Mon, Mar 7, 2016 at 1:50 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> Hi Ryan,
>
> Thanks, let me know if you need me to make any changes or run through
> any tests.
>
> A quick question if I may: How is the config generated when the node is
> deploying? I have found that storage config in curtin_userdata on the
> maas server appears to be ignored or clobbered e.g.
>

If you're using maas 1.8, or maas 1.9; maas itself is generating storage
configuration

https://maas.ubuntu.com/docs/storage.html#storage

Ideally you don't need to inject your own custom partitioning/storage
config; you
configure maas in the UI and it emits storage configuration to curtin.

It's not clear to me how you're combining your own user-data with what MaaS
supplies.


> If I execute: /var/lib/cloud/instance/scripts/part-001 # fails due to bug
> cd curtin


> cat configs/config-000.cfg # I see the storage config I have set on the
> maas server in curtin_userdata
>
> #cloud-config
> ...
> ...
>
> partitioning_commands:
>   builtin: [curtin, block-meta, custom]
> storage:
>   config:
>   - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
> disk, wipe: superblock}
>   - {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 1, offset:
> 4194304B, size: 128026935296B, type: partition, wipe: superblock}
>   - {fstype: ext4, id: nvme0n1p1_format, label: 'rootfs', type: format,
> path: /dev/nvme0n1p1, volume: nvme0n1p1}
>   version: 1
>
> cat configs/config-002.cfg # appears to be the device(s) that are found
> during commissioning
>
> partitioning_commands:
>   builtin: [curtin, block-meta, custom]
> storage:
>   config:
>   - {grub_device: true, id: sdc, model: Samsung SSD 840, name: sdc,
> ptable: gpt, serial: S1D9NSAFB19195M,
> type: disk, wipe: superblock}
>   - {device: sdc, id: sdc-part1, name: sdc-part1, number: 1, offset:
> 4194304B, size: 1000198897664B,
> type: partition, uuid: 8bcce503-ad8f-495e-a158-669829585db2, wipe:
> superblock}
>   - {fstype: ext4, id: sdc-part1_format, label: '', type: format, uuid:
> 0195af9d-764d-4b35-8e53-07573aa4c057,
> volume: sdc-part1}
>   - {device: sdc-part1_format, id: sdc-part1_mount, path: /, type: mount}
>   version: 1
> ...
> ...
> 
>
> I was trying to test an install to one of the other disks which also
> failed.
>

It's hard to say;  if you have the entire curtin config sent I may be able
to parse out what's going on:
>From the maas cli:

maas  node get-curtin-config 

and attach to this bug.


>
> I had to remove the nvme device and 2 other devices from the web ui as
> configs/config-002.cfg had every disk listed, including the nvme device
> which I had specified in curtin_userdata. The config data is that from
> commissioning.
>
> I also noted that despite me selecting a different boot device that it
> was still trying to install grub to sda.
>


>
> Does this sound like another bug with curtin or should I raise it with
> the maas project?
>

Boot device selection *could* be a maas issue or curtin.  I suggest
opening a new bug against MAAS for the boot device selection,
and I can add a MAAS task to this one.  In both places, please append
the output from the maas get-curtin-config output attached.  This helps
us debug whether MAAS sent curtin valid configuration and determine
if we need to fix the bug in MAAS or curtin itself.

In _this_ bugs case; if the config you send which defines 'number' field in
the partition dictionary, then curtin will *faithfully* attempt to use
 directly; ie; curtin is doing what it was told.

In the case where 'number' is not defined, curtin will attempt to determine
the
correct partition number.  For NVME devices, the logic is not sufficient
since
it doesn't really know that the underlying device is an NVME and NVME
devices
use different scheme for naming partition device entries (p vs.
just )

In this bug, we will teach curtin to detect NVME devices and pick the
correct partition dev path
if the config does _NOT_ include a specified 'number' value.

I'll open a MAAS task in this bug to help track if MAAS itself needs to
know a device is an NVME
and then specify the 'number' differently ('p1' vs '1').


--
> You received this bug notification because you are subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> https://bugs.launchpad.net/bugs/1401190
>
> Title:
>   curtin makes assumptions about partition names on all devices
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions
>

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify 

Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices

[Ryan Harper]

On Mon, Mar 7, 2016 at 2:15 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> Hi Ryan,
>
> Here you go
>
> /var/lib/cloud/instance/scripts/part-001 extract
>
> cd curtin
>
> cat configs/config-000.cfg
> #cloud-config
> …
> ...
> partitioning_commands:
>   builtin: [curtin, block-meta, custom]
> storage:
>   config:
>   - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
> disk, wipe: superblock}
>   - {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 'p1',
> offset: 4194304B, size: 128026935296B, type: partition, wipe: superblock}
>   - {fstype: ext4, id: nvme0n1p1_format, label: 'rootfs', type: format,
> path: /dev/nvme0n1p1, volume: nvme0n1p1}
>   version: 1
>
> bin/curtin --showtrace --install-deps install
> --config=configs/config-000.cfg
> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
> Creating new GPT entries.
> The operation has completed successfully.
> An error occured handling 'nvme0n1p1': IOError - [Errno 2] No such file or
> directory: '/sys/block/nvme0n1/nvme0n1None/size'
> Traceback (most recent call last):
>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
>   File "curtin/commands/block_meta.py", line 62, in block_meta
> meta_custom(args)
>   File "curtin/commands/block_meta.py", line 1083, in meta_custom
> handler(command, storage_config_dict)
>   File "curtin/commands/block_meta.py", line 565, in partition_handler
> with open(os.path.join(previous_partition, "size"), "r") as fp:
> IOError: [Errno 2] No such file or directory:
> '/sys/block/nvme0n1/nvme0n1None/size'
> [Errno 2] No such file or directory: '/sys/block/nvme0n1/nvme0n1None/size'
> Installation failed with exception: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: 'Creating new GPT entries.\nThe operation has completed
> successfully.\nAn error occured handling \'nvme0n1p1\': IOError - [Errno 2]
> No such file or directory:
> \'/sys/block/nvme0n1/nvme0n1None/size\'\nTraceback (most recent call
> last):\n  File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in
> main\nret = args.func(args)\n  File "curtin/commands/block_meta.py",
> line 62, in block_meta\nmeta_custom(args)\n  File
> "curtin/commands/block_meta.py", line 1083, in meta_custom\n
> handler(command, storage_config_dict)\n  File
> "curtin/commands/block_meta.py", line 565, in partition_handler\nwith
> open(os.path.join(previous_partition, "size"), "r") as fp:\nIOError: [Errno
> 2] No such file or directory:
> \'/sys/block/nvme0n1/nvme0n1None/size\'\n[Errno 2] No such file or
> directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\n'
> Stderr: ''
> Traceback (most recent call last):
>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
>   File "curtin/commands/install.py", line 399, in cmd_install
> raise e
>


OK, no need to let you continue to debug getting curtin partition handling
to learn about NVME.

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Rob Sanderson]

Hi Ryan,

Here you go

/var/lib/cloud/instance/scripts/part-001 extract

cd curtin

cat configs/config-000.cfg
#cloud-config
…
...
partitioning_commands:
  builtin: [curtin, block-meta, custom]
storage:
  config:
  - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type: disk, 
wipe: superblock}
  - {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 'p1', offset: 
4194304B, size: 128026935296B, type: partition, wipe: superblock}
  - {fstype: ext4, id: nvme0n1p1_format, label: 'rootfs', type: format, path: 
/dev/nvme0n1p1, volume: nvme0n1p1}
  version: 1

bin/curtin --showtrace --install-deps install --config=configs/config-000.cfg 
http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
Creating new GPT entries.
The operation has completed successfully.
An error occured handling 'nvme0n1p1': IOError - [Errno 2] No such file or 
directory: '/sys/block/nvme0n1/nvme0n1None/size'
Traceback (most recent call last):
  File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
ret = args.func(args)
  File "curtin/commands/block_meta.py", line 62, in block_meta
meta_custom(args)
  File "curtin/commands/block_meta.py", line 1083, in meta_custom
handler(command, storage_config_dict)
  File "curtin/commands/block_meta.py", line 565, in partition_handler
with open(os.path.join(previous_partition, "size"), "r") as fp:
IOError: [Errno 2] No such file or directory: 
'/sys/block/nvme0n1/nvme0n1None/size'
[Errno 2] No such file or directory: '/sys/block/nvme0n1/nvme0n1None/size'
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: 'Creating new GPT entries.\nThe operation has completed 
successfully.\nAn error occured handling \'nvme0n1p1\': IOError - [Errno 2] No 
such file or directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\nTraceback 
(most recent call last):\n  File "/home/ubuntu/curtin/curtin/commands/main.py", 
line 209, in main\nret = args.func(args)\n  File 
"curtin/commands/block_meta.py", line 62, in block_meta\n
meta_custom(args)\n  File "curtin/commands/block_meta.py", line 1083, in 
meta_custom\nhandler(command, storage_config_dict)\n  File 
"curtin/commands/block_meta.py", line 565, in partition_handler\nwith 
open(os.path.join(previous_partition, "size"), "r") as fp:\nIOError: [Errno 2] 
No such file or directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\n[Errno 2] 
No such file or directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\n'
Stderr: ''
Traceback (most recent call last):
  File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
ret = args.func(args)
  File "curtin/commands/install.py", line 399, in cmd_install
raise e
ProcessExecutionError: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: 'Creating new GPT entries.\nThe operation has completed 
successfully.\nAn error occured handling \'nvme0n1p1\': IOError - [Errno 2] No 
such file or directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\nTraceback 
(most recent call last):\n  File "/home/ubuntu/curtin/curtin/commands/main.py", 
line 209, in main\nret = args.func(args)\n  File 
"curtin/commands/block_meta.py", line 62, in block_meta\n
meta_custom(args)\n  File "curtin/commands/block_meta.py", line 1083, in 
meta_custom\nhandler(command, storage_config_dict)\n  File 
"curtin/commands/block_meta.py", line 565, in partition_handler\nwith 
open(os.path.join(previous_partition, "size"), "r") as fp:\nIOError: [Errno 2] 
No such file or directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\n[Errno 2] 
No such file or directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\n'
Stderr: ''
Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: 'Creating new GPT entries.\nThe operation has completed 
successfully.\nAn error occured handling \'nvme0n1p1\': IOError - [Errno 2] No 
such file or directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\nTraceback 
(most recent call last):\n  File "/home/ubuntu/curtin/curtin/commands/main.py", 
line 209, in main\nret = args.func(args)\n  File 
"curtin/commands/block_meta.py", line 62, in block_meta\n
meta_custom(args)\n  File "curtin/commands/block_meta.py", line 1083, in 
meta_custom\nhandler(command, storage_config_dict)\n  File 
"curtin/commands/block_meta.py", line 565, in partition_handler\nwith 
open(os.path.join(previous_partition, "size"), "r") as fp:\nIOError: [Errno 2] 
No such file or directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\n[Errno 2] 
No such file or directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\n'
Stderr: ''

Cheers,
Rob

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

Title:
  curtin makes assumptions about partition names on 

[Bug 1401190] Re: curtin makes assumptions about partition names on all devices

[Rob Sanderson]

Also worth noting that curtin runs:

curtin --install-deps install --config=configs/config-000.cfg
--config=configs/config-001.cfg --config=configs/config-002.cfg
--config=configs/config-003.cfg --config=configs/config-004.cfg
http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-
tgz

and  config-002.cfg contains the nvme device (unrelated to the above but
looks like it will cause problems in the next step i.e. once we can get
curtin to select the correct partition)


cat configs/config-002.cfg
partitioning_commands:
  builtin: [curtin, block-meta, custom]
storage:
  config:
  - {id: sdc, model: Samsung SSD 840, name: sdc, serial: S1D9NSAFB19195M, type: 
disk,
wipe: superblock}
  - {id: sda, model: ST2000DM001-1CH1, name: sda, serial: Z3409QB2, type: disk, 
wipe: superblock}
  - {id: sdb, model: ST2000DM001-1CH1, name: sdb, serial: Z3409S81, type: disk, 
wipe: superblock}
  - {grub_device: true, id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: 
msdos,
type: disk, wipe: superblock}
  - {device: nvme0n1, id: nvme0n1-part1, name: nvme0n1-part1, number: 1, 
offset: 4194304B,
size: 128026935296B, type: partition, uuid: 
edf17540-d929-41cc-85de-c4df78802b8d,
wipe: superblock}
  - {fstype: ext4, id: nvme0n1-part1_format, label: '', type: format, uuid: 
ce3b35c2-48ee-4d6f-9b20-0ff9642b2961,
volume: nvme0n1-part1}
  - {device: nvme0n1-part1_format, id: nvme0n1-part1_mount, path: /, type: 
mount}
  version: 1

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+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 1553261] Re: [FFe] Standing FFe for MAAS 2.0

[Stéphane Graber]

Ok, I'm assuming you meant "2.0 alpha" in the updated description.

Anyway, sounds fine to me, approved.

** Changed in: maas (Ubuntu)
   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/1553261

Title:
  [FFe] Standing FFe for MAAS 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1553261/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Rob Sanderson]

OK, just recommissioning the node so I can retest. 20 mins!

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Rob Sanderson]

Hi Ryan,

Thanks, let me know if you need me to make any changes or run through
any tests.

A quick question if I may: How is the config generated when the node is
deploying? I have found that storage config in curtin_userdata on the
maas server appears to be ignored or clobbered e.g.

If I execute: /var/lib/cloud/instance/scripts/part-001 # fails due to bug
cd curtin

cat configs/config-000.cfg # I see the storage config I have set on the
maas server in curtin_userdata

#cloud-config
...
...

partitioning_commands:
  builtin: [curtin, block-meta, custom]
storage:
  config:
  - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type: disk, 
wipe: superblock}
  - {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 1, offset: 
4194304B, size: 128026935296B, type: partition, wipe: superblock}
  - {fstype: ext4, id: nvme0n1p1_format, label: 'rootfs', type: format, path: 
/dev/nvme0n1p1, volume: nvme0n1p1}
  version: 1

cat configs/config-002.cfg # appears to be the device(s) that are found
during commissioning

partitioning_commands:
  builtin: [curtin, block-meta, custom]
storage:
  config:
  - {grub_device: true, id: sdc, model: Samsung SSD 840, name: sdc, ptable: 
gpt, serial: S1D9NSAFB19195M,
type: disk, wipe: superblock}
  - {device: sdc, id: sdc-part1, name: sdc-part1, number: 1, offset: 4194304B, 
size: 1000198897664B,
type: partition, uuid: 8bcce503-ad8f-495e-a158-669829585db2, wipe: 
superblock}
  - {fstype: ext4, id: sdc-part1_format, label: '', type: format, uuid: 
0195af9d-764d-4b35-8e53-07573aa4c057,
volume: sdc-part1}
  - {device: sdc-part1_format, id: sdc-part1_mount, path: /, type: mount}
  version: 1
...
...


I was trying to test an install to one of the other disks which also
failed.

I had to remove the nvme device and 2 other devices from the web ui as
configs/config-002.cfg had every disk listed, including the nvme device
which I had specified in curtin_userdata. The config data is that from
commissioning.

I also noted that despite me selecting a different boot device that it
was still trying to install grub to sda.

Does this sound like another bug with curtin or should I raise it with
the maas project?

Cheers,
Rob

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+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 1554195] [NEW] Nova (juno) ignores logging_*_format_string in syslog output

[George Shuklin]

Public bug reported:

Nova in juno ignores following settings in configuration file ([DEFAULT] 
section):
logging_context_format_string
logging_default_format_string
logging_debug_format_suffix
logging_exception_prefix

when sending logs via syslog. Log entries on stderr / in log files are
fine (use logging_*_format).

Steps to reproduce:

1. set up custom logging stings and enable syslog:

[DEFAULT]
logging_default_format_string=MYSTYLE-DEFAULT-%(message)s
logging_context_format_string=MYSTYLE-CONTEXT-%(message)s
use_syslog=true

2. restart nova and perform some actions

3. Check the syslog content

Expected behaviour: MYSTYLE- prefix in all messages.
Actual behaviour: no changes in log message styles.

This bug is specific to Juno version of nova.

** Affects: nova
 Importance: Undecided
 Status: New

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

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

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

Title:
  Nova (juno) ignores logging_*_format_string in syslog output

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1554195/+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 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory

[Paul Gevers]

Hi Andres,

On 07-03-16 06:07, Andres Rodriguez wrote:
> Sorry for not being clear enough.

NP, as long as you follow up on questions that is ok.

> The actual issue/concern I have is:
> 
> stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No
> such file or directory

Ack. I have a belly feeling that this may be related to the
implementation in ucf of Debian wish list bug 812321¹. Can you try once
again after you "touch /etc/dbconfig-common/maas-region-controller.conf".

> Now, the way I'm reproducing this issue right now is an install. I have
> remove/purged all the packages, include dbconfig common packages and
> made sure that /etc/dbconfig-common doesn't exist :

This looks like dbconfig-common isn't cleaning up properly on purge and
keeps the file registered with ucf. Weird, I'll try to investigate, but
I do purging a lot with all kind of example packages in my test suite²
and have never seen this before.

> The installation resumes, and It asks me the question to:
http://pastebin.ubuntu.com/15319155/

Right. As expected, these are questions from ucf. So it may be that the
issue lies there.

> Right after answering the questions (no matter if I say install the
> package maintainer's version  or  keep the local version currently
> installed) , it is always the same result:
> 
> Setting up maas-region-controller (2.0.0~alpha1+bzr4736-0ubuntu1~xenial2) ...
> dbconfig-common: writing config to 
> /etc/dbconfig-common/maas-region-controller.conf
> stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such 
> file or directory

That at least is a bug in ucf. When you answer to use the package
maintainers version, it must create the file as requested. So I guess we
could at least file an additional bug against ucf. But let's wait until
we find out if there isn't just one issue here.

> As you can see, the file doesn't get created. Now, what I'm really
> wondering if is there is only an issue in systems where dbconfig-common
> was first upgraded to the latest version  (2.0.3), and not on a freshly
> installed system where dbconfig-common is latest, as I've not been able
> to reproduce this on a freshly installed system yet.

As said, I suspect this may be because the file is still registered with
ucf. During install (after purge or on a clean system) ucf should not
need to ask the question. It only should do that when there once was
already a file (either still is or ucf knows that the admin has deleted
the file).

> Now, to answer your last question, the question raised by UCF was never there 
> because we preseed the following:
> 
> set_question maas-region-controller/dbconfig-install true

Doesn't look related. But how ugly is this, anyways. This means that you
are preventing an admin from defering the setup to later, e.g. because
she doesn't have the admin rights on the database he wants to use. By
the way, you do know that when an admin installs dbconfig-no-thanks,
dbconfig-common will not run, irrespective of your preseeding.

> Or maybe, the preseeding doesn't really matter and we just have never
> gotten into a similar situation, hence it never really has been shown
> before.

As said, this may be related to an updated ucf. I'll try to reproduce.

Paul

¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812321
² https://ci.debian.net/packages/d/dbconfig-common/unstable/amd64/ (test
log; test case install-examples)


** Bug watch added: Debian Bug tracker #812321
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812321

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

Title:
  dbconfig-common: writing config to /etc/dbconfig-common/maas-region-
  controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-
  controller.conf': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Ryan Harper]

One more try, lets specify the partition "number" as 'p1' instead.

- {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 'p1', offset:
4194304B, size: 128026935296B, type: partition, uuid:
e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}


On Mon, Mar 7, 2016 at 1:24 PM, Ryan Harper 
wrote:

> OK; thanks.  I need to work with nvme devices on Xenial;  it looks like
> the storage naming rules for partitions are different for NVME devices (p1,
> p2, p3) versus other disks (1, 2, 3 4);
>
>
> On Mon, Mar 7, 2016 at 12:54 PM, Rob Sanderson <1401...@bugs.launchpad.net
> > wrote:
>
>> Hi Ryan,
>>
>> I have tried that but no luck.
>>
>> Config using curtin defaults:
>>
>> --
>> cat configs/config-002.cfg
>>
>> partitioning_commands:
>>   builtin: [curtin, block-meta, custom]
>> storage:
>>   config:
>>   - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
>> disk, wipe: superblock}
>>   - {device: nvme0n1, id: nvme0n1-part1, name: nvme0n1-part1, number: 1,
>> offset: 4194304B, size: 128026935296B, type: partition, uuid:
>> e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
>>   - {fstype: ext4, id: nvme0n1-part1_format, label: 'rootfs', type:
>> format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877, volume: nvme0n1-part1,
>> path: /dev/nvme0n1p1}
>>   - {device: nvme0n1-part1_format, id: nvme0n1-part1_mount, path: /,
>> type: mount}
>>   version: 1
>>
>> bin/curtin --showtrace --install-deps install
>> --config=configs/config-002.cfg
>>
>>
>> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
>> Creating new GPT entries.
>> The operation has completed successfully.
>> The operation has completed successfully.
>> An error occured handling 'nvme0n1-part1_format': ValueError -
>> '/dev/nvme0n11': no such file or directory
>> Traceback (most recent call last):
>>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
>> ret = args.func(args)
>>   File "curtin/commands/block_meta.py", line 62, in block_meta
>> meta_custom(args)
>>   File "curtin/commands/block_meta.py", line 1083, in meta_custom
>> handler(command, storage_config_dict)
>>   File "curtin/commands/block_meta.py", line 672, in format_handler
>> mkfs.mkfs_from_config(volume_path, info)
>>   File "curtin/block/mkfs.py", line 207, in mkfs_from_config
>> label=info.get('label'))
>>   File "curtin/block/mkfs.py", line 145, in mkfs
>> raise ValueError("'%s': no such file or directory" % path)
>> ValueError: '/dev/nvme0n11': no such file or directory
>> '/dev/nvme0n11': no such file or directory
>> Installation failed with exception: Unexpected error while running
>> command.
>> Command: ['curtin', 'block-meta', 'custom']
>> Exit code: 3
>> Reason: -
>> Stdout: 'Creating new GPT entries.\nThe operation has completed
>> successfully.\nThe operation has completed successfully.\nAn error occured
>> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
>> file or directory\nTraceback (most recent call last):\n  File
>> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
>> args.func(args)\n  File "curtin/commands/block_meta.py", line 62, in
>> block_meta\nmeta_custom(args)\n  File "curtin/commands/block_meta.py",
>> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
>> File "curtin/commands/block_meta.py", line 672, in format_handler\n
>> mkfs.mkfs_from_config(volume_path, info)\n  File "curtin/block/mkfs.py",
>> line 207, in mkfs_from_config\nlabel=info.get(\'label\'))\n  File
>> "curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no
>> such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such
>> file or directory\n\'/dev/nvme0n11\': no such file or directory\n'
>> Stderr: ''
>> Traceback (most recent call last):
>>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
>> ret = args.func(args)
>>   File "curtin/commands/install.py", line 399, in cmd_install
>> raise e
>> ProcessExecutionError: Unexpected error while running command.
>> Command: ['curtin', 'block-meta', 'custom']
>> Exit code: 3
>> Reason: -
>> Stdout: 'Creating new GPT entries.\nThe operation has completed
>> successfully.\nThe operation has completed successfully.\nAn error occured
>> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
>> file or directory\nTraceback (most recent call last):\n  File
>> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
>> args.func(args)\n  File "curtin/commands/block_meta.py", line 62, in
>> block_meta\nmeta_custom(args)\n  File "curtin/commands/block_meta.py",
>> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
>> File "curtin/commands/block_meta.py", line 672, in format_handler\n
>> mkfs.mkfs_from_config(volume_path, info)\n  File 

[Bug 1553237] Re: Cannot stop samba service

[Tristan Grimaux]

I marked it as a security bug because changes in Samba configuration,
that might have security changes, will not be taken into effect until
the server host is re-initiated

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

Title:
  Cannot stop samba service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1553237/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Ryan Harper]

OK; thanks.  I need to work with nvme devices on Xenial;  it looks like the
storage naming rules for partitions are different for NVME devices (p1, p2,
p3) versus other disks (1, 2, 3 4);


On Mon, Mar 7, 2016 at 12:54 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> Hi Ryan,
>
> I have tried that but no luck.
>
> Config using curtin defaults:
>
> --
> cat configs/config-002.cfg
>
> partitioning_commands:
>   builtin: [curtin, block-meta, custom]
> storage:
>   config:
>   - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
> disk, wipe: superblock}
>   - {device: nvme0n1, id: nvme0n1-part1, name: nvme0n1-part1, number: 1,
> offset: 4194304B, size: 128026935296B, type: partition, uuid:
> e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
>   - {fstype: ext4, id: nvme0n1-part1_format, label: 'rootfs', type:
> format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877, volume: nvme0n1-part1,
> path: /dev/nvme0n1p1}
>   - {device: nvme0n1-part1_format, id: nvme0n1-part1_mount, path: /, type:
> mount}
>   version: 1
>
> bin/curtin --showtrace --install-deps install
> --config=configs/config-002.cfg
>
> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
> Creating new GPT entries.
> The operation has completed successfully.
> The operation has completed successfully.
> An error occured handling 'nvme0n1-part1_format': ValueError -
> '/dev/nvme0n11': no such file or directory
> Traceback (most recent call last):
>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
>   File "curtin/commands/block_meta.py", line 62, in block_meta
> meta_custom(args)
>   File "curtin/commands/block_meta.py", line 1083, in meta_custom
> handler(command, storage_config_dict)
>   File "curtin/commands/block_meta.py", line 672, in format_handler
> mkfs.mkfs_from_config(volume_path, info)
>   File "curtin/block/mkfs.py", line 207, in mkfs_from_config
> label=info.get('label'))
>   File "curtin/block/mkfs.py", line 145, in mkfs
> raise ValueError("'%s': no such file or directory" % path)
> ValueError: '/dev/nvme0n11': no such file or directory
> '/dev/nvme0n11': no such file or directory
> Installation failed with exception: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: 'Creating new GPT entries.\nThe operation has completed
> successfully.\nThe operation has completed successfully.\nAn error occured
> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
> file or directory\nTraceback (most recent call last):\n  File
> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
> args.func(args)\n  File "curtin/commands/block_meta.py", line 62, in
> block_meta\nmeta_custom(args)\n  File "curtin/commands/block_meta.py",
> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
> File "curtin/commands/block_meta.py", line 672, in format_handler\n
> mkfs.mkfs_from_config(volume_path, info)\n  File "curtin/block/mkfs.py",
> line 207, in mkfs_from_config\nlabel=info.get(\'label\'))\n  File
> "curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no
> such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such
> file or directory\n\'/dev/nvme0n11\': no such file or directory\n'
> Stderr: ''
> Traceback (most recent call last):
>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
>   File "curtin/commands/install.py", line 399, in cmd_install
> raise e
> ProcessExecutionError: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: 'Creating new GPT entries.\nThe operation has completed
> successfully.\nThe operation has completed successfully.\nAn error occured
> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
> file or directory\nTraceback (most recent call last):\n  File
> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
> args.func(args)\n  File "curtin/commands/block_meta.py", line 62, in
> block_meta\nmeta_custom(args)\n  File "curtin/commands/block_meta.py",
> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
> File "curtin/commands/block_meta.py", line 672, in format_handler\n
> mkfs.mkfs_from_config(volume_path, info)\n  File "curtin/block/mkfs.py",
> line 207, in mkfs_from_config\nlabel=info.get(\'label\'))\n  File
> "curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no
> such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such
> file or directory\n\'/dev/nvme0n11\': no such file or directory\n'
> Stderr: ''
> Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> 

[Bug 1553237] Re: Cannot stop samba service

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security 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/1553237

Title:
  Cannot stop samba service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1553237/+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 1554186] [NEW] walinuxagent ephemeral warning lacks full command for removal of file

[Ben Howard]

Public bug reported:

The walinuxagent ephemeral warning lacks the full command for removal of
the DATALOSS_WARNING_README.txt written to the ephemeral device.

** Affects: walinuxagent (Ubuntu)
 Importance: Medium
 Assignee: Ben Howard (utlemming)
 Status: In Progress

** Changed in: walinuxagent (Ubuntu)
 Assignee: (unassigned) => Ben Howard (utlemming)

** Changed in: walinuxagent (Ubuntu)
   Importance: Undecided => Medium

** Changed in: walinuxagent (Ubuntu)
   Status: New => In Progress

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

Title:
  walinuxagent ephemeral warning lacks full command for removal of file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1554186/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Rob Sanderson]

Hi Ryan,

I have tried that but no luck.

Config using curtin defaults:
--
cat configs/config-002.cfg

partitioning_commands:
  builtin: [curtin, block-meta, custom]
storage:
  config:
  - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type: disk, 
wipe: superblock}
  - {device: nvme0n1, id: nvme0n1-part1, name: nvme0n1-part1, number: 1, 
offset: 4194304B, size: 128026935296B, type: partition, uuid: 
e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
  - {fstype: ext4, id: nvme0n1-part1_format, label: 'rootfs', type: format, 
uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877, volume: nvme0n1-part1, path: 
/dev/nvme0n1p1}
  - {device: nvme0n1-part1_format, id: nvme0n1-part1_mount, path: /, type: 
mount}
  version: 1

bin/curtin --showtrace --install-deps install
--config=configs/config-002.cfg

http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
Creating new GPT entries.
The operation has completed successfully.
The operation has completed successfully.
An error occured handling 'nvme0n1-part1_format': ValueError - '/dev/nvme0n11': 
no such file or directory
Traceback (most recent call last):
  File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
ret = args.func(args)
  File "curtin/commands/block_meta.py", line 62, in block_meta
meta_custom(args)
  File "curtin/commands/block_meta.py", line 1083, in meta_custom
handler(command, storage_config_dict)
  File "curtin/commands/block_meta.py", line 672, in format_handler
mkfs.mkfs_from_config(volume_path, info)
  File "curtin/block/mkfs.py", line 207, in mkfs_from_config
label=info.get('label'))
  File "curtin/block/mkfs.py", line 145, in mkfs
raise ValueError("'%s': no such file or directory" % path)
ValueError: '/dev/nvme0n11': no such file or directory
'/dev/nvme0n11': no such file or directory
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: 'Creating new GPT entries.\nThe operation has completed 
successfully.\nThe operation has completed successfully.\nAn error occured 
handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such file 
or directory\nTraceback (most recent call last):\n  File 
"/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret = 
args.func(args)\n  File "curtin/commands/block_meta.py", line 62, in 
block_meta\nmeta_custom(args)\n  File "curtin/commands/block_meta.py", line 
1083, in meta_custom\nhandler(command, storage_config_dict)\n  File 
"curtin/commands/block_meta.py", line 672, in format_handler\n
mkfs.mkfs_from_config(volume_path, info)\n  File "curtin/block/mkfs.py", line 
207, in mkfs_from_config\nlabel=info.get(\'label\'))\n  File 
"curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no 
such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such file or 
directory\n\'/dev/nvme0n11\': no such file or directory\n'
Stderr: ''
Traceback (most recent call last):
  File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
ret = args.func(args)
  File "curtin/commands/install.py", line 399, in cmd_install
raise e
ProcessExecutionError: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: 'Creating new GPT entries.\nThe operation has completed 
successfully.\nThe operation has completed successfully.\nAn error occured 
handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such file 
or directory\nTraceback (most recent call last):\n  File 
"/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret = 
args.func(args)\n  File "curtin/commands/block_meta.py", line 62, in 
block_meta\nmeta_custom(args)\n  File "curtin/commands/block_meta.py", line 
1083, in meta_custom\nhandler(command, storage_config_dict)\n  File 
"curtin/commands/block_meta.py", line 672, in format_handler\n
mkfs.mkfs_from_config(volume_path, info)\n  File "curtin/block/mkfs.py", line 
207, in mkfs_from_config\nlabel=info.get(\'label\'))\n  File 
"curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no 
such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such file or 
directory\n\'/dev/nvme0n11\': no such file or directory\n'
Stderr: ''
Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: 'Creating new GPT entries.\nThe operation has completed 
successfully.\nThe operation has completed successfully.\nAn error occured 
handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such file 
or directory\nTraceback (most recent call last):\n  File 
"/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret = 
args.func(args)\n  File "curtin/commands/block_meta.py", 

[Bug 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Landscape Builder]

** Tags removed: kanban-cross-team

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Andreas Hasenack]

I think the pollinate job is also ignoring https_proxy.

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Andreas Hasenack]

Sorry, pressed enter too quickly:


root@maaslds:/var/log/maas/proxy# grep entropy access.log
root@maaslds:/var/log/maas/proxy# dig +short entropy.ubuntu.com
91.189.94.10
91.189.94.24
root@maaslds:/var/log/maas/proxy# grep 91.189.94.10 access.log
root@maaslds:/var/log/maas/proxy# grep 91.189.94.24 access.log
root@maaslds:/var/log/maas/proxy# 

The proxy recorded no access for the entropy site ("entropy.ubuntu.com")

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1554152] Re: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Andreas Hasenack]

** Tags added: kanban-cross-team landscape

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

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1551421] Re: dpkg installation routine of dlm depends on corosync to be installed and started

[James Page]

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

** This bug has been marked a duplicate of bug 1248054
   [SRU] dlm package installation fails

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

Title:
  dpkg installation routine of dlm depends on corosync to be installed
  and started

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1551421/+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 1554152] [NEW] pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment

[Scott Moser]

Public bug reported:

cloud-init runs pollinate via 'cc_seed_random.py' config job.

Some points
a.) in addition to seeding via pollinate seed_random will seed the random 
device with data from the datasource if it is provided (azure and openstack 
provide a random seed for this purpose)
b.) we really want seed_random to run before ssh , so that keys are generated 
with good entropy in place.
c.) seed_random runs early via 'init_modules' mostly to accomplish 'b'.  
Unfortunately, network is not guaranteed at this point if the datasource is a 
'local' datasource (such as config drive).
e.) in many cases pollinate will not have access to https://entropy.ubuntu.com 
(due to firewall or disconnected)
f.) in xenial, cloud-init reports events to maas as they occur, and when this 
module fails, it reports that.
g.) maas marks nodes as failed deployment when cloud-init reports failure

End result, if you dont have access to entropy.ubuntu.com, then you fail
deployment.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cloud-init 0.7.7~bzr1176-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
NonfreeKernelModules: ufs qnx4 hfsplus hfs minix ntfs msdos
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Mon Mar  7 17:30:00 2016
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Affects: maas
 Importance: Undecided
 Status: New

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug uec-images xenial

** Also affects: cloud-init
   Importance: Undecided
   Status: New

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

** 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 cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1554152

Title:
  pollinate fails in many circumstances, cloud-init reports that
  failure, maas reports node failed deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+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 1491745] Re: Package does not ship dlm_stonith

[James Page]

** Changed in: dlm (Ubuntu)
   Status: New => Triaged

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

Title:
  Package does not ship dlm_stonith

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1491745/+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 1553253] Re: package dlm 4.0.1-0ubuntu4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[James Page]

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

** Changed in: dlm (Ubuntu)
   Status: New => Triaged

** Changed in: dlm (Ubuntu)
   Importance: Undecided => High

** This bug has been marked a duplicate of bug 1248054
   [SRU] dlm package installation fails

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

Title:
  package dlm 4.0.1-0ubuntu4 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1553253/+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 1554134] [NEW] [FFe] python-django-compressor 2.0

[James Page]

Public bug reported:

I'd like to rev django-compressor to 2.0; this is a single version jump
from 1.6 and brings some important improvements, but will require MIR's
for three extra packages:

- python-rjsmin
- python-rcssmin

These two where vendored into the django-compressor source tree.

- python-csscompressor

Most importantly this brings us inline with what the OpenStack project
are testing with upstream, which will minimize and bugs caused by a diff
in version in this component (supports the OpenStack dashboard).

>

Upstream changelog:

v2.0 (01/07/2015)
-

`Full Changelog `_

- Add Django 1.9 compatibility

- Remove official support for Django 1.4 and 1.7

- Add official support for Python 3.5

- Remove official support for Python 2.6

- Remove support for coffin and jingo

- Fix Jinja2 compatibility for Django 1.8+

- Stop bundling vendored versions of rcssmin and rjsmin, make them
proper dependencies

- Remove support for CSSTidy

- Remove support for beautifulsoup 3.

- Replace cssmin by csscompressor (cssmin is still available for
backwards-compatibility but points to rcssmin)

>

2.0 has been in Debian for some time; however for various reasons I've
not got to it prior to now.

Proposed merge changelog:

  * Merge from Debian unstable.  Remaining changes:
- d/p/disable-coffin-tests.patch: Dropped, no longer required as
  upstream dropped support for coffin.
- d/control: Drop BD's on django-discover-runner and csstidy; not
  required in Ubuntu.
- d/control: Drop BD's on coffin and jingo, no longer supported
  upstream.
- d/control: Drop (Build-)Depends on django-overextends and
  django-sekizai, as these are optional dependencies.
- d/p/disable-django-sekizai.patch: Skip django-sekizai if its not
  installed.

minimizing the dependency list by skipping some optional framework
support.

** Affects: python-django-compressor (Ubuntu)
 Importance: High
 Status: New

** Changed in: python-django-compressor (Ubuntu)
   Importance: Undecided => High

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

Title:
  [FFe] python-django-compressor 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-django-compressor/+bug/1554134/+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 1554122] [NEW] FFe: Sync python-pymysql 0.7.2-1 (main) from Debian unstable (main)

[Mattia Rizzolo]

Public bug reported:

Please sync python-pymysql 0.7.2-1 (main) from Debian unstable (main)

Explanation of FeatureFreeze exception:
among other things this new upstream releases makes pymysql compliant with newer
mysql/mariadb; as you may notice, the current package in xenial FTBFS.

Changelog entries since current xenial version 0.6.2-2:

python-pymysql (0.7.2-1) unstable; urgency=medium

  * New upstream version (Closes: #799776)
  * Fixed VCS URLs (https)
  * Removed patch test-datatypes.patch and test-issue-36.patch
(Applied upstream)
  * Added Build-Depends-Indep: python3-unittest2
  * Added patch skip_not_working_tests.patch
  * Standards-Version is 3.9.7 now (no change)
  * Reordered d/copyright
  * Added myself to d/copyright
  * Added myself as uploader
  * Added Debian tests
  * Added Build-Depends: dh-python

 -- Ondřej Nový   Sun, 06 Mar 2016 01:01:50 +0100

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

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

Title:
  FFe: Sync python-pymysql 0.7.2-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pymysql/+bug/1554122/+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 831487] Re: Dependency on package unattended-upgrades on Ubuntu Server

[Robie Basak]

Now that unattended-upgrades defaults to installing security updates in
Xenial, I think this needs more attention. In mitigation, one can
disable unattended-upgrades without removing the package (dpkg-
reconfigure may work, but certainly hitting the files in
/etc/apt/apt.conf.d will) but I understand that one can get more
confidence by just purging a package that provides unwanted
functionality.

Unless there's a good reason that unattended-upgrades must be a
dependency. Can it be a Recommends instead, or perhaps be seeded as a
Recommends directly?

** Tags added: rls-x-incoming

** Changed in: software-properties (Ubuntu)
Milestone: None => ubuntu-16.04

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

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

Title:
  Dependency on package unattended-upgrades on Ubuntu Server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/831487/+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 831487] [NEW] Dependency on package unattended-upgrades on Ubuntu Server

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Robie Basak (racb):

The package, which includes the always-useful add-apt-repository,
depends on package unattended-upgrades. This is not good on servers, as
you may want to add PPAs with the convenience of add-apt-repository but
still want to control everything that gets upgraded on the machine.

Tested on both Ubuntu 10.04 LTS and 11.04.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
Dependency on package unattended-upgrades on Ubuntu Server
https://bugs.launchpad.net/bugs/831487
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to the bug report.

-- 
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 1554098] Re: Rebase libseccomp from (2.2.3-3) -> 2.3.0

[dann frazier]

s390x support has been backported to Ubuntu 2.2.3 packages. Is there
some bug fix or additional functionality missing from that backport? If
so, I suggest we reframe/retitle this bug to be about that functionality
- that'll be more actionable than a new upstream version at this stage.

** Changed in: libseccomp (Ubuntu)
   Status: New => Incomplete

** Changed in: libseccomp (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Rebase libseccomp from (2.2.3-3) -> 2.3.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1554098/+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 1551558] Re: vmhgfs-fuse to open-vm-tools package

[AdlerHorst]

I installed the open-vm-tools and a

udo mount  -t  hgfs  .host:/ /mnt/hgfs

ends in

mount: unknown filesystem type 'vmhgfs'


Distributor ID: Ubuntu
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
Codename:   xenial


** Attachment added: "Printscreen of my installed packages"
   
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1551558/+attachment/4591671/+files/Bildschirmfoto1.png

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

Title:
  vmhgfs-fuse to open-vm-tools package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1551558/+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 1532659] Re: vmhgfs kernel module missing entirely on trusty

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: open-vm-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  vmhgfs kernel module missing entirely on trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1532659/+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 1554098] Re: Rebase libseccomp from (2.2.3-3) -> 2.3.0

[Gary Gaydos]

** Package changed: ubuntu => libseccomp (Ubuntu)

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

Title:
  Rebase libseccomp from (2.2.3-3) -> 2.3.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1554098/+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 1554098] [NEW] Rebase libseccomp from (2.2.3-3) -> 2.3.0

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #1 - Heinz-Werner Seeck  - 
2016-03-07 07:49:12 ==
Please upgrade to the newest level of libseccomp.
Due to the following statement from the website.

Version 2.3.0 - February 29, 2015
Added support for the s390 and s390x architectures

Getting the new version from: 
https://github.com/seccomp/libseccomp/releases

** Affects: libseccomp (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-138501 severity-high 
targetmilestone-inin1604
-- 
Rebase libseccomp from (2.2.3-3) -> 2.3.0
https://bugs.launchpad.net/bugs/1554098
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to libseccomp 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 1469143] Re: kpartx -d fails with image paths longer than 63 characters

[Simo Punnonen]

Tested the above scenario on vivid, appears to work

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

Title:
  kpartx -d fails with image paths longer than 63 characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1469143/+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 1502539] Re: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build

[Woden Cafe]

This is also affecting our environment.

When attempting to install vmware tools, it suggests using open-vm-
tools, so I do that instead, and then we encounter errors.

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

Title:
  open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1502539/+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 1401190] Re: curtin makes assumptions about partition names on all devices

[Ryan Harper]

Yeah, looks like the mkfs code is expecting you to include label: 'some
label' in the format dictionary.
Can you try injecting a label into the format dictionary:


 - {fstype: ext4, id: nvme0n1-part1_format, label: 'SOME_LABEL_HERE', type:
format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877,
volume: nvme0n1-part1}

This is a bug in curtin as label's aren't required.

On Sun, Mar 6, 2016 at 3:58 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> ls -la /dev/nvme0*
> crw--- 1 root root  10, 57 Mar  6 21:10 /dev/nvme0
> brw-rw 1 root disk 259,  0 Mar  6 21:44 /dev/nvme0n1
> brw-rw 1 root disk 259,  1 Mar  6 21:44 /dev/nvme0n1p1
>
> --
> You received this bug notification because you are subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> https://bugs.launchpad.net/bugs/1401190
>
> Title:
>   curtin makes assumptions about partition names on all devices
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions
>

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+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 1369465] Fix included in openstack/nova 12.0.2

[Doug Hellmann]

This issue was fixed in the openstack/nova 12.0.2 release.

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

Title:
  nova resize doesn't resize(extend) rbd disk files when using rbd disk
  backend

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1369465/+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 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

[Christopher Townsend]

I tried adding "lxc.include = /usr/share/lxc/config/nesting.conf" as I
didn't know this existed.  However, it didn't help.

As you say, I can create unprivileged containers as user ubuntu, I just
can't start them.  Are you able to start unprivileged containers as user
ubuntu?  If so, how are you starting them?  I need to start them from
the host's shell, so I'm doing something like this:

$ sudo lxc-attach -n test-libertine -- sudo -u ubuntu -H lxc-start -n
test

where test-libertine is the privileged container and test is the
unprivileged container.

Also, here is the privileged container's configuration file:

# Template used to create this container: /usr/share/lxc/templates/lxc-download
# Parameters passed to the template: -a amd64 -d ubuntu -r xenial
# For additional config options, please look at lxc.container.conf(5)

# Distribution configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.arch = x86_64

# Container specific configuration
lxc.rootfs = /var/lib/lxc/test-libertine/rootfs
lxc.utsname = test-libertine

# Network configuration
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:da:08:f7

lxc.aa_profile = lxc-container-default-with-nesting
lxc.include = /usr/share/lxc/config/nesting.conf


Here is the output of /proc/self/cgroup while in a shell inside the privileged 
container:

# cat /proc/self/cgroup 
11:devices:/
10:freezer:/
9:pids:/
8:memory:/
7:cpuset:/
6:hugetlb:/
5:blkio:/
4:net_cls,net_prio:/
3:perf_event:/
2:cpu,cpuacct:/
1:name=systemd:/

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

Title:
  Unprivileged nested Xenial container will not start inside a
  privileged Xenial container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+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 1553251] Re: USN-2915-1 introduced a regression in is_safe_url()

[Marc Deslauriers]

First round of regression fixes used incomplete patch. Proper upstream
commits are:

https://github.com/django/django/commit/ada7a4aefb9bec4c34667b511022be6057102f98
https://github.com/django/django/commit/552f03869ea7f3072b3fa19ffb6cb2d957fd8447

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

Title:
  USN-2915-1 introduced a regression in is_safe_url()

To manage notifications about this bug go to:
https://bugs.launchpad.net/django/+bug/1553251/+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 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values

[Tore Anderson]

I tested it on Vivid, and it does not work. The dev_loss_tmo and
fast_io_fail_tmo sysfs settings do *not* get set. More information on my
test environment below:

root@ucstest:~# cat /etc/multipath.conf
defaults {
  fast_io_fail_tmo 8
  dev_loss_tmo 1024
}
devices
  device {
vendor "HP.*"
product "P2000G3.*"
path_grouping_policy "multibus"
fast_io_fail_tmo 16
dev_loss_tmo 2048
  }
}
root@ucstest:~# multipath -ll
3600c0ff0001204a9d12b75510100 dm-0 HP  ,P2000G3 FC/iSCSI
size=30G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  |- 1:0:0:1 sdb 8:16 active ready running
  |- 1:0:1:1 sdc 8:32 active ready running
  |- 2:0:0:1 sdd 8:48 active ready running
  `- 2:0:1:1 sde 8:64 active ready running

I know for a fact that the device{} section is being applied, because if
I remove the path_grouping_policy keyword and restart multipathd, the
topology changes to one path per group:

root@ucstest:~# sed -i 's/path_grouping/#path_grouping/' /etc/multipath.conf
root@ucstest:~# systemctl restart multipath-tools.service
root@ucstest:~# multipath -ll
3600c0ff0001204a9d12b75510100 dm-0 HP  ,P2000G3 FC/iSCSI
size=30G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 1:0:1:1 sdc 8:32 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:0:1 sdd 8:48 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
  `- 2:0:1:1 sde 8:64 active ready running

After reverting that change and restarting again, I can confirm that my
config file timeout settings are being read by multipathd:

root@ucstest:~# multipathd -k'show config' | grep -B5 -A1 dev_loss_tmo
defaults {
verbosity 2
wwids_file /etc/multipath/wwids
fast_io_fail_tmo 8
dev_loss_tmo 1024
}
--
device {
vendor "HP.*"
product "P2000G3.*"
path_grouping_policy multibus
fast_io_fail_tmo 16
dev_loss_tmo 2048
}

However, they are *not* being applied to sysfs:

root@ucstest:~# grep . /sys/class/fc_remote_ports/rport-*/*tmo
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-2/fast_io_fail_tmo:off

Versions:

root@ucstest:~# dpkg -l kpartx multipath-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   
  ArchitectureDescription
+++-=-===-===-
ii  kpartx
0.4.9-3ubuntu12.15.04.2 amd64   create device 
mappings for partitions
ii  multipath-tools   
0.4.9-3ubuntu12.15.04.2 amd64   maintain 
multipath block device access

Tore

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

Title:
  DevLossTO, FastIoFailTO settings do not match multipath.conf expected
  values

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+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 1551601] Re: DPDK init scripts need some hardening against broken specifications in /etc/dpdk/interfaces

[ChristianEhrhardt]

** Patch added: "Updated revision of the debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1551601/+attachment/4591564/+files/dpdk_2.2.0-0ubuntu3-to-2.2.0-0ubuntu4.debdiff

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

Title:
  DPDK init scripts need some hardening against broken specifications in
  /etc/dpdk/interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1551601/+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 1551601] Re: DPDK init scripts need some hardening against broken specifications in /etc/dpdk/interfaces

[ChristianEhrhardt]

Since there was no update yet I wrapped in another minor enhancement that is 
tied directly with this LP Bug.
Git repository is updated as well.

** Patch removed: "upload for 2.2.0-0ubuntu4 fixing LP: #1551601, #1551767, 
#1551796, #1551752"
   
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1551601/+attachment/4586614/+files/dpdk_2.2.0-0ubuntu3-to-2.2.0-0ubuntu4.debdiff

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

Title:
  DPDK init scripts need some hardening against broken specifications in
  /etc/dpdk/interfaces

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

[Mauricio Faria de Oliveira]

The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.

-- 
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 1386637] Re: multipath shows non-mpath disks as being multipath

[Mauricio Faria de Oliveira]

The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.

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

Title:
  multipath shows non-mpath disks as being multipath

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1386637/+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 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values

[Mauricio Faria de Oliveira]

The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.

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

Title:
  DevLossTO, FastIoFailTO settings do not match multipath.conf expected
  values

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+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 1541902] Re: [FFE] Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM

[Breno Leitão]

I would like to justify this FFe as this is an important feature for
Ubuntu 16.04/ppc64el

[Technical Justification]
This feature enables GPU pass through to work decently on Ubuntu KVM. Without 
this feature, GPU pass through works with a very bad performance, which is 
completely unusable in production. This feature enables a huge performance 
improvement, allowing Ubuntu KVM deployment in production environments.

[ Customer justification]
There are numerous partners interested in this feature, and a real set of 
customers that will be taking benefit directly if this feature makes Ubuntu 
16.04 release.

[Testing plan]
This set of patch is being tested internally at IBM.

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

Title:
  [FFE] Enable DDW on qemu aiming GPU passthrough performance on Ubuntu
  KVM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1541902/+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 1541902] Re: Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM

[Breno Leitão]

** Changed in: qemu (Ubuntu)
   Status: Incomplete => Confirmed

** Summary changed:

- Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM
+ [FFE] Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM

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

Title:
  [FFE] Enable DDW on qemu aiming GPU passthrough performance on Ubuntu
  KVM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1541902/+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 1554009] Re: use after free and mem leak in lpm6

[ChristianEhrhardt]

One of the patches got an ack upstream, the other is still waiting for 
attention.
None is committed yet.

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

Title:
  use after free and mem leak in lpm6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1554009/+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 1553251] Re: USN-2915-1 introduced a regression in is_safe_url()

[Marc Deslauriers]

Ubuntu 12.04 LTS isn't affected by the regression.

** Changed in: python-django (Ubuntu Precise)
   Status: Confirmed => Invalid

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

Title:
  USN-2915-1 introduced a regression in is_safe_url()

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

[Launchpad Bug Tracker]

This bug was fixed in the package squid3 - 3.3.8-1ubuntu6.6

---
squid3 (3.3.8-1ubuntu6.6) trusty-security; urgency=medium

  [ Scott Moser ]
  * debian/patches/increase-default-forward-max-tries.patch:
change the default setting of 'forward_max_tries' from 10
to 25. (LP: #1547640)

  [ Marc Deslauriers ]
  * SECURITY UPDATE: denial of service via crafted UDP SNMP request
- debian/patches/CVE-2014-6270.patch: fix off-by-one in
  src/snmp_core.cc.
- CVE-2014-6270
  * SECURITY UPDATE: error handling vulnerability
- debian/patches/CVE-2016-2571.patch: better handling of huge response
  headers in src/http.cc.
- CVE-2016-2571
  * Fix security issues that only apply when package is rebuilt with the
enable-ssl flag, which is not the case in the Ubuntu archive.
- debian/patches/CVE-2014-0128.patch: denial of service via a crafted
  range request.
- debian/patches/CVE-2015-3455.patch: incorrect X509 server certificate
  domain matching.

 -- Marc Deslauriers   Fri, 04 Mar 2016
14:58:52 -0500

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package squid3 - 3.3.8-1ubuntu16.2

---
squid3 (3.3.8-1ubuntu16.2) wily-security; urgency=medium

  [ Scott Moser ]
  * debian/patches/increase-default-forward-max-tries.patch:
change the default setting of 'forward_max_tries' from 10
to 25. (LP: #1547640)

  [ Marc Deslauriers ]
  * SECURITY UPDATE: denial of service via crafted UDP SNMP request
- debian/patches/CVE-2014-6270.patch: fix off-by-one in
  src/snmp_core.cc.
- CVE-2014-6270
  * SECURITY UPDATE: error handling vulnerability
- debian/patches/CVE-2016-2571.patch: better handling of huge response
  headers in src/http.cc.
- CVE-2016-2571
  * Fix security issues that only apply when package is rebuilt with the
enable-ssl flag, which is not the case in the Ubuntu archive.
- debian/patches/CVE-2014-0128.patch: denial of service via a crafted
  range request.
- debian/patches/CVE-2015-3455.patch: incorrect X509 server certificate
  domain matching.

 -- Marc Deslauriers   Fri, 04 Mar 2016
14:59:48 -0500

** Changed in: squid3 (Ubuntu Trusty)
   Status: Triaged => Fix Released

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package squid3 - 3.1.19-1ubuntu3.12.04.6

---
squid3 (3.1.19-1ubuntu3.12.04.6) precise-security; urgency=medium

  * SECURITY UPDATE: denial of service via crafted UDP SNMP request
- debian/patches/CVE-2014-6270.patch: fix off-by-one in
  src/snmp_core.cc.
- CVE-2014-6270
  * SECURITY UPDATE: error handling vulnerability
- debian/patches/CVE-2016-2571.patch: better handling of huge response
  headers in src/http.cc.
- CVE-2016-2571
  * Fix security issue that only applies when package is rebuilt with the
enable-ssl flag, which is not the case in the Ubuntu archive.
- debian/patches/CVE-2014-0128.patch: denial of service via a crafted
  range request.
  * debian/patches/increase-default-forward-max-tries.patch:
change the default setting of 'forward_max_tries' from 10
to 25. (LP: #1547640)

 -- Marc Deslauriers   Fri, 04 Mar 2016
14:57:14 -0500

** Changed in: squid3 (Ubuntu Precise)
   Status: Triaged => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-0128

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-6270

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2571

** Changed in: squid3 (Ubuntu Wily)
   Status: Triaged => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-3455

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+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 1553251] Re: USN-2915-1 introduced a regression in is_safe_url()

[Launchpad Bug Tracker]

This bug was fixed in the package python-django - 1.7.9-1ubuntu5.3

---
python-django (1.7.9-1ubuntu5.3) wily-security; urgency=medium

  * SECURITY REGRESSION: is_safe_url() with non-unicode url (LP: #1553251)
- debian/patches/CVE-2016-2512-regression.patch: force url to unicode
  in django/utils/http.py, added test to
  tests/utils_tests/test_http.py.
- CVE-2016-2512

 -- Marc Deslauriers   Fri, 04 Mar 2016
11:06:58 -0500

** Changed in: python-django (Ubuntu Wily)
   Status: Confirmed => Fix Released

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

Title:
  USN-2915-1 introduced a regression in is_safe_url()

To manage notifications about this bug go to:
https://bugs.launchpad.net/django/+bug/1553251/+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 1553251] Re: USN-2915-1 introduced a regression in is_safe_url()

[Launchpad Bug Tracker]

This bug was fixed in the package python-django - 1.6.1-2ubuntu0.13

---
python-django (1.6.1-2ubuntu0.13) trusty-security; urgency=medium

  * SECURITY REGRESSION: is_safe_url() with non-unicode url (LP: #1553251)
- debian/patches/CVE-2016-2512-regression.patch: force url to unicode
  in django/utils/http.py, added test to
  tests/utils_tests/test_http.py.
- CVE-2016-2512

 -- Marc Deslauriers   Fri, 04 Mar 2016
11:07:40 -0500

** Changed in: python-django (Ubuntu Trusty)
   Status: Confirmed => Fix Released

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

Title:
  USN-2915-1 introduced a regression in is_safe_url()

To manage notifications about this bug go to:
https://bugs.launchpad.net/django/+bug/1553251/+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 1554031] Re: error: internal error: unable to execute QEMU command ‘block-commit’: Could not reopen file: Permission denied

[Jignasha]

** Description changed:

  $ uname -a
  Linux ubuntu-kilo 3.19.0-51-generic #57~14.04.1-Ubuntu SMP Fri Feb 19 
14:36:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  
  $ visrh version
  Compiled against library: libvirt 1.2.12
  Using library: libvirt 1.2.12
  Using API: QEMU 1.2.12
  Running hypervisor: QEMU 2.2.0
  
- $visrh blockcomit 
+ $ virsh blockcommit {{ vm_id }} vda --active --pivot --verbose
  unable to execute QEMU command ‘block-commit’: Could not reopen file: 
Permission denied
  
- blockcommit has above error 
- what is default security_driver used by qemu on ubuntu 
+ blockcommit has above error
+ what is default security_driver used by qemu on ubuntu
  & how we can configure rules to solve in right way

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

Title:
  error: internal error: unable to execute QEMU command ‘block-commit’:
  Could not reopen file: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1554031/+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 1554032] [NEW] debian-sys-maint password is unnecessary attack surface

[Robie Basak]

Public bug reported:

Now that we have auth_socket, we should stop using passwords for debian-
sys-maint and use auth_socket authentication instead. Then there is no
secret for an attacker to guess.

** Affects: mysql-5.6 (Ubuntu)
 Importance: Low
 Status: Triaged

** Changed in: mysql-5.6 (Ubuntu)
   Status: New => Triaged

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

Title:
  debian-sys-maint password is unnecessary attack surface

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1554032/+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 1553928] Re: postfix-pgsql SSL connection to postgres

[Ubuntu Foundations Team Bug Bot]

The attachment "postfix-2.11.0.pgsql.connstring.diff" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

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

Title:
  postfix-pgsql SSL connection to postgres

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1553928/+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 1554031] [NEW] error: internal error: unable to execute QEMU command ‘block-commit’: Could not reopen file: Permission denied

[Jignasha]

Public bug reported:

$ uname -a
Linux ubuntu-kilo 3.19.0-51-generic #57~14.04.1-Ubuntu SMP Fri Feb 19 14:36:55 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ visrh version
Compiled against library: libvirt 1.2.12
Using library: libvirt 1.2.12
Using API: QEMU 1.2.12
Running hypervisor: QEMU 2.2.0

$visrh blockcomit 
unable to execute QEMU command ‘block-commit’: Could not reopen file: 
Permission denied

blockcommit has above error 
what is default security_driver used by qemu on ubuntu 
& how we can configure rules to solve in right way

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

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

Title:
  error: internal error: unable to execute QEMU command ‘block-commit’:
  Could not reopen file: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1554031/+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 1554009] [NEW] use after free and mem leak in lpm6

[ChristianEhrhardt]

Public bug reported:

Debugging bundled autotests showed issues in DPDK 2.2.

Patches are sent upstream for discussion and should be integrated as add on 
delta to our 2.2 release.
http://dpdk.org/dev/patchwork/patch/11067/
http://dpdk.org/dev/patchwork/patch/11065/

Currently we are waiting for the upstream discussion to finish and apply.
Then we will pick and apply those as backport patches in packaging.

** Affects: dpdk (Ubuntu)
 Importance: Medium
 Assignee: ChristianEhrhardt (paelzer)
 Status: Triaged

** Changed in: dpdk (Ubuntu)
   Status: New => Triaged

** Changed in: dpdk (Ubuntu)
   Importance: Undecided => Medium

** Changed in: dpdk (Ubuntu)
 Assignee: (unassigned) => ChristianEhrhardt (paelzer)

** Changed in: dpdk (Ubuntu)
Milestone: None => ubuntu-16.04

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

Title:
  use after free and mem leak in lpm6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1554009/+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 1525662] Re: package samba-common 2:4.1.17+dfsg-4ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[David]

No info.. Sorry

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

Title:
  package samba-common 2:4.1.17+dfsg-4ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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