Bug 1386295 - [RFE] Have option to select default gateway if provisioning hosts with multiple nics and networks. [NEEDINFO]
Summary: [RFE] Have option to select default gateway if provisioning hosts with multip...
Keywords:
Status: CLOSED DUPLICATE of bug 1376924
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Networking
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-18 15:09 UTC by Stefan Nemeth
Modified: 2021-06-10 11:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-04 06:54:24 UTC
Target Upstream Version:
mhulan: needinfo? (snemeth)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1376924 0 medium CLOSED satellite 6 provisioning a client with 2 nics will have to default gateways 2021-06-10 11:32:28 UTC

Internal Links: 1376924

Description Stefan Nemeth 2016-10-18 15:09:48 UTC
Description of problem:

When provisioning a host with multiple nics and multiple networks, if the networks have defined default gateway, there is no option to choose between them and choose which is going to be default. 

Option to write settings into
/etc/sysconfig/network file

Steps to Reproduce:
1.create a host with multiple nics
2.create networks with defined gateways
3.try to provision

Comment 2 Marek Hulan 2016-10-25 09:22:59 UTC
Could you please describe how do you configure your interfaces? Do they use DHCP as boot mode?

Comment 4 Marek Hulan 2017-04-04 06:54:24 UTC
I didn't get a response but I think it has been solved by BZ 1376924. Only the primary interface is now configured with DEFROUTE=yes, the rest is set to no. If this does not solve the problem for you, please let us know.

*** This bug has been marked as a duplicate of bug 1376924 ***


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