Bug 2078984

Summary: [RHC] It is possible to connect to RHC even with invalid server value
Product: Red Hat Enterprise Linux 7 Reporter: mabezerr
Component: rhcAssignee: CSI Client Tools Bugs <csi-client-tools-bugs>
Status: CLOSED MIGRATED QA Contact: Red Hat subscription-manager QE Team <rhsm-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.9CC: ahitacat, gchamoul, link
Target Milestone: rcKeywords: MigratedToJIRA, Rebase, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Linux   
Whiteboard: SCRUB_20220502
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-07 13:09:38 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 mabezerr 2022-04-26 16:06:57 UTC
### Description of problem:

When I try to connect to RHC using an invalid server value, connect is established and error code is 0. 

```
# connecting with invalid --server
✗ rhc connect --username <<value>> --password <<value>> --server "http://non-existent.server"
Connecting mabezerr-jenkins-rhel79 to Red Hat.
This might take a few seconds.

| Connecting to Red Hat Subscription Management..WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
/ Connecting to Red Hat Subscription Management..WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
[...]
| Connecting to Red Hat Subscription Management..WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
● Connected to Red Hat Subscription Management
● Activated the Red Hat connector daemon

Manage your Red Hat connector systems: https://red.ht/connector
```

# now, checking the error code - I was expecting for "1"
(iqe_venv) ➜  iqe-rhc-client-plugin git:(ESSNTL-1535) ✗ echo $?
0


### Version-Release number of selected component (if applicable):
✗ cat /etc/redhat-release    
Red Hat Enterprise Linux Server release 7.9 (Maipo)

### How reproducible:
call "rhc connect" command and insert any invalid value for --server field.


### Steps to Reproduce:
1. Use rhc command with all necessary fields (username, password, server)
2. Check output
3. Run command "echo $?" to see the errorcode on output.

### Actual results:
It is possible to establish connection on RHC with invalid --server value


### Expected results:

I did the same for RHEL9 just to check, and here is the expected behavior:

# using same credentials as used on RHEL7
✗ rhc connect --username <<value>> --password <<value>> --server "http://non-existent.server"
Connecting mabezerr-insights-rhel9 to Red Hat.
This might take a few seconds.

error: [Errno -2] Name or service not known

# Now checking error code, I can see the expected value "1"
(venv) ➜  iqe_insights_client git:(master) ✗ echo $?
1


### Additional info:

# RHC version for RHEL7
✗ rhc --version
rhc version 0.2.0

Comment 3 Link Dupont 2022-06-21 18:17:29 UTC
This is a bug that was fixed in rhc-0.2.1. We'd need to get this bug (for RHEL 7.9) approved for Rebase to backport rhc-0.2.1 to RHEL 7.9.

Comment 5 RHEL Program Management 2023-09-07 13:06:28 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 6 RHEL Program Management 2023-09-07 13:09:38 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.