mgr/dashboard: multicluster management e2e tests

[nizamial09]

auth, edit, reconnect and disconnect another cluster

Contribution Guidelines

• To sign and title your commits, please refer to Submitting Patches to Ceph.

• If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

• When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

• Tracker (select at least one)
  • References tracker ticket
  • Very recent bug; references commit where it was introduced
  • New feature (ticket optional)
  • Doc update (no ticket needed)
  • Code cleanup (no ticket needed)
• Component impact
  • Affects Dashboard, opened tracker ticket
  • Affects Orchestrator, opened tracker ticket
  • No impact that needs to be tracked
• Documentation (select at least one)
  • Updates relevant documentation
  • No doc update is appropriate
• Tests (select at least one)
  • Includes unit test(s)
  • Includes integration test(s)
  • Includes bug reproducer
  • No tests

Show available Jenkins commands

• jenkins retest this please
• jenkins test classic perf
• jenkins test crimson perf
• jenkins test signed
• jenkins test make check
• jenkins test make check arm64
• jenkins test submodules
• jenkins test dashboard
• jenkins test dashboard cephadm
• jenkins test api
• jenkins test docs
• jenkins render docs
• jenkins test ceph-volume all
• jenkins test ceph-volume tox
• jenkins test windows
• jenkins test rook e2e

[cloudbehl]

jenkins retest this please

[nizamial09]

jenkins test dashboard

[nizamial09]

jenkins test dashboard cephadm

[cloudbehl]

@nizamial09 lets focus on merging this one. So we can catch any unwanted changes on multi-cluster.

[nizamial09]

@nizamial09 lets focus on merging this one. So we can catch any unwanted changes on multi-cluster.

updated, it passed locally for me. let's see how this run goes.

[nizamial09]

@cloudbehl good thing is we have multi-cluster e2e passing now. but there are other flaky failures in the e2e which are unrelated

 Muti-cluster management page
    ✓ should authenticate the second cluster (7466ms)
    ✓ should switch to the second cluster and back to hub
    ✓ should reconnect the second cluster (6773ms)
    ✓ should edit the second cluster
    ✓ should disconnect the second cluster (6780ms)