From 10fb24d123c81988ca9a87e50eb4a2e6d7d1938b Mon Sep 17 00:00:00 2001 From: Chin-Ya Huang Date: Fri, 12 Jan 2024 10:11:23 +0800 Subject: [PATCH] test(manual): cordoned node controller renders the backup target unusable longhorn-7619 Signed-off-by: Chin-Ya Huang --- ...de-cordoned-before-longhorn-installation.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 docs/content/manual/release-specific/v1.6.0/test-list-backup-when-cluster-has-node-cordoned-before-longhorn-installation.md diff --git a/docs/content/manual/release-specific/v1.6.0/test-list-backup-when-cluster-has-node-cordoned-before-longhorn-installation.md b/docs/content/manual/release-specific/v1.6.0/test-list-backup-when-cluster-has-node-cordoned-before-longhorn-installation.md new file mode 100644 index 0000000000..a5a40de4d8 --- /dev/null +++ b/docs/content/manual/release-specific/v1.6.0/test-list-backup-when-cluster-has-node-cordoned-before-longhorn-installation.md @@ -0,0 +1,18 @@ +--- +title: Test list backup when cluster has node cordoned before Longhorn installation +--- + +## Related issue +https://github.com/longhorn/longhorn/issues/7619 + +## Test step + +**Given** a cluster has 3 worker nodes. +**And** 2 worker nodes are cordoned. +**And** Longhorn is installed. + +**When** Setting up a backup target. + +**Then** no error is observed on the UI Backup page. +**And** Backup custom resources are created if the backup target has existing backups. +