Wait for Foreman tasks in backup integration tests

Open Beginner friendly
  • Is something wrong?
#894 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@jakduch is already working on this.

Since Sep 27, 2026.

  • #895 by @jakduch — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
cli, testing-qa

Research direction

Locate the backup integration fixture that invokes foremanctl backup, then compare its success-path setup with the failing CI jobs linked in the issue. Verify the fixture waits for active tasks while the user-facing default remains fail-fast, and rerun the Satellite and IOP integration jobs to confirm successful archive creation.

Written by the indexing model from the issue text.

Description

The backup integration fixture exercises successful archive creation immediately after deployment. Satellite and IOP deployments can still have valid Foreman tasks in progress, but the fixture invokes foremanctl backup without --wait-for-tasks. The production preflight then correctly rejects the backup before any archive is written.

This is reproducible in the exact-head CI for PR #892:

The success-path fixture should opt into waiting for active tasks. The user-facing default must remain fail-fast unless --wait-for-tasks is explicitly requested.

Dominant language
Python
Stars
26
Forks
56
Avg merge
2d 18h
Merged PRs (30d)
34

Getting set up

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.

More from theforeman/foremanctl

All issues in theforeman/foremanctl

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.