Bug 1333067 - TFTP is not configured by the scenario katello as promised in documentation
Summary: TFTP is not configured by the scenario katello as promised in documentation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: Allison Heslin
QA Contact: Brandi Munilla
URL:
Whiteboard:
Depends On: 1124430
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2016-05-04 15:09 UTC by Peter Vreman
Modified: 2019-09-25 20:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-11 00:20:47 UTC
Target Upstream Version:
Embargoed:
mbacovsk: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1332911 0 high CLOSED Installation and Configuration steps contradicting and confusing 2021-02-22 00:41:40 UTC

Internal Links: 1332911

Description Peter Vreman 2016-05-04 15:09:53 UTC
Description of problem:

After installing the Satellite server with scenario 'katello' the TFTP is not installed as promised in the Documentation

---
3.4.2. Configuring DNS and DHCP on Satellite Server

You can configure DNS and DHCP on Satellite Server. TFTP is automatically configured.
---

[crash] root@li-lc-1578:~# rpm -qa | grep tftp
[crash] root@li-lc-1578:~# ls -l /var/lib/tftpboot
ls: cannot access /var/lib/tftpboot: No such file or directory


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


How reproducible:


Steps to Reproduce:
1. Follow the instructions Top-Down to install a single server 'Satellite Server' only. That means all the steps of 'Capsule Server' shall be skipped, because those are referring to a second server.
2.
3.

Actual results:
User is left in the why the TFTP is not installed. He installed a 'Satellite Server' but the TFTP is not installed.

Expected results:
Guide the user better to install Services
- Correct documentation what is really nstalled by the default settings
--  For a 'Satellite Server' with scenario 'katello'
--  For a 'Capsule Server' with scenario 'capsule'
- When to do installation on both the 'Satellite Server' or 'Capsule Server' ?


Additional info:

Comment 1 Stephen Wadeley 2016-05-04 15:33:39 UTC
Hello Peter


Thank you for raising this bug.


Asking lzap to confirm if something has changed as I was told that in 6.1 TFTP is enabled by default.

Comment 2 Peter Vreman 2016-05-04 15:54:32 UTC
This is a regression over Sat6.1 that has a good introduction:

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Installation_Guide/index.html#sect-Red_Hat_Satellite-Installation_Guide-Configuring_DNS_DHCP_and_TFTP

The sections of Sat6.1 '2.3.3.1. Additional DNS, DHCP and TFTP Options' is missing.


It is also related to the overall issue with Installation Manaul that it is unclear what is 'Satellite Server' and 'Capsule Server'. Does 'Satellite Server' include an internal Capsule or not?
E.g. Do i need to run both 'foreman-installer --scenario=katello' and 'foreman-installer --scenario=capsule' on a single server?

Alternative i recommend is have a better set scenario with default settings:
- satellite-server-without-capsule
- satellite-server-with-capsule
- capsule-server

Comment 3 Lukas Zapletal 2016-05-06 10:19:12 UTC
I don't do the installer stuff, can't tell who changed it. Martin and Brad wrote it upstream, switching over.

My opinion: for TFTP, DHCP and DNS we should stick with upstream, therefore install and configure all of them by default, set for starting only TFTP and DNS (not DHCP).

Comment 5 Allison Heslin 2016-05-06 15:03:54 UTC
This bug has a dependency on BZ1124430. Currently TFTP is not enabled by default, so I have updated the task to enable it. 

I'm still working on addressing the second, overall issue.

Comment 7 Allison Heslin 2016-05-10 17:27:23 UTC
I've added the changes to TFTP and am addressing the second issue in bz1332972. I copied the comment into that bug since that's where the issue will be addressed.

Comment 8 Andrew Dahms 2016-05-11 00:20:47 UTC
This content is now live on the Customer Portal.

Closing.


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