Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/monitoring/elasticsearch/node_detail_mb·js - Monitoring app Elasticsearch node detail mb Offline Node should show node summary of NA for offline node

[kibanamachine]

A test failed on a tracked branch

TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="elasticsearchNodeDetailStatus"] [data-test-subj="transportAddress"])
Wait timed out after 10051ms
    at /opt/local-ssd/buildkite/builds/kb-cigroup-6-ceb2082ab9ed2290/elastic/kibana-hourly/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5) {
  remoteStacktrace: ''
}

First failure: CI Build - 7.x

[kibanamachine]

New failure: CI Build - 7.x

[jbudz]

Skipped in #115255 (comment)

master: 9a15bee
7.x: dee55d3

[elasticmachine]

Pinging @elastic/stack-monitoring (Team:Monitoring)

[klacabane]

Right before failing to locate the transportAddress element we're supposed to click a node in the "elasticsearch nodes list" which should route us to the node detail page where the element lives.

In the few failures I could reproduce locally, it looks like we register the click on the node but the redirection does not happen so we stay on the "nodes list" page and eventually fail. Could the link be disabled during a short time ? Could the redirection somehow loop us back to the nodes detail page ?

[klacabane]

I've been experimenting with this test a bit without much success so far. To get the test to crash in a painless way I've wrapped the case in a for loop that executes it continuously until breakage.
Some points:

• the page is in a functional state when the test breaks. The list of nodes is appearing, with clickable anchors that have correct href and a similar state than a working anchor (I've adding some attribute logging around the element we target).
• the page being in a functional state, we click the anchor but we don't get redirection. To reiterate, when we click on it the anchor does have the correct href set and selenium is successfully registering a click event
• when the test breaks, there is no http request sent (monitored via devtools network) when we click the anchor. we can move on with the hypothesis around a redirection loop that brings us back to the node list.
• i experimented with some of the testSubjects methods, like isEnabled or isDisplayed to no avail

One positive point is that I could get the test to pass consistently by adding a 1sec sleep before clicking the link. Maybe we have a stale element ? I didn't find anything explicit about this so far:

const initialElement = getElement()
const initialId = element.id;
try {
  element.click();
} catch (/* click didnt work */) {
  const currentElement = getElement();
  assert(initialId === currentElement.id); // always true
}

[neptunian]

I will try to reproduce locally as well. I wonder if, when it fails, the route is for the correct node page or still on the nodes listing page. Would be curious to log the current window.location.

[klacabane]

Fixed by #115612