Bug 1535437

Summary: Capsule details shows 'TFTP server: false' in services tab, when tftp_servername is not configured
Product: Red Hat Satellite Reporter: Ivan Necas <inecas>
Component: Foreman ProxyAssignee: Lukas Zapletal <lzap>
Status: CLOSED WONTFIX QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.2.0CC: bbuckingham, chrobert, egolov, ehelms, rlavi, vsedmik, vvasilev
Target Milestone: Unspecified   
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: 2023-09-07 14:17:50 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:
Attachments:
Description Flags
Screenshot of the TFTP server: false info none

Description Ivan Necas 2018-01-17 11:57:29 UTC
Created attachment 1382370 [details]
Screenshot of the TFTP server: false info

Description of problem:
When tftp_servername is not set in the configuration, the services tab on capsule details shows 'TFTP server' false: this causes confusion, as it looks like that the tftp is not configured properly, which is not the case.



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


How reproducible:
100%

Steps to Reproduce:
1. installer satellite with tftp enabled
2. got to internal capsule details, service tab
3. see TFTP server: false

Actual results:
`TFTP server false`

Expected results:
Since we fallback to the proxy url as the next server, we should probably
show this info in the `TFTP server name` as well`

Comment 2 Ondřej Pražák 2019-02-05 14:16:01 UTC
Created redmine issue http://projects.theforeman.org/issues/25990 from this bug

Comment 3 Bryan Kearney 2019-02-06 11:06:21 UTC
Upstream bug assigned to lzap

Comment 4 Bryan Kearney 2019-02-06 11:06:22 UTC
Upstream bug assigned to lzap

Comment 5 Lukas Zapletal 2019-08-06 15:02:17 UTC
Can you remove the 6.6 flag? It turns out this is more what that we expected, it's not fatal error and Satellite 6.6 can be released without this. TY

Comment 9 Bryan Kearney 2019-12-11 11:05:51 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25990 has been resolved.

Comment 11 Lukas Zapletal 2020-06-11 12:22:46 UTC
The original UI issue bug was not actually fixed by the patch, we have decided to completely rework how TFTP servername is handled in such way that the thread was lost during the process :)

I am putting this back to backlog with low priority tho.

Comment 16 Bryan Kearney 2023-09-06 04:00:37 UTC
Upstream bug assigned to lzap