Bug#770776: release-notes: Bug#770776: LXC breakage and workarounds when upgrading VMs to jessie

2015-01-01 Thread Niels Thykier
Control: tags -1 pending

On 2014-12-30 16:59, Tomas Pospisek wrote:
> On Sun, 7 Dec 2014, Adam D. Barratt wrote:
> 
> [...]
> 
> So please check, if required criticise and please apply the patch.
> 

Applied with modifications (please see attached patch).  The summary:

 * Some minor wording changes / sentence movements.
 * Move section to issues rather than upgrading
 * (More) Cross-linking between LXC section and systemd migration
   section.
 * Add a note that the LXC section does *not* apply to "normal"
   end-user systems.


> Thanks you all for contributing and considering and have a wonderful 2015!
> *t
> 
> PS: Many thanks to Niels and Holger for their kind and supportive words!
> This patch is dedicated to you guys!!
> 

Same to you and you are welcome :)

> PPS: Adam and Niels and Daniel, could you please have a look at #774204.
>  If you don't object Daniel, I'd propose to NMU that and ask you
>  release team to have it included in jessie. Please follow up in
>  #774204!

Ok, will follow up.

~Niels


>From 8c90bfcdccee633689895828084637cf5cb2e682 Mon Sep 17 00:00:00 2001
From: nthykier 
Date: Thu, 1 Jan 2015 12:20:39 +
Subject: [PATCH] en/issues: Document LXC migration issues

Amendments by nthykier:
 * Some minor wording changes / sentence movements.
 * Move section to issues rather than upgrading
 * (More) Cross-linking between LXC section and systemd migration
   section.
 * Add a note that the LXC section does *not* apply to "normal"
   end-user systems.

Signed-off-by: Niels Thykier 

git-svn-id: svn+ssh://svn.debian.org/svn/ddp/manuals/trunk/release-notes@10573 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 en/issues.dbk | 83 +++
 1 file changed, 78 insertions(+), 5 deletions(-)

diff --git a/en/issues.dbk b/en/issues.dbk
index b9dcf29..fd35ba7 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -210,11 +210,15 @@ $ echo 'openssh-server openssh-server/permit-root-login boolean true' | debconf-
 preference for another init such as sysvinit-core or upstart, it is recommended to setup
-APT pinning prior to the upgrade.  As an example, to prevent
-systemd from being
-installed during the upgrade, you can create a file called
-/etc/apt/preferences.d/local-pin-init with
-the following contents:
+APT pinning prior to the upgrade.  This may also be required if
+you are upgrading LXC containers before the host.  In this case,
+please refer to 
+  
+  As an example, to prevent systemd from being installed during the
+upgrade, you can create a file called
+/etc/apt/preferences.d/local-pin-init with the
+following contents:
   
   
 Package: systemd-sysv
@@ -300,6 +304,75 @@ ProtectSystem=yes
   
 
 
+
+
+Upgrade considerations for LXC hosts and containers
+
+
+  
+This section only applies to systems that has LXC containers and
+hosts.  Normal end user systems usually do not have these.
+  
+
+
+The upgrade from wheezy to jessie will migrate your system to the
+systemd init system by default (see ).
+
+
+When upgrading a LXC container, respectively a LXC virtual
+machine, this will have different consequences depending on
+whether the host system has already
+been upgraded to jessie or not.
+
+
+
+Upgrading LXC guests running on wheezy hosts
+
+
+  If you are upgrading a LXC guest container that is running on a
+  Wheezy host system, then you will need to
+  prevent the guest from being automatically migrated to systemd.  You
+  prevent the migration via pinning, as described in .
+
+
+  This is required as the Wheezy host lacks functionality to boot a
+  system running systemd.
+
+
+  You should be able to switch over to systemd inside the LXC guest
+  once you have upgraded the host system to
+  Jessie. See the next paragraph for things that need to be adapted on
+  Jessie hosts.
+
+
+
+
+Upgrading LXC guests running on jessie hosts
+
+
+  In order to be able to boot LXC guests with systemd, you need to
+  adapt your LXC container configuration.  The container configuration
+  can usually be found in
+  /var/lib/lxc/CONTAINER_NAME/config
+  You need to add the following two settings to the configuration:
+
+
+lxc.autodev = 1
+lxc.kmsg = 0
+
+
+
+
+Further information
+
+  You can find further information on LXC in Debian
+  in the Debian wiki.
+
+
+
+
 
 
   
-- 
2.1.4



Bug#770776: release-notes: Bug#770776: LXC breakage and workarounds when upgrading VMs to jessie

2014-12-30 Thread Tomas Pospisek

On Sun, 7 Dec 2014, Adam D. Barratt wrote:


Is this still relevant after the upload of lxc 1.0.6-5?


Yes, it still is. There are still manual steps needed during upgrade. 
Attached you'll find my second try at a patch to the release notes.


If my suggested addition is acceptable and not too far off the mark, then 
I suggest to apply it *now*. Changes and improvements can be incorporated 
into the patched release-notes. The reason is, that it took me one month 
to come back to this issue and I don't know when I'll have the next 
opportunity to work on this. And I'd rather have the problem documented in 
the interest of the users.


That said, please do criticise, if there's something to improve.

So please check, if required criticise and please apply the patch.

Thanks you all for contributing and considering and have a wonderful 2015!
*t

PS: Many thanks to Niels and Holger for their kind and supportive words!
This patch is dedicated to you guys!!

PPS: Adam and Niels and Daniel, could you please have a look at #774204.
 If you don't object Daniel, I'd propose to NMU that and ask you
 release team to have it included in jessie. Please follow up in
 #774204!diff --git en/upgrading.dbk en/upgrading.dbk
index 13b1a30..f7dc09c 100644
--- en/upgrading.dbk
+++ en/upgrading.dbk
@@ -1136,6 +1136,79 @@ entries.  You should use visudo for this:
 
 
 
+
+LXC
+
+
+The upgrade from wheezy to jessie will migrate your system to
+the systemd init system.
+
+
+When upgrading a LXC container, respectively a LXC virtual
+machine, this will have different consequences depending on
+whether the host system has allready
+been upgraded to jessie or not.
+
+
+
+Upgrading LXC guests running on wheezy hosts
+
+
+If you are upgrading a LXC guest container that is running on a
+wheezy host system, then you will need to
+prevent the guest from being automatically migrated to systemd.
+
+
+If you don't prevent the system from migrating to systemd, then
+you will risk, that your guest system will not be able to boot.
+
+
+This is due to functionality missing in wheezy hosts, that are
+required to boot a jessie system with systemd.
+
+
+You prevent the migration via pinning, as described in chapter
+.
+
+
+You should be able to switch over to systemd inside the LXC guest
+once you have upgraded the host system to jessie. See the next
+paragraph for things that need to be adapted on jessie hosts.
+
+
+
+
+Upgrading LXC guests running on jessie hosts
+
+
+In order to be able to boot LXC guests with systemd, you need
+to adapt your LXC container configuration.
+
+
+The container configuration can usually be found in
+
+
+/var/lib/lxc/CONTAINER_NAME/config
+
+
+You need to add the following two setting to the configuration:
+
+
+lxc.autodev = 1
+lxc.kmsg = 0
+
+
+
+
+Further information
+
+You can find further information on LXC in Debian
+in the Debian wiki.
+
+
+
+
+