Skip to content

Actions: longhorn/longhorn

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
2,500+ workflow runs
2,500+ workflow runs

Filter by Workflow

⌥ + click/return to exclude

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
[BUG] Auto-salvage creates duplicate replica for strict-local volumes during node reboot [Issue Management] Update Community Issue Status, Sprint and Milestone #15418: Issue #12319 labeled by derekbit
6s
6s
[BUG] Auto-salvage creates duplicate replica for strict-local volumes during node reboot [Issue Management] Update Issue Status in Longhorn Sprint Project #8705: Issue #12319 assigned by derekbit
13s
13s
[BUG] Auto-salvage creates duplicate replica for strict-local volumes during node reboot [Issue Management] Close Issue #3187: Issue #12319 unlabeled by derekbit
1s
1s
[Issue Management] Close Stale Issues and PRs [Issue Management] Close Stale Issues and PRs #1339: Scheduled
26s master
master
26s
[BUG] System managed components don't respect System Managed Components Node Selector [Issue Management] Update Community Issue Status, Sprint and Milestone #15417: Issue comment #12834 (comment) created by derekbit
10s
10s
[BUG] System managed components don't respect System Managed Components Node Selector [Issue Management] Update Issue Status in Longhorn Sprint Project #8704: Issue #12834 labeled by derekbit
19s
19s
[BUG] System managed components don't respect System Managed Components Node Selector [Issue Management] Update Community Issue Status, Sprint and Milestone #15416: Issue #12834 labeled by derekbit
10s
10s
[BUG] System managed components don't respect System Managed Components Node Selector [Issue Management] Create Backport/Automation/UI Issue #22536: Issue #12834 labeled by derekbit
15s
15s
[BUG] System managed components don't respect System Managed Components Node Selector [Issue Management] Update Community Issue Status, Sprint and Milestone #15415: Issue comment #12834 (comment) created by derekbit
19s
19s
[IMPROVEMENT] Add validation to prevent duplicate disk paths when patching node via kubectl [Issue Management] Update Community Issue Status, Sprint and Milestone #15414: Issue comment #12480 (comment) created by longhorn-io-github-bot
18s
18s
[BUG] Snapshot timeout deadline? [Issue Management] Update Community Issue Status, Sprint and Milestone #15413: Issue comment #12828 (comment) created by shuo-wu
16s
16s
[BUG] System managed components don't respect System Managed Components Node Selector [Issue Management] Update Community Issue Status, Sprint and Milestone #15412: Issue comment #12834 (comment) edited by COLDTURNIP
50s
50s
[BUG] System managed components don't respect System Managed Components Node Selector [Issue Management] Update Community Issue Status, Sprint and Milestone #15411: Issue comment #12834 (comment) created by longhorn-io-github-bot
39s
39s
[BUG] System managed components don't respect System Managed Components Node Selector [Issue Management] Update Community Issue Status, Sprint and Milestone #15410: Issue comment #12834 (comment) created by COLDTURNIP
18s
18s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Update Community Issue Status, Sprint and Milestone #15409: Issue #12883 closed by Mmx233
14s
14s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Add Wontfix Label To Not-Planned Issue #1993: Issue #12883 closed by Mmx233
9s
9s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Create Backport/Automation/UI Issue #22535: Issue #12883 labeled by Mmx233
1s
1s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Update Issue Status in Longhorn Sprint Project #8703: Issue #12883 labeled by Mmx233
39s
39s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Update Community Issue Status, Sprint and Milestone #15408: Issue #12883 labeled by Mmx233
22s
22s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Update Issue Status in Longhorn Sprint Project #8702: Issue #12883 labeled by Mmx233
2s
2s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Create Backport/Automation/UI Issue #22534: Issue #12883 labeled by Mmx233
1s
1s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Update Community Issue Status, Sprint and Milestone #15407: Issue #12883 labeled by Mmx233
2s
2s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Update Issue Status in Longhorn Sprint Project #8701: Issue #12883 labeled by Mmx233
2s
2s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Update Community Issue Status, Sprint and Milestone #15406: Issue #12883 labeled by Mmx233
3s
3s
[BUG] V2 Data Engine: fsync'd data lost/truncated after pod force-kill and volume reattach [Issue Management] Create Backport/Automation/UI Issue #22533: Issue #12883 labeled by Mmx233
1s
1s
ProTip! You can narrow down the results and go further in time using created:<2026-04-01 or the other filters available.