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

Egress service does not handle invalid nodeSelectors correctly

    XMLWordPrintable

Details

    • No
    • CNF Network Sprint 235, CNF Network Sprint 236
    • 2
    • False
    • Hide

      None

      Show
      None

    Description

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

      Description of problem:

      The egress service nodeSelector parsing does
      not take into account wrong values that cause
      errors (such as "name part must consist of alphanumeric characters"),
      and the controller does not handle them gracefully given a bad input.
      when a bad input is given it should log an error and ignore the service

       

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

       

      How reproducible:

      create an egress service with a bad nodeSelector:
      "{"nodeSelector":{"matchLabels":{"a:b": "c&"}}}"
      
      ovnkube-master controller does not handle it gracefully

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

      Attachments

        Issue Links

          Activity

            People

              obraunsh@redhat.com Ori Braunshtein
              openshift-crt-jira-prow OpenShift Prow Bot
              Anurag Saxena Anurag Saxena
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: