Bug 1995102

Summary:	[RFE] Request to add CLI option to perform network connectivity check for RH Cloud Plugin.
Product:	Red Hat Satellite	Reporter:	Jameer Pathan <jpathan>
Component:	RH Cloud	Assignee:	Shimon Shtein <sshtein>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	ahumbe, aruzicka, dsinglet
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	Unused
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:	2024-06-06 01:02:06 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 Jameer Pathan 2021-08-18 13:05:19 UTC

Description of problem:
In Sat6.9 the old insights client plugin, provides a way to validate network connectivity, which is very helpful for the customers using HTTP Proxy in the network. 

This request is to add CLI option to perform network connectivity check for RH Cloud Plugin too. 

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

Additional info:
- See BZ#1976930#c1 for more info.

Comment 4 Eric Helms 2024-06-06 01:02:06 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 "SAT-" 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.