Bug 2178891

Summary:	yum module install container-tools
Product:	Red Hat Enterprise Linux 8	Reporter:	hm_kwon
Component:	container-tools-1.0-module	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED MIGRATED	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.5	CC:	jligon, jnovy, lsm5
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-11 19:40:44 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 hm_kwon 2023-03-16 04:24:55 UTC

I use the version Redhat8.5 Linux 4.18.0-348.el8.x86_64 and It's offline.
So I made a local repository. (local-repo)

[root@localhost offline]# yum module install container-tools
Updating Subscription Management repositories.
Unable to read consumer identity
Last metadata expiration check: 1:52:38 ago on Thu 16 Mar 2023 11:25:56 AM KST.
Installing module 'container-tools:rhel8' from Fail-Safe repository @modulefailsafe is not allowed
No default profiles for module container-tools:rhel8. Available profiles: common
Error: Installing module from Fail-Safe repository is not allowed

How can I solve this problem?

Regards,
Kwon

Comment 1 RHEL Program Management 2023-09-11 19:35:39 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 2 RHEL Program Management 2023-09-11 19:40:44 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.