@JorisK said: fix/update-transfer-size-calculation Confirming that the branch fixes it

@carloum70 If you are willing to try this, you can reset the primary management interface (PMI) on a bond, WIthin the bash shell: : xe pif-list This will show the PIFs and their current network associations. Identify the bond master PIF If you have a bonded network, the master PIF is the one that represents the bond. You can list it with: xe pif-list network-uuid=<bond-uuid> The master PIF is the one that will be used as the primary interface for the bond. Reset the management interface to the bond master Use the xe-reset-networking command with the --reset-primary option: xe-reset-networking --reset-primary This will move the management interface to the bond master PIF, which is the correct way to reassign it when the bond is created or reconfigured.

Got a response Yes, sorry, this was not properly pointed out in the release message. This comes from using https://github.com/piraeusdatastore/linstor-csi/releases/tag/v1.13.0 So you can still use the new operator, but you have to downgrade the LINSTOR CSI version until you upgrade the cluster. So doing that for now with the following helm values --- operator: resources: requests: cpu: 250m memory: 500Mi limits: memory: 1Gi installCRDs: true imageConfigOverride: - base: quay.io/piraeusdatastore components: linstor-satellite: image: piraeus-server tag: v1.33.1 linstor-csi: image: piraeus-csi tag: v1.12.0 tls: certManagerIssuerRef: name: pp-step-issuer kind: StepClusterIssuer group: certmanager.step.sm