Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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`

Created redmine issue http://projects.theforeman.org/issues/25990 from this bug

Upstream bug assigned to lzap

Upstream bug assigned to lzap

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

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25990 has been resolved.

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.

Upstream bug assigned to lzap