Add RISC-V support for testcloud provision

[peeweep]

Depend on: teemtee/testcloud#29

Pull Request Checklist

• implement the feature

[gemini-code-assist]

Code Review

This pull request adds support for the riscv64 architecture in the tmt schemas and the testcloud provisioner. The feedback suggests sorting the imported classes alphabetically in tmt/steps/provision/testcloud.py to maintain PEP 8 compliance.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[LecrisUT]

/packit build

[happz]

Given the dependency on a particular (unreleased) version of testcloud, should we add also a minimal version constraint to the specfile? Combining this tmt version and any testcloud version will not work correctly.

[LecrisUT]

should we add also a minimal version constraint to the specfile?

Oh boy, do you want to do the copr build dependency dance? We are in the issue of multiple python version dependency in different Fedora releases

[happz]

should we add also a minimal version constraint to the specfile?

Oh boy, do you want to do the copr build dependency dance? We are in the issue of multiple python version dependency in different Fedora releases

I'm not sure I follow, or at least I don't understand what kind of "dance" would this be. I'm asking because unless I misunderstand something, I see the following two issues:

• Once this MR is merged, virtual will fail to run unless the right version of testcloud is available, the one tmt could import RISCV64ArchitectureConfiguration from. tmt combined with any other testcloud version would report "failed to import testcloud" kind of error.
• Once tmt with this MR is released, updating tmt on my workstation will most likely not pull in new testcloud package, because I already have one installed. Running tmt will crash, and I will need to update testcloud as well.

TL;DR, there's a library that will add a functionality, and there's an app that requires said functionality to build new feature on top of it. It's certainly possible to package the app without requiring the library be of version that provides the functionality, or newer, but doesn't that spell breakage in possibly many environments, lowering the user experience?

[LecrisUT]

I'm not sure I follow, or at least I don't understand what kind of "dance" would this be

• we need the new testcloud version in both copr repos. PRs will be fine by
  

  tmt/.packit.yaml

  Lines 52 to 53 in 699dff2

  	additional_repos:
  	- copr://@teemtee/stable

• on testing-farm we inject the copr repo via
  

  tmt/.packit.yaml

  Lines 74 to 76 in 699dff2

  	- type: repository-file
  	# yamllint disable-line rule:line-length
  	id: https://copr.fedorainfracloud.org/coprs/g/teemtee/stable/repo/fedora-rawhide/group_teemtee-stable-fedora-rawhide.repo

  
  But that provides python3.15 versions of testcloud, not the versions that we want in the copr build artifacts (python3.14dist(testcloud))

I am not saying that we should not add the requirement restriction, just that we have to figure out the order of copr when we do so. Remember the fmf issue we had a few weeks prior

[happz]

I am not saying that we should not add the requirement restriction

Hm, I guess "Oh boy, do you want to do the copr build dependency dance?" fooled me then, I took it as a rather sarcastic way of questioning the idea of adding a versioned requirement.

just that we have to figure out the order of copr when we do so.

Sure.

Remember the fmf issue we had a few weeks prior

Wasn't that complicated by fmf also depending on tmt for some reason?

[peeweep]

If using a testcloud version without teemtee/testcloud#29, it'll fail with:

cannot import name 'RISCV64ArchitectureConfiguration' from 'testcloud.domain_configuration'

Updated the minimum testcloud version to 0.11.9 in pyproject.toml and tmt.spec (assuming teemtee/testcloud#29 will be merged in 0.11.9)