Do CUT test for buildah following below rules
Goal: Please run the upgrade tests for your component and modules your assigned team supports. The goal is to verify the functionality after a major version upgrade to RHEL-9.
Context: Upgradability is a feature of RHEL. While the RHEL Upgrades Subsystem team is responsible for the quality of core functionality of the upgradability toolchain (i.e. Leapp upgrade tool and the upgrade paths), they do not and can not cover all of the RHEL functionality. It is up to each assigned team to undertake functional testing of their components and modules after the upgrade.

Key information

• Compose to upgrade from: the latest RHEL-8.10.0-updates compose (https://download.eng.bos.redhat.com/rhel-8/composes/RHEL-8/)
  • make sure the following build versions are in the compose: leapp-0.20.0-2.el8_10, leapp-upgrade-el8toel9-0.23.0-2.el8_10
• Upgrade path: RHEL-8.10 to RHEL-9.8
• RHEL-9.8 RTT testing result: RHEL-9.8 RTT Compose Status Page
• Scope: Upgrade tests according to the Test Plan of your team
• Sign-off deadline: Fri 2026-02-06 (end of CTC2)
• File defects via: Jira(RHEL Project). Component: leapp-repository
• Defects relevant to partners should be labeled known_issue_98

Documents

• Components Upgrade Testing confluence page

How to perform the upgrade

• manually (you can replicate this steps into your tooling)
  • Upgrade_8_to_9_howto.md
• using tmt upgrade plans
  • rel-major-upgrade:README

Contact/feedback channels

For technical questions, you can use:

• slack: #team-rhel-upgrades
• Email: upgrades-and-conversions@redhat.com

Workflow

1. Update assignee in this issue to the person responsible for the testing.
2. Switch status to "IN PROGRESS" when the work starts.
3. Severity is designated as 'Important'; individual teams are responsible for setting the Priority according to their respective task loads.
4. Report the testing status:
   1. If you hit a test blocker (e.g. infra issue, or product defect that blocks the testing) set "Blocked: True" and add details in "Blocked Reason: field in this issue..
   2. If you find a new defect, please file a bug and add label 'known_issue_98' to the bug. You can also list the bugs in this issue.
   3. If there is a potential release blocker, please file a bug with 'Release Blocker: Proposed Blocker', and add a comment with the header "Release blocker". For the release blocker definition, please refer to the RHEL Development Guide.
   4. Finally, if no release blocker is found and the testing is finished, add a comment that your SST/SSG/team approves the compose for release.
5. Switch the ticket to "CLOSED" when the work ends.

Note: Feel free to use comments in Jira. You'll help others understand what's going on and get support eventually.
Thank you