profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/innobead/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
David Ko innobead @suse Taiwan A hands-on senior software manager and architect with 10+ years software development experience. https://www.linkedin.com/in/dnkforever/

harvester/harvester 1429

Open source hyperconverged infrastructure (HCI) software

innobead/kubefire 142

KubeFire 🔥, creates and manages Kubernetes Clusters using Firecracker microVMs

innobead/huber 65

Huber 📦, simplify the package management from GitHub projects with a built-in awesome list of popular projects

innobead/gogradle 5

A Golang plugin for building, testing, dependency management and popular frameworks (gRPC, Gin, Swagger, ...) supported

innobead/kubepm 2

--KubePM, a package manager for Kuberentes development setup-- replaced by Huber, https://github.com/innobead/huber

innobead/charts 0

Helm Charts

push eventlonghorn/longhorn-tests

Khushboo

commit sha 3619f4730a25c7b31a4da3eb8062938e281639a6

Fix pdoc error Signed-off-by: Khushboo <fnu.khushboo@suse.com>

view details

push time in 20 hours

PR merged longhorn/longhorn-tests

Fix pdoc error

Fix for pdoc error

Reason of failure : the hardcoded fixes nfs.s3 got replaced by a var which requires the env variable. At the time when pdoc is running the env variable is unavailable. Fix: Returning None if the env variable can’t be found

Signed-off-by: Khushboo fnu.khushboo@suse.com

+6 -1

0 comment

1 changed file

khushboo-rancher

pr closed time in 20 hours

PullRequestReviewEvent

issue commentlonghorn/longhorn

[Backport] [BUG] fsfreeze race condition

@longhorn/qa from 1.3, we will use backport issues instead of backporting labels only for ensuring the issues getting verified in all corresponding release branches, so please remember to close the backport issue after verifying in the release branch.

innobead

comment created time in 21 hours

startedkcp-dev/kcp

started time in 21 hours

push eventlonghorn/website

Derek Su

commit sha 08f1f2bf3fcea48c5f95b5ec6faa1a262cfb9b6b

Add Kb - Generate pprof runtime profiling data Longhorn #3153 Signed-off-by: Derek Su <derek.su@suse.com>

view details

push time in 21 hours

PR merged longhorn/website

Add Kb - Generate pprof runtime profiling data

Longhorn #3153

Signed-off-by: Derek Su derek.su@suse.com

+34 -0

0 comment

1 changed file

derekbit

pr closed time in 21 hours

PR merged longhorn/longhorn-tests

Reviewers
Update manual test case for "Test backing image / Test upload"

Update backing image test upload manual test case with extended tests for uploading through Rancher UI and Ingress Controller. To covering following issues:

  • longhorn/longhorn#3129
  • longhorn/longhorn#2937
+19 -0

1 comment

1 changed file

kaxing

pr closed time in a day

push eventlonghorn/longhorn-tests

Yung

commit sha 3d99d8b1bd757b14a39ed0fe747bbb581825cecb

modified: docs/content/manual/release-specific/v1.2.0/test-backing-image-upload.md Update backing image test upload manual testcase with extended tests through different proxies. Signed-off-by: Yung <yung.shen@suse.com>

view details

Yung

commit sha de81dff4a6c2d60cd16f0f5144a2b5e731e12b17

Update test-backing-image-upload.md based on comments. Signed-off-by: Yung <yung.shen@suse.com>

view details

Yung

commit sha eef5a28c8703cd365776a69a2545329c93c22072

Update test-backing-image-upload.md based on comments - Use the offical Rancher component naming: Cluster Explorer and Apps & Marketplace, to make the test case more consistent. Signed-off-by: Yung <yung.shen@suse.com>

view details

push time in a day

PullRequestReviewEvent

pull request commentlonghorn/longhorn-tests

add rockylinux support to integration test

@meldafrawi Please remember to add the related issue in the ticket description. I already updated it.

meldafrawi

comment created time in a day

PullRequestReviewEvent
PullRequestReviewEvent

push eventlonghorn/longhorn-tests

Chris Chien

commit sha f1050e47c393fa2a590a903af26b7e5b0374c20d

fix pod not terminated problem Signed-off-by: Chris Chien <chris.chien@suse.com>

view details

Chris Chien

commit sha ba24bce905981e6725da4e7d7f3a2783cb470b2f

minor fix for flake8 Signed-off-by: Chris Chien <chris.chien@suse.com>

view details

push time in a day

PR merged longhorn/longhorn-tests

Reviewers
Failed test case : test_rwx.py::test_rwx_statefulset_scale_down_up

Signed-off-by: Chris Chien chris.chien@suse.com Failed in all recent tests.

Because when script started to check pod should not exist, pod was still terminating. Modified code to make sure pod really not exist before entering next steps.

Update This PR was from task in issue #3081

+11 -7

0 comment

1 changed file

chanow816

pr closed time in a day

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

push eventlonghorn/longhorn-tests

Chris Chien

commit sha d8d897f35e37412e9261cf1f4933017d61d272b4

Update wait_for_all_instance_manager_running Signed-off-by: Chris Chien <chris.chien@suse.com>

view details

push time in 2 days

PR merged longhorn/longhorn-tests

Reviewers
Flakiness test case : test_node_config_annotation_missing (test_node.py)

This test case is flakiness because during testing run time , instance-manager-r restarted and in teardown step check instance-manager-r running well.

Sometimes, test completed and entering teardown steps, the instance-manager-r still in terminating then got a new name, but teardown still use old name(terminated one), script got api response code 500 and direct raise error.

So I added try - except section in wait_for_all_instance_manager_running(), let the retry mechanism can still work.

+24 -18

0 comment

1 changed file

chanow816

pr closed time in 2 days

PullRequestReviewEvent

push eventlonghorn/longhorn-tests

Khushboo

commit sha 8726ddad6852d7b330c4a9b9a956f21e855789f7

Add test cases skeleton for im deletion Signed-off-by: Khushboo <fnu.khushboo@suse.com>

view details

push time in 2 days

PullRequestReviewEvent

push eventlonghorn/longhorn-tests

Shatakshi

commit sha dbf732a4ddea4d0ab56372d595211f6dd2ca9bcb

Fix shellcheck errors Signed-off-by: Shatakshi <shatakshi.gupta85@gmail.com>

view details

push time in 2 days

PR merged longhorn/longhorn-tests

Fix shellcheck errors

Signed-off-by: Shatakshi shatakshi.gupta85@gmail.com Related to Bugbash. Fixed errors reported by sonatype lift.

+5 -5

0 comment

4 changed files

Shatakshi0805

pr closed time in 2 days

Pull request review commentlonghorn/longhorn-tests

Update manual test case for "Test backing image / Test upload"

 title: Test backing image 9. Create and attach a volume with the backing image. Verify the data content is correct. 10. Do cleanup. +### Upload via Rancher URI+<sup>Related issue: [3129](https://github.com/longhorn/longhorn/issues/3129)</sup>+1. Create or import cluster into Rancher+2. Go into the cluster+3. Click Longhorn from the left sidebar+4. Open Longhorn UI from the Rancher UI+   - An example URL: <small>`https://rancer.server.domain/k8s/clusters/CLUSTER-ID/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/proxy/#/backingImage`</small>+5. Create a new backing image with **Upload From Local**+6. Verify the uploaded image matches its size or checksum

Agree, we don't need to duplicate the steps in different test cases and focus on what you want to test. Here, it's upload through rancher ui or ingress.

kaxing

comment created time in 2 days