[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#770776: marked as done (LXC breakage and workarounds when upgrading VMs to jessie)

Your message dated Wed, 14 Jan 2015 19:49:34 +0100
with message-id <54B6BA3E.1000908@thykier.net>
and subject line Re: Bug#770776: release-notes: Bug#770776: LXC breakage and workarounds when upgrading VMs to jessie
has caused the Debian Bug report #770776,
regarding LXC breakage and workarounds when upgrading VMs to jessie
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

770776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770776
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: important
Tags: patch

Dear release-notes maintainers,

LXC VMs become unbootable when upgraded to jessie.

The upgrade migrates systems automatically to systemd, after which the
VMs won't be able to boot.

The simplest workaround currently is to upgrade and then, before
rebooting, to switch back to sysv.

I'm trying to collect information about this problem and possible
work-arounds in the wiki [1], and will try to extract and refine a
proposed text for the release-notes.

My first proposed text for the release-notes is below. Please let me
know if you prefer me to submit a proper patch against a SVN checkout of

In chapter "4.5.7. Special care for specific packages" I propose to
introduce a new subchapter " LXC" with the following text:

  The upgrade from wheezy to jessie will switch the init system to
  systemd. Currently LXC VMs running systemd inside are not able to
  The workaround is to proceed with the upgrade, but *before* a
  reboot of the VM, switch back to the original init system.
  You can determine your current init system with the following
      # dpkg -S /sbin/init | sed 's/:.*//'
  If you are running with the default sysvinit init system, then
  switch back to your original init system with:
      # apt-get install sysvinit-core systemd-shim

  This will reinstall the sysvinit init system and deinstall systemd.

  You can find further information on LXC in Debian
  [[https://wiki.debian.org/LXC|in the Debian wiki]].



[1] https://wiki.debian.org/LXC

-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
On 2015-01-01 13:23, Niels Thykier wrote:
> Control: tags -1 pending
> [...]
> 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.

I got no remarks on this patch, so I am taking the liberty of closing
this now.  If you notice anything that needs to be improved with this
section, please file a new bug for it.

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

For reference, this got closed as well and has been unblocked now.


--- End Message ---

Reply to: