On Mon, 2014-03-24 at 09:40 -0700, Kir Kolyshkin wrote:
Thank you for detailed position. I have already rolled back to the old
versioning scheme,
please check packages in wheezy-test and let me know if anything is
wrong there.
Things look pretty good in wheezy-test. Thanks for the work.
Hi all
I happened to be able to crash one hostnode of our testing cluster when
restoring a CT.
Hostnodes:
* 3 hostnodes running Debian 7 amd64 with OpenVZ kernel
* Kernel: 042stab085.20
* VE_ROOT / VE_PRIVATE is on an NFS mount shared by nodes
Test-CT:
* Debian 7 from self-made template
*
These may be alternatives for version numbering (I've tested them with
dpkg --compare-versions):
As a complete upstream version:
42.85.20
Combining old and new schema:
042+stab085.20
El 26/03/14 17:07, Roman Haefeli ha escrit:
On Mon, 2014-03-24 at 09:40 -0700, Kir Kolyshkin wrote:
Thank you
Hello Roman,
Could you file a bug to bugzilla.openvz.org and assign it to me?
Thanks.
On Wed, Mar 26, 2014 at 05:35:55PM +0100, Roman Haefeli wrote:
Hi all
I happened to be able to crash one hostnode of our testing cluster when
restoring a CT.
Hostnodes:
* 3 hostnodes running Debian 7
I can confirm there is an issue in upgrading on wheezy (stable).
It uses linux-image-openvz-amd64 042+1 instead of
the regular version and generates /boot/vmlinuz-2.6.32-openvz-amd64 instead
of the prefixed version, i.e.:
/boot/vmlinuz-2.6.32-openvz-042stab084.17-amd64
