Bug #50771
closedmgr/dashboard: test_error force maintenance dashboard check
0%
Description
2021-05-11T17:21:42.502 INFO:tasks.workunit.client.0.smithi005.stdout: 1) Hosts page
2021-05-11T17:21:42.502 INFO:tasks.workunit.client.0.smithi005.stdout: when Orchestrator is available
2021-05-11T17:21:42.502 INFO:tasks.workunit.client.0.smithi005.stdout: should force enter host into maintenance:
2021-05-11T17:21:42.502 INFO:tasks.workunit.client.0.smithi005.stdout: AssertionError: Timed out retrying: Expected to find content: 'Continue' within the selector: 'cd-modal button' but never did.
2021-05-11T17:21:42.502 INFO:tasks.workunit.client.0.smithi005.stdout: at HostsPageHelper.maintenance (https://smithi005.front.sepia.ceph.com:8443/__cypress/tests?p=cypress/integration/orchestrator/01-hosts-force-maintenance.e2e-spec.ts:215:16)
2021-05-11T17:21:42.503 INFO:tasks.workunit.client.0.smithi005.stdout: at HostsPageHelper.descriptor.value (https://smithi005.front.sepia.ceph.com:8443/__cypress/tests?p=cypress/integration/orchestrator/01-hosts-force-maintenance.e2e-spec.ts:367:20)
2021-05-11T17:21:42.503 INFO:tasks.workunit.client.0.smithi005.stdout: at Context.eval (https://smithi005.front.sepia.ceph.com:8443/__cypress/tests?p=cypress/integration/orchestrator/01-hosts-force-maintenance.e2e-spec.ts:334:23)
2021-05-11T17:21:42.503 INFO:tasks.workunit.client.0.smithi005.stdout:
Updated by Nizamudeen A almost 3 years ago
- Status changed from In Progress to Fix Under Review
Updated by Ernesto Puerta almost 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Ernesto Puerta almost 3 years ago
- Has duplicate Bug #51672: mgr/dashboard: test_dashboard_e2e.sh: "AssertionError: Timed out retrying: Expected to find content: 'Continue' within the selector: 'cd-modal button' but never did." added
Updated by Backport Bot almost 3 years ago
- Copied to Backport #51685: pacific: mgr/dashboard: test_error force maintenance dashboard check added
Updated by Loïc Dachary over 2 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".