Bug 2182678

Summary:	[RFE] ansible-test sanity offline operations support
Product:	Red Hat Enterprise Linux 9	Reporter:	Ahmed Eladawy <aeladawy>
Component:	ansible-core	Assignee:	Dimitri Savineau <dsavinea>
Status:	CLOSED MIGRATED	QA Contact:	Matt Clay <mclay>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	jwboyer
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA
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-12 10:03:19 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ahmed Eladawy 2023-03-29 10:27:20 UTC

Description of problem:

As per bugzilla 2172520 , ansible-test sanity does not support offline operation.

Version-Release number of selected component (if applicable):

ansible-core-2.14.2-1.el9ap.x86_64
ansible-test-2.14.2-1.el9ap.x86_64


As per customer user , this bugzilla has been created.

Comment 2 RHEL Program Management 2023-09-12 09:58:19 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-12 10:03:19 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.