Jack Lin

https://www.linkedin.com/in/jack-lin-a43506a2/ [email protected]

SUSE Taiwan SUSE Software Engineer

Results 13 comments of


                                            Jack Lin

[BUG] Somehow the Rebuilding field inside volume.meta is set to true causing the volume to stuck in attaching/detaching loop

From other user's report, this might be the root cause There was one Volume with 2 replicas (A,B) A failed first and B tried to rebuild A by syncing files...

[BUG] LH manager reboots due to the webhook is not ready

The root cause is that we now have conversion-webhook(`:9501`), admission-webhook(`:9502`) in longhorn-manager We set the readiness port to `9501` The order of starting is as follow 1. conversion-webhook 2. admission-webhook...

chore(vendor): update go-common-libs/go-iscsi-helper and resolve breaking changes

Depends on PRs: - `longhorn-engine`: https://github.com/longhorn/longhorn-engine/pull/1050 - `longhorn-instance-manager`: https://github.com/longhorn/longhorn-instance-manager/pull/434 - `longhorn-share-manager`: https://github.com/longhorn/longhorn-share-manager/pull/155

chore(vendor): update go-common-libs/go-iscsi-helper and resolve breaking changes

> This pull request is now in conflict. Could you fix it @ChanYiLin? 🙏 Fixed.

fix: parse the process name to get the process type instead of using port count

Need to wait until IM PR merged, so I can update the vendor here. https://github.com/longhorn/longhorn-instance-manager/pull/407

fix: parse the process name to get the process type instead of using port count

Wait for https://github.com/longhorn/go-common-libs/pull/25

fix: parse the process name to get the process type instead of using port count

> This pull request is now in conflict. Could you fix it @ChanYiLin? 🙏 fixed.

fix: parse the process name to get the process type instead of using port count

> @ChanYiLin any updates? Waiting for https://github.com/longhorn/longhorn-instance-manager/pull/407 So we can update the vendor in manager

feat(doc): introduce global tolerations and nodeselectors for user deployed components

> @ChanYiLin I have completed the review. Can we specify where users can find the **Edit as YAML** button on the Rancher UI? Hi @jillian-maroket It is quite hard to...

feat(doc): introduce global tolerations and nodeselectors for user deployed components

Hi @jillian-maroket Fixed, thank you!

1
2
›