-
Bug
-
Resolution: Can't Do
-
Normal
-
None
-
4.12
-
Moderate
-
None
-
False
-
Description of problem:
With the current Agent based installer we need to have a option to specify
some more details while we use DHCP. Current configs aligns to nmstate which
takes the agent config to consideration and likely following will fail,
--------------------
apiVersion: v1alpha1
kind: AgentConfig
metadata:
name: ocp4
rendezvousIP: 10.47.xx.xx
hosts:
- hostname: master-0.ocp4.xyz.com
role: master
interfaces:
- name: eno49
macAddress: b8:83:03:81:0d:70
- name: eno50
macAddress: b8:83:03:81:0d:71
rootDeviceHints:
deviceName: /dev/sda
networkConfig:
interfaces:
- name: bond0
type: bond
state: up
mtu: 9000
mac-address: b8:83:03:81:0d:70
ipv4:
enabled: true
dhcp: true
link-aggregation:
mode: 802.3ad
options:
miimon: "150"
port:
- eno49
- eno50
dns-resolver:
config:
server:
- 10.47.xx.xx
routes:
config:
- destination: 0.0.0.0/0
next-hop-address: 10.47.108.1
next-hop-interface: bond0
table-id: 254
----------------
Here, the requirement is to have the DHCP offering along with privilege to get
the bonding configured which isn't possible with current agent based
installer. If we try something like above it will fail as per the
"error-output-for-the-create-image-command.txt" file attached here.
Version-Release number of selected component (if applicable):
4.12
How reproducible:
- Create an agent config as per above to have bonding created where the IP addresses would be DHCP reservations. - Run the installer
Steps to Reproduce:
1. Create agent config to have DHCP with Bond config 2. Run the command to create ISO 3.
Actual results:
- Results in to errors and from documentation we don't see any options to have this kind of setup.
Expected results:
- Shall allow DHCP bonding with declaration of DHCP reservations with specifying routes with nmstate.
Additional info: