Failure in browser_ui/3_create/repository/merge_with_code_owner_in_subgroup_spec.rb | Create Codeowners when the project is in a subgroup and the code owner is the root group behaves like code owner merge request is approved and merged

Full description

Create Codeowners when the project is in a subgroup and the code owner is the root group behaves like code owner merge request is approved and merged

File path

./qa/specs/features/ee/browser_ui/3_create/repository/merge_with_code_owner_in_subgroup_spec.rb

Stack trace

Failure/Error: raise Validatable::PageValidationError, "#{element.name} did not appear on #{self.name} as expected"

QA::Page::Validatable::PageValidationError:
  navbar did not appear on QA::Page::Main::Menu as expected
Shared Example Group: "code owner merge request" called from ./qa/specs/features/ee/browser_ui/3_create/repository/merge_with_code_owner_in_subgroup_spec.rb:37

First happened in https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/9737248.

Related test case: https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/347801.

Screenshot:

added Enterprise Edition QA Quality failurenew found:staging.gitlab.com priority2 test labels

Failed most recently in staging pipeline: https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/9748544

changed due date to May 11, 2023

assigned to @nprabakaran

mentioned in issue gitlab-org/quality/testcase-sessions#68562 (closed)

Able to reproduce it locally when run against staging.

Passed when feature flag identity_verification_phone_number was set to false on staging.

/cc @hmehra

This issue was automatically tagged with the label groupcode review by TanukiStan, a machine learning classification model, with a probability of 1.

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 groupcode review labels

added devopscreate sectiondev labels

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

added automation:ml wrong groupsource code typeignore labels and removed groupcode review label

added failureinvestigating label and removed failurenew label

Passed in the pipeline where the feature flag identity_verification_phone_number was set to false on staging.

@eugielimpin would you have any idea of why it might be failing? Happy to get on a call and pair

Yep, I can reproduce it on staging as well.

The tests pass when the feature flag identity_verification_phone_number is enabled & Email confirmation setting = Off/Soft.

But, when Email confirmation setting = Hard, it gives the error that the Account hasn't been activated yet.

This is because, during the tests we create a QA user, who we then to try to log-in as

=> Built a QA::Resource::User with username 'qa-user-80c3ee21a6481d45' via api in 1.31 seconds
...

filling :login_field with "qa-user-80c3ee21a6481d45"
> Account not activated

My hunch is that we aren't bypassing identity verification properly when both identity_verification & identity_verification_phone_number are enabled. So, I'll create a follow-up issue for this in our groupanti-abuse board

Off/Soft	Hard
QA test with soft email confirmation	QA test with hard email confirmation

@hmehra Assigning this issue to you.

Closing this issue, since I have created a follow-up here: https://gitlab.com/gitlab-org/modelops/anti-abuse/team-tasks/-/issues/334

Setting label(s) Category:Source Code Management based on groupsource code.

added Category:Source Code Management label

mentioned in issue gitlab-org/quality/testcase-sessions#68649 (closed)

assigned to @hmehra

unassigned @nprabakaran

mentioned in issue #406686 (closed)

closed

mentioned in issue #406689 (closed)

mentioned in issue #406691 (closed)

mentioned in merge request !117633 (merged)