Bug 1371226 - Not appending the satellite capsule port number in the 'server url' causes the wizard to loop to the begining
Summary: Not appending the satellite capsule port number in the 'server url' causes th...
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Image
Version: 6.2.0
Hardware: x86_64
OS: Linux
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Marek Hulan
URL: http://projects.theforeman.org/issues...
Depends On:
TreeView+ depends on / blocked
Reported: 2016-08-29 16:11 UTC by Reartes Guillermo
Modified: 2019-09-26 15:40 UTC (History)
7 users (show)

Fixed In Version: foreman-discovery-image-3.4.1-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:

Attachments (Terms of Use)
screenshot when omiting the discovery port number in the server url (105.72 KB, image/png)
2016-08-29 16:11 UTC, Reartes Guillermo
no flags Details

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16450 0 None None None 2016-09-06 15:06:46 UTC
Red Hat Bugzilla 1371231 0 unspecified CLOSED Re-discovering an existing host fails 2021-02-22 00:41:40 UTC

Internal Links: 1371231

Description Reartes Guillermo 2016-08-29 16:11:59 UTC
Created attachment 1195424 [details]
screenshot when omiting the discovery port number in the server url

Description of problem:

If one omits the discovery port (normally 9090) in the 'Server URL' prompt, the wizard TUI loops back to the first dialog. It is kinda confusing. 
An actual error is issued, but on another virtual terminal.

Version-Release number of selected component (if applicable):
 * Sat 6.1.2
 * foreman-discovery-image-3.1.1-16.el7sat.noarch

How reproducible:

Steps to Reproduce:
1. boot with the iso foreman-discovery-image-3.1.1-16.el7sat
2. select nic, select static, setup the network
3. enter the server url (without appending the port number to the url)
4. select proxy
5. the TUI begins anew.

Actual results:

If one enters for the 'Server URL' : "https://sixthsat1.example.com" (instead of the correct: https://sixthsat1.example.com:9090)
It does neither succeeds nor fails, at least for the wizard TUI.
On another virtual terminal, an actual error can be seen.
On the current VT, the wizard TUI starts again, but no error message was shown.

Expected results:

The TUI wizard sould improve/add validation for the 'Server URL' field, and check for the PORT number.

Is the discovery service port mandatort? If so, it must be checked before trying to connect to the Satellite Capsule.


Comment 2 Lukas Zapletal 2016-09-06 14:10:57 UTC
Thanks, valid bug, fixed.


Comment 3 Bryan Kearney 2016-09-06 16:19:17 UTC
Upstream bug component is Discovery Plugin

Comment 4 Bryan Kearney 2016-09-07 18:19:45 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16450 has been resolved.

Comment 5 Lukas Zapletal 2017-02-23 08:31:28 UTC
Resolved upstream, next Sat version.

Comment 7 Lukas Zapletal 2017-06-28 10:30:45 UTC
6.3 (3.4.0)

Comment 10 Lukas Zapletal 2018-01-01 11:11:58 UTC
This bug is supposed to be fixed in 3.4.1 FDI in Satellite 6.3 beta.

Comment 11 Satellite Program 2018-02-21 16:54:37 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336

Note You need to log in before you can comment on or make changes to this bug.