[BUG] failure of language tests when specifying options for multi-worker tests in FLAVOR=universal #158

New Issue

2023-03-12T19:41:26Z

tcooper commented

2023-03-12 19:41:26 +00:00

(Migrated from github.com)

Describe the bug

The install_{language}_language tests of the FLAVOR=universal test suite fail consistently in production openQA system when options for FLAVOR=universal supporting multi-worker tests are added.

When multi-worker options are provided the test jumps straight into the Network Configuration spoke after Language Selection instead of back to the Anaconda Main Hub. This causes a persistent failure of needle match and the test eventually times out.

When multi-worker options are not provided the test returns to the Anaconda Main Hub correctly after Network Configuration.

The behavior, although the test flow is slightly different for 8.7 and 9.1, is consistent in both OS with failure after Language Specification when multi-worker options are provided.

Refs

No multi-worker options: install_european_language (re-start of successful test)
Multi-worker options: install_european_language (re-start of failing test)

Note: The two tests were run concurrently as re-starts of previous tests at the same time on separate workers.

Expected behavior

The install_{language}_language tests of the FLAVOR=universal test suite pass consistently regardless of multi-worker options being supplied or not.

Screenshots

`install_european_language` stuck in Network Configuration after Language Selection

`install_european_language` progresses to Anaconda Main Hub after Language Selection

## Describe the bug The `install_{language}_language` tests of the `FLAVOR=universal` test suite fail consistently in production openQA system when options for `FLAVOR=universal` supporting multi-worker tests are added. When multi-worker options are provided the test jumps straight into the Network Configuration spoke after Language Selection instead of back to the Anaconda Main Hub. This causes a persistent failure of needle match and the test eventually times out. When multi-worker options are not provided the test returns to the Anaconda Main Hub correctly after Network Configuration. The behavior, although the test flow is slightly different for 8.7 and 9.1, is consistent in both OS with failure after Language Specification when multi-worker options are provided. ### Refs - No multi-worker options: [`install_european_language`](https://openqa.rockylinux.org/tests/11523#) (re-start of successful test) - Multi-worker options: [`install_european_language`](https://openqa.rockylinux.org/tests/11524#) (re-start of failing test) Note: The two tests were run concurrently as re-starts of previous tests at the same time on separate workers. ## Expected behavior The `install_{language}_language` tests of the `FLAVOR=universal` test suite pass consistently regardless of multi-worker options being supplied or not. ## Screenshots ### `install_european_language` stuck in Network Configuration after Language Selection ![install_european_language-post-language-select-failure](https://user-images.githubusercontent.com/542846/224568799-784c8f81-71e6-4187-b198-65b916991cd3.png) ### `install_european_language` progresses to Anaconda Main Hub after Language Selection ![install_european_language-post-language-select-success](https://user-images.githubusercontent.com/542846/224568807-899f5d26-1c7f-4b30-8636-27c0b8e141a5.png)

Sign in to join this conversation.