Multiple QA failures in Canary and Production
<!---
Before opening a new QA failure issue, make sure to first search for it in the
QA failures board: https://gitlab.com/groups/gitlab-org/-/boards/1385578
The issue should have the following:
- The relative path of the failing spec file in the title, e.g. if the login
test fails, include `qa/specs/features/browser_ui/1_manage/login/log_in_spec.rb` in the title.
This is required so that existing issues can easily be found by searching for the spec file.
- If the issue is about multiple test failures, include the path for each failing spec file in the description.
- A link to the failing job.
- The stack trace from the job's logs in the "Stack trace" section below.
- A screenshot (if available), and HTML capture (if available), in the "Screenshot / HTML page" section below.
- A link to the corresponding test case(s) in the summary.
--->
### Summary
Failing spec(s):
- https://gitlab.com/gitlab-org/gitlab/-/issues/390570+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390568+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390567+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390565+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390559+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390563+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390562+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390561+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390560+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390558+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390557+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390556+
- https://gitlab.com/gitlab-org/gitlab/-/issues/390555+
Multiple QA specs failed when https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/pipelines/1713209 was deployed
### Stack trace
Several cases of 404
```ruby
2) Plan Epics milestone dates API updates epic dates when adding another issue
Failure/Error:
Resource::ProjectMilestone.fabricate_via_api! do |milestone|
milestone.project = project
milestone.start_date = start_date
milestone.due_date = due_date
end
QA::Resource::Errors::ResourceFabricationFailedError:
Fabrication of QA::Resource::ProjectMilestone using the API failed (404) with `{"message":"404 Project Not Found"}`.
Correlation Id: 4fe3b589a52321be4fe9c6b4e3f5b116
Sentry Url: https://sentry.gitlab.net/gitlab/gitlabcom/?environment=gprd&query=correlation_id%3A%224fe3b589a52321be4fe9c6b4e3f5b116%22
Kibana - Discover Url: https://log.gprd.gitlab.net/app/discover#/?_a=%28index:%277092c4e2-4eb5-46f2-8305-a7da2edad090%27%2Cquery%3A%28language%3Akuery%2Cquery%3A%27json.correlation_id%20%3A%204fe3b589a52321be4fe9c6b4e3f5b116%27%29%29&_g=%28time%3A%28from%3A%272023-02-05T15:46:33.186Z%27%2Cto%3A%272023-02-06T15:46:33.186Z%27%29%29
Kibana - Dashboard Url: https://log.gprd.gitlab.net/app/dashboards#/view/5e6d3440-7597-11ed-9f43-e3784d7fe3ca?_g=%28time%3A%28from:%272023-02-05T15:46:33.186Z%27%2Cto%3A%272023-02-06T15:46:33.186Z%27%29%29&_a=%28filters%3A%21%28%28query%3A%28match_phrase%3A%28json.correlation_id%3A%274fe3b589a52321be4fe9c6b4e3f5b116%27%29%29%29%29%29
# ./qa/resource/api_fabricator.rb:147:in `api_post_to'
# ./qa/resource/api_fabricator.rb:123:in `api_post'
# ./qa/resource/api_fabricator.rb:28:in `fabricate_via_api!'
# ./qa/resource/base.rb:65:in `block (2 levels) in fabricate_via_api!'
```
Page did not fully load.:
```ruby
Failures:
1) Plan Issue creation closes an issue
Failure/Error: Page::Project::Menu.perform(&:click_issues)
QA::Support::Repeater::WaitExceededError:
Page did not fully load. This could be due to an unending async request or loading icon.
# ./qa/support/repeater.rb:74:in `repeat_until'
# ./qa/support/waiter.rb:20:in `wait_until'
# ./qa/support/wait_for_requests.rb:11:in `wait_for_requests'
# ./qa/page/sub_menus/common.rb:19:in `within_sidebar'
# ./qa/page/project/sub_menus/issues.rb:19:in `click_issues'
# ./qa/scenario/actable.rb:16:in `perform'
# ./qa/specs/features/browser_ui/2_plan/issue/create_issue_spec.rb:49:in `block (3 levels) in <module:QA>'
# ./qa/specs/spec_helper.rb:120:in `block (2 levels) in <top (required)>'
# ./qa/specs/knapsack_runner.rb:15:in `run'
# ./qa/specs/runner.rb:57:in `perform'
# ./qa/scenario/template.rb:10:in `block in perform'
# ./qa/scenario/template.rb:8:in `tap'
# ./qa/scenario/template.rb:8:in `perform'
# ./qa/scenario/template.rb:50:in `perform'
# ./qa/scenario/template.rb:10:in `block in perform'
```
Unable to find visible css "input[id=\"url\"]"
```ruby
Failures:
1) Monitor Alert settings when using Prometheus integration behaves like sends test alert using authorization key creates new alert
Failure/Error: Flow::AlertSettings.integration_credentials
Capybara::ElementNotFound:
Unable to find visible css "input[id=\"url\"]"
Shared Example Group: "sends test alert using authorization key" called from ./qa/specs/features/browser_ui/8_monitor/alert_management/create_alert_using_authorization_key_spec.rb:99
# ./qa/page/project/settings/alerts.rb:108:in `webhook_url'
# ./qa/flow/alert_settings.rb:49:in `block in integration_credentials'
# ./qa/scenario/actable.rb:16:in `perform'
# ./qa/flow/alert_settings.rb:47:in `integration_credentials'
# ./qa/specs/features/browser_ui/8_monitor/alert_management/create_alert_using_authorization_key_spec.rb:40:in `block (3 levels) in <module:QA>'
# ./qa/specs/features/browser_ui/8_monitor/alert_management/create_alert_using_authorization_key_spec.rb:9:in `block (4 levels) in <module:QA>'
# ./qa/specs/spec_helper.rb:120:in `block (2 levels) in <top (required)>'
# ./qa/specs/knapsack_runner.rb:15:in `run'
# ./qa/specs/runner.rb:57:in `perform'
# ./qa/scenario/template.rb:10:in `block in perform'
# ./qa/scenario/template.rb:8:in `tap'
# ./qa/scenario/template.rb:8:in `perform'
# ./qa/scenario/template.rb:50:in `perform'
# ./qa/scenario/template.rb:10:in `block in perform'
# ./qa/scenario/template.rb:8:in `tap'
```
### Screenshot / HTML page
<!--
Attach the screenshot and HTML snapshot of the page from the job's artifacts:
1. Download the job's artifacts and unarchive them.
1. Open the `gitlab-qa-run-2020-*/gitlab-{ce,ee}-qa-*/{,ee}/{api,browser_ui}/<path to failed test>` folder.
1. Select the `.png` and `.html` files that appears in the job logs (look for `HTML screenshot: /path/to/html/page.html` / `Image screenshot: `/path/to/html/page.png`).
1. Drag and drop them here.
Note: You don't need to include a screenshot if the information it contains can be included as text. Include the text instead.
E.g., error 500/404, "Retry later" errors, etc.
If you include multiple screenshots it can be helpful to hide all but the first in a details/summary element, to avoid excessive scrolling:
<details><summary>Expand for screenshot</summary>
drag and drop the screenshot here
</details>
-->
### Possible fixes
<!-- Default due date. -->
<!-- Base labels. -->
<!-- Work classification type label, please apply ignore type label until the investigation is complete and an [issue type](https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification) is determined.-->
<!-- Test failure type label, please use just one.-->
<!--
Choose the stage that appears in the test path, e.g. ~"devops::create" for
`qa/specs/features/browser_ui/3_create/web_ide/add_file_template_spec.rb`.
-->
<!--
Select a label for where the failure was found, e.g. if the failure occurred in
a nightly pipeline, select ~"found:nightly".
-->
<!--
https://about.gitlab.com/handbook/engineering/quality/guidelines/#priorities:
- ~"priority::1": Tests that are needed to verify fundamental GitLab functionality.
- ~"priority::2": Tests that deal with external integrations which may take a longer time to debug and fix.
-->
<!-- Select the current milestone if ~"priority::1" or the next milestone if ~"priority::2". -->
issue