Bug 2169982

Summary: [RFE] DHCP based installation shall allow creation network bonding and allowing custom/specifying routes with nmstate.
Product: Red Hat Enterprise Linux 9 Reporter: Parikshit Khedekar <pkhedeka>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: high Docs Contact:
Priority: unspecified    
Version: 9.2CC: ferferna, jcall, jiji, jishi, network-qe, sfaye, till
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: nmstate-2.2.7-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2203277 (view as bug list) Environment:
Last Closed: 2023-05-09 07:32:13 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:
Bug Depends On:    
Bug Blocks: 2203277    
Attachments:
Description Flags
Errors we get while creating image with above config. none

Description Parikshit Khedekar 2023-02-15 10:02:42 UTC
Created attachment 1944268 [details]
Errors we get while creating image with above config.

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:

Comment 2 Gris Ge 2023-02-16 04:05:39 UTC
Patch posted to upstream: https://github.com/nmstate/nmstate/pull/2240

Example YAML file:

```yml
---
interfaces:
  - name: eth1
    type: ethernet
    state: up
    ipv4:
      dhcp: true
      enabled: true
    ipv6:
      dhcp: true
      autoconf: true
      enabled: true
routes:
  config:
  - destination: 198.51.100.0/24
    metric: 150
    next-hop-address: 192.0.2.1
    next-hop-interface: eth1
    table-id: 254
  - destination: 2001:db8:2::/64
    metric: 151
    next-hop-address: 2001:db8:1::2
    next-hop-interface: eth1
```

Comment 6 Mingyu Shi 2023-02-25 15:31:42 UTC
Verified with nmstate-2.2.7-1.el9

Comment 8 errata-xmlrpc 2023-05-09 07:32:13 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 (nmstate bug fix and enhancement update), 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/RHBA-2023:2190