Skip to content

Actions: longhorn/longhorn

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
53,459 workflow runs
53,459 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Create Backport/Automation/UI Issue #21065: Issue #12384 labeled by w7team
1s
1s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Update Community Issue Status, Sprint and Milestone #10627: Issue #12384 labeled by w7team
23s
23s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Update Issue Status in Longhorn Sprint Project #5995: Issue #12384 labeled by w7team
29s
29s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Update Community Issue Status, Sprint and Milestone #10626: Issue #12384 labeled by w7team
2s
2s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Update Issue Status in Longhorn Sprint Project #5994: Issue #12384 labeled by w7team
2s
2s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Create Backport/Automation/UI Issue #21064: Issue #12384 labeled by w7team
1s
1s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Update Issue Status in Longhorn Sprint Project #5993: Issue #12384 labeled by w7team
14s
14s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Create Backport/Automation/UI Issue #21063: Issue #12384 labeled by w7team
1s
1s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Update Community Issue Status, Sprint and Milestone #10625: Issue #12384 labeled by w7team
13s
13s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Update Issue Status in Longhorn Sprint Project #5992: Issue #12384 labeled by w7team
1s
1s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Add Issue To Projects #1744: Issue #12384 opened by w7team
11s
11s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Create Backport/Automation/UI Issue #21062: Issue #12384 labeled by w7team
1s
1s
[IMPROVEMENT] After blocking the node, the instance-manager service cannot be created, causing the business node to be unable to use the storage. [Issue Management] Update Community Issue Status, Sprint and Milestone #10624: Issue #12384 labeled by w7team
1s
1s
[DOC] V2 data engine: delete snapshot after volume-head behaves inconsistently vs v1 [Issue Management] Update Community Issue Status, Sprint and Milestone #10623: Issue comment #12355 (comment) created by longhorn-io-github-bot
18s
18s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Create Backport/Automation/UI Issue #21061: Issue #12383 labeled by w7team
Skipped
Skipped
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Create Backport/Automation/UI Issue #21060: Issue #12383 labeled by w7team
1s
1s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Update Issue Status in Longhorn Sprint Project #5991: Issue #12383 labeled by w7team
1s
1s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Update Community Issue Status, Sprint and Milestone #10622: Issue #12383 labeled by w7team
28s
28s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Update Community Issue Status, Sprint and Milestone #10621: Issue #12383 labeled by w7team
2s
2s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Update Issue Status in Longhorn Sprint Project #5990: Issue #12383 labeled by w7team
30s
30s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Update Issue Status in Longhorn Sprint Project #5989: Issue #12383 labeled by w7team
12s
12s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Create Backport/Automation/UI Issue #21059: Issue #12383 labeled by w7team
1s
1s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Update Community Issue Status, Sprint and Milestone #10620: Issue #12383 labeled by w7team
12s
12s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Update Issue Status in Longhorn Sprint Project #5988: Issue #12383 labeled by w7team
2s
2s
[IMPROVEMENT]The systemManagedComponentsNodeSelector limits the scheduling scope of the instanceManager, which is misleading for dividing storage-specific nodes. [Issue Management] Create Backport/Automation/UI Issue #21058: Issue #12383 labeled by w7team
1s
1s