[lxc-users] LXC 1.1.3 update blocks container startup.

[Andrey Repin]

Greetings, Serge Hallyn!

>> >> >> >> What lxc version did you say you were using?
>> >> >> >
>> >> >> > Were using - 1.1.2.
>> >> >> > Then I got an upgrade and my DC didn't came up after a host reboot.
>> >> >> > Had to roll back to 1.1.2 to recover operation.
>> >> >> 
>> >> >> So to reconfirm, you now run 1.1.2, which is fine?
>> >> 
>> >> > D'oh, so was the aa-status output from 1.1.3 too?
>> >> 
>> >> No, that was with 1.1.2 active.
>> >> If it is essential to get status from 1.1.3 installed, I can arrange it, but
>> >> I'll need to schedule a maintenance window.
>> 
>> > Well hold on.  Is this trusty?  Can you show the contents of any
>> > /etc/apt/sources.list.d/* and /etc/apt/sources.list?  I'll try on a
>> > vm with all the same stuff enabled before you do that.
>> 
>> It is Precise (12.04) running Trusty kernel (linux-generic-lts-trusty)
>> Now, that you've said it. I probably have screwed something.
>> The two "backports" repos shouldn't be there. I think. I'm now trying to get
>> rid of them and reinstall whatever I've pulled from them.

> Ok let me know if that fixes it.  If not I'll try to reproduce tomorrow.

I did not manage to pinpoint any discrepancies. It did reinstall some
packages after removing the backports repos, but they were largely irrelevant,
like, apache/php.
There's some upstream backports pulled through Samba4 (namely LSB subsystem),
but the same packages are pulled on prototype system, and it works just fine.
Can we coordinate a session sometime after 18:00Z and look into it in a more
interactive manner? I'm largely omnipresent in LXC IRC.


-- 
With best regards,
Andrey Repin
Tuesday, October 6, 2015 15:14:44

Sorry for my terrible english...