Bug 2111776

Summary:	CI tier0.functional is failing – missing python3-tox
Product:	Red Hat Enterprise Linux 9	Reporter:	Lumír Balhar <lbalhar>
Component:	python3.9	Assignee:	Lukáš Zachar <lzachar>
Status:	CLOSED MIGRATED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, jwboyer, python-maint
Target Milestone:	rc	Keywords:	MigratedToJIRA, TestOnly
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-20 17:46:45 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 Lumír Balhar 2022-07-28 07:50:35 UTC

According to the logs, it seems that CI for python3.9 in C9S uses tests from Fedora but they are not able to install all dependencies because python3-tox is not available in C9S.

CI dashboard for python3.9-3.9.13-3.el9: https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/46788980
Log: http://artifacts.osci.redhat.com/testing-farm/43f0271b-e6e5-4681-8d80-4845f34e3b48/work-tests.ymlkrBhcu/ansible-output.txt

Comment 1 Miro Hrončok 2022-08-02 11:41:18 UTC

tox is in EPEL 9 now, so we could enable it. See the following commits for an example of how to use it:

https://gitlab.com/redhat/centos-stream/rpms/pyproject-rpm-macros/-/commit/76dc49fd1e2564d611175f3d3ad2c83cf43c2ab5
https://gitlab.com/redhat/centos-stream/rpms/pyproject-rpm-macros/-/commit/44772c3c74a73be96ed350a043f4a7a34e405ee7

Comment 2 RHEL Program Management 2023-09-20 17:41:43 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-20 17:46:45 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.