Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-84274

[NMT workflow test] nm-initrd-generator: bonding arp_ip_target option not parsed correctly

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • No
    • Important
    • rhel-net-mgmt
    • ssg_networking
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      None


      ( ) Code changes are included in a downstream build attached to an errata.


      ( ) All required testing (manual and/or automated) passes successfully.


      ( ) Related documentation updates (if applicable) have been completed.

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. None ( ) Code changes are included in a downstream build attached to an errata. ( ) All required testing (manual and/or automated) passes successfully. ( ) Related documentation updates (if applicable) have been completed.
    • Pass
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      According to the dracut manpage, multiple IP addresses in the arp_ip_target bonding option should be separated by semi-colon. However nm-initrd-generator parses the option using _nm_setting_bond_validate_option and in turn nm_utils_bond_option_ip_split, which expects comma as a separator. Comma can't be used in the dracut option because commas are used to separate different bonding options.

              rhn-engineering-vbenes Vladimir Benes
              rh-ee-sfaye Stanislas Faye
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: