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

Support for single stack ipv6-only environment

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhel-9.6
    • nmstate
    • None
    • None
    • None
    • rhel-net-mgmt
    • None
    • 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

      ( ) Integration test case is available upstream.

      ( ) Code is reviewed and merged upstream.

      ( ) Preliminary testing is done.

      ( ) Upstream documentation is written in the upstream MR.

      ( ) Release notes text is written in the RHEL issue.

      ( ) A demo is recorded

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. None ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done. ( ) Upstream documentation is written in the upstream MR. ( ) Release notes text is written in the RHEL issue. ( ) A demo is recorded
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      What were you trying to do that didn't work?

      Deploy environment with IPV6 only stack using nmstate (nmpolicy feature) 

      What is the impact of this issue to you?

      Our Telco Partner deploy single stack IPV6 only OCP cluster for customers and can not deploy at scale without using nmstate (nmpolicy feature).

      Please provide the package NVR for which the bug is seen:

      How reproducible is this bug?:

      Always

      Steps to reproduce

      1. Create nmstate configuration file for br-ex wih only ipv6 address
      capture:
  gw: routes.running.destination=="0.0.0.0/0"
  base-iface: interfaces.name==capture.gw.routes.running.0.next-hop-interface
  new-iface: capture.base-iface | interfaces.ipv6.forwarding:=null
  base-iface-routes: routes.running.next-hop-interface==capture.base-iface.interfaces.0.name
  bridge-routes: capture.base-iface-routes | routes.running.next-hop-interface:="br-ex"
  new-mtu: capture.bridge-routes | routes.running.mtu:="1280"
desired:
  routes:
    config: "{{ capture.new-mtu.routes.running }}"
  interfaces:
  - name: br-ex
    type: ovs-interface
    state: up
    mac-address: "{{ capture.new-iface.interfaces.0.mac-address }}"
    ipv6: "{{ capture.new-iface.interfaces.0.ipv6 }}"
  - name: br-ex
    type: ovs-bridge
    state: up
    bridge:
      options:
        mcast-snooping-enable: false
      port:
        - name: "{{ capture.new-iface.interfaces.0.name }}"
        - name: br-ex
      1. Apply the manifest using nmstate

      Expected results

      Actual results

              nm-team Network Management Team
              ecisse@redhat.com El Hadji Sidi Ahmed Cisse
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: