Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1109866

Summary: Install the capsule with two network interfaces
Product: Red Hat Satellite Reporter: Martin Korbel <mkorbel>
Component: Foreman ProxyAssignee: Ivan Necas <inecas>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.3CC: bbuckingham, bkearney, cwelton, greartes, jhutar, mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Release Note
Doc Text:
The current install is only supported on a single NIC.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-16 18:43:38 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
katello-installetr.log
none
dhcpd.conf
none
db.100.168.192.in-addr.arpa
none
db.test.example.com none

Description Martin Korbel 2014-06-16 13:59:18 UTC
Created attachment 909138 [details]
katello-installetr.log

Description of problem:
The satellite/smartproxy makes bad configurations for DNS and DHCP, when we have two interface (eth0 - public, eth1 - private). We want to configure the services (DNS and DHCP), which are provided into the private (eth0) network.
We have got this situation:
- Server with two interfaces
  * eth0 - 10.34.37.148 (this is public network in the domain usersys.redhat.com) 
  * eth1 - 192.168.100.1 (this is private network in the domain test.example.com)
- Server can be or may not be router (NAT). In my case it is the router.
 > sed -i 's/net.ipv4.ip_forward = 0/net.ipv4.ip_forward = 1/' /etc/sysctl.conf
 > sysctl -p
 > echo 1 > /proc/sys/net/ipv4/ip_forward
 > iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.0/16 -j MASQUERADE
 > service iptables save
- We have got a satellite 6 on this machine or on some other machine (in my case satellite is on the same  machine). 


Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140611

How reproducible:
100%

Steps to Reproduce:
1. We can run this command.
> katello-installer --capsule-dns true --capsule-dns-forwarders "10.34.32.1" --capsule-dns-interface eth1 --capsule-dns-zone test.example.com --capsule-dhcp true --capsule-dhcp-gateway 192.168.100.1 --capsule-dhcp-interface eth1 --capsule-dhcp-nameservers 192.168.100.1 --capsule-dhcp-range "192.168.100.10 192.168.100.100" --capsule-tftp true --capsule-tftp-servername 192.168.100.1

Actual results:
The configuration of capsule fails
Could not start Service[named]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait named start' returned 2: 
 /Stage[main]/Dns::Service/Service[named]/ensure: change from stopped to running failed: Could not start Service[named]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait named start' returned 2: 
 Could not start Service[dhcpd]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait dhcpd start' returned 1: 
 /Stage[main]/Dhcp/Service[dhcpd]/ensure: change from stopped to running failed: Could not start Service[dhcpd]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait dhcpd start' returned 1: 


Problem is that, we have got a incomplete configuration of DHCP and DNS.
DHCP problems:
/etc/dhcp/dhcpd.conf (the file is in the attachment)
- next-server <missing-ip>;
- subnet <missing-ip> netmask <missing-mask> {
- option subnet-mask <missing-mask> ;

DNS problems:
I'm not really sure, but I think, in the DNS files, there should be the domain "test.example.com"
/var/named/dynamic/db.test.example.com (the file is in the attachment)
- @ IN NS xxx.usersys.redhat.com.
- xxx.usersys.redhat.com. IN A  <missing-ip>

/var/named/dynamic/db.100.168.192.in-addr.arpa (the file is in the attachment)
- @ IN NS xxx.usersys.redhat.com.
- completely missing the reverse record for 192.168.100.1


When we fix these problems manually and run again katello-install (reproducer step 1), all goes well.

Expected results:
All would go well automatically


Additional info:
katello-installer.log  (the file is in the attachment)

Comment 1 Martin Korbel 2014-06-16 13:59:55 UTC
Created attachment 909139 [details]
dhcpd.conf

Comment 2 Martin Korbel 2014-06-16 14:00:30 UTC
Created attachment 909140 [details]
db.100.168.192.in-addr.arpa

Comment 3 Martin Korbel 2014-06-16 14:00:51 UTC
Created attachment 909141 [details]
db.test.example.com

Comment 4 RHEL Program Management 2014-06-16 14:19:32 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 7 Martin Korbel 2014-06-19 08:18:21 UTC
Update of reproducer of this bug:
-----------------------------------------------------------------------------
I have tested this bug with Satellite-6.0.3-RHEL-6-20140618.0. 
Unfortunately, I detected  my small mistake in reproducer, but this my mistake is very important and it completely changing the view on this bug. :o(

At the first time running of the capsule installer, there was eth1 down. After first fail,  I switched on eth1 and I tried to install capsule again. But the capsule installator didn't able to fix this problem (configuration of DNS and DHCP).


One thing is still bad in the configuration of DHCP. 

> option domain-name "usersys.redhat.com";

It should be 

> option domain-name "test.example.com";

Comment 8 Corey Welton 2014-07-23 18:48:18 UTC
Will try to QE this if resources allow.

Comment 9 Corey Welton 2017-01-16 18:43:38 UTC
I do not envision this bug being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.