Bug 2428855

Summary:	tmt+provision-bootc: fails to install from EPEL 10.2
Product:	[Fedora] Fedora EPEL	Reporter:	Carl George 🎩 <carl>
Component:	tmt	Assignee:	Cristian Le <fedora>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel10	CC:	fedora, lzachar, mhlavink, mvadkert, psplicha, tbajer
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tmt-1.67.0-1.el10_2	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-02-18 05:03:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Carl George 🎩 2026-01-13 03:09:47 UTC

Description of problem:
tmt+provision-bootc from EPEL 10.2 has one or more unresolved dependencies, causing it to be uninstallable.


Version-Release number of selected component (if applicable):
tmt+provision-bootc-1.64.0-3.el10_2


How reproducible:
always


Steps to Reproduce:
1. dnf install tmt+provision-bootc


Actual results:
Error: 
 Problem: problem with installed package filesystem-3.18-17.el10.x86_64
  - package tmt+provision-bootc-1.64.0-3.el10_2.noarch from epel requires (podman-machine if (filesystem(x86-64) or filesystem(aarch-64))), but none of the providers can be installed
  - conflicting requests


Expected results:
successful installation


Additional info:
The installability test for this bodhi update reported success.  I looked at the log, and it seems that during the test podman-machine is getting installed from the centos-stream-buildroot repo, which is not a normal repo available to end users to satisfy runtime requirements.  It shouldn't be enabled during the installability test, and I'll report that as well.

Comment 1 Carl George 🎩 2026-01-13 03:27:30 UTC

https://github.com/fedora-ci/installability-pipeline/issues/60

Comment 2 Petr Šplíchal 2026-01-29 15:03:14 UTC

Filed an upstream issue here:

* https://github.com/teemtee/tmt/issues/4534

We'll try to handle that in the next sprint.

Comment 3 Cristian Le 2026-02-05 09:48:33 UTC

Will be resolved next release (next week)

Comment 4 Fedora Update System 2026-02-13 16:18:40 UTC

FEDORA-EPEL-2026-b932b6d2c2 (tmt-1.67.0-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-b932b6d2c2

Comment 5 Fedora Update System 2026-02-14 01:49:14 UTC

FEDORA-EPEL-2026-b932b6d2c2 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-b932b6d2c2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-02-18 05:03:28 UTC

FEDORA-EPEL-2026-b932b6d2c2 (tmt-1.67.0-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.