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

Use sym links to mark yml files at nmstatectl service

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • rhel-9.4
    • rhel-9.2.0.z
    • nmstate
    • nmstate-2.2.22-1.el9
    • None
    • Important
    • ZStream
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • 22
    • 1
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT - RHEL 8.10/9.4 DTM 18-20
    • Approved Blocker
    • Hide

      Given a system administrator using MCO to generate a YAML file at `/etc/nmstate` in an OpenShift environment to configure an IPv6 dual stack,
      When they restart the nmstatectl service,
      Then the original `.yml` file should remain in its location at `/etc/nmstate` and a symbolic link `.applied` pointing to the original `.yml` file should be created in the same directory

      Definition of done:

      • The implementation meets the acceptance criteria
      • Unit test and integration test are written and pass
      • The code is part of a build attached to a downstream errata
      Show
      Given a system administrator using MCO to generate a YAML file at `/etc/nmstate` in an OpenShift environment to configure an IPv6 dual stack, When they restart the nmstatectl service, Then the original `.yml` file should remain in its location at `/etc/nmstate` and a symbolic link `.applied` pointing to the original `.yml` file should be created in the same directory Definition of done: The implementation meets the acceptance criteria Unit test and integration test are written and pass The code is part of a build attached to a downstream errata
    • Pass
    • None
    • None

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

      At  openshift hypershift kubevirt provider a yml config is generated at /etc/nmstate using machine-config-operator to configure ipv6 dual stack. This file is later on moved by nmstate to .applied and that breaks MCO InPlace upgrade since that's a configuration drift https://docs.openshift.com/container-platform/4.14/post_installation_configuration/machine-configuration-tasks.html#machine-config-drift-detection_post-install-machine-configuration-tasks.

      Please provide the package NVR for which bug is seen:

      How reproducible: Always

      Steps to reproduce

      1. Create config at /etc/nmstate
      2. Run systemctl restart nmstate

      Expected results

      The .yml file should still be there and a .applied symlink to it should be created to mark it.

      Actual results

      The .yml file is moved to .applied

              fge@redhat.com Gris Ge
              ellorent Felix Enrique Llorente Pastora
              Felix Enrique Llorente Pastora Felix Enrique Llorente Pastora
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: