Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
DescriptionParikshit 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:
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
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: