2021-11-04: QA smoke test failure in gstg

Current Status

More information will be added as we investigate the issue.

Failing job: https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/5347375
Failing QA pipeline: https://ops.gitlab.net/gitlab-org/quality/staging/-/pipelines/874034
Coordinated pipeline: https://ops.gitlab.net/gitlab-org/release/tools/-/pipelines/873823
Diff of changes on gstg: https://gitlab.com/gitlab-org/security/gitlab/-/compare/f4620a9fe55...97ee889c8d7

Failing job logs:

Plan Editing scoped labels on issues correctly applies simple and multiple colon scoped pairs labels
     Failure/Error:
       show.select_labels_and_refresh(
         [
           new_label_same_scope,
           new_label_different_scope,
           new_label_same_scope_multi_colon,
           new_label_different_scope_multi_colon
         ]
       )
     
     Capybara::ElementNotFound:
       Unable to find css "[data-qa-selector=\"labels_edit_button\"],.qa-labels-edit-button"
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/node/finders.rb:303:in `block in synced_resolve'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/node/base.rb:83:in `synchronize'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/node/finders.rb:292:in `synced_resolve'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/node/finders.rb:53:in `find'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/session.rb:762:in `find'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/dsl.rb:53:in `call'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/dsl.rb:53:in `find'
     # ./qa/page/base.rb:206:in `click_element'
     # ./qa/support/page/logging.rb:80:in `click_element'
     # ./qa/page/component/issuable/sidebar.rb:108:in `block in select_labels_and_refresh'
     # ./qa/support/retrier.rb:51:in `block in retry_until'
     # ./qa/support/repeater.rb:43:in `repeat_until'
     # ./qa/support/retrier.rb:42:in `retry_until'
     # ./qa/page/component/issuable/sidebar.rb:107:in `select_labels_and_refresh'
     # ./qa/specs/features/ee/browser_ui/2_plan/scoped_labels/editing_scoped_labels_spec.rb:41:in `block (4 levels) in <module:QA>'
     # ./qa/scenario/actable.rb:16:in `perform'
     # ./qa/specs/features/ee/browser_ui/2_plan/scoped_labels/editing_scoped_labels_spec.rb:40:in `block (3 levels) in <module:QA>'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
     # ./spec/spec_helper.rb:92:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
     # ./qa/specs/runner.rb:74: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:44: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/bootable.rb:44:in `launch!'
Finished in 11 minutes 35 seconds (files took 3.17 seconds to load)
16 examples, 1 failure
Failed examples:
rspec ./qa/specs/features/ee/browser_ui/2_plan/scoped_labels/editing_scoped_labels_spec.rb:39 # Plan Editing scoped labels on issues correctly applies simple and multiple colon scoped pairs labels

Timeline

Recent Events (available internally only):

All times UTC.

2021-11-04

06:30 - QA smoke tests fail and is retried: https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/5347201.
07:08 - @rpereira2 declares incident in Slack after the retry also fails.
10:26 - Confirmed that feature flag labels_widget being turned on in staging is the cause of the failure.
10:45 - Feature flag labels_widget is turned off on staging and production, and a new QA pipeline is started.
11:00 - QA pipeline passes.

Corrective Actions

Corrective actions should be put here as soon as an incident is mitigated, ensure that all corrective actions mentioned in the notes below are included.

Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.

Click to expand or collapse the Incident Review section.

Incident Review

Ensure that the exec summary is completed at the top of the incident issue, the timeline is updated and relevant graphs are included in the summary
If there are any corrective action items mentioned in the notes on the incident, ensure they are listed in the "Corrective Action" section
Fill out relevant sections below or link to the meeting review notes that cover these topics

Customer Impact

Who was impacted by this incident? (i.e. external customers, internal customers)
1. ...
What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
1. ...
How many customers were affected?
1. ...
If a precise customer impact number is unknown, what is the estimated impact (number and ratio of failed requests, amount of traffic drop, ...)?
1. ...

What were the root causes?

Incident Response Analysis

How was the incident detected?
1. ...
How could detection time be improved?
1. ...
How was the root cause diagnosed?
1. ...
How could time to diagnosis be improved?
1. ...
How did we reach the point where we knew how to mitigate the impact?
1. ...
How could time to mitigation be improved?
1. ...
What went well?
1. ...

Post Incident Analysis

Did we have other events in the past with the same root cause?
1. ...
Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
1. ...
Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
1. ...

Lessons Learned

Guidelines

Blameless RCA Guideline

Resources

If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)

Edited Nov 04, 2021 by Reuben Pereira