longhorn: [BUG]When the manager started, it reports failed to release lock
When a manager starts with other managers at the same time, some of them already finished the upgrade process but reports:
E0521 01:05:33.053845 1 leaderelection.go:282] Failed to release lock: Lease.coordination.k8s.io "longhorn-manager-upgrade-lock" is invalid: spec.leaseDurationSeconds: Invalid value: 0: must be greater than 0
This will delay the starting of managers in multiple nodes.
Longhorn version: v0.8.1
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 25 (18 by maintainers)
Commits related to this issue
- docs: add manual test for upgrade lease lock This tests the fix for the upgrade leader election issue described in longhorn/longhorn#1379. Signed-off-by: Michael William Le Nguyen <michael@mail.ttp.... — committed to ttpcodes/longhorn-tests by ttpcodes 4 years ago
- docs: add manual test for upgrade lease lock This tests the fix for the upgrade leader election issue described in longhorn/longhorn#1379. Signed-off-by: Michael William Le Nguyen <michael@mail.ttp.... — committed to longhorn/longhorn-tests by ttpcodes 4 years ago
- docs: add manual test for upgrade lease lock This tests the fix for the upgrade leader election issue described in longhorn/longhorn#1379. Signed-off-by: Michael William Le Nguyen <michael@mail.ttp.... — committed to yasker/longhorn-tests by ttpcodes 4 years ago
- docs: add manual test for upgrade lease lock This tests the fix for the upgrade leader election issue described in longhorn/longhorn#1379. Signed-off-by: Michael William Le Nguyen <michael@mail.ttp.... — committed to longhorn/longhorn-tests by ttpcodes 4 years ago
Hello,
After upgrade to
v1.0.0we are having the same error you mentioned but also causing an outage of thelonghorn-manager