[Bug 1528583] Re: [FFe] Please update to MySQL 5.7 series

[Martin Pitt]

> I think it'd be acceptable to allow other packages through proposed
despite a MySQL dep8 test failure

There should not be any others, as mysql-5.7 only exists in xenial-
proposed, and we test packages against xenial-release as much as
possible.

-- 
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 1563551] Re: Sync ethtool 1:4.5-1 (main) from Debian testing (main)

[Martin Pitt]

Looks ok, approved and accepted.

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

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

Title:
  Sync ethtool 1:4.5-1 (main) from Debian testing (main)

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

-- 
Ubuntu-server-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

[Martin Pitt]

It looks like dbconfig-common needs to be adjusted for MySQL 5.7. It
fails on "mysql: [ERROR] mysql: Empty value for 'port' specified."

-- 
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 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 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 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 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 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 adopt

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

[Martin Packman]

Updated the description with the example upgrade testing using the test
packages in the ppa.

** 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.
  
  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 juju2 version updated. The 
current juju-core package will become juju-core1. Users upgrading from wily and 
trusty will get juju2 as part of the upgrade. Update-alternatives will provide 
support for toggling /usr/bin/juju between juju1 and juju2 binaries.
+ 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;
+ scenarios:
  
- Trusty
- No juju -> install juju on xenial, juju-core is installed.
- Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives 
toggles
+ New Xenial:
+ No juju, apt-get install juju, juju version will be 2.0.
+ Example using ppa: 
  
- Wily
- No juju -> install juju on xenial, juju-core is installed.
- Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives 
toggles
+ 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.
 

[Bug 1555700] Re: [FFE] Please merge tgt 1.0.63 from Debian (unstable)

[Martin Pitt]

Seems Ryan is still investigating whether or not to enable AIO in the
first place. If you decide to disable it, then there's no FFE, and if
you want to enable it and can make sure that it does not negatively
affect other modes, then Adam already gave the OK.

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

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

Title:
  [FFE] Please merge tgt 1.0.63 from Debian (unstable)

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

-- 
Ubuntu-server-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

[Martin Pitt]

This is conceptually part of Juju 2.0, so the FFE for that should apply
to charm tools too. +1

** Changed in: charm-tools (Ubuntu)
   Status: New => Triaged

-- 
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 1560148] Re: [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

[Martin Pitt]

120 kB changelog essentially means "many changes". What testing has been
done with the new version? Do any of the reverse dependencies (cluster-
glue, collectd, heartbeat, zabbix, etc.) need updating as well? How were
these tested with the new openipmi?

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

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

Title:
  [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

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

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

[Bug 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Martin Packman]

Hm, looks like the adventures with reworking the packaging yesterday
(which I didn't follow the reasoning behind, but ended up basing the
beta2 packaging branch on an existing xnox branch) lost the Build-
Depends we had on archive golang packages.

What we had:



Missing here:



So, they should be added back in.

That said, the juju qa team hasn't spent any time this cycle on
adventures with golang packaging. What time we have had on distro tasks
has been sucked up basically packaging mongo 3 (and mongo 2.6 for
migration purposes).

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

Title:
  [needs packaging] juju2 beta is not in xenial

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

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

[Bug 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Martin Pitt]

FTR, I did an initial source NEW review of juju2. In the initial MIR bug
1267393 (two years ago) the deal was to *reduce* the embedded code
copies and replace them with golang-google-api-dev & co. build
dependencies. juju-core now does have a handful of those, but still an
awful lot of embedded copies  which are available in the archive (such
as golang-github-bmizerany-pat-dev).

But the current juju2 package in NEW goes back to square 1: It *solely*
uses embedded code copies (including packages which are very active and
well maintained in Ubuntu such as lxd!), and there's now about 50% more
modules bundled.

Please rework the package to use archive dependencies as much as
possible. 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/1560315

Title:
  [needs packaging] juju2 beta is not in xenial

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

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

[Bug 1559615] Re: package systemd 225-1ubuntu9.1 failed to install/upgrade: triggers looping, abandoned

[Martin Pitt]

dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  munin-node -> munin-node
 packages' pending triggers which are or may be unresolvable:
  ca-certificates: update-ca-certificates
  dbus: /etc/dbus-1/system.d
  systemd: /etc/init.d
  libc-bin: ldconfig
  initramfs-tools: update-initramfs
  menu: /usr/share/menu
  munin-node: perl-major-upgrade
  ureadahead: /etc/init: /etc/init.d

** Package changed: systemd (Ubuntu) => munin (Ubuntu)

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

Title:
  package systemd 225-1ubuntu9.1 failed to install/upgrade: triggers
  looping, abandoned

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

-- 
Ubuntu-server-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

[Martin Packman]

> Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you haven't
> carried this forward. Is this expected (not described in changelog)? Perhaps 
> it
> is because of --disable-scripting but I'm not sure.

Indeed. We have always built juju-mongodb without the javascript engine
because the security team had concerns and we didn't need it anyway.
Note in 3.2 V8 has gone, and they're back to spidermonkey:



-- 
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 1559699] Re: [1.9.1] Commissioning doesn't detect partitioning of secondary hard disk

[Martin Nowack]

Thank you for the clarification.

Yes, it is pre-partioned. 
The bigger problem with this is, that even the disk is not used, all the 
partitions get *deleted*.

According to current documentation
(http://maas.ubuntu.com/docs/changelog.html) it says:

"Default Storage Partitioning Layout - Flat
[...]
The current default Partitioning layout is ‘Flat’, maintaining backwards 
compatibility with previous MAAS releases. This means MAAS will take the first 
disk it finds in the system and use it as the root and boot disk.
"
I was expecting there are no modifications on secondary disks.

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

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

Title:
  [1.9.1] Commissioning doesn't detect partitioning of secondary hard
  disk

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

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

[Bug 1559711] [NEW] DHCP.leases: Lease without mac address generated

[Martin Nowack]

Public bug reported:

Following lease entry was generated in dhcp.leases:

lease x.x.x.x {
  starts 0 2016/03/20 13:30:00;
  ends 0 2016/03/20 13:30:00;
  cltt 0 2016/03/20 13:30:00;
  binding state free;
}

This entry doesn't contain a "hardware ethernet ..." entry,
therefore dhcp/leases_parser_fast.py fails.

Replacing line 78 with the following works around the issue:
if not has_expired(entry, now) and hasattr(entry.hardware, 'mac'):


maas-cluster-controller:
  Installed: 1.9.1+bzr4543-0ubuntu1~trusty1
  Candidate: 1.9.1+bzr4543-0ubuntu1~trusty1
  Version table:
 *** 1.9.1+bzr4543-0ubuntu1~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
100 /var/lib/dpkg/status
 1.7.6+bzr3376-0ubuntu2~14.04.1 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1.5+bzr2252-0ubuntu1 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

Title:
  DHCP.leases: Lease without mac address generated

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

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

[Bug 1559699] [NEW] [1.9.1] Commissioning doesn't detect partitioning of secondary hard disk

[Martin Nowack]

Public bug reported:

During commissioning of a node the partitioning of the second hard disk is not 
detected,
still the hard disk itself is correctly detected.
For the first hard disk, everything works as expected.

Use release: Ubuntu Trusty.


  Installed: 1.9.1+bzr4543-0ubuntu1~trusty1
  Candidate: 1.9.1+bzr4543-0ubuntu1~trusty1
  Version table:
 *** 1.9.1+bzr4543-0ubuntu1~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
100 /var/lib/dpkg/status
 1.7.6+bzr3376-0ubuntu2~14.04.1 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1.5+bzr2252-0ubuntu1 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

Title:
  [1.9.1] Commissioning doesn't detect partitioning of secondary hard
  disk

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

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

[Bug 1551175] Re: "net join" to Active Directory may fail

[Martin]

Can you point the patch pilots on this Bug report or tell me how to do
this ?

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

Title:
  "net join" to Active Directory may fail

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

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

[Bug 1551175] Re: "net join" to Active Directory may fail

[Martin]

Here is a quilt patch. Please let me know if it is not working properly.


** Patch added: "net-join.diff"
   
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1551175/+attachment/4601102/+files/net-join.diff

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

Title:
  "net join" to Active Directory may fail

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

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

[Bug 1556175] Re: networking.service hangs on shutdown -- killing dhclient has no effect any more

[Martin Pitt]

Lamont apparently knows what's going on. He'll restore the -export
versions soon, so that we can switch isc-dhcp back to those.

** Changed in: isc-dhcp (Ubuntu)
 Assignee: Martin Pitt (pitti) => (unassigned)

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

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

** Changed in: bind9 (Ubuntu)
 Assignee: (unassigned) => LaMont Jones (lamont)

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

Title:
  networking.service hangs on shutdown -- killing dhclient has no effect
  any more

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

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

[Bug 1556175] Re: networking.service hangs on shutdown -- killing dhclient has no effect any more

[Martin Pitt]

Further bisection shows that 4.3.3-5ubuntu5 is the last version that
works, and 4.3.3-5ubuntu7 is the first version that fails (ubuntu6
cannot be tested as that FTBFSed).

The corresponding diff is http://launchpadlibrarian.net/242313487/isc-
dhcp_4.3.3-5ubuntu5_4.3.3-5ubuntu7.diff.gz -- the change was that this
now links to the non-export bind libraries. There is no
rationale/explanation of that, but supposedly the internal libraries
handle SIGTERM differently.

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

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

Title:
  networking.service hangs on shutdown -- killing dhclient has no effect
  any more

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

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

[Bug 1546214] Re: Docker containers lose their cgroup after systemd reload

[Martin Pitt]

I was about to point out the Delegate= option if docker.service wants to
maintain its sub-cgroups by itself -- but it seems that already landed
upstream two days ago: https://github.com/jheiss/docker/commit/64b87f0

There have been plenty of discussions about that "who owns the cgroup
hiearchy"/"single writer" topic, and I don't think this will change
anytime soon (nor will we change the behaviour downstream), so I'll
close the systemd task.

I'll see to pulling this patch into Xenial's docker.

** Changed in: docker.io (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Docker containers lose their cgroup after systemd reload

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1546214/+subscriptions

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

[Bug 1555997] Re: chmod fails with "Operation not permitted" on chowned files in ephemeral container

[Martin Pitt]

This still works fine with Linux 4.4.0-8, but fails on 4.4.0-10, so it's
a kernel regression.

This can be reproduced much simpler without LXC:

$ mkdir /tmp/lower /tmp/upper /tmp/work /tmp/merged
$ sudo mount -t overlay overlay 
-olowerdir=/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/work /tmp/merged
$ sudo touch /tmp/merged/testfile
$ sudo chown $USER:$USER /tmp/merged/testfile
$ $ chmod +x /tmp/merged/testfile 
chmod: changing permissions of '/tmp/merged/testfile': Operation not permitted


** Summary changed:

- chmod fails with "Operation not permitted" on chowned files in ephemeral 
container
+ overlay fs: chmod fails with "Operation not permitted" on chowned files

** Summary changed:

- overlay fs: chmod fails with "Operation not permitted" on chowned files
+ overlay fs regression: chmod fails with "Operation not permitted" on chowned 
files

** Package changed: lxc (Ubuntu) => linux (Ubuntu)

** Tags added: regression-release

** Description changed:

- I'm investigating some failures in autopkgtest's testsuite, and stumbled
- over something really weird: In an ephemeral container it is apparently
- not possible any more to chmod files that started out being root owned
- and got chowned later:
+ This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment
+ #3 for simple reproducer.
+ 
+ ORIGINAL BUG REPORT
+ ===
+ I'm investigating some failures in autopkgtest's testsuite, and stumbled over 
something really weird: In an ephemeral container it is apparently not possible 
any more to chmod files that started out being root owned and got chowned later:
  
  $ sudo lxc-start-ephemeral -o adt-wily
  (log in as ubuntu/ubuntu)
  ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile
  [sudo] password for ubuntu:
  hello
  ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile
  ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile
  chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted
  
  However, if the file was *not* previously chowned, it works as expected:
  
  ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2
  ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2
  ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2
  
  (no errors and testfile2 becomes executable)
  
  There is no visible permission difference in the files at all, other
  than being group-writable (but changing the group w bit in either
  direction does not change the error at all):
  
  -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile
  -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2
  
  ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile*
    File: ‘/tmp/testfile’
    Size: 6 Blocks: 8  IO Block: 4096   regular file
  Device: 15h/21d   Inode: 28  Links: 1
  Access: (0644/-rw-r--r--)  Uid: ( 1000/  ubuntu)   Gid: ( 1000/  ubuntu)
  Access: 2016-03-11 10:26:19.574364117 +0100
  Modify: 2016-03-11 10:26:19.574364117 +0100
  Change: 2016-03-11 10:26:21.930343210 +0100
   Birth: -
    File: ‘/tmp/testfile2’
    Size: 6 Blocks: 8  IO Block: 4096   regular file
  Device: 15h/21d   Inode: 29  Links: 1
  Access: (0664/-rw-rw-r--)  Uid: ( 1000/  ubuntu)   Gid: ( 1000/  ubuntu)
  Access: 2016-03-11 10:26:58.730145919 +0100
  Modify: 2016-03-11 10:26:58.730145919 +0100
  Change: 2016-03-11 10:27:44.530203985 +0100
   Birth: -
  
  There are also no ACLs involved (I checked with getfacl).
  
  This does not happen with a normal lxc-start, so this might very well be
  a bug in Linux' overlayfs. However, it also does not happen with the
  more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug
  perhaps this isn't using overlayfs?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0~rc9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: i3
  Date: Fri Mar 11 10:21:20 2016
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  dnsmasq.conf:
   enable-tftp
   tftp-root=/tmp/tftp
   dhcp-boot=pxelinux.0
  lxc.conf: lxc.lxcpath = /srv/lxc

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

Title:
  overlay fs regression: chmod fails with "Operation not permitted" on
  chowned files

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

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

[Bug 1555997] Re: chmod fails with "Operation not permitted" on chowned files in ephemeral container

[Martin Pitt]

I tried to purge all lxc/lxd packages and install LXC 2.0.0~rc1-0ubuntu1
again, but this now not working at all any more on xenial's kernel --
the container never starts and I get a lot of apparmor violations.

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

Title:
  chmod fails with "Operation not permitted" on chowned files in
  ephemeral container

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

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

[Bug 1555997] [NEW] chmod fails with "Operation not permitted" on chowned files in ephemeral container

[Martin Pitt]

Public bug reported:

I'm investigating some failures in autopkgtest's testsuite, and stumbled
over something really weird: In an ephemeral container it is apparently
not possible any more to chmod files that started out being root owned
and got chowned later:

$ sudo lxc-start-ephemeral -o adt-wily
(log in as ubuntu/ubuntu)
ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile
[sudo] password for ubuntu:
hello
ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile
ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile
chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted

However, if the file was *not* previously chowned, it works as expected:

ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2
ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2
ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2

(no errors and testfile2 becomes executable)

There is no visible permission difference in the files at all, other
than being group-writable (but changing the group w bit in either
direction does not change the error at all):

-rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile
-rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2

ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile*
  File: ‘/tmp/testfile’
  Size: 6   Blocks: 8  IO Block: 4096   regular file
Device: 15h/21d Inode: 28  Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/  ubuntu)   Gid: ( 1000/  ubuntu)
Access: 2016-03-11 10:26:19.574364117 +0100
Modify: 2016-03-11 10:26:19.574364117 +0100
Change: 2016-03-11 10:26:21.930343210 +0100
 Birth: -
  File: ‘/tmp/testfile2’
  Size: 6   Blocks: 8  IO Block: 4096   regular file
Device: 15h/21d Inode: 29  Links: 1
Access: (0664/-rw-rw-r--)  Uid: ( 1000/  ubuntu)   Gid: ( 1000/  ubuntu)
Access: 2016-03-11 10:26:58.730145919 +0100
Modify: 2016-03-11 10:26:58.730145919 +0100
Change: 2016-03-11 10:27:44.530203985 +0100
 Birth: -

There are also no ACLs involved (I checked with getfacl).

This does not happen with a normal lxc-start, so this might very well be
a bug in Linux' overlayfs. However, it also does not happen with the
more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug
perhaps this isn't using overlayfs?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxc 2.0.0~rc9-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: i3
Date: Fri Mar 11 10:21:20 2016
EcryptfsInUse: Yes
PackageArchitecture: all
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dnsmasq.conf:
 enable-tftp
 tftp-root=/tmp/tftp
 dhcp-boot=pxelinux.0
lxc.conf: lxc.lxcpath = /srv/lxc

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


** Tags: amd64 apport-bug xenial

** Description changed:

  I'm investigating some failures in autopkgtest's testsuite, and stumbled
  over something really weird: In an ephemeral container it is apparently
  not possible any more to chmod files that started out being root owned
  and got chowned later:
  
  $ sudo lxc-start-ephemeral -o adt-wily
  (log in as ubuntu/ubuntu)
  ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile
- [sudo] password for ubuntu: 
+ [sudo] password for ubuntu:
  hello
  ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile
  ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile
  chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted
  
  However, if the file was *not* previously chowned, it works as expected:
  
  ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2
  ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2
- ubuntu@adt-wily-hvzj1eoa:~$ chmod +- /tmp/testfile2
+ ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2
  
  (no errors and testfile2 becomes executable)
  
  There is no visible permission difference in the files at all:
  
  -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile
  -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2
  
- 
  ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile*
-   File: ‘/tmp/testfile’
-   Size: 6 Blocks: 8  IO Block: 4096   regular file
+   File: ‘/tmp/testfile’
+   Size: 6 Blocks: 8  IO Block: 4096   regular file
  Device: 15h/21d   Inode: 28  Links: 1
  Access: (0644/-rw-r--r--)  Uid: ( 1000/  ubuntu)   Gid: ( 1000/  ubuntu)
  Access: 2016-03-11 10:26:19.574364117 +0100
  Modify: 2016-03-11 10:26:19.574364117 +0100
  Change: 2016-03-11 10:26:21.930343210 +0100
-  Birth: -
-   File: ‘/tmp/testfile2’
-   Size: 6 Blocks: 8  IO Block: 4096   regular file
+  Birth: -
+   File: ‘/tmp/testfile2’
+   Size: 6 Blocks: 8  IO Block: 4096   regular file
  Device: 15h/21d   Inode: 29   

[Bug 1552827] Re: [MIR][FFE] Please sync python-pika-pool (0.1.3-1) from Debian (unstable)

[Martin Pitt]

promoted to main

** Changed in: python-pika-pool (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR][FFE] Please sync python-pika-pool (0.1.3-1) from Debian
  (unstable)

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

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

[Bug 1554266] Re: sshd does not start on newly installed desktop system

[Martin Pitt]

I tried to purge and reinstall openssh-server on today's cloud image
(with i-s-h 1.29ubuntu1) and ssh.service does start up right away as
expected. So this naïve reproducer doesn't work. Max, how does openssh-
server get installed in your case? Sorry for my ignorance, I don't know
much about preseeding -- is this just translated into some apt-get
install calls? Do they happen in a chroot with a policy-rc.d or similar?

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

Title:
  sshd does not start on newly installed desktop system

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

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

[Bug 1554481] Re: [FFe] OpenSSH 7.2p1

[Martin Pitt]

ssh has tons of reverse dependencies, most of which don't have
autopkgtests. However, the risk seems acceptable as the changelog does
not mention any removed features or different interpretation of existing
config options; and this does not depend on anything else, so if this
hypothetically breaks MaaS or something similar, we could still roll
back.

So please go ahead, thanks!

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

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

Title:
  [FFe] OpenSSH 7.2p1

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

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

[Bug 1553097] Re: lxc-attach does not output stderr any more if stdout is redirected

[Martin Pitt]

Given that this seems to be somewhat brittle, would you mind adding some
integration tests for lxc-attach for various combinations of
stdin/stdout/stderr redirection?

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

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

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

Title:
  lxc-attach does not output stderr any more if stdout is redirected

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

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

[Bug 1553097] Re: latest LXC breaks autopkgtest's LXC runner

[Martin Pitt]

This is indeed a regression in lxc-attach. Until 2.0.0~rc1 this DTRT:

$ sudo lxc-attach -n adt-virt-lxc-lbmmpf -- sh -c 'echo ERR>&2' >/dev/null
ERR

but not any more with rc5:
$ sudo lxc-attach -n a -- sh -c 'echo ERR>&2' >/dev/null
# (no output)

** Summary changed:

- latest LXC breaks autopkgtest's LXC runner
+ lxc-attach does not output stderr any more if stdout is redirected

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

Title:
  lxc-attach does not output stderr any more if stdout is redirected

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

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

[Bug 1553097] [NEW] latest LXC breaks autopkgtest's LXC runner

[Martin Pitt]

Public bug reported:

With lxc 2.0.0~rc5-0ubuntu1 the autopkgtest LXC runner is still broken
(even with bug 1551960 fixed) when stderr is a terminal:

$ adt-run gzip --- lxc -s adt-wily
[...]
adt-run [10:15:45]: ERROR: erroneous package: got 10 lines of results from 
extract where 4 expected:
gpgv: Signature made Mon 27 Oct 2014 09:48:46 AM CET using RSA key ID BD4CA59E
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./gzip_1.6-4ubuntu1.dsc
Get:1 http://archive.ubuntu.com/ubuntu/ wily/main gzip 1.6-4ubuntu1 (dsc) 
[1,907 B]
Get:2 http://archive.ubuntu.com/ubuntu/ wily/main gzip 1.6-4ubuntu1 (tar) 
[1,075 kB]
Get:3 http://archive.ubuntu.com/ubuntu/ wily/main gzip 1.6-4ubuntu1 (diff) 
[14.9 kB]
/tmp/adt-virt-lxc.shared.xklzp9z7/downtmp/build.ehH/gzip-1.6
gzip
1.6-4ubuntu1
1

Thie first couple of lines are supposed to go to stderr, not stdout.
This works if stderr is not a terminal, but a pipe, with e. g. "adt-run
-l /dev/null gzip --- lxc -s adt-wily" (where stderr is sent to a pipe
which gets tee'ed to both the log file and the real stderr).

This is probably a regression in LXC, and it doesn't happen with older
LXC nor LXD nor any other backend. But it might also be some intentional
change which autopkgtest needs to be adjusted to, so for now I keep
tasks for both projects.

** Affects: autopkgtest (Ubuntu)
 Importance: High
 Status: Triaged

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

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

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

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

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

Title:
  latest LXC breaks autopkgtest's LXC runner

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

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

[Bug 1549403] Re: [FFe]: improvements and fixes to cloud-init networking

[Martin Pitt]

Many thanks for addressing this. Fixing this for an LTS is much
appreciated indeed, as it will make the cloud images much more useful
particularly for "real hardware" use cases, and also get rid of some
gross hacks in e. g. autopkgtest, and fix the broken ppc64el images
along the way (bug 1541757).

Do you have a plan how to test and roll this out? I can help testing
this on various architectures and cloud+QEMU, but I think before this
lands in the  official cloud images this should be tested from a PPA (e.
g. by running dist-upgrade on a current cloud image and removing the
ifnames=0 hack from the grub config).

FF approved, thanks!

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

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

Title:
  [FFe]: improvements and fixes to cloud-init networking

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

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

[Bug 1551960] Re: lxc-attach does not work any more with input redirection

[Martin Pitt]

With that fix applied the adt-virt-lxc tests work fine again, so
removing the autopkgtest task again (I added it in case I need to adjust
something to the new LXC in that regard).

** No longer affects: autopkgtest (Ubuntu)

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

Title:
  lxc-attach does not work any more with input redirection

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

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

[Bug 1551960] Re: lxc-attach does not work any more with input redirection

[Martin Pitt]

I locally applied https://github.com/lxc/lxc/commit/12752e2 to our
current package and built it. Now it looks better:

# lxc-attach -n a runlevel
N 5
# lxc-attach -n a runlevel /dev/null
N 5
# lxc-attach -n a runlevel /dev/null | cat

So redirecting stdin only now does not show this
"lxc_console_cb_tty_master: 683 Bad file" error any more, and
redirecting stderr now works too. But redirecting stdout in addition
still doesn't?

Maybe I'm missing another fix from trunk, though.

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

Title:
  lxc-attach does not work any more with input redirection

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

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

[Bug 1551960] Re: lxc-attach does not work any more with input redirection

[Martin Pitt]

Nevermind, I built upstream git master, and that lxc-attach works fine.
Thanks Christian!

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

Title:
  lxc-attach does not work any more with input redirection

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

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

[Bug 1551935] Re: lxc-copy message is the wrong way around

[Martin Pitt]

Thanks Christian for the fast fix!

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

Title:
  lxc-copy message is the wrong way around

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

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

[Bug 1551960] [NEW] lxc-attach does not work any more with input redirection

[Martin Pitt]

Public bug reported:

LXC 2.0.0~rc{2,3,4} break autopkgtest's LXC runner. Downgrading to
2.0.0~rc1 works again. The issue is that lxc-attach stops working
properly with input redirection.

# lxc-start -n a

Until 2.0.0~rc1 I could redirect lxc-attach's stdout:
# lxc-attach -n a runlevel /dev/null |cat
N 5

But now this does not work any more:
# lxc-attach -n a runlevel 
N 5
# lxc-attach -n a runlevel /dev/null
# lxc-attach -n a runlevel /dev/null | cat
# 

I. e. the last two commands don't have any output at all any more.

** Affects: autopkgtest (Ubuntu)
 Importance: High
 Status: New

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


** Tags: regression-release xenial

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

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

** Tags added: regression-release xenial

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

Title:
  lxc-attach does not work any more with input redirection

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

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

[Bug 1551935] Re: lxc-copy message is the wrong way around

[Martin Pitt]

Well, the point is not really about "simpler", but "might change/be
i18n'ed" and thus "is not predictable". However, this is really a side
issue to this report. The non-machine-readability was originally bug
1197754, but it applies to lxc-copy as well. If/once the message is
stable, I can parse "^Created ([^ ]+)", but this still isn't a nice API.

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

Title:
  lxc-copy message is the wrong way around

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

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

[Bug 1551935] [NEW] lxc-copy message is the wrong way around

[Martin Pitt]

Public bug reported:

$ sudo lxc-copy -n adt-wily -e
Created adt-wily as clone of adt-wily_1WtXPo

This should say "Created adt-wily_1WtXPo as a clone of adt-wily". This
might seem trivial, but is highly relevant when trying to parse that
message to find out the cloned container name. This is still not easy at
all :-(

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

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

Title:
  lxc-copy message is the wrong way around

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

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

[Bug 1536827] Re: adt-build-lxc unmounted my home directory

[Martin Pitt]

adt-build-lxc only uses LXC commands, it does not do any mounting by
itself. I use ecyrptfs /home as well, so this isn't broken in general.
If you can reproduce this, please attach the full output of the program
you were running, and the output of "journalctl -b" and /var/log/lxc/*.

** Package changed: autopkgtest (Ubuntu) => lxc (Ubuntu)

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

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

Title:
  adt-build-lxc unmounted my home directory

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

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

[Bug 1541914] Re: passwd depends on init-system-helpers (>= 1.18~); however: Version of init-system-helpers on system is 1.14

[Martin Pitt]

I did a couple of trusty→ xenial upgrades but could not reproduce this.

The first error in that log was this:

dpkg: considering deconfiguration of init-system-helpers, which would be broken 
by installation of upstart ...
dpkg: yes, will deconfigure init-system-helpers (broken by upstart)
Preparing to unpack .../upstart_1.13.2-0ubuntu18_amd64.deb ...
De-configuring init-system-helpers (1.14) ...
Unpacking upstart (1.13.2-0ubuntu18) over (1.12.1-0ubuntu4.2) ...

which got introduced by
http://launchpadlibrarian.net/222852012/upstart_1.13.2-0ubuntu16_1.13.2-0ubuntu17.diff.gz

This apparently leads to a dependency loop. The Replaces: must be kept,
but we could drop the Breaks: to make apt's job of  breaking such loops
simpler.

** Package changed: init-system-helpers (Ubuntu) => upstart (Ubuntu)

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

** Changed in: upstart (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  passwd depends on init-system-helpers (>= 1.18~); however: Version of
  init-system-helpers on system is 1.14

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

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

[Bug 1549136] [NEW] Move "lxc" dependencies to "lxc1"

[Martin Pitt]

Public bug reported:

"lxc" now says "This is a transitional dummy package. It can safely be
removed.", but this isn't true:

$ sudo LANG= dpkg -P lxc
dpkg: dependency problems prevent removal of lxc:
 lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43).
 lxd depends on lxc.
 juju-local depends on lxc (>= 1.0.0~alpha1-0ubuntu14).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxc 2.0.0~rc2-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: i3
Date: Wed Feb 24 07:57:23 2016
EcryptfsInUse: Yes
PackageArchitecture: all
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dnsmasq.conf:
 enable-tftp
 tftp-root=/tmp/tftp
 dhcp-boot=pxelinux.0
lxc.conf: lxc.lxcpath = /srv/lxc
modified.conffile..etc.apparmor.d.lxc.lxc.default.with.nesting: [modified]
modified.conffile..etc.default.lxc: [modified]
mtime.conffile..etc.apparmor.d.lxc.lxc.default.with.nesting: 2016-02-22T23:39:08
mtime.conffile..etc.default.lxc: 2016-02-22T23:39:08

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

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

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


** Tags: amd64 apparmor apport-bug xenial

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

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

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

Title:
  Move "lxc" dependencies to "lxc1"

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

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

[Bug 1539903] Re: tomcat-8 in main for upcoming 16.04 LTS

[Martin Pitt]

** Changed in: libcommons-dbcp-java (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  tomcat-8 in main for upcoming 16.04 LTS

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

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

[Bug 1539903] Re: tomcat-8 in main for upcoming 16.04 LTS

[Martin Pitt]

Fixed by https://launchpad.net/ubuntu/+source/libcommons-dbcp-
java/1.4-5ubuntu2

** Also affects: libcommons-dbcp-java (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libcommons-dbcp-java (Ubuntu)
   Status: New => In Progress

** Changed in: libcommons-dbcp-java (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  tomcat-8 in main for upcoming 16.04 LTS

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

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

[Bug 1539903] Re: tomcat-8 in main for upcoming 16.04 LTS

[Martin Pitt]

** Changed in: jakarta-taglibs-standard (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  tomcat-8 in main for upcoming 16.04 LTS

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

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

[Bug 1539903] Re: tomcat-8 in main for upcoming 16.04 LTS

[Martin Pitt]

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

** Changed in: bsh (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: excalibur-logkit (Ubuntu)
   Status: New => Fix Committed

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

Title:
  tomcat-8 in main for upcoming 16.04 LTS

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

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

[Bug 1539903] Re: tomcat-8 in main for upcoming 16.04 LTS

[Martin Pitt]

https://launchpad.net/ubuntu/+source/jakarta-taglibs-standard/1.1.2-4
moves to 3.1, but is currently depwaiting on libservlet3.1-java. It'll
start to build in about an hour.

** Changed in: jakarta-taglibs-standard (Ubuntu)
   Status: New => Fix Committed

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

Title:
  tomcat-8 in main for upcoming 16.04 LTS

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

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

[Bug 1539903] Re: tomcat-8 in main for upcoming 16.04 LTS

[Martin Pitt]

Adding tasks for other reverse dependencies of libservlet3.0-java* which
need to be moved to 3.1.

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

** Also affects: excalibur-logkit (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jakarta-taglibs-standard (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libcommons-logging-java (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: hsqldb1.8.0 (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: libcommons-logging-java (Ubuntu)
   Status: New => Fix Committed

** Changed in: libcommons-logging-java (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  tomcat-8 in main for upcoming 16.04 LTS

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

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

[Bug 1547528] Re: How to handle specific HW needs for dep8 tests in CI

[Martin Pitt]

There is nothing to fix in the autopgtest package, so moving to the more
generic project (which also encompasses the infrastructure to run
tests).

** Package changed: autopkgtest (Ubuntu) => auto-package-testing

** Changed in: auto-package-testing
   Status: New => Incomplete

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

Title:
  How to handle specific HW needs for dep8 tests in CI

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1547528/+subscriptions

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

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Martin Pitt]

The error message is pretty clear. src/util/virsystemd.c does

if (virDBusCallMethod(conn,
  NULL,
  &error,
  "org.freedesktop.machine1",
  "/org/freedesktop/machine1",
  "org.freedesktop.machine1.Manager",
  "CreateMachineWithNetwork",
[...]
"After", "as", 1, "libvirtd.service",
 "Before", "as", 1, "libvirt-guests.service") < 0) {

and these properties are unknown/invalid for machines. You can't specify
an ordering dependency to an object that you create *right now*, as
there is no way to enforce them. So just dropping these two lines ought
to fix it.

(Also, it would be nice if a failure to register to machined wasn't
fatal)

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: libvirt (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

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

-- 
Ubuntu-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 1547528] [NEW] How to handle specific HW needs for dep8 tests in CI

[Martin Pitt]

ChristianEhrhardt [2016-02-19 14:02 -]:
> But due to that we found that in our case sse3 can't be guaranteed in the 
> test environment - so we agreed on ubuntu-devel that we should detect and 
> skip the test then to avoid false positives.

This indeed sounds like the most practical option. It also allows you
to skip only parts of your tests which depend on SSE3. You might have
others which don't.

> But later infinity pointed out if we shouldn't bump our scalingstack
> machine configs as all underlying HW would support that.  In our
> case that would be the flavour autopkgtest.

I'm not sure if such options can be specified in Openstack Nova
flavors, but I'm in no way an expert there. I suggest that you open an
RT and ask IS about that?

Even if we get that, I still suggest to test /proc/mounts and skip the
test -- after all, people want to run these tests in other envs than
the Canonical data center.

> In later discussions there were arguments that for specific software
> should have some kind of exception process where e.g. some part of the
> d/t/control should be able to specify those needs as Restriction/Class
> /or-else.

Class: would be possible, but this is a very specific requirement, and
dpdk would probably remain the only user of it. So let's not
over-design this :-) Also, we don't yet actually implement test
classes. But first and foremost, we don't have testbeds that support
SSE3, so the above Nova config discussion will have to be done either
way.

> I don't want to suggest how this would be implemented best:
> - bump flavours

> - implement new type of restriction in d/t/control

Not going to happen, sorry.

> - implement even qemu-opt in d/t/control

You can already specify options to adt-virt-qemu, so this is already
available. But QEMU options absolutely don't belong into d/t/control,
so this isn't going to happen either.

Thanks,
Martin

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

Title:
  How to handle specific HW needs for dep8 tests in CI

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

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

[Bug 1546455] Re: Many instances of 'apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" sock_type="dgram" protocol=0' in syslog

[Martin Pitt]

apparmor was already uploaded:
https://launchpad.net/ubuntu/+source/apparmor/2.10-3ubuntu2

Unsubscribing sponsors.

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

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

Title:
  Many instances of 'apparmor="DENIED" operation="create"
  profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec"
  sock_type="dgram" protocol=0' in syslog

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

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

[Bug 1547245] Re: php7.0: remove dependencies that come from universe

[Martin Pitt]

This was already uploaded without closing this bug:
https://launchpad.net/ubuntu/+source/php7.0/7.0.3-5ubuntu1

** Changed in: php7.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: php7.0 (Ubuntu)
   Status: Fix Released => Fix Committed

** Changed in: php7.0 (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

Title:
  php7.0: remove dependencies that come from universe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547245/+subscriptions

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

[Bug 1546637] Re: Sync jakarta-taglibs-standard 1.1.2-4 (main) from Debian unstable (main)

[Martin Pitt]

This bug was fixed in the package jakarta-taglibs-standard - 1.1.2-4
Sponsored for Nish Aravamudan (nacc)

---
jakarta-taglibs-standard (1.1.2-4) unstable; urgency=medium

  * Team upload.
  * Removed the Servlet, JSP and EL API jars from the classpath specified
in the manifest (Closes: #806905)
  * Transition to the Servlet API 3.1 (Closes: #780701, #801012)
  * debian/control:
- Removed the deprecated DM-Upload-Allowed field
- Standards-Version updated to 3.9.6 (no changes)
- Use canonical URLs for the Vcs-* fields
  * Switch to debhelper level 9
  * debian/rules: Improved the clean target

 -- Emmanuel Bourg   Wed, 02 Dec 2015 23:29:51 +0100

** Changed in: jakarta-taglibs-standard (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync jakarta-taglibs-standard 1.1.2-4 (main) from Debian unstable
  (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jakarta-taglibs-standard/+bug/1546637/+subscriptions

-- 
Ubuntu-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 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

[Martin Pitt]

Serge Hallyn [2016-02-18 16:39 -]:
> Just to be sure, can you show the systemd version you were using here?
> The intent was to check with systemd from wily-proposed, with the
> regular wily kernel.

I thought the idea was to use a xenial kernel on wily?

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

Title:
  unprivileged lxc containers won't start, need to put sessions into
  "pids"  cgroup controller

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

-- 
Ubuntu-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 1545913] [NEW] [FFe] juju-core 2.0

[Martin Pitt]

Launchpad Bug Tracker [2016-02-17 19:37 -]:
> - Removal of LXC from 2.0 codebase

Does that mean "in favor of LXD", or "juju-local will be dropped"? I
guess/hope the latter, but making sure :-)

-- 
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 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Martin Pitt]

> Hence my original proposed test for the file's existence.

This isn't very robust, as it blows up if the glob expands to more than
one file. That also Should Not Happen™, but I prefer to just quiesce the
error. I fixed that in http://anonscm.debian.org/cgit/collab-maint/pm-
utils.git/commit/?id=aa33266.

I'll reupload the SRU with that too, thanks for pointing out!

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1544612/+subscriptions

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

[Bug 1502045] Re: Move from consolekit to logind

[Martin Pitt]

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

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

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

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

Title:
  Move from consolekit to logind

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

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

[Bug 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Martin Pitt]

I uploaded the adjusted patch to the trusty-proposed SRU queue.

** Tags added: hw-specific

** Changed in: pm-utils (Ubuntu Trusty)
   Status: New => In Progress

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1544612/+subscriptions

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

[Bug 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Martin Pitt]

Thanks Dirk! I committed http://anonscm.debian.org/cgit/collab-maint/pm-
utils.git/commit/?id=1b7600eca which is more liberal about the spelling
now.

** Changed in: pm-utils (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1544612/+subscriptions

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

[Bug 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Martin Pitt]

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

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

** Changed in: pm-utils (Ubuntu)
   Status: New => In Progress

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

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1544612/+subscriptions

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

[Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

[Martin Pitt]

bug 1539488 is nothing new and not related to systemd.

** Tags removed: verification-failed

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

Title:
  unprivileged lxc containers won't start, need to put sessions into
  "pids"  cgroup controller

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

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

[Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

[Martin Pitt]

Bas, any chance to test the update in -proposed so that we can release
that?

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

Title:
  unprivileged lxc containers won't start, need to put sessions into
  "pids"  cgroup controller

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

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

[Bug 1543051] Re: New helpers version fail on "unknown initscript"

[Martin Pitt]

Fix committed to Debian master branch: http://anonscm.debian.org/cgit
/collab-maint/init-system-helpers.git/commit/?id=628cb4328

Will backport to xenial.

** Changed in: init-system-helpers (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  New helpers version fail on "unknown initscript"

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

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

[Bug 1543051] Re: New helpers version fail on "unknown initscript"

[Martin Pitt]

I now downloaded the current xenial/amd64 Launchpad chroot tarball
(which is really still wily), dist-upgraded that, and installed ofono,
and I can reproduce the regression with that.

** Changed in: init-system-helpers (Ubuntu)
   Status: New => In Progress

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

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

Title:
  New helpers version fail on "unknown initscript"

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

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

[Bug 1543051] Re: New helpers version fail on "unknown initscript"

[Martin Pitt]

I tried to reproduce this in a current xenial schroot (with policy-rc.d)
and VM, and apt-get install ofono works in both cases. In the build log
this happens while upgrading init-system-helpers as well, though, which
might have an influence on this.

** Changed in: init-system-helpers (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  New helpers version fail on "unknown initscript"

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

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

[Bug 1543025] Re: Wrong UTC zoneinfo in cloud-images

[Martin Pitt]

I downloaded the current amd64 cloud image and dissected it with kpartx,
i. e. without booting. /usr/share/zoneinfo/Zulu is correct there, i. e.
127 bytes. So indeed it sounds like this file gets overwritten by cloud-
init.

** 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/1543025

Title:
  Wrong UTC zoneinfo in cloud-images

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

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

[Bug 1543025] Re: Wrong UTC zoneinfo in cloud-images

[Martin Pitt]

I think the bug is here in cloudinit/distros/__init__.py:

def set_etc_timezone(tz, tz_file=None, tz_conf="/etc/timezone",
 tz_local="/etc/localtime"):
util.write_file(tz_conf, str(tz).rstrip() + "\n")
# This ensures that the correct tz will be used for the system
if tz_local and tz_file:
util.copy(tz_file, tz_local)
return

/etc/localtime ought to be a symlink to the selected file in
/usr/share/zoneinfo/, not a copy (it used to in the past due to the
possibility of /usr/ being on a separate file system, but that got fixed
by initramfs-tools in a better way now). So with the copy() the symlink
doesn't get updated, and instead it clobbers the file in /usr/.

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

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: High
   Status: Triaged

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

Title:
  Wrong UTC zoneinfo in cloud-images

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

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

[Bug 1543016] [NEW] lxc-destroy --quiet is not quiet

[Martin Pitt]

Public bug reported:

Since version 2.0.0beta, lxc-destroy is now verbose even when calling
with --quiet:

$ sudo lxc-clone -o adt-xenial -n foo
$ sudo lxc-destroy --quiet -n foo 
Destroyed container foo

Not a biggie, but it broke some expectation in autopkgtest. I'll work
around it there, but this doesn't look intended.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxc 2.0.0~beta2-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CurrentDesktop: i3
Date: Mon Feb  8 09:05:08 2016
EcryptfsInUse: Yes
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dnsmasq.conf:
 enable-tftp
 tftp-root=/tmp/tftp
 dhcp-boot=pxelinux.0
lxc.conf: lxc.lxcpath = /srv/lxc

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


** Tags: amd64 apparmor apport-bug xenial

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

Title:
  lxc-destroy --quiet is not quiet

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

** Changed in: init-system-helpers (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

I don't think we ever support running lxc-android-config *in* a
container, so this doesn't block the removal and merging the new init-
system-helpers.

** Changed in: lxc-android-config (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1541914] Re: passwd depends on init-system-helpers (>= 1.18~); however: Version of init-system-helpers on system is 1.14

[Martin Pitt]

https://platform-qa-jenkins.ubuntu.com/view/Upgrade/job/upgrade_ubuntu-
trusty-xenial-basic-amd64_qemu/74/console

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

Title:
  passwd depends on init-system-helpers (>= 1.18~); however: Version of
  init-system-helpers on system is 1.14

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

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

[Bug 1454725] Re: openvpn no longer called with "--script-security 2"

[Martin Pitt]

Uploaded this. It would be great if you could test 2.3.10-1ubuntu2 and
confirm that this works now, as I don't use OpenVPN in that mode.

** Changed in: openvpn (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  openvpn no longer called with "--script-security 2"

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

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

[Bug 1454725] Re: openvpn no longer called with "--script-security 2"

[Martin Pitt]

Yes, I think that makes sense, if that change is still
intended/sensible.

** Changed in: openvpn (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: openvpn (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: openvpn (Ubuntu)
Milestone: None => ubuntu-16.02

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

Title:
  openvpn no longer called with "--script-security 2"

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

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

[Bug 1454725] Re: openvpn does not use OPTARGS from /etc/default/openvpn

[Martin Pitt]

** Summary changed:

- openvpn fails after upgrade from 14.10 to 15.04
+ openvpn does not use OPTARGS from /etc/default/openvpn

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

Title:
  openvpn does not use OPTARGS from /etc/default/openvpn

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

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

[Bug 1460712] Re: Powernap systemd setup is broken

[Martin Pitt]

The two suggested changes make sense; please drop "Requires=network"
completely, you only need the After=network.target.

But I can't get powernap to run at all in current xenial -- running
"sudo /usr/sbin/powernapd" in a VM or a container immediately exits. It
just writes the pid file and then exits with 0.

** Changed in: powernap (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  Powernap systemd setup is broken

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

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

[Bug 1511524] Re: OpenVPN PAM authentication broken on 15.10 Server

[Martin Pitt]

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

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

Title:
  OpenVPN PAM authentication broken on 15.10 Server

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

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

[Bug 1454273] Re: irqbalance should not run in container - add systemd unit

[Martin Pitt]

Standard LXC images don't have irqbalance. Upstream says that in some
corner cases you might want it in containers too, and as you have to
explicitly install it I don't consider this high importance.

** Changed in: irqbalance (Ubuntu)
   Importance: High => Medium

** Tags removed: systemd-boot

** Summary changed:

- irqbalance should not run in container - add systemd unit
+ irqbalance should not run in container

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

Title:
  irqbalance should not run in container

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

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

[Bug 1454273] Re: irqbalance should not run in container - add systemd unit

[Martin Pitt]

** Changed in: irqbalance (Ubuntu)
Milestone: ubuntu-15.11 => None

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

Title:
  irqbalance should not run in container - add systemd unit

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

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

[Bug 1533833] Re: unprivileged lxc containers won't start, need to put sessions into "pids" cgroup controller

[Martin Pitt]

Bug 1538960 is unrelated and a local configuration error.

** Tags removed: verification-failed

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

Title:
  unprivileged lxc containers won't start, need to put sessions into
  "pids"  cgroup controller

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

lxc-android-config will be fixed by landing
https://code.launchpad.net/~vorlon/lxc-android-config/apport-job-
cleanup/+merge/274497

** Changed in: lxc-android-config (Ubuntu)
   Status: New => Fix Committed

** Changed in: lxc-android-config (Ubuntu)
   Status: Fix Committed => In Progress

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

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

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

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

** No longer affects: gnupg2 (Debian)

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

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

** Also affects: lxc-android-config (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

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

** Changed in: flash-kernel (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

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

** Changed in: memtest86+ (Ubuntu)
   Status: New => Fix Committed

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

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

** Changed in: flash-kernel (Ubuntu)
   Importance: Undecided => Low

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

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

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

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

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

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

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

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

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1539016] Re: Remove /bin/running-in-container

[Martin Pitt]

Added tasks for all packages in main and restricted. universe and
multiverse are still running.

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

** Also affects: memtest86+ (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: flash-kernel (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1527641] Re: package init 1.22ubuntu11 failed to install/upgrade: pre-dependency problem - not installing init

[Martin Pitt]

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

** This bug has been marked a duplicate of bug 1032823
   package libdevmapper-event1.02.1 2:1.02.48-4ubuntu7.1 failed to 
install/upgrade: ErrorMessage: dependency problems - leaving unconfigured

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

Title:
  package init 1.22ubuntu11 failed to install/upgrade: pre-dependency
  problem - not installing init

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

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

[Bug 1539016] [NEW] Remove /bin/running-in-container

[Martin Pitt]

Public bug reported:

We still have an ubuntu delta in init-system-helper that adds /bin
/running-in-container. This is just a (currently over-complicated)
wrapper around "systemd-detect-virt --container". That works under any
init system and is what upstreams and some packages already use, so
let's cut out that delta.

I'm currently running an archive grep to find remaining users.

** Affects: init-system-helpers (Ubuntu)
 Importance: Low
 Assignee: Martin Pitt (pitti)
 Status: In Progress

** Changed in: init-system-helpers (Ubuntu)
   Status: New => In Progress

** Changed in: init-system-helpers (Ubuntu)
   Importance: Undecided => Low

** Changed in: init-system-helpers (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  Remove /bin/running-in-container

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

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

[Bug 1410604] Re: ISST-LTE: unable to open rtc device

[Martin Pitt]

The only place known to me that does that is /etc/init.d/hwclock.sh,
which is from util-linux. Something similar is also done under upstart
from /etc/init/hwclock.conf where hwclock is called with --systz. This
quite plausibly opens rtc as well.

However, these two scripts aren't being run at all any more under
systemd -- there it would be timedated which accesses /dev/rtc, but I
don't see how this is being activated that early (it usually doesn't run
at boot at all).

Can you please confirm whether this happens under upstart or systemd? In
the latter case, can you please do

   sudo journalctl -b > /tmp/journal.txt

and attach /tmp/journal.txt here? Thanks!

** Package changed: init-system-helpers (Ubuntu) => util-linux (Ubuntu)

** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Low

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

Title:
  ISST-LTE: unable to open rtc device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1410604/+subscriptions

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

[Bug 1534340] Re: openssh server 6.6 does not report max auth failures

[Martin Pitt]

Hello Kees, or anyone else affected,

Accepted openssh into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:6.6p1-2ubuntu2.5 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: openssh (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  openssh server 6.6 does not report max auth failures

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

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

[Bug 1536021] Re: [xenial/armhf] lxc-stop --kill hangs forever, container pid 1 in 'D' state

[Martin Pitt]

restarting lxcfs helps: The hanging container pid 1 and lxc-stop
finally finish, and the container stops.

** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu)

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

Title:
  [xenial/armhf] lxc-stop --kill hangs forever, container pid 1 in 'D'
  state

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

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

[Bug 1536568] Re: please merge openvpn from debian

[Martin Pitt]

Sponsored, thank you!

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

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

Title:
  please merge openvpn from debian

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

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

[Bug 1536522] Re: juju-local: systemd units fail on boot

[Martin Pitt]

Oh, I see what's wrong: They run /var/lib/juju/init/juju-agent-martin-
local/exec-start.sh, which runs

  /home/martin/.juju/local/tools/machine-0/jujud

This can't work, as my home directory does not exist until I log in
(it's encrypted). This will equally affect /home on NFS and the like.

 * Do these juju and mongodb processes need to run as root? If they can
run as (my) user, then these two services should become session services
instead of system services.

 * If they do need to run as root, please put the data into /var/lib
somewhere, as you can't assume access to /home directories with system
services.

** Summary changed:

- juju-local: systemd units fail on boot
+ juju-local: systemd units fail on boot if /home is not accessible before 
logging in

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

Title:
  juju-local: systemd units fail on boot if /home is not accessible
  before logging in

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

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

[Bug 1536522] [NEW] juju-local: systemd units fail on boot if /home is not accessible before logging in

[Martin Pitt]

Public bug reported:

I have juju-local deployed on current xenial. This works fine right
after installation (except for bug 1534106), but after a fresh boot
"juju status" hangs. I have two failed units:

$ systemctl --failed
  UNITLOAD   ACTIVE SUBDESCRIPTION
● juju-agent-martin-local.service loaded failed failed juju agent for machine-0
● juju-db-martin-local.serviceloaded failed failed juju state database


Unfortunately they don't do any error logging to the journal, they just exit 
with 127:

$ sudo systemctl status -l juju-agent-martin-local.service
● juju-agent-martin-local.service - juju agent for machine-0
   Loaded: loaded 
(/var/lib/juju/init/juju-agent-martin-local/juju-agent-martin-local.service; 
enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Do 2016-01-21 08:51:31 CET; 27min 
ago
 Main PID: 1017 (code=exited, status=127)

Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Main 
process exited, code=exited, status=127/n/a
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Unit 
entered failed state.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Failed with 
result 'exit-code'.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Service 
hold-off time over, scheduling restart.
Jan 21 08:51:31 donald systemd[1]: Stopped juju agent for machine-0.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Start 
request repeated too quickly.
Jan 21 08:51:31 donald systemd[1]: Failed to start juju agent for machine-0.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Unit 
entered failed state.
Jan 21 08:51:31 donald systemd[1]: juju-agent-martin-local.service: Failed with 
result 'start-limit'.

juju-db-martin-local.service repeatedly fails with exit code 1, but
otherwise it's a similar output.

They can be manually started after booting with sudo systemctl start
'juju-*' though, and then things work. So it looks like they are missing
some dependency?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: juju-core 1.25.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
Uname: Linux 4.3.0-6-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 21 09:16:05 2016
EcryptfsInUse: Yes
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  juju-local: systemd units fail on boot if /home is not accessible
  before logging in

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

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

[Bug 1536525] [NEW] juju-local: Don't depend on rsyslog

[Martin Pitt]

Public bug reported:

Please drop the "Depends: rsyslog-gnutls". rsyslog is not a required
part of the installation any more as we have the systemd journal now.
With enabling persistent journal having rsyslog is just a waste as it
logs everything again but in a much less convenient way.

I disabled rsyslog.service to work around bug 1534106, so juju is
clearly not strictly requiring rsyslog to operate. Thus, can you  please
at least drop this to Recommends: so that it can be purged? Or even
better yet, eliminate the dependency completely and use the systemd
journal?

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: juju-core 1.25.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
Uname: Linux 4.3.0-6-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 21 09:26:51 2016
EcryptfsInUse: Yes
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  juju-local: Don't depend on rsyslog

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

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

[Bug 1534106] Re: rsyslogd crashed with SIGSEGV with juju-local configuration

[Martin Pitt]

** Changed in: rsyslog (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

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

Title:
  rsyslogd crashed with SIGSEGV with juju-local configuration

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

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