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

Switch to DynamicUser=yes

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • openvswitch
    • None
    • rhel-sst-network-fastdatapath
    • ssg_networking
    • 8
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Given a system running openvswitch with image-based updates (like bootc or ostree), 

      When the system is upgraded or switched to a new image, 

      Then, openvswitch should work correctly using DynamicUser=yes and there should be no failures caused by user/group ID mismatches.

      Show
      Given a system running openvswitch with image-based updates (like bootc or ostree),  When the system is upgraded or switched to a new image,  Then, openvswitch should work correctly using DynamicUser=yes and there should be no failures caused by user/group ID mismatches.
    • None
    • None
    • None

      See https://github.com/containers/bootc/issues/673

      Basically as far as I can tell, openvswitch is a near picture-perfect use case for DynamicUser=yes.

      Avoiding the floating uid/gid with "statically owned" files in /etc would work better with image-based update systems (bootc is just one example).

              ovsdpdk-triage ovsdpdk triage
              walters@redhat.com Colin Walters
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: