Bug 1422620 - [RFE] the satellite-installer command should have a better default for --foreman-proxy-dns-reverse
Summary: [RFE] the satellite-installer command should have a better default for --fore...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Marek Hulan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-15 17:18 UTC by Peter Gervase
Modified: 2019-04-01 20:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18538 0 None None None 2017-02-16 14:57:00 UTC

Description Peter Gervase 2017-02-15 17:18:07 UTC
Description of problem:
If you look at the help for satellite-installer, you can see what the defaults are for the options. Looking at the default for dhcp-option-domain, that gets set based on your environment. However, looking at the dns-reverse, it has a default that doesn't get adjusted based on your system.

# satellite-installer --help | grep -ie dhcp-option -ie dns-reverse
    --foreman-proxy-dhcp-option-domain  DHCP use the dhcpd config option domain-name (default: ["usersys.redhat.com"])
    --foreman-proxy-dns-reverse   DNS reverse zone name (default: "100.168.192.in-addr.arpa")
# ip a | grep -e 192 -ie 10
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    inet 10.10.181.147/21 brd 10.10.183.255 scope global dynamic eth0
[root@ex403 ~]# 

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

How reproducible:
100%

Steps to Reproduce:
1. run the satellite-installer --help command
2. look for dns-reverse
3.

Actual results:
It always has a default of 100.168.192.in-addr.arpa no matter what your networking is.

Expected results:
The default should get based on what your default route is. For systems with more than one nic, that might not be what gets used, but at least it has a chance of being a useful default.

Additional info:

Comment 1 Stephen Benjamin 2017-02-16 14:56:59 UTC
Created redmine issue http://projects.theforeman.org/issues/18538 from this bug

Comment 2 Satellite Program 2017-02-20 09:17:22 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18538 has been resolved.

Comment 5 Satellite Program 2018-02-21 16:51:07 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.