openshift / openshift/os

enable additional tests

Open
#568 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

lifecycle/frozen
Dominant language
Shell
Stars
135
Forks
131
Avg merge
4d 13h
Merged PRs (30d)
6

Description

We hit a situation where the downstream tests behind the RHT firewall caught an issue with the RHCOS compose because we aren't running the same suite of tests upstream. Notably the kola testiso tests.

+ kola testiso -S --qemu-native-4k --qemu-multipath --scenarios iso-install --output-dir tmp/kola-metal4k
Testing scenarios: [iso-install]
Successfully tested scenario pxe-install for 49.84.202106211326-0 on bios (metal)
Successfully tested scenario iso-install for 49.84.202106211326-0 on bios (metal)
Successfully tested scenario iso-offline-install for 49.84.202106211326-0 on bios (metal)
[Pipeline] }
Error: scenario iso-install: timed out after 10m0s
2021-06-21T14:25:48Z cli: scenario iso-install: timed out after 10m0s

In this case, the root cause was a missing patch to Ignition in the 4.9 builds.

In build-test-qemu.sh, there is a TODO about turning on additional tests but there is a want for multiple tiers and splitting them into pods.

https://github.com/openshift/os/blob/38dd8888309f8a43a9163ee9372416e1bddac0b8/ci/build-test-qemu.sh#L26-L28

Are we in a position to try turning on more tests now? Do we need to design how multiple tiers would work? Or are we waiting for a gangplank future?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the TODO in ci/build-test-qemu.sh and compare the upstream test coverage with the cited kola testiso command and its iso-install scenarios. Investigate whether additional tests can be enabled directly or require test tiers and separate pods. Done means an agreed testing approach and enabled coverage that includes the relevant upstream scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
build-system, ci-cd, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.