Multiple QA failures in Canary and Production
Summary
Failing spec(s):
- Failure in browser_ui/3_create/snippet/delete_f... (#390570 - closed)
- Failure in browser_ui/2_plan/issue/create_issue... (#390568 - closed)
- Failure in browser_ui/1_manage/group/transfer_p... (#390567 - closed)
- Failure in api/2_plan/closes_issue_via_pushing_... (#390565 - closed)
- Failure in browser_ui/10_govern/change_vulnerab... (#390559 - closed)
- Failure in browser_ui/3_create/repository/file/... (#390563 - closed)
- Failure in browser_ui/2_plan/issue/create_issue... (#390562 - closed)
- Failure in browser_ui/10_govern/scan_result_pol... (#390561 - closed)
- Failure in api/2_plan/epics_milestone_dates_spe... (#390560 - closed)
- Failure in api/2_plan/epics_milestone_dates_spe... (#390558 - closed)
- Failure in browser_ui/8_monitor/alert_managemen... (#390557 - closed)
- Failure in browser_ui/8_monitor/alert_managemen... (#390556 - closed)
- Failure in browser_ui/6_release/pipeline_status... (#390555 - closed)
Multiple QA specs failed when https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/pipelines/1713209 was deployed
Stack trace
Several cases of 404
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.:
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"]"
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'