Re: [DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-12-10 Thread Roland Kammerer
On Mon, Dec 10, 2018 at 11:53:16AM +, Yannis Milios wrote: > > Hello, > > Yannis, did you managed to get rid of this warning ? Same thing here > > since last upgrade. > > > > Nothing really bad happening except this annoying warning ... > > > No, I haven’t, but doesn’t bother me as soon as

Re: [DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-12-10 Thread Yannis Milios
> Hello, > Yannis, did you managed to get rid of this warning ? Same thing here > since last upgrade. > > Nothing really bad happening except this annoying warning ... No, I haven’t, but doesn’t bother me as soon as everything is working properly. My understanding is that this warning is set

Re: [DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-12-10 Thread Julien Escario
Le 27/11/2018 à 18:08, Yannis Milios a écrit : > Upgraded to linstor-proxmox (3.0.2-3) and seems to be working well with > libpve-storage-perl  (5.0-32). > There's a warning notification during live migrates about the upgraded > storage API, but at the end the process is completed successfully.. >

Re: [DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-11-27 Thread Yannis Milios
Upgraded to linstor-proxmox (3.0.2-3) and seems to be working well with libpve-storage-perl (5.0-32). There's a warning notification during live migrates about the upgraded storage API, but at the end the process is completed successfully.. "Plugin "PVE::Storage::Custom::LINSTORPlugin" is

Re: [DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-11-27 Thread Jean-Daniel TISSOT
Hi, And the method for upgrading Proxmox is pveupgrade. Manual page for pveupgrade say : > pveupgrade(1) Proxmox Documentation pveupgrade(1) > > > NAME > > pveupgrade - wrapper arournd "apt-get dist-upgrade" > > > SYNOPSIS > > pveupgrade [--shell] > > > DESCRIPTION > > This is a small wrapper

Re: [DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-11-27 Thread Yannis Milios
Ok, I used "dist-upgrade" because that's what Proxmox recommends to do when upgrading their systems. On Tue, 27 Nov 2018 at 15:41, Roland Kammerer wrote: > On Tue, Nov 27, 2018 at 03:22:07PM +, Yannis Milios wrote: > > Hi Roland, > > > > I just did a simple ‘apt dist-upgrade’ and the rest

Re: [DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-11-27 Thread Roland Kammerer
On Tue, Nov 27, 2018 at 03:22:07PM +, Yannis Milios wrote: > Hi Roland, > > I just did a simple ‘apt dist-upgrade’ and the rest followed ... Ah yes, that is how "dist-upgrade" works. "upgrade" would not have done that. Anyways, there are "-3" versions of the plugins out now and one should be

Re: [DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-11-27 Thread Yannis Milios
Hi Roland, I just did a simple ‘apt dist-upgrade’ and the rest followed ... Yannis On Tue, 27 Nov 2018 at 14:58, Roland Kammerer wrote: > On Tue, Nov 27, 2018 at 02:13:58PM +, Yannis Milios wrote: > > Just for the record, Proxmox has released libpve-storage-perl/stable > 5.0-32 > >

Re: [DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-11-27 Thread Roland Kammerer
On Tue, Nov 27, 2018 at 02:13:58PM +, Yannis Milios wrote: > Just for the record, Proxmox has released libpve-storage-perl/stable 5.0-32 > today, which seems to break linstor-proxmox plugin. > > Reverting to libpve-storage-perl/stable 5.0-30 and reinstalling > linstor-proxmox package fixes

[DRBD-user] linstor-proxmox broken after upgrading to PVE/libpve-storage-perl/stable 5.0-32

2018-11-27 Thread Yannis Milios
Just for the record, Proxmox has released libpve-storage-perl/stable 5.0-32 today, which seems to break linstor-proxmox plugin. Reverting to libpve-storage-perl/stable 5.0-30 and reinstalling linstor-proxmox package fixes the problem. During the upgrade, the following action is taking place ...