Bug 2062344

Summary:	RPMS should be in the Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) but are not
Product:	Red Hat Enterprise Linux 8	Reporter:	Carl Baker <carl.baker>
Component:	junit5	Assignee:	Alexander Kurtakov <akurtako>
Status:	NEW ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	---	CC:	carl.baker, john.smith
Target Milestone:	rc
Target Release:	---
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:		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 Baker 2022-03-09 15:21:14 UTC

Description of problem:

In process of migrating from rhel7 to rhel8

Certain rpms like junit, junit5, hamcrest-core, opentest4j, and
univocity-parsers can be downloaded from redhat.com web site but can't
be obtained using the subscription-manager even though they are
listed as being in the Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs).
Can download other from this repo but not these.

The downloaded from the website have the following names:
hamcrest-1.3-29.module+el8.2.1+7436+4afdca1f.src.rpm
junit-4.12-14.module+el8.2.1+7436+4afdca1f.src.rpm
junit5-5.6.2-2.module+el8.2.1+7436+4afdca1f.src.rpm
opentest4j-1.2.0-2.module+el8.2.1+7436+4afdca1f.src.rpm
univocity-parsers-2.8.4-3.module+el8.2.1+7436+4afdca1f.src.rpm

but are not listed in any of the modules components


Thanks

Comment 1 Jie Kang 2022-03-09 15:48:15 UTC

These packages are part of the Eclipse module in RHEL 8. They should theoretically be accessible after enabling the Eclipse module via:
```
dnf module enable eclipse
```

(might need sudo).


It's possible these specific packages (junit5 in particular) were marked to not be shipped in the Eclipse module as they are provided elsewhere (either system rpms, or maybe the javapackages-tools module) but I don't personally have context on that at the moment. I've assigned it to the Eclipse team to investigate further.