Releases: LINBIT/linstor-server
Releases · LINBIT/linstor-server
v1.20.2
v1.20.1
[1.20.1] - 2022-12-13
Added
- Added NodeConnection API. Currently only used for path settings (similar to rscCon, but on node level)
Changed
- Only delete DRBD resource files after successful Controller connection (before on startup)
- MKFS: always skip discard on ZFS backed volumes
- Client resource DRBD ready state as soon as 2 nodes are connected (before it waited for all)
- ResourceGroup-Spawn: Always assume partial mode if resource group doesn't have any volume groups
- Upgraded okhttp 3rd party library, to fix a IPv6 TLS bug
- Satellite now only deletes old .res files after controller established connection (instead of after startup)
Fixed
- Orphan StorPooDfn, KeyValueStores and SnapDfn are now deleted with all their child objects
- ErrorReports delete ignored since parameter if no other was specified
v1.20.0
[1.20.0] - 2022-10-18
Added
- Added SnapshotVolumeNode as part of SnapshotNode to include a snapshot state
- Status of EBS volumes and snapshots are now queried periodically
- Added property DrbdOptions/ForceInitialSync that forces thin resources to do an initial full sync
Fixed
- Snapshots and SnapshotVolumes now properly delete their properties + cleanup migration existing DB entries
- Randomized Cluster/LocalId for CRD setups since all installations had the same ID
- Backup restore now creates new DRBD metadata and forces the initial sync to be a full sync
v1.20.0-rc.1
Added
- Added basic support for SED
- Added support for Amazon EBS storage
- Added ignore reason for storage layers. Used to skip processing resource which would fail anyway.
Changed
- Improved DB-update-logging
- ZFS: only scan datasets used by Linstor
- Improved auto-diskful mechanic, also removing exceeding replicas
Fixed
- Fixed backup with mixing internal and external metadata
- Fixed storage-pool size-check on snapshot restore
- Fixed several issues with backup-shipping (NPE, failed shippings, ...)
- Fixed auto snapshot not working after controller restart
- Fixed "LinStor" spelling errors
- Fixed PropsCon concurrentModExc
- Fixed very long k8s CRD DB backend Controller loading time
v1.19.1
v1.19.0
linstor-server 1.19.0
- Added scheduled backup shipping
- CRD backend fixes/improvements
- SOS-Report support now sending large files
- SOS-Report added more filters
- Physical-storage api use LVM VDO commands
- Fix user DRBD verify algorithm list reading/setting
- Attempt to fix stuck volume resizes
- Fix Postgresql external files updates
- Fix support for Google/DigitalOcean S3 remotes
- Autoplace: better tiebreaker with autoplace constraints
- API Version 1.14.0
v1.19.0-rc.1
linstor-server 1.19.0-rc.1
- Added scheduled backup shipping
- CRD backend fixes/improvements
- SOS-Report support now sending large files
- SOS-Report added more filters
- Physical-storage api use LVM VDO commands
- Fix user DRBD verify algorithm list reading/setting
- Attempt to fix stuck volume resizes
- Fix Postgresql external files updates
- API Version 1.14.0
v1.18.2
v1.18.1
linstor-server 1.18.1
- update drbd-options for drbd-utils 9.21.1
- Fix s3 multipart upload bug involving unit mismatch
- Allow mixing resource storage pool types for migration purposes
- Several bug fixes related to the Kubernetes database driver
- Small fixes in backup shipping
- When the DB has an error, the controller will now also have an error and stop running as the DB was empty/faulty
- Log more information on startup
- Fix local IP finding on controller
- Fix zfs snapshot restore duplicate zpool name
- Fix volume-group properties not correctly handled
- Extend rs-discard-granularity automatic checks
- Fix Node modify node-type port
- Fixes in TaskScheduler(race-conditions, exceptions)
- API Version 1.13.1
v1.18.1-rc.2
linstor-server 1.18.1-rc.2
- update drbd-options for drbd-utils 9.21.1
- Fix s3 multipart upload bug involving unit mismatch
- Allow mixing resource storage pool types for migration purposes
- Several bug fixes related to the Kubernetes database driver
- Small fixes in backup shipping
- When the DB has an error, the controller will now also have an error and stop running as the DB was empty/faulty
- Log more information on startup
- API Version 1.13.1