Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2152719

Summary: Adding CDS server fails with a misleading error.
Product: Red Hat Update Infrastructure for Cloud Providers Reporter: mithun kalyat <mkalyat>
Component: CDSAssignee: RHUI Bug List <rhui-bugs>
Status: CLOSED DUPLICATE QA Contact: Radek Bíba <rbiba>
Severity: medium Docs Contact:
Priority: low    
Version: 4.1.1CC: gtanzill, pmoravec
Target Milestone: ---Keywords: Triaged
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: 2024-11-22 07:31:20 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 mithun kalyat 2022-12-12 19:45:59 UTC
Adding CDS server fails with a misleading error.

Adding CDS server fails.

             -= Red Hat Update Infrastructure Management Tool =-


-= Content Delivery Server (CDS) Management =-

   l   list all known CDS instances managed by the RHUI
   a   register (add) a new CDS instance
   r   reinstall and reapply configuration to an existing CDS instance
   d   unregister (delete) a CDS instance from the RHUI

   logout
       removes stored authentication credentials and exits

   <   move to the previous screen
   ^, home
       move to the home screen
   /, clear
       clears the screen
   ?, help
       display help
   q, quit, exit
       exit

                                             Connected: rhua.example.com
------------------------------------------------------------------------------
rhui (cds) => a

Prior to registering a CDS, the instance must be provisioned with sshd running.

Hostname of the CDS instance to register:
cds01.example.com

Username with SSH access to cds01.example.com and sudo privileges:
rhua

Absolute path to an SSH private key to log into cds01.example.com as rhua:
/home/rhua/.ssh/id_rsa

Optional absolute path to user supplied SSL key file:



Checking SSH authentication on instance...
rhua.com | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/libexec/platform-python"
    },
    "changed": false,
    "ping": "pong"
}
Done.

The following CDS has been successfully added:

  Hostname:             cds01.example.com
  SSH Username:         rhua
  SSH Private Key:      /home/rhua/.ssh/id_rsa

The CDS will now be configured:

Checking that the RHUA services are reachable from the instance...

Something happened, check the log file for more information: ~/.rhui/rhui.log
 

And from rhui.log:

rhui.common.exceptions.RhuiException: Port 443 on the host rhua.example.com is not accessible from cds01.example.com.

Port is opened and to connect: 

[rhua@cds01 ~]$ telnet rhua.example.com 443
Trying 172.24.131.19...
Connected to rhua.example.com.
Escape character is '^]'.
^]

The actual issue is here with the user used for registering CDS does not have have sudo access to run commands without password.

==========
Username with SSH access to cds01.example.com and sudo privileges:
rhua
==========

Once sudo passwordless configured, able to get further.

This was reported by two of our customers and complaining about the misleading error/message when it failed "rhui.common.exceptions.RhuiException: Port 443 on the host rhua.example.com is not accessible from cds01.example.com".

For better experience, it would be nice to show a useful error message related to configuring sudo instead the port connectivity error.

Comment 1 Radek Bíba 2022-12-13 08:35:24 UTC
This is in fact a duplicate of bug 1644887, which was originally filed against RHUI 3 but is still relevant in version 4. The RHUI docs should be explicit about requiring a passwordless sudo configuration.

Parth, would you please take a look? The instructions should go to Chapter 6. Managing content delivery servers. Please see bug 1644887 comment 6; however, it's the configuration guide that needs an update, not the installation guide.

Comment 3 Radek Bíba 2024-11-22 07:31:20 UTC
Closing since the documentation bug report has been resolved.

*** This bug has been marked as a duplicate of bug 1644887 ***

Comment 4 Red Hat Bugzilla 2025-03-23 04:25:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days