[Bug 1546312] Re: Please update to open-vm-tools 10.0.7

[John Savanyo]

In order to enable cloud-init to work on vSphere/ESXi, Ubuntu needs to
include open-vm-tools 10.0.7 or later. Can you please include this in
16.04 release. It does not appear to be included in Beta2.

Thanks,
John

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

Title:
  Please update to open-vm-tools 10.0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1546312/+subscriptions

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

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

[Serge Hallyn]

I'll try building the package source from kilo on the xenial host and
see if that succeeds.  I'm having doubts.

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

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

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

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

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

[Serge Hallyn]

Hm, building 2.2.0 (close to what is in the kilo cloud archive) doesn't
help.

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

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

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

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

[Bug 1562653] Re: Ubuntu 15.10: QEMU VM hang if memory >= 1T

[changlimin]

The issue is sloved after change cpuid[8008];

--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -2547,7 +2547,7 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index, 
uint32_t count,
 if (env->features[FEAT_8000_0001_EDX] & CPUID_EXT2_LM) {
 /* 64 bit processor */
 /* XXX: The physical address space is limited to 42 bits in exec.c. */
-*eax = 0x3028; /* 48 bits virtual, 40 bits physical */
+*eax = 0x3029; /* 48 bits virtual, 41 bits physical */
 } else {
 if (env->features[FEAT_1_EDX] & CPUID_PSE36) {
 *eax = 0x0024; /* 36 bits physical */

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

Title:
  Ubuntu 15.10: QEMU VM hang if memory >= 1T

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1562653/+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 1557852] Re: [needs-packaging] juju-mongodb3.2 in xenial, wily, and trusty

[Michael Hudson-Doyle]

I made a smaller testcase: http://paste.ubuntu.com/15573440/. I still
have no idea what's going on, but I think the patch in Curtis' branch is
a reasonable response to the issue.

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

Title:
  [needs-packaging] juju-mongodb3.2 in xenial, wily, and trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557852/+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 1557852] Re: [needs-packaging] juju-mongodb3.2 in xenial, wily, and trusty

[Michael Hudson-Doyle]

Something very odd is going on with the problem offset-outside-of-
bounds.patch is addressing. I hacked the offending source file down to
http://paste.ubuntu.com/15573220/.

This fails to compile with -O2:

ubuntu@promonarchy-remi:~/xenial-mongodb-3.2$ g++ -o foo.o -c -O2 -Werror 
-std=c++11 -Ibuild/opt -Isrc src/mongo/bson/bson_obj_test.cpp 
In file included from src/mongo/db/jsobj.h:49:0,
 from src/mongo/bson/bson_obj_test.cpp:28:
src/mongo/bson/bsonelement.h: In member function ‘virtual void 
{anonymous}::UnitTest__BSONObj__getFields::_doTest()’:
src/mongo/bson/bsonelement.h:231:23: error: offset outside bounds of constant 
string [-Werror]
 return data + 1;
   ^
cc1plus: all warnings being treated as errors

It succeeds with -O1 though. It _also_ succeeds with -O1 and all the
-fxxx flags that -O2 implies on top of -O1. It _also_ succeeds if almost
any line is removed from the file. But if you remove a few lines and
change it to -O3, it fails again. So I guess some threshold-based
optimization eventually transforms the code in the file into something
that triggers the warning. I'm not quite confident enough to call this a
compiler bug, but it's certainly user hostile.

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

Title:
  [needs-packaging] juju-mongodb3.2 in xenial, wily, and trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557852/+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 1547183] Re: Remove php5 specific packages from the archive

[Steve Langasek]

Removing packages from xenial:
php-pinba 1.0.0-2build6 in xenial
php5-pinba 1.0.0-2build6 in xenial amd64
php5-pinba 1.0.0-2build6 in xenial arm64
php5-pinba 1.0.0-2build6 in xenial armhf
php5-pinba 1.0.0-2build6 in xenial i386
php5-pinba 1.0.0-2build6 in xenial powerpc
php5-pinba 1.0.0-2build6 in xenial ppc64el
php5-pinba 1.0.0-2build6 in xenial s390x
Comment: php7 support not released, removed from Debian unstable; LP: #1547183
1 package successfully removed.


** Changed in: php-pinba (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove php5 specific packages from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/civicrm/+bug/1547183/+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 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

The proposed packaging updates are now available in Adam's PPA:



This includes:

* Switch from golang-go.net-dev to golang-x-net-dev as mentioned by ~jdstrand
* Use of Suggests to keep Juju 1.X tools around through upgrade from ~adconrad

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

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1545913] Re: [FFe] juju-core 2.0

[Richard Harding]

These updates were presented to slangasek and the point of the making
juju1 the default is the one point left that we requested feedback on.

Feedback from slangasek is that if we're not prepared to make juju1 the default 
then:
"upon upgrade, juju == juju2; if you want juju1, run juju-1.$fwibble instead"

The Juju team defers to the distro team in regards to Juju upgrades and
will move forward with this plan during updates and update the juju2
command such that if it detects you're a new juju2 user with existing
juju1 environments.yaml file we will direct you to the new command to
run as a helpful hint.

Please direct feedback on this decision to slangasek.

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

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1557852] Re: [needs-packaging] juju-mongodb3.2 in xenial, wily, and trusty

[Curtis Hovey]

Hi Robie

Attached are my changes. that I pushed to

lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2

> Thank you for the update. I've reviewed the patches now they have
> headers so I can follow what's going on. Most look OK. I'm unhappy
> with two:  1. arm64-immediate-delete-should-wait-cursor.patch IMHO
> inappropriately disables a test that correctly tests positive. This
> should be fixed properly, or allowed to FTBFS on arm64, or arm64
> builds need to be disabled. Happy to follow Ubuntu archive admin or
> release team guidance.

I revisited upstream bugs, commits and commits from other repos. I
found a patch that affected the failing test. In my experience, only
arm64 was failing, but the upstream report implies the tests can
fail on many types of hardware.

https://github.com/mongodb/mongo/commit/b6d309a15215a9243f21eb33cc6bcb6fbca58e56.patch

I successfully built and tested xenial arm64, amd64, and ppc64el.

> 2. offset-outside-of-bounds.patch: tests disabled due to GCC-5. As
> noted this should be fixed properly and upstreamed. Perhaps this
> should be combined into disable-warnings.patch? Not sure if this is OK
> to upload or not. Happy to follow Ubuntu archive admin or release team
> guidance.

I can file an bug upstream. I am not inclined attempt this fix myself
as I have other tasks that I am told are higher priority.

> The changelog needs updating to match changes made based on 2.6 - I

I updated the changelog to match what I propose for juju-mongodb2.6

** Patch added: "changes for review"
   
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557852/+attachment/4618927/+files/juju-mongodb3.2-review1.diff

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

Title:
  [needs-packaging] juju-mongodb3.2 in xenial, wily, and trusty

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

[Serge Hallyn]

Thanks very much for testing.

I think I have a system I can use to try and bisect tonight/tomorrow.

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

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

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

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

Re: [Bug 1315888] Re: Zlib functions (gzopen etc.) are undefined while gzopen64 etc. exist

[Nish Aravamudan]

On 26.03.2016 [00:04:59 -], Heineken wrote:
> The test build at: https://launchpad.net/~nacc/+archive/ubuntu/lp1315888
> works fine, that you very much for your effort!

Thank you very much for you testing! I have been pretty heads-down with
PHP7 and 16.04, but will file a SRU as soon as I can.

-Nish

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

Title:
  Zlib functions (gzopen etc.) are undefined while gzopen64 etc. exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/php/+bug/1315888/+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 1545913] Re: [FFe] juju-core 2.0

[Richard Harding]

- adding a comment to the juju 2.0 FFe that clarifies that the juju
client is built and runs on all architectures, including 32bit.

Comment added under the heading Mongodb to this effect since that's
where the confusion derived from.


- document the process for avoiding a late stage FFe and package upload for 
16.10

Added section to the FFe under the heading "Future release planning"


- move the juju binary metapackage suggest juju-1.25 so that upgrades will make 
sure that juju 1 stays available

This change is made and new builds are being done.


- make juju1 the higher update-alternatives priority.

We cannot make this change due to direction from product management. We
have filed this for record under
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670.

We've also created the Juju bug to perform the update that outputs the 
mitigating messaging to help the user in the 2.0 Juju.
https://bugs.launchpad.net/juju-core/+bug/1564622


- trim the binary size of the juju package by reducing the duplication

See bug https://bugs.launchpad.net/juju-core/+bug/1564677 for the work
to perform this. This will be a goal of the next full release to perform
this action to reduce the Juju binary size.


- investigate the ability to perform stripping to reduce size

See bug https://bugs.launchpad.net/juju-core/+bug/1564662 for this work.
This will be a goal for the next full release to perform this action and
reduce the Juju binary size. However, we need time to validate that it
is 100% safe and we feel the risk is too high to push it through today.

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

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1557830] Re: [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

[Curtis Hovey]

I pushed a small change to the changelog
   * New upstream release (LP #1557830).
at
   lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6'

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

Title:
  [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+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 1564670] Re: After upgrade Juju 1.X should still be the default

[Richard Harding]

See bug https://bugs.launchpad.net/juju-core/+bug/1564622 for the fix in
Juju to properly output the messaging to the user.

** Description changed:

  When upgrading to Xenial the new default Juju version is going to be
  2.0.
  
  Because 2.0 clients are not compatible with 1.X environments, this means
  existing environments will be inaccessible unless the 1.X client is
  switched to. The plan is to give a warning when creating Juju 2
  configuration for the first time, something along the lines of:
  
- $ sudo apt-get update
- $ juju status
- WARNING Creating new juju 2 configuration.
- Use `update-alternatives --config juju` to switch for 1.X environments.
- $ juju status
- ERROR Unable to connect to model "".
- Please check your credentials or use 'juju bootstrap' to create a new model.
+ Feedback suggests that we should correct this by having juju 1.X be the
+ higher priority in update alternatives.
  
- There has been some concern that this is still too confusing and 1.X
- should remain the default juju without explicit user intervention.
+ Product management has give feedback that the preference it to push
+ toward the direction of Juju 2 at all times. Since this process would
+ default to Juju 1 if a Juju 2 users installs Juju 1 for legacy reasons,
+ we are instead going to implement the following:
+ 
+ $ sudo apt-get update
+ $ juju status
+ WARNING Creating new juju 2 configuration.
+ Use `update-alternatives --config juju` to switch for 1.X environments.
+ $ juju status
+ ERROR Unable to connect to model "".
+ Please check your credentials or use 'juju bootstrap' to create a new 
model.

** Description changed:

  When upgrading to Xenial the new default Juju version is going to be
  2.0.
  
  Because 2.0 clients are not compatible with 1.X environments, this means
  existing environments will be inaccessible unless the 1.X client is
  switched to. The plan is to give a warning when creating Juju 2
  configuration for the first time, something along the lines of:
  
  Feedback suggests that we should correct this by having juju 1.X be the
  higher priority in update alternatives.
  
  Product management has give feedback that the preference it to push
  toward the direction of Juju 2 at all times. Since this process would
  default to Juju 1 if a Juju 2 users installs Juju 1 for legacy reasons,
  we are instead going to implement the following:
  
- $ sudo apt-get update
- $ juju status
- WARNING Creating new juju 2 configuration.
- Use `update-alternatives --config juju` to switch for 1.X environments.
- $ juju status
- ERROR Unable to connect to model "".
- Please check your credentials or use 'juju bootstrap' to create a new 
model.
+ $ sudo apt-get update
+ $ juju status
+ WARNING Creating new juju 2 configuration.
+ Use `update-alternatives --config juju` to switch 
+ for 1.X environments.
+ $ juju status
+ ERROR Unable to connect to model "".
+ Please check your credentials or use 'juju bootstrap' to 
+ create a new model.

** Description changed:

  When upgrading to Xenial the new default Juju version is going to be
  2.0.
  
  Because 2.0 clients are not compatible with 1.X environments, this means
  existing environments will be inaccessible unless the 1.X client is
  switched to. The plan is to give a warning when creating Juju 2
  configuration for the first time, something along the lines of:
  
  Feedback suggests that we should correct this by having juju 1.X be the
  higher priority in update alternatives.
  
  Product management has give feedback that the preference it to push
  toward the direction of Juju 2 at all times. Since this process would
  default to Juju 1 if a Juju 2 users installs Juju 1 for legacy reasons,
  we are instead going to implement the following:
  
  $ sudo apt-get update
- $ juju status
+ 
+ $ juju status
  WARNING Creating new juju 2 configuration.
- Use `update-alternatives --config juju` to switch 
- for 1.X environments.
- $ juju status
+ Use `update-alternatives --config juju` to switch
+ for 1.X environments.
+ 
+ $ juju status
  ERROR Unable to connect to model "".
- Please check your credentials or use 'juju bootstrap' to 
- create a new model.
+ Please check your credentials or use 'juju bootstrap' to
+ create a new model.

** Also affects: juju-core
   Importance: Undecided
   Status: New

** No longer affects: juju-core

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

Title:
  After upgrade Juju 1.X should still be the default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670/+subscriptions

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

[Bug 1547183] Re: Remove php5 specific packages from the archive

[Nish Aravamudan]

While php-pinba has a branch with php7 support, it's unclear when/if
that will be released
(https://github.com/tony2001/pinba_extension/issues/23) and it's a leaf
package.

** Also affects: php-pinba (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove php5 specific packages from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/civicrm/+bug/1547183/+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 1564670] Re: After upgrade Juju 1.X should still be the default

[Richard Harding]

See https://bugs.launchpad.net/juju-core/+bug/1564622 for the reasoning
of this path.

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

Title:
  After upgrade Juju 1.X should still be the default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670/+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 1564662] Re: Juju binaries should be stripped

[Richard Harding]

This will be a target for the Juju team to update and verify that the
stripping of the binary is safe and passes all testing. This requires
building in some gating based on if the binary is golang vs gccgo.


** Also affects: juju-core
   Importance: Undecided
   Status: New

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
Milestone: None => 2.1.0

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

Title:
  Juju binaries should be stripped

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1564662/+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 1564670] [NEW] After upgrade Juju 1.X should still be the default

[Martin Packman]

Public bug reported:

When upgrading to Xenial the new default Juju version is going to be
2.0.

Because 2.0 clients are not compatible with 1.X environments, this means
existing environments will be inaccessible unless the 1.X client is
switched to. The plan is to give a warning when creating Juju 2
configuration for the first time, something along the lines of:

$ sudo apt-get update
$ juju status
WARNING Creating new juju 2 configuration.
Use `update-alternatives --config juju` to switch for 1.X environments.
$ juju status
ERROR Unable to connect to model "".
Please check your credentials or use 'juju bootstrap' to create a new model.

There has been some concern that this is still too confusing and 1.X
should remain the default juju without explicit user intervention.

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

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

Title:
  After upgrade Juju 1.X should still be the default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670/+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 1547183] Re: Remove php5 specific packages from the archive

[Steve Langasek]

Removing packages from xenial:
php-mysqlnd-ms 1.6.0-1build1 in xenial
php5-mysqlnd-ms 1.6.0-1build1 in xenial amd64
php5-mysqlnd-ms 1.6.0-1build1 in xenial arm64
php5-mysqlnd-ms 1.6.0-1build1 in xenial armhf
php5-mysqlnd-ms 1.6.0-1build1 in xenial i386
php5-mysqlnd-ms 1.6.0-1build1 in xenial powerpc
php5-mysqlnd-ms 1.6.0-1build1 in xenial ppc64el
php5-mysqlnd-ms 1.6.0-1build1 in xenial s390x
Comment: php5-only; LP: #1547183
1 package successfully removed.


** Changed in: php-mysqlnd-ms (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove php5 specific packages from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/civicrm/+bug/1547183/+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 1547183] Re: Remove php5 specific packages from the archive

[Steve Langasek]

Removing packages from xenial:
php-ps 1.3.7-1ubuntu2 in xenial
php5-ps 1.3.7-1ubuntu2 in xenial amd64
php5-ps 1.3.7-1ubuntu2 in xenial arm64
php5-ps 1.3.7-1ubuntu2 in xenial armhf
php5-ps 1.3.7-1ubuntu2 in xenial i386
php5-ps 1.3.7-1ubuntu2 in xenial powerpc
php5-ps 1.3.7-1ubuntu2 in xenial ppc64el
Comment: FTBFS, removed from Debian testing, php5-only; LP: #1547183
1 package successfully removed.


** Changed in: php-ps (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove php5 specific packages from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/civicrm/+bug/1547183/+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 1564662] [NEW] Juju binaries should be stripped

[Martin Packman]

Public bug reported:

Previously the juju team has been asked to strip the go binaries in the
distro packaging. Per bug 1265970 that was not possible as with go 1.2
it introduced bugs such as bug 1200255.

With go 1.6 in xenial, it may now be safe to strip the juju binaries,
but this needs testing on all architectures, including exercising the
reflect code.

See irc log for more background:



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

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

Title:
  Juju binaries should be stripped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564662/+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 1547183] Re: Remove php5 specific packages from the archive

[Nish Aravamudan]

php-ps has not been updated in PECL since 2013 and has a build-
dependency on a package unavailable since vivid (libgd2-xpm-dev).

** Also affects: php-ps (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove php5 specific packages from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/civicrm/+bug/1547183/+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 1564388] Re: mysqlnd is vulnerable to BACKRONYM (CVE-2015-3152)

[Seth Arnold]

MITRE assigned CVE-2015-8838: http://www.openwall.com/lists/oss-
security/2016/03/31/13

Thanks

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

** Summary changed:

- mysqlnd is vulnerable to BACKRONYM (CVE-2015-3152)
+ mysqlnd is vulnerable to BACKRONYM (CVE-2015-8838)

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

Title:
  mysqlnd is vulnerable to BACKRONYM (CVE-2015-8838)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1564388/+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 1545913] Re: [FFe] juju-core 2.0

[Richard Harding]

** Description changed:

  The juju team is requesting an FFE for juju-core. Juju2 represents API
  changes and new features and bugfixes for juju.  We are NOT requesting a
  place on any image for xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  Related FFes
  
  
  Required for Juju 2.0:
  
  juju-mongodb3.2: bug 1557852
  juju-mongodb2.6: bug 1557830
  juju-mongo-tools3.2: bug 1558336
  
  (see note below about mongodb for details)
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
  openstack: Already in universe, dep wait on conjure -> juju 2.0
  charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun 

[Bug 1534368] Re: HTTP/2 is not enabled for nginx-extras

[Seth Arnold]

Thomas and the nginx team have convinced me that nginx's http/2
implementation is widely used and mature enough to enable before 16.04
LTS release.

Thanks

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

Title:
  HTTP/2 is not enabled for nginx-extras

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1534368/+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 1545913] Re: [FFe] juju-core 2.0

[Richard Harding]

** Description changed:

  The juju team is requesting an FFE for juju-core. Juju2 represents API
  changes and new features and bugfixes for juju.  We are NOT requesting a
  place on any image for xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  Related FFes
  
  
  Required for Juju 2.0:
  
  juju-mongodb3.2: bug 1557852
  juju-mongodb2.6: bug 1557830
  juju-mongo-tools3.2: bug 1558336
  
  (see note below about mongodb for details)
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
  openstack: Already in universe, dep wait on conjure -> juju 2.0
  charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun 

[Bug 1564451] Re: User processes are counted towards systemd limit for sshd processes

[Seth Arnold]

I'm having trouble reproducing this. I started a few thousand /bin/sleep
commands and was able to log in via ssh as another user; the error
message when logging in again as my normal user account showed an error
message that looked appropriate.

In one ssh:
sarnold@sec-xenial-amd64:~$ for i in `seq 1 6000` ; do /bin/sleep 10 & done
...
[15813] 24043
[15814] 24044
[15815] 24045
-bash: fork: retry: Resource temporarily unavailable
-bash: fork: retry: Resource temporarily unavailable

In another terminal:
$ ssh -oControlPath=none  root@sec-xenial-amd64
Welcome to Ubuntu Xenial Xerus (development branch) (GNU/Linux 4.4.0-16-generic 
x86_64)

 * Documentation:  https://help.ubuntu.com/

0 packages can be updated.
0 updates are security updates.

Last login: Thu Mar 31 15:42:23 2016 from 192.168.122.1
root@sec-xenial-amd64:~# 

$ ssh -oControlPath=none  sec-xenial-amd64
shell request failed on channel 0

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

Title:
  User processes are counted towards systemd limit for sshd processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1564451/+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 1564451] Re: User processes are counted towards systemd limit for sshd processes

[Seth Arnold]

** Information type changed from Private Security to Public Security

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

Title:
  User processes are counted towards systemd limit for sshd processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1564451/+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 1528583] Re: [FFe] Please update to MySQL 5.7 series

[Matthias Klose]

** Tags removed: block-proposed

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

Title:
  [FFe] Please update to MySQL 5.7 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1528583/+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 1564518] Re: Illegal instruction when cross compiling for armv5

[Michael Hudson-Doyle]

Can you provide some more details?

 * Source of hello.go (although I can probably guess this one :-)
 * Output of "GOOS=linux GOARCH=arm GOARM=5 go build -x hello.go" for the 
packaged go and the official go
 * Binaries produced by the two above commands

I don't have access to any armv5 hw but I'll see what I can do.

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

Title:
  Illegal instruction when cross compiling for armv5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1564518/+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 1562918] Re: cloud-init does not create defined users

[Leander Janssen]

Please ignore my last comment (#4).

When specifying an explicit primary-group it should of course already exist, 
before useradd can create the user.
When removing the primary-group statement from the user definition the user is 
created just fine (including it's primary group with the same name as the user).

For me this has fixed the issue I've reported.

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

Title:
  cloud-init does not create defined users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1562918/+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 1562918] Re: cloud-init does not create defined users

[Leander Janssen]

When I remove the groups: part I get the following errors in the
/var/log/cloud-init.log:

Mar 31 22:35:45 test [CLOUDINIT] stages.py[DEBUG]: Running module users-groups 
() with frequency once-per-instance
Mar 31 22:35:45 test [CLOUDINIT] handlers.py[DEBUG]: start: 
init-network/config-users-groups: running config-users-groups with frequency 
once-per-instance
Mar 31 22:35:45 test [CLOUDINIT] util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/nocloud/sem/config_users_groups - wb: [420] 24 bytes
Mar 31 22:35:45 test [CLOUDINIT] helpers.py[DEBUG]: Running config-users-groups 
using lock ()
Mar 31 22:35:45 test [CLOUDINIT] __init__.py[DEBUG]: Adding user ansible
Mar 31 22:35:45 test [CLOUDINIT] util.py[DEBUG]: Running hidden command to 
protect sensitive input/output logstring: ['useradd', 'ansible', '--shell', 
'/bin/bash', '--gid', 'ansible', '--comment', 'Ansible', '--groups', 'sudo', 
'-m']
Mar 31 22:35:45 test [CLOUDINIT] util.py[WARNING]: Failed to create user ansible
Mar 31 22:35:46 test [CLOUDINIT] util.py[DEBUG]: Failed to create user 
ansible#012Traceback (most recent call last):#012  File 
"/usr/lib/python3/dist-packages/cloudinit/distros/__init__.py", line 406, in 
add_user#012util.subp(adduser_cmd, logstring=log_adduser_cmd)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/util.py", line 1704, in subp#012
cmd=args)#012cloudinit.util.ProcessExecutionError: Unexpected error while 
running command.#012Command: ['useradd', 'ansible', '--shell', '/bin/bash', 
'--gid', 'ansible', '--comment', 'Ansible', '--groups', 'sudo', '-m']#012Exit 
code: 6#012Reason: -#012Stdout: ''#012Stderr: "useradd: group 'ansible' does 
not exist\n"
Mar 31 22:35:46 test [CLOUDINIT] handlers.py[DEBUG]: finish: 
init-network/config-users-groups: FAIL: running config-users-groups with 
frequency once-per-instance
Mar 31 22:35:46 test [CLOUDINIT] util.py[WARNING]: Running module users-groups 
() failed
Mar 31 22:35:46 test [CLOUDINIT] util.py[DEBUG]: Running module users-groups 
() 
failed#012Traceback (most recent call last):#012  File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 735, in 
_run_modules#012freq=freq)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#012
return self._runners.run(name, functor, args, freq, clear_on_fail)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012
results = functor(*args)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/config/cc_users_groups.py", line 34, 
in handle#012cloud.distro.create_user(user, **config)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/distros/__init__.py", line 419, in 
create_user#012self.add_user(name, **kwargs)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/distros/__init__.py", line 409, in 
add_user#01
 2raise e#012  File 
"/usr/lib/python3/dist-packages/cloudinit/distros/__init__.py", line 406, in 
add_user#012util.subp(adduser_cmd, logstring=log_adduser_cmd)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/util.py", line 1704, in subp#012
cmd=args)#012cloudinit.util.ProcessExecutionError: Unexpected error while 
running command.#012Command: ['useradd', 'ansible', '--shell', '/bin/bash', 
'--gid', 'ansible', '--comment', 'Ansible', '--groups', 'sudo', '-m']#012Exit 
code: 6#012Reason: -#012Stdout: ''#012Stderr: "useradd: group 'ansible' does 
not exist\n"
Mar 31 22:35:46 test [CLOUDINIT] stages.py[DEBUG]: Running module ssh () with frequency 
once-per-instance

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

Title:
  cloud-init does not create defined users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1562918/+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 1562918] Re: cloud-init does not create defined users

[Leander Janssen]

I've applied the diff.
The defined users are now being created, but only when their primary group is 
created first using the groups statement.
The users are also correctly added to the specified additionals groups.
 
I've pasted my userdata below:

#cloud-config

groups:
  - ansible
  - sysop

users:
  - name: sysop
gecos: "System Operator"
primary-group: sysop
groups: "sudo,adm"
shell: /bin/bash
lock-passwd: false
passwd:  
  - name: ansible
gecos: Ansible
primary-group: ansible
groups: sudo
shell: /bin/bash

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

Title:
  cloud-init does not create defined users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1562918/+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 1564388] Re: mysqlnd is vulnerable to BACKRONYM (CVE-2015-3152)

[Seth Arnold]

I've asked MITRE if this needs a new CVE or not:

http://www.openwall.com/lists/oss-security/2016/03/31/10

Thanks

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

Title:
  mysqlnd is vulnerable to BACKRONYM (CVE-2015-3152)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1564388/+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 1515278] Re: [SRU] rabbit queues should expire when unused

[Mathew Hodson]

** Also affects: python-oslo.messaging (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: oslo.messaging (Ubuntu Wily)

** No longer affects: oslo.messaging (Ubuntu)

** No longer affects: python-oslo.messaging (Ubuntu Trusty)

** Changed in: python-oslo.messaging (Ubuntu)
   Status: New => Fix Committed

** Changed in: python-oslo.messaging (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: python-oslo.messaging (Ubuntu)
   Importance: Undecided => Medium

** Changed in: python-oslo.messaging (Ubuntu Wily)
   Importance: Undecided => Medium

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

Title:
  [SRU] rabbit queues should expire when unused

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1515278/+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 1546735] Re: openipmi package compile without SSL

[Brian Murray]

Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

** Also affects: openipmi (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775847
   Importance: Unknown
   Status: Unknown

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

Title:
  openipmi package compile without SSL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+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 1564388] Re: mysqlnd is vulnerable to BACKRONYM (CVE-2015-3152)

[Seth Arnold]

** Information type changed from Private Security to Public Security

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

Title:
  mysqlnd is vulnerable to BACKRONYM (CVE-2015-3152)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1564388/+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 1521958] Re: rabbit: starvation of connections for reply

[Mathew Hodson]

** No longer affects: oslo.messaging (Ubuntu)

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

Title:
  rabbit: starvation of connections for reply

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1521958/+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 1557599] Re: php packages: add php-mbstring dependency

[Nish Aravamudan]

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

** Also affects: php-apigen (Ubuntu)
   Importance: Undecided
   Status: New

** Attachment added: "attachment"
   https://bugs.launchpad.net/bugs/1557599/+attachment/4618772/+files/attachment

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

Title:
  php packages: add php-mbstring dependency

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

[Nish Aravamudan]

** Attachment added: "attachment"
   https://bugs.launchpad.net/bugs/1557599/+attachment/4618773/+files/attachment

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

Title:
  php packages: add php-mbstring dependency

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/phing/+bug/1557599/+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 1563159] Re: [MIR] golang-github-mattn-go-colorable

[Stéphane Graber]

promoted to main

** Changed in: golang-github-mattn-go-colorable (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-mattn-go-colorable in
Ubuntu.
https://bugs.launchpad.net/bugs/1563159

Title:
  [MIR] golang-github-mattn-go-colorable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-mattn-go-colorable/+bug/1563159/+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 1563160] Re: [MIR] golang-github-mattn-go-isatty

[Stéphane Graber]

promoted to main.

** Changed in: golang-github-mattn-go-isatty (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-mattn-go-isatty in
Ubuntu.
https://bugs.launchpad.net/bugs/1563160

Title:
  [MIR] golang-github-mattn-go-isatty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-mattn-go-isatty/+bug/1563160/+subscriptions

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

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

[Mike Rushton]

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

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

It froze on the exact same spot.

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

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

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

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

[Bug 1545913] Re: [FFe] juju-core 2.0

[Richard Harding]

Add item

- document the process for avoiding a late stage FFe and package upload
for 16.10

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

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1545913] Re: [FFe] juju-core 2.0

[Richard Harding]

In an IRC conversation with: stgraber, infinity, mgz

We agreed that the outstanding issues are the following:

- adding a comment to the juju 2.0 FFe that clarifies that the juju client is 
built and runs on all architectures, including 32bit.
- move the juju binary metapackage suggest juju-1.25 so that upgrades will make 
sure that juju 1 stays available
- make juju1 the higher update-alternatives priority.
- trim the binary size of the juju package by reducing the duplication
- investigate the ability to perform stripping to reduce size

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

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1556306] Re: vhost-user: qemu stops processing packets under high load of traffic

[Brian Murray]

Hello Vincent, or anyone else affected,

Accepted qemu into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.3+dfsg-
5ubuntu9.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: qemu (Ubuntu Wily)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
   vhost-user: qemu stops processing packets under high load of traffic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1556306/+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 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

I've edited the bug the clarify the juju-mongodb situation. There's a
change to both tweak the version of mongodb and make the unit tests more
reliable, which was held from landing for beta3 waiting on the package
in ubuntu. It will be included in the rc.

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

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1558336] Re: [needs-packaging] juju-mongo-tools3.2 in xenial, wily, and trusty

[Curtis Hovey]

Hi Robie.

> In override_dh_clean, rm -rf /tmp/go-build* will interfere with other

Thank you for calling this out. I have removed it. It is not needed.

> Other notes (I can fix up):

The rules were written to work for wily and trusty. I look forward
to removing the work arounds or using a better technique. My hope
is that when officially backporting packages to wily and trusty, only
the control file will change.

> No need for override_dh_strip any more (golang-go produced binaries can
> now be stripped according to bug 1318027). When fixed, can remove
> lintian overrides. Maybe best to leave for now as we're short on time,
> but can leave a bug open to do later.
> 
> No need for override_dh_builddeb since xz is default on Xenial, or are
> you leaving this for backporting ease? If so, then do we know xz will
> work as far back as you want to backport?

I think this is needed to trusty.

> debian/copyright looks superficially OK to me, and I'm happy that Curtis
> can maintain these accurately. Leaving it for the AA to review once.
> Same with debian/missing-sources. Good job on identifying that this was
> required and taking care of it.
> 
> Embedded dependencies: I see 10 bundled dependencies, and four -dev
> packages which presumably override them (cannot check due to lack of
> build, see below). Are the others acceptable to AAs to bundle?

I have reviewed the build logs for my trials on xenial, wily, and trusty.
Only the trusty built with all the embedded go packages.

> Changelog should close LP bug. Changelog arch reference is presumably
> superseded now as we're bulding Arch: any?

Oops, yes a bullet point needs to be removed, Done.

> I'm not sure where to get the orig tarball and there is no debian/watch
> file.

/me hangs head in shame. I didn't commit the watch file. It is not in
the tree.

> Cannot (easily) check lintian without orig tarball.

> Cannot (easily) build test without orig tarball. So I basically just
> reviewed the debian/ directory by looking at it only. It is nice and
> small and easy to review - thanks.

I recreate the tarfile when creating the source package. The quickest
command is
bzr bd S -- -uc -us

Attached is a diff of the changes made per the review

** Patch added: "diff from review 1"
   
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1558336/+attachment/4618684/+files/juju-mongo-tools3.2-review1.diff

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

Title:
  [needs-packaging] juju-mongo-tools3.2 in xenial, wily, and trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1558336/+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 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

** Description changed:

  The juju team is requesting an FFE for juju-core. Juju2 represents API
  changes and new features and bugfixes for juju.  We are NOT requesting a
  place on any image for xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  Related FFes
  
  
  Required for Juju 2.0:
  
  juju-mongodb3.2: bug 1557852
  juju-mongodb2.6: bug 1557830
  juju-mongo-tools3.2: bug 1558336
+ 
+ (see note below about mongodb for details)
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
  openstack: Already in universe, dep wait on conjure -> juju 2.0
  charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun 

[Bug 1564187] Re: issue with conditional in postinst

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.7~bzr1192-0ubuntu2

---
cloud-init (0.7.7~bzr1192-0ubuntu2) xenial; urgency=medium

  [Logan Rosen]
  * debian/cloud-init.postinst: fix shell syntax in upgrade (LP: #1564187)

 -- Scott Moser   Thu, 31 Mar 2016 10:09:09 -0400

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

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

Title:
  issue with conditional in postinst

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1564187/+subscriptions

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

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

[Serge Hallyn]

Failing any brighter ideas, this should be pretty bisectable to figure
out what happened.  Hardware availability is the main problem.  Would
you be able to use your system to bisect to the commit introducing the
bug?

Actually before we get to that, could you try installing the 14.04 slof
package on the 16.04 system, and see whether that fixes it?


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

** 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 the bug report.
https://bugs.launchpad.net/bugs/1563887

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

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

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

[Bug 1508120] Re: please break out embedded code copies into archive packages

[Nicholas Skaggs]

Here's the ppa with the packages:

https://launchpad.net/~nskaggs/+archive/ubuntu/juju/+packages

And here's the status for each dependency mentioned.

http://paste.ubuntu.com/15569917/

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

Title:
  please break out embedded code copies into archive packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1508120/+subscriptions

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

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

[Mike Rushton]

Same issue with -m 2048

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

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

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

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

[Bug 1508120] Re: please break out embedded code copies into archive packages

[Nicholas Skaggs]

Jamie, the additional packages are:

golang-github-altoros-gosigma
golang-github-dustin-go-humanize
golang-github-gabriel-samfira-sys
golang-github-gosuri-uitable
golang-github-joyent-gocommon
golang-github-joyent-gomanta
golang-github-joyent-gosdc
golang-github-joyent-gosign
golang-github-mattn-go-runewidth
golang-gnuflag-dev
golang-gopkg-errgo.v1
golang-gopkg-goose.v1
golang-gopkg-lxc-go-lxc.v2
golang-gopkg-macaroon.v1
golang-gopkg-natefinch-npipe.v2

These are currently packaged in my ppa and should be ready for upload
for Y.

There are 2 additional that are not targeted.

google.golang.org/cloud
gopkg.in/macaroon-bakery.v1

have a spiderweb of depends, and I think we would prefer to leave them
as embeds, but we can work on it during Y and come to a solution.

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

Title:
  please break out embedded code copies into archive packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1508120/+subscriptions

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

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

[Jeff Lane]

** Tags added: hwcert-server

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

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

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

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

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

[Jeff Lane]

This also needs a 1.9 target as well.  I just discovered this while
investigating proxy issues on a customer MAAS server and found that they
have an open maas proxy with a ton of external connections to it :/

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

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

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

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

[Bug 1549789] Re: [SRU] Updated walinuxagent to 2.0.16

[Brian Murray]

Hello Ben, or anyone else affected,

Accepted walinuxagent into precise-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/walinuxagent/2.0.16-0ubuntu1~12.04.0
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: walinuxagent (Ubuntu Precise)
   Status: New => Fix Committed

-- 
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:
  [SRU] 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

[Bug 1544764] Re: ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

[Brian Murray]

** Also affects: walinuxagent (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

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

[Brian Murray]

** Also affects: walinuxagent (Ubuntu Precise)
   Importance: Undecided
   Status: New

-- 
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 1550461] Re: walinuxagent conflicts with networkmanager

[Brian Murray]

** Also affects: walinuxagent (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  walinuxagent conflicts with networkmanager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1550461/+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 1546776] Re: [FFe] charm-tools 2.0

[Stéphane Graber]

it hasn't

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

Title:
  [FFe] charm-tools 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1546776/+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 1564518] [NEW] Illegal instruction when cross compiling for armv5

[David Lechner]

Public bug reported:

I installed the golang-1.6 package for trusty and tried to cross-compile
a trivial hello world program for armv5

GOOS=linux GOARCH=arm GOARM=5 go build hello.go

When running the program on an actual arm machine though, the resulting
hello executable crashes with "Illegal Instruction".

This same command with the official golang 1.6 Linux binary from the go
website creates a working executable, so I am guessing that there is
some compile option that is different in Ubuntu and that it probably has
to to with floating points. armv5 should be using soft float instead of
VFP.

** Affects: golang-1.6 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Illegal instruction when cross compiling for armv5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1564518/+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: [SRU] Updated walinuxagent to 2.0.16

[Brian Murray]

Hello Ben, or anyone else affected,

Accepted walinuxagent into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/walinuxagent/2.0.16-0ubuntu1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: walinuxagent (Ubuntu Trusty)
   Status: New => Fix Committed

-- 
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:
  [SRU] 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

[Bug 1544764] Re: ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

[Brian Murray]

Hello Stephen, or anyone else affected,

Accepted walinuxagent into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/walinuxagent/2.0.16-0ubuntu1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: walinuxagent (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

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

[Brian Murray]

Hello Ben, or anyone else affected,

Accepted walinuxagent into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/walinuxagent/2.0.16-0ubuntu1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: walinuxagent (Ubuntu Trusty)
   Status: New => Fix Committed

-- 
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 1550461] Re: walinuxagent conflicts with networkmanager

[Brian Murray]

Hello Ben, or anyone else affected,

Accepted walinuxagent into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/walinuxagent/2.0.16-0ubuntu1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: walinuxagent (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  walinuxagent conflicts with networkmanager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1550461/+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 1508120] Re: please break out embedded code copies into archive packages

[Jamie Strandboge]

MY last comment was confusing. Let me retry:

In https://bugs.launchpad.net/ubuntu/+source/juju-
core/+bug/1545913/comments/12 I mentioned that the number of embedded
copies is reduced in juju2 on 16.04 and juju2 is using archive -dev
packages for  many of the copies listed in this bug. Great! :)

Please enumerate the remaining 15 embedded copies and the plan to
address them.

Thanks!

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

Title:
  please break out embedded code copies into archive packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1508120/+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 1564250] Re: Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state

[Jorge Niedbalski]

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

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

Title:
  Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1564250/+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 1508120] Re: please break out embedded code copies into archive packages

[Jamie Strandboge]

In https://bugs.launchpad.net/ubuntu/+source/juju-
core/+bug/1545913/comments/12 I mentioned that a number of the embedded
copies are now being used in the juju 2 packaging (thanks!). I've also
asked that the remaining 15 embedded copies be enumerated with the plan
to address them.

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

Title:
  please break out embedded code copies into archive packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1508120/+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 1545913] Re: [FFe] juju-core 2.0

[Jamie Strandboge]

"The security team has requested changes to the current juju packaging
with the ultimate goal of breaking out the embedded non-juju golang
dependencies.

As part of this FFE, the juju-core package depends upon all currently
packaged golang depends that are already in the archive.

The remaining ~15 dependencies have been packaged and will be uploaded
to the archive once the archive has opened again for Y development. We
will not be attempting to add these additional packages as part of this
FFE."

I looked at the Packages file in the PPA and verified that juju was
Built-Using the specified packages. One small thing, juju Build-Depends
on golang-go.net-dev but this is a transitional package that pulls in
golang-x-net-dev (which is found in Built-Using). Please adjust the
Build-Depends to use golang-x-net-dev instead.

With my security team hat on, progress was made on bug #1508120 with the
current packaging in the ppa so juju is heading in the right direction
wrt to embedded code copies. Therefore the security team will not block
this FFe. Thank you for making these changes.

With my MIR team hat on I'll comment on the embedded code copes,
conditional ACK provided bug #1508120 is updated to enumerate the
remaining ~15 dependencies and the plan to address them.

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

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1546776] Re: [FFe] charm-tools 2.0

[Robie Basak]

I don't think the Juju 2.0 FFe has actually been approved, has it?
That's bug 1545913.

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

Title:
  [FFe] charm-tools 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1546776/+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 1336847] Re: apache2 SSL mpm-worker mod_fcgid Resource deadlock avoided

[ChristianEhrhardt]

Hi Markus,
sorry to get to this so late.

I couldn't reproduce that today.
But then "a while even under non heavy server" is kind of unspecific.
Also there were plenty of updates to the packages

If this really still applies to your environment please share more detail on 
what you do to reproduce this.
Until then I'd mark the bug incomplete to help the overview of open bugs.
Please if you want and can provide the data and that issue still affects you 
feel free to set it back to new.

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

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

Title:
  apache2 SSL mpm-worker mod_fcgid Resource deadlock avoided

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1336847/+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 1564250] Re: Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state

[Alvaro Uría]

All HA deploys on Trusty were affected (icehouse, kilo, liberty):

How to reproduce:
1) landscape-client triggers automatic apt-get upgrade
corosync:amd64 (2.3.3-1ubuntu1, 2.3.3-1ubuntu2)

2) corosync restarts but pacemaker remains stopped (corosync Invalid IPC
credentials)

3) on 2 deploys (icehouse and kilo), we could manually service corosync
stop && service corosync start && service pacemaker start

4) on other deploys (icehouse, kilo, liberty), we had to reboot lxc <--
and always came OK

It might be related to lp#1439649.

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

Title:
  Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1564250/+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 1550461] Re: walinuxagent conflicts with networkmanager

[Brian Murray]

** Also affects: walinuxagent (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  walinuxagent conflicts with networkmanager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1550461/+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 1403499] Re: apache2 mod_reqtimeout erroneous timeouts

[ChristianEhrhardt]

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

** Changed in: apache2 (Ubuntu Wily)
   Status: New => Fix Released

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

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

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

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

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

Title:
  apache2 mod_reqtimeout erroneous timeouts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1403499/+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 1428288] Re: dist-upgrade failed: apache2 postinst failed on absolute symlinks in mods-enabled

[ChristianEhrhardt]

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

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

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

Title:
  dist-upgrade failed: apache2 postinst failed on absolute symlinks in
  mods-enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1428288/+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 1544764] Re: ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

[Brian Murray]

** Also affects: walinuxagent (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

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

[Brian Murray]

** Also affects: walinuxagent (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
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 1549789] Re: [SRU] Updated walinuxagent to 2.0.16

[Ben Howard]

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

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

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

-- 
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:
  [SRU] 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

[Bug 1428288] [NEW] dist-upgrade failed: apache2 postinst failed on absolute symlinks in mods-enabled

[Launchpad Bug Tracker]

You have been subscribed to a public bug by ChristianEhrhardt (paelzer):

I tried to upgrade from 12.04 LTS to 14.04 LTS using "do-release-
upgrade".  The system had previously (a few minutes previously) been
upgraded from 10.04 LTS to 12.04 LTS.  As far as I can tell, the first
upgrade was successful, but the second failed when trying to configure
apache2:

disable obsolete module dav_fs
Module dav_fs disabled.
disable obsolete module dav
ERROR: The following modules depend on dav and need to be disabled first: 
dav_svn
dpkg: error processing package apache2 (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports has already been reached
…
Please report this bug in a browser at 
http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug 
and attach the files in /var/log/dist-upgrade/ to the bug report. 
installArchives() failed 

I think this is caused by the fact that I have absolute symlinks in
/etc/apache2/mods-enabled:

root@sigurd:/home/bjh21# ls -o /etc/apache2/mods-enabled/dav*
lrwxrwxrwx 1 root 36 Nov 12  2012 /etc/apache2/mods-enabled/dav.load -> 
/etc/apache2/mods-available/dav.load
lrwxrwxrwx 1 root 30 Nov 12  2012 /etc/apache2/mods-enabled/dav_svn.conf -> 
../mods-available/dav_svn.conf
lrwxrwxrwx 1 root 40 Nov 12  2012 /etc/apache2/mods-enabled/dav_svn.load -> 
/etc/apache2/mods-available/dav_svn.load

The code that detects obsolete modules in apache2.postinst looks like it
will (accidentally) not work with absolute symlinks:

refresh_modules()
{
if we_are_upgrading_from_wheezy $@ && [ -d /etc/apache2/mods-enabled/ ] 
; then
shopt -s nullglob
for link in /etc/apache2/mods-enabled/*.load ; do
target=$(readlink "$link") || true
if [ -z "$target" ] ; then
continue
fi

module=$(basename "$link" | sed 's/\.load//') ||
true

if [ ! -e "/etc/apache2/mods-enabled/$target" ] ; then
echo "disable obsolete module $module"
a2dismod -m -q "$module"

etc.

Concatenating the symlink contents with the directory name only works
for relative symlinks.  A simpler approach would be simply to check the
link for existence, which will treat broken links as non-existent:

if [ ! -e "${link}" ]; then

** Affects: apache2 (Ubuntu)
 Importance: Medium
 Status: Triaged

-- 
dist-upgrade failed: apache2 postinst failed on absolute symlinks in 
mods-enabled
https://bugs.launchpad.net/bugs/1428288
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 1315029] Re: shib2.load prevents webdav from reading .htpasswd file

[ChristianEhrhardt]

Thanks for letting us know what solved that for you, closing bug.

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

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

Title:
  shib2.load prevents webdav from reading .htpasswd file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1315029/+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 1403499] Re: apache2 mod_reqtimeout erroneous timeouts

[Robie Basak]

** Also affects: apache2 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: apache2 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

Title:
  apache2 mod_reqtimeout erroneous timeouts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1403499/+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 1403499] [NEW] apache2 mod_reqtimeout erroneous timeouts

[Launchpad Bug Tracker]

You have been subscribed to a public bug by ChristianEhrhardt (paelzer):

Please update mod_reqtimeout from Apache 2.4 upstream.

There is bug 56216 (mod_reqtimeout: Resolve unexpected timeouts on keepalive 
requests 
under the Event MPM.) , see 
https://issues.apache.org/bugzilla/show_bug.cgi?id=56216

The fix has been committed to Apache 2.4 and will be in 2.4.11.
We can reproduce the bug on Ubuntu 14.04 with package apache2 version 
2.4.7-1ubuntu4.

The fix can be retrieved from

http://svn.apache.org/viewvc?view=revision=1587697

Thanks for considering this.

Regards,

Martin

** Affects: apache2 (Ubuntu)
 Importance: Medium
 Status: Fix Released

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

** Affects: apache2 (Ubuntu Wily)
 Importance: Medium
 Status: Fix Released

-- 
apache2 mod_reqtimeout erroneous timeouts
https://bugs.launchpad.net/bugs/1403499
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 1547183] Re: Remove php5 specific packages from the archive

[Nish Aravamudan]

** Also affects: php-mysqlnd-ms (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove php5 specific packages from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/civicrm/+bug/1547183/+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 1546776] Re: [FFe] charm-tools 2.0

[James Page]

I've uploaded all packages apart from updates to charm and charm-tools,
which Marco is just finishing off.

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

Title:
  [FFe] charm-tools 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1546776/+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 1559935] Please test proposed package

[James Page]

Hello James, or anyone else affected,

Accepted keystone into liberty-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:liberty-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-liberty-needed to verification-liberty-done. If it
does not fix the bug for you, please add a comment stating that, and
change the tag to verification-liberty-failed. In either case, details
of your testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

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

Title:
  [SRU] nova 12.0.2, keystone 8.1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1559935/+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 1341607] Re: HTTP authentication does not work

[ChristianEhrhardt]

According to Seths comment and that nobody else jumped in with the same
issue I'd consider setting the bug as incomplete as there are non-
deprecated new ways available.

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

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

Title:
  HTTP authentication does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1341607/+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 1308570] Re: Sites not served after Precise - Trusty upgrade - new apache2 documentroot path

[ChristianEhrhardt]

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

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

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

Title:
  Sites not served after Precise - Trusty upgrade - new apache2
  documentroot path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1308570/+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 1307156] Re: package apache2 2.4.6-2ubuntu2.2 failed to install/upgrade: ErrorMessage: EOF on stdin at conffile prompt

[ChristianEhrhardt]

Hi,
it looks like some files were removed manually.

modified.conffile..etc.apache2.conf.available.charset.conf: [deleted]
modified.conffile..etc.apache2.conf.available.localized.error.pages.conf: 
[deleted]
modified.conffile..etc.apache2.conf.available.other.vhosts.access.log.conf: 
[deleted]
modified.conffile..etc.apache2.conf.available.security.conf: [deleted]
modified.conffile..etc.apache2.conf.available.serve.cgi.bin.conf: [deleted]
modified.conffile..etc.bash.completion.d.apache2: [deleted]

In that case behaviour is kind of undefined.
If this still is an issue for you please consider purging (properly removing) 
and reinstalling the package.
Marking the bug incomplete, feel free to reopen if that still is an issue after 
purging and installing.

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

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

Title:
  package apache2 2.4.6-2ubuntu2.2 failed to install/upgrade:
  ErrorMessage: EOF on stdin at conffile prompt

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

[ChristianEhrhardt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1372449/+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 1563089] Re: Memory Leak when new cluster configuration is formed.

[Jorge Niedbalski]

** Patch removed: "Xenial Patch"
   
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+attachment/4617458/+files/fix-lp-1563089-xenial.debdiff

** Patch added: "Xenial Patch"
   
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+attachment/4618461/+files/fix-lp-1563089-xenial.debdiff

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

Title:
  Memory Leak when new cluster configuration is formed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+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 1545913] Re: [FFe] juju-core 2.0

[Robie Basak]

** Description changed:

  The juju team is requesting an FFE for juju-core. Juju2 represents API
  changes and new features and bugfixes for juju.  We are NOT requesting a
  place on any image for xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
+ 
+ Related FFes
+ 
+ 
+ Required for Juju 2.0:
+ 
+ juju-mongodb3.2: bug 1557852
+ juju-mongodb2.6: bug 1557830
+ juju-mongo-tools3.2: bug 1558336
+ 
+ Required consumers:
+ 
+ conjure: bug 1561037
+ bigdata: bug 1561043
+ openstack: ?TBC
+ charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
- 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun adopting 2.0, and is dependent upon 2.0 being 
inside xenial.
  
  * Multiple external customers 

[Bug 1545913] Re: [FFe] juju-core 2.0

[Adam Stokes]

** Description changed:

  The juju team is requesting an FFE for juju-core. Juju2 represents API
  changes and new features and bugfixes for juju.  We are NOT requesting a
  place on any image for xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  Related FFes
  
  
  Required for Juju 2.0:
  
  juju-mongodb3.2: bug 1557852
  juju-mongodb2.6: bug 1557830
  juju-mongo-tools3.2: bug 1558336
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
- openstack: ?TBC
+ openstack: Already in universe, dep wait on conjure -> juju 2.0
  charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun adopting 2.0, and is dependent 

[Bug 1563393] Re: [FreezeException Needed] Update nginx to 1.9.13.

[Launchpad Bug Tracker]

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

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

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

Title:
  [FreezeException Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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 1407136] Re: Apache 2.4 --- "authz_core" logs lots of messages

[ChristianEhrhardt]

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

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

Title:
  Apache 2.4 ---  "authz_core"  logs lots of messages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1407136/+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 1564250] Re: Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state

[Alvaro Uría]

** Tags added: canonical-bootstack

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

Title:
  Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1564250/+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 1416885] Re: Default DocumentRoot migration occurs even if /var/www/html was already being used

[Chaskiel Grundman]

Jessie's apache2 2.4.10 looks very different:

if is_fresh_install $@ || we_are_upgrading_from_wheezy $@ ; then
local do_copy=true
local dir ext
for dir in /var/www /var/www/html ; do
for ext in html cgi pl php xhtml htm ; do
if [ -e $dir/index.$ext ] ; then
do_copy=false
break 2
fi
done
if [ -h $dir/index.html ] ; then
do_copy=false
break
fi
done
if $do_copy ; then
cp /usr/share/apache2/default-site/index.html 
/var/www/html/index.html
fi
 fi


A possible source of this change is:
apache2 (2.4.9-2) unstable; urgency=medium

  * Fix logic in postinst to detect existing index.* files in both
DocumentRoots, the old /var/www and the new /var/www/html. Also
change the compiled in default DocumentRoot to /var/www/html.
Closes: #743915

(but the bug description does not match this change)

Note that if you decide to request that I interact with debian anyway,
just close the bug instead. I made this report as a courtesy so that
other users could avoid being affected, not so I could do more work.

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

Title:
  Default DocumentRoot migration occurs even if /var/www/html was
  already being used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1416885/+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 1528251] Re: WARNING: no suitable primes in /etc/ssh/primes

[Colin Watson]

I won't forget to do it with the 7.3 upload, and would rather have the
bug open until it's actually fixed.

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

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

Title:
  WARNING: no suitable primes in /etc/ssh/primes

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1528251/+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 1564187] Re: issue with conditional in postinst

[Scott Moser]

Thanks for bug report.


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

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

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

Title:
  issue with conditional in postinst

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