Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-41640

The data structure for services's label is flipped, with values acting as key and key as values

XMLWordPrintable

    • Important
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • Done

      This is a clone of issue OCPBUGS-41618. The following is the description of the original issue:

      Description of problem:

          The label data for networking services is inverted, it should be stored as "key=value", but it's currently stored as "value=key"

      Version-Release number of selected component (if applicable):

          4.17.0-0.nightly-2024-09-09-120947
          4.18.0-0.nightly-2024-09-09-212926

      How reproducible:

          Always

      Steps to Reproduce:

          1. Navigate to Networking - Services page. and create a sample Service with lable
             eg: 
      apiVersion: v1
      kind: Service
      metadata:
        name: exampleasd
        namespace: default
        labels:
          testkey1: testvalue1
          testkey2: testvaule2
      spec:
        selector:
          app: MyApp
        ports:
          - protocol: TCP
            port: 80
            targetPort: 9376    
      
          2. Check the Labels on Service details page
          3. Check the Labels on Labels column on Networking -> Services page
          

      Actual results:

          the data is shown as 'testvalue1=testkey1' and 'testvalue2=testkey2'

      Expected results:

          it should be shown as 'testkey1=testvalue1' and 'testkey2=testvalue2'

      Additional info:

          

            upalatuc@redhat.com Ugo Palatucci
            openshift-crt-jira-prow OpenShift Prow Bot
            Xiyun Zhao Xiyun Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: