Failure in browser_ui/9_data_stores/user/parent_group_access_termination_spec.rb | Data Stores User when parent group membership is terminated is not allowed to edit the project files

Full description

Data Stores User when parent group membership is terminated is not allowed to edit the project files

File path

./qa/specs/features/browser_ui/9_data_stores/user/parent_group_access_termination_spec.rb

Stack trace

Failure/Error: members_page.remove_member(user.username)

Capybara::ElementNotFound:
  Unable to find css "[data-qa-selector=\"user_action_dropdown\"],.qa-user-action-dropdown" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[3]/DIV[1]/DIV[3]/MAIN[1]/DIV[2]/DIV[1]/DIV[2]/DIV[2]/DIV[1]/DIV[1]/DIV[2]/TABLE[1]/TBODY[1]/TR[1]">

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

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

Screenshot:

added 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/9769411

changed due date to May 13, 2023

assigned to @ddavison

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

marked this issue as related to #407225 (closed)

bundle exec rspec qa/specs/features/browser_ui/9_data_stores/user/parent_group_access_termination_spec.rb

Appears to work okay on GDK -- notably in the screenshot above the option to open the members isn't available. It should look something like this.

However -- I've retried running this in staging and I can reproduce just as in the original issue.

And shortly later -- the tests are passing in staging for me when I run locally. I'm unsure what may have caused this, as it was temporarily reproducible, but appears to be working again now locally.

Screen_Recording_2023-04-13_at_18.06.23

added found:canary.staging.gitlab.com label

This issue was automatically tagged with the label groupsource code by TanukiStan, a machine learning classification model, with a probability of 0.66.

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 groupsource code labels

added devopscreate sectiondev labels

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

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

mentioned in issue gitlab-com/gl-infra/production#8717 (closed)

[Apr 13 2023 15:34:32 UTC (QA Tests)] INFO  -- filling :login_field with "gitlab-qa-bot"
[Apr 13 2023 15:34:32 UTC (QA Tests)] INFO  -- clicking the coordinates of :login_field
[Apr 13 2023 15:34:32 UTC (QA Tests)] INFO  -- filling :password_field with "*****"
[Apr 13 2023 15:34:32 UTC (QA Tests)] INFO  -- clicking the coordinates of :password_field
[Apr 13 2023 15:34:38 UTC (QA Tests)] INFO  -- clicking :sign_in_button
[Apr 13 2023 15:34:42 UTC (QA Tests)] INFO  -- Visiting QA::Resource::Group at https://staging.gitlab.com/groups/gitlab-qa-sandbox-group-5/group-to-test-access-termination-205f652d460aef70
[Apr 13 2023 15:34:43 UTC (QA Tests)] INFO  -- clicking :sidebar_menu_item_link
[Apr 13 2023 15:34:46 UTC (QA Tests)] INFO  -- filling :search_bar_input with "qa-user-044ca8aaab5fcf45"
[Apr 13 2023 15:34:46 UTC (QA Tests)] INFO  -- clicking the coordinates of :search_bar_input
[Apr 13 2023 15:34:46 UTC (QA Tests)] INFO  -- clicking :search_button
[Apr 13 2023 15:34:47 UTC (QA Tests)] INFO  -- clicking :user_action_dropdown
[Apr 13 2023 15:34:57 UTC (QA Tests)] INFO  -- Saving screenshot..
      is not allowed to edit the project files (FAILED - 1)

It's clear that we should be using the gitlab-qa-bot user here who should have admin access.

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

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

added Category:Source Code Management label

This was a valid failure - see 2023-04-13: QA pipelines failing on gstg and gs... (gitlab-com/gl-infra/production#8717 - closed) but is now resolved.

closed