<!--- 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/ui/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. ---> # QA Failure ## Summary <!-- Describe in detail what failed. --> Multiple E2E test failures in `e2e:self-managed`: - `spec/ui/self_managed/upgrade_license_spec.rb` - `spec/ui/self_managed/remove_license_spec.rb` - `spec/ui/self_managed/renew_license_spec.rb` - `spec/ui/self_managed/license_usage_export_spec.rb` - `spec/ui/self_managed/add_seats_spec.rb` - `spec/ui/self_managed/multi_year_subscription_spec.rb` Failing jobs: - https://gitlab.com/gitlab-org/customers-gitlab-com/-/jobs/4543474334 - https://gitlab.com/gitlab-org/customers-gitlab-com/-/jobs/4543474333 ### Stack trace Example: ```ruby User upgrades self-managed subscription with cloud license successfully upgraded to ultimate and syncs to GitLab with cloud license Failure/Error: activate_instance_with_code(subscription) Watir::Wait::TimeoutError: timed out after 30 seconds, waiting for true condition on #<Watir::TextField: located: false; {:"data-qa-selector"=>"activation_code_value", :tag_name=>"input"}> # ./vendor/ruby/3.2.0/gems/watir-7.2.2/lib/watir/wait.rb:43:in `until' # ./vendor/ruby/3.2.0/gems/watir-7.2.2/lib/watir/wait.rb:110:in `wait_until' # ./page/base.rb:225:in `find_element' # ./page/base.rb:44:in `block (3 levels) in singleton class' # ./page/base.rb:70:in `public_send' # ./page/base.rb:70:in `block (3 levels) in singleton class' # ./helper/flow.rb:60:in `block in activate_instance_with_code' # ./page/base.rb:22:in `perform' # ./helper/flow.rb:54:in `activate_instance_with_code' # ./spec/ui/self_managed/upgrade_license_spec.rb:20:in `block (3 levels) in <module:QA>' # ./vendor/ruby/3.2.0/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:124:in `block in run' # ./vendor/ruby/3.2.0/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `loop' # ./vendor/ruby/3.2.0/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `run' # ./vendor/ruby/3.2.0/gems/rspec-retry-0.6.2/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry' # ./vendor/ruby/3.2.0/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:37:in `block (2 levels) in setup' ``` ### 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 `qa/tmp` 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 <!-- Base labels. -->