QA failure in gdk-qa-reliable-with-load-balancer job

Summary

Failing job(s): https://gitlab.com/gitlab-org/gitlab/-/jobs/4511153438

Stack trace

$ eval "$QA_COMMAND"
bundler: failed to load command: bin/qa (bin/qa)
/builds/gitlab-org/gitlab/qa/qa/page/validatable.rb:15:in `block in validate_elements_present!': navbar did not appear on QA::Page::Main::Menu as expected (QA::Page::Validatable::PageValidationError)
	from /builds/gitlab-org/gitlab/qa/qa/page/validatable.rb:13:in `each'
	from /builds/gitlab-org/gitlab/qa/qa/page/validatable.rb:13:in `validate_elements_present!'
	from /builds/gitlab-org/gitlab/qa/qa/page/main/login.rb:265:in `sign_in_using_gitlab_credentials'
	from /builds/gitlab-org/gitlab/qa/qa/page/main/login.rb:74:in `block in sign_in_using_credentials'
	from /builds/gitlab-org/gitlab/qa/vendor/ruby/3.0.0/gems/capybara-3.39.2/lib/capybara.rb:305:in `using_wait_time'
	from /builds/gitlab-org/gitlab/qa/vendor/ruby/3.0.0/gems/capybara-3.39.2/lib/capybara/session.rb:809:in `using_wait_time'
	from /builds/gitlab-org/gitlab/qa/vendor/ruby/3.0.0/gems/capybara-3.39.2/lib/capybara/dsl.rb:28:in `using_wait_time'
	from /builds/gitlab-org/gitlab/qa/qa/page/main/login.rb:64:in `sign_in_using_credentials'
	from /builds/gitlab-org/gitlab/qa/qa/page/main/login.rb:120:in `set_up_new_password_if_required'
	from /builds/gitlab-org/gitlab/qa/qa/page/main/login.rb:124:in `set_up_new_admin_password_if_required'
	from /builds/gitlab-org/gitlab/qa/qa/page/main/login.rb:87:in `sign_in_using_admin_credentials'
	from /builds/gitlab-org/gitlab/qa/qa/scenario/actable.rb:16:in `perform'
	from /builds/gitlab-org/gitlab/qa/qa/ee/resource/license.rb:94:in `rescue in rescue in fabricate_via_api!'
	from /builds/gitlab-org/gitlab/qa/qa/ee/resource/license.rb:73:in `rescue in fabricate_via_api!'
	from /builds/gitlab-org/gitlab/qa/qa/ee/resource/license.rb:66:in `fabricate_via_api!'
	from /builds/gitlab-org/gitlab/qa/qa/resource/base.rb:65:in `block (2 levels) in fabricate_via_api!'
	from /builds/gitlab-org/gitlab/qa/qa/resource/base.rb:96:in `log_and_record_fabrication'
	from /builds/gitlab-org/gitlab/qa/qa/resource/base.rb:65:in `block in fabricate_via_api!'
	from /builds/gitlab-org/gitlab/qa/qa/resource/base.rb:86:in `do_fabricate!'
	from /builds/gitlab-org/gitlab/qa/qa/resource/base.rb:64:in `fabricate_via_api!'
	from /builds/gitlab-org/gitlab/qa/qa/resource/base.rb:37:in `fabricate!'
	from /builds/gitlab-org/gitlab/qa/qa/ee/strategy.rb:15:in `perform_before_hooks'
	from /builds/gitlab-org/gitlab/qa/qa/runtime/release.rb:25:in `public_send'
	from /builds/gitlab-org/gitlab/qa/qa/runtime/release.rb:25:in `method_missing'
	from /builds/gitlab-org/gitlab/qa/qa/scenario/template.rb:40:in `perform'
	from /builds/gitlab-org/gitlab/qa/qa/scenario/template.rb:10:in `block in perform'

Screenshot / HTML page

Possible fixes

changed due date to July 05, 2023

changed milestone to %16.2

added QA Quality devopscreate failurenew found:master priority2 test typeignore labels

added sectiondev label

cc @mlapierre in case you might have insight

The rest of the jobs didn't fail on validation

@niskhakova There was a problem with replication lag, but that was disabled in !124018 (merged)

The remaining failures still need investigation.

But I believe this is a duplicate of #415648 (closed) so I'll close this for now.

Thanks for the clarification! Looks like I missed that issue, will keep an eye on it

This issue was automatically tagged with the label grouppipeline execution by TanukiStan, a machine learning classification model, with a probability of 0.64.

If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.

If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.

Authors who do not have permission to update labels can leave the issue to be triaged by group leaders initially assigned by TanukiStan

This message was generated automatically. You're welcome to improve it.

added automation:ml grouppipeline execution labels

added devopsverify sectionci labels and removed devopscreate sectiondev labels

Another occurrence https://gitlab.com/gitlab-org/gitlab/-/jobs/4513781484

Looks like the issue is that user wasn't able to sign in Screenshot doesn't have any visible errors

mentioned in issue gitlab-org/quality/pipeline-triage#203 (closed)

marked this issue as a duplicate of #415648 (closed)

closed

marked this issue as related to #415648 (closed)