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

[4.15] conformance tests failing due to openshift-multus config

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.15.0
    • 4.13, 4.14, 4.15
    • Networking / multus
    • None
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None
    • NA
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-19830. The following is the description of the original issue:
      —
      Description of problem:

      There are several testcases in conformance testsuite that are failing due to openshift-multus configuration.

      We are running conformance testsuite as part of our Openshift on Openstack CI. We use that just to confirm correct functionality of the cluster. The command we are using to run the test suite is:

      openshift-tests run  --provider '{\"type\":\"openstack\"}' openshift/conformance/parallel

      The name of the tests that failed are:
      1. sig-arch] Managed cluster should ensure platform components have system-* priority class associated [Suite:openshift/conformance/parallel]

      Reason is:

      6 pods found with invalid priority class (should be openshift-user-critical or begin with system-):
openshift-multus/whereabouts-reconciler-6q6h7 (currently "")
openshift-multus/whereabouts-reconciler-87dwn (currently "")
openshift-multus/whereabouts-reconciler-fvhwv (currently "")
openshift-multus/whereabouts-reconciler-h68h5 (currently "")
openshift-multus/whereabouts-reconciler-nlz59 (currently "")
openshift-multus/whereabouts-reconciler-xsch6 (currently "")

      2. [sig-arch] Managed cluster should only include cluster daemonsets that have maxUnavailable or maxSurge update of 10 percent or maxUnavailable of 33 percent [Suite:openshift/conformance/parallel]
      Reason is:

      fail [github.com/openshift/origin/test/extended/operators/daemon_set.go:105]: Sep 23 16:12:15.283: Daemonsets found that do not meet platform requirements for update strategy:
  expected daemonset openshift-multus/whereabouts-reconciler to have maxUnavailable 10% or 33% (see comment) instead of 1, or maxSurge 10% instead of 0
Ginkgo exit error 1: exit with code 1

      3.[sig-arch] Managed cluster should set requests but not limits [Suite:openshift/conformance/parallel]

      Reason is:

      fail [github.com/openshift/origin/test/extended/operators/resources.go:196]: Sep 23 16:12:17.489: Pods in platform namespaces are not following resource request/limit rules or do not have an exception granted:
  apps/v1/DaemonSet/openshift-multus/whereabouts-reconciler/container/whereabouts defines a limit on cpu of 50m which is not allowed (rule: "apps/v1/DaemonSet/openshift-multus/whereabouts-reconciler/container/whereabouts/limit[cpu]")
  apps/v1/DaemonSet/openshift-multus/whereabouts-reconciler/container/whereabouts defines a limit on memory of 100Mi which is not allowed (rule: "apps/v1/DaemonSet/openshift-multus/whereabouts-reconciler/container/whereabouts/limit[memory]")
Ginkgo exit error 1: exit with code 1

      4. [sig-node][apigroup:config.openshift.io] CPU Partitioning cluster platform workloads should be annotated correctly for DaemonSets [Suite:openshift/conformance/parallel]

      Reason is:

      fail [github.com/openshift/origin/test/extended/cpu_partitioning/pods.go:159]: Expected
    <[]error | len:1, cap:1>: [
        <*errors.errorString | 0xc0010fa380>{
            s: "daemonset (whereabouts-reconciler) in openshift namespace (openshift-multus) must have pod templates annotated with map[target.workload.openshift.io/management:{\"effect\": \"PreferredDuringScheduling\"}]",
        },
    ]
to be empty

      How reproducible: Always
      Steps to Reproduce: Run conformance testsuite:
      https://github.com/openshift/origin/blob/master/test/extended/README.md

      Actual results: Testcases failing
      Expected results: Testcases passing

            [OCPBUGS-25652] [4.15] conformance tests failing due to openshift-multus config

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.15.0 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2023:7198

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.15.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:7198

            Kathryn Alexander added a comment -

            The docs team is preparing the bug text for the 4.15 release notes. Based on the fix and affects version, this bug needs to be included in the release notes. Please update your issue by 2/12.

            Set the Release Note Type to Bug Fix and provide the Release Note Text in the following format:

            Cause: What actions or circumstances cause this bug to present.
            Consequence: What happens when the bug presents.
            Fix: What was done to fix the bug.
            Result: Bug doesn’t present anymore.

            If your bug was actually found and fixed in 4.15 or should be internal only, set the Release Note Type to Release Note Not Required.

            Kathryn Alexander added a comment - The docs team is preparing the bug text for the 4.15 release notes. Based on the fix and affects version, this bug needs to be included in the release notes. Please update your issue by 2/12. Set the Release Note Type to Bug Fix and provide the Release Note Text in the following format: Cause : What actions or circumstances cause this bug to present. Consequence : What happens when the bug presents. Fix : What was done to fix the bug. Result : Bug doesn’t present anymore. If your bug was actually found and fixed in 4.15 or should be internal only, set the Release Note Type to Release Note Not Required .

            Weibin Liang added a comment -

            Verified in 4.15.0-0.nightly-2024-01-30-150231

            $ oc describe pod whereabouts-reconciler-5c8c7 -n openshift-multus
Name:                 whereabouts-reconciler-5c8c7
Namespace:            openshift-multus
Priority:             2000001000
Priority Class Name:  system-node-critical
Service Account:      multus-ancillary-tools
Node:                 weliang-30n-bbc6k-worker-b-lw9d8/10.0.128.3
Start Time:           Tue, 30 Jan 2024 16:14:13 -0500
Labels:               app=whereabouts-reconciler
                      controller-revision-hash=7c76754d9f
                      name=whereabouts-reconciler
                      pod-template-generation=1
Annotations:          <none>
Status:               Running
IP:                   10.0.128.3
IPs:
  IP:           10.0.128.3
Controlled By:  DaemonSet/whereabouts-reconciler
Containers:
  whereabouts:
    Container ID:  cri-o://98717e610ee7676757e97e9cdb10dab5e86fc1ca9c597bba99fbabdb3ab0e329
    Image:         quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:6768fecfb5c1f41ab237a38ab0b43bd1422446e4760127d1c89002e039bf82cc
    Image ID:      c9c474f9755049c7d318a58953c55c457235158e018c0ea2e3b7469d8dd0fa33
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
    Args:
      -c
      /usr/src/whereabouts/bin/entrypoint.sh -log-level debug
      
    State:          Running
      Started:      Tue, 30 Jan 2024 16:14:14 -0500
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:     50m
      memory:  50Mi

            Weibin Liang added a comment - Verified in 4.15.0-0.nightly-2024-01-30-150231 $ oc describe pod whereabouts-reconciler-5c8c7 -n openshift-multus Name:                 whereabouts-reconciler-5c8c7 Namespace:            openshift-multus Priority:             2000001000 Priority Class Name:  system-node-critical Service Account:      multus-ancillary-tools Node:                 weliang-30n-bbc6k-worker-b-lw9d8/10.0.128.3 Start Time:           Tue, 30 Jan 2024 16:14:13 -0500 Labels:               app=whereabouts-reconciler                       controller-revision-hash=7c76754d9f                       name=whereabouts-reconciler                       pod-template-generation=1 Annotations:          <none> Status:               Running IP:                   10.0.128.3 IPs:   IP:           10.0.128.3 Controlled By:  DaemonSet/whereabouts-reconciler Containers:   whereabouts:     Container ID:  cri-o: //98717e610ee7676757e97e9cdb10dab5e86fc1ca9c597bba99fbabdb3ab0e329     Image:         quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:6768fecfb5c1f41ab237a38ab0b43bd1422446e4760127d1c89002e039bf82cc     Image ID:      c9c474f9755049c7d318a58953c55c457235158e018c0ea2e3b7469d8dd0fa33     Port:          <none>     Host Port:     <none>     Command:       /bin/sh     Args:       -c       /usr/src/whereabouts/bin/entrypoint.sh -log-level debug            State:          Running       Started:      Tue, 30 Jan 2024 16:14:14 -0500     Ready:          True     Restart Count:  0     Requests:       cpu:     50m       memory:  50Mi

            OpenShift Jira Bot added a comment -

            Hi zshi@redhat.com,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi zshi@redhat.com , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment -

            Looks like this bug is far enough along in the workflow that a code fix is ready. Customers and support need to know the backport plan. Please complete the "Target Backport Versions" field to indicate which version(s) will receive the fix.

            OpenShift Jira Bot added a comment - Looks like this bug is far enough along in the workflow that a code fix is ready. Customers and support need to know the backport plan. Please complete the " Target Backport Versions " field to indicate which version(s) will receive the fix.

              zshi@redhat.com Zenghui Shi
              openshift-crt-jira-prow OpenShift Prow Bot
              Weibin Liang Weibin Liang
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: