Skip to content

Actions: vesoft-inc/nebula-operator

Actions

Auto label

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
check_label.yml
323 workflow runs
323 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

backup not support concurrency value Auto label #535: Issue #456 unlabeled by jinyingsunny
February 28, 2024 10:01 15s
February 28, 2024 10:01 15s
backup not support concurrency value Auto label #534: Issue #456 opened by jinyingsunny
February 28, 2024 10:00 18s
February 28, 2024 10:00 18s
backup not support concurrency value Auto label #533: Issue #456 labeled by jinyingsunny
February 28, 2024 10:00 18s
February 28, 2024 10:00 18s
restore cross namespace, when set clusterNamespace with wrong value ,no error log print Auto label #532: Issue #451 opened by jinyingsunny
February 26, 2024 07:02 15s
February 26, 2024 07:02 15s
restore cross namespace, when set clusterNamespace with wrong value ,no error log print Auto label #531: Issue #451 labeled by jinyingsunny
February 26, 2024 07:02 17s
February 26, 2024 07:02 17s
restore cross namespace, when set clusterNamespace with wrong value ,no error log print Auto label #530: Issue #451 labeled by jinyingsunny
February 26, 2024 07:02 14s
February 26, 2024 07:02 14s
restore cross namespace, when set clusterNamespace with wrong value ,no error log print Auto label #529: Issue #451 labeled by jinyingsunny
February 26, 2024 07:02 17s
February 26, 2024 07:02 17s
when i am commented out dynamic param, the value keeps as the Previous setting Auto label #528: Issue #445 unlabeled by jinyingsunny
February 25, 2024 10:20 14s
February 25, 2024 10:20 14s
when i am commented out dynamic param, the value keeps as the Previous setting Auto label #527: Issue #445 labeled by jinyingsunny
February 25, 2024 10:20 17s
February 25, 2024 10:20 17s
when i am commented out dynamic param, the value keeps as the Previous setting Auto label #526: Issue #445 closed by jinyingsunny
February 25, 2024 10:19 15s
February 25, 2024 10:19 15s
when restart single storaged pod, if the number is wrong, it steal keep retry and block the following correct restart command Auto label #525: Issue #443 unlabeled by jinyingsunny
February 25, 2024 10:13 16s
February 25, 2024 10:13 16s
when restart single storaged pod, if the number is wrong, it steal keep retry and block the following correct restart command Auto label #524: Issue #443 labeled by jinyingsunny
February 25, 2024 10:13 12s
February 25, 2024 10:13 12s
when restart single storaged pod, if the number is wrong, it steal keep retry and block the following correct restart command Auto label #523: Issue #443 closed by jinyingsunny
February 25, 2024 10:11 16s
February 25, 2024 10:11 16s
when restart metad cluster without transfer meta leader Auto label #522: Issue #423 unlabeled by jinyingsunny
February 25, 2024 10:05 12s
February 25, 2024 10:05 12s
when restart metad cluster without transfer meta leader Auto label #521: Issue #423 labeled by jinyingsunny
February 25, 2024 10:05 16s
February 25, 2024 10:05 16s
when restart metad cluster without transfer meta leader Auto label #520: Issue #423 closed by jinyingsunny
February 25, 2024 10:04 18s
February 25, 2024 10:04 18s
when br-restore not finished but delete nr and new nebula cluster, then operator print error log Auto label #519: Issue #450 opened by jinyingsunny
February 23, 2024 06:56 12s
February 23, 2024 06:56 12s
when br-restore not finished but delete nr and new nebula cluster, then operator print error log Auto label #518: Issue #450 labeled by jinyingsunny
February 23, 2024 06:56 17s
February 23, 2024 06:56 17s
when br-restore not finished but delete nr and new nebula cluster, then operator print error log Auto label #517: Issue #450 labeled by jinyingsunny
February 23, 2024 06:56 12s
February 23, 2024 06:56 12s
when br-restore not finished but delete nr and new nebula cluster, then operator print error log Auto label #516: Issue #450 labeled by jinyingsunny
February 23, 2024 06:56 14s
February 23, 2024 06:56 14s
backup to s3, when bucket not exist ,backup mission keep no moving Auto label #515: Issue #448 closed by jinyingsunny
February 23, 2024 03:29 13s
February 23, 2024 03:29 13s
backup to s3, when bucket not exist ,backup mission keep no moving Auto label #514: Issue #448 opened by jinyingsunny
February 22, 2024 03:21 13s
February 22, 2024 03:21 13s
backup to s3, when bucket not exist ,backup mission keep no moving Auto label #513: Issue #448 labeled by jinyingsunny
February 22, 2024 03:21 13s
February 22, 2024 03:21 13s
backup to s3, when bucket not exist ,backup mission keep no moving Auto label #512: Issue #448 labeled by jinyingsunny
February 22, 2024 03:21 14s
February 22, 2024 03:21 14s
backup to s3, when bucket not exist ,backup mission keep no moving Auto label #511: Issue #448 labeled by jinyingsunny
February 22, 2024 03:21 14s
February 22, 2024 03:21 14s