Bug 1278720 - Improve error message on incorrect Foreman credentials
Summary: Improve error message on incorrect Foreman credentials
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.1.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-06 09:30 UTC by Sachin Ghai
Modified: 2017-01-05 15:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-05 15:57:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12412 0 None None None 2016-04-22 16:50:41 UTC

Description Sachin Ghai 2015-11-06 09:30:54 UTC
Description of problem:

I was trying pxe-less discovery via external capsule and using FDI image "fdi-bootable-3.0.4.iso".

Steps to reproduce:

1. boot the VM/host using unmodified ISO
2. select the Manual network configuration option since dhcp feature was disabled on capsule.
3. on Foreman Credentials screen
a) Specify the URL
b) select connection-type 'Server' instead of 'Proxy'

Ideally user should get an error but user successfully moved to next "Custom Facts" screen. And on clicking 'Confirm' button', first screen "Manual Pxe-less workflow" appears.

Note: In case user enters incorrect URL with incorrect domain or without any port then also user should get an error.


Build ver:
--------
Satellite 6.1.4 compose3

on capsule:
rubygem-smart_proxy_discovery-1.0.3-1.el7sat.noarch

on sat6 server:
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
rubygem-smart_proxy_discovery-1.0.3-1.git.0.3a55100.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.20-1.el7sat.noarch

Image: fdi-bootable-3.0.4.iso

Comment 1 Sachin Ghai 2015-11-06 09:31:18 UTC
Upstream issue filed: http://projects.theforeman.org/issues/12412

Comment 3 Lukas Zapletal 2015-11-11 07:52:03 UTC
Not a blocker, I propose this for 6.2.

Comment 4 Bryan Kearney 2017-01-05 15:57:08 UTC
This is an older bug which has been reported upstream. We are not going to track this bug downstream. When the upstream issue is resolved, the next build will contain the fix. Thank you.


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