Hi!
Here is the final release of 1.4 after 2 release candidates, it adds
support for device mapper write-cache and DRBD over NVMe.
We also improved the internal handling of snapshot objects which in turn
fixed a few snapshot related bugs and enabled support for external metadata
snapshots.
Hi!
This release has a rather big packaging change, per default python3 will
now be used.
The library was ported a long time ago to python3, while still running
python2 per default, but now
as python2 is EoL, we will per default run on python3 now.
Linbit provided packages will still use python2
Hi Robert and Rene,
thanks for the quick response. Yes, indeed Debian 9.11 seems to have
Python 3.5.3 as default for python3.
Cheers,
w.w.
On Tue, 14 Jan 2020, Robert Altnoeder wrote:
On 1/14/20 6:15 PM, Wolfgang Walkowiak wrote:
I seem to have (preliminarily) fixed it by modifying line
Hi Rene et al,
thank you for this new release. I just tried updating our linstor
controller (on a Debian 9.11 LXC container) to this new version,
ie updating the following linstor packages:
linstor-client 1.0.9-1 0.9.9-1
linstor-common 1.4.0-1
On 1/14/20 6:15 PM, Wolfgang Walkowiak wrote:
> I seem to have (preliminarily) fixed it by modifying line 373 in
> linstorapi.py as follows:
>
> # data = json.loads(resp_data)
> data = json.loads(resp_data.decode('utf-8'))
Hello,
what is the exact version of Python that
Thanks for reporting, this seems to be a problem with python 3.5.
Pythons 3.5 json.loads only accepts str type, only after python 3.6 it will
also accept str, bytes or bytearray.
I'll have that fixed in the next version so it also supports 3.5, we don't
have distributions with 3.5 so we didn't
Hi Rene et al,
I seem to have (preliminarily) fixed it by modifying line 373 in
linstorapi.py as follows:
# data = json.loads(resp_data)
data = json.loads(resp_data.decode('utf-8'))
At least
# linstor r l
provides sensible output again.
Please check whether is the
