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

[4.15 clone] NTO render fails on ContainerRuntimeConfig manifest

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.15
    • Node Tuning Operator
    • None
    • -
    • Important
    • No
    • CNF Compute Sprint 252
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, If a user created a `ContainerRuntimeConfig` resource as an extra manifest for a single-node {product-title} cluster (SNO) installation, the boostrap process failed with the error: `more than one ContainerRuntimeConfig found that matches MCP labels`. With this release, the incorrect processing of `ContainerRuntimeConfig` resources is fixed, which resolves the issue. (link:https://issues.redhat.com/browse/OCPBUGS-30152[*OCPBUGS-30152*])
      ______________
      *Cause*: User creates a ContainerRuntimeConfig resource as an extra-manifest for SNO installation.
      *Consequence*: Bootstrap fails with error "more than one ContainerRuntimeConfig found that matches MCP labels" .
      *Fix*: Incorrect processing of ContainereRuntimeConfig resource was fixed in performance profile renderer code.
      *Result*: Bug doesn’t present anymore.
      Show
      * Previously, If a user created a `ContainerRuntimeConfig` resource as an extra manifest for a single-node {product-title} cluster (SNO) installation, the boostrap process failed with the error: `more than one ContainerRuntimeConfig found that matches MCP labels`. With this release, the incorrect processing of `ContainerRuntimeConfig` resources is fixed, which resolves the issue. (link: https://issues.redhat.com/browse/OCPBUGS-30152 [* OCPBUGS-30152 *]) ______________ *Cause*: User creates a ContainerRuntimeConfig resource as an extra-manifest for SNO installation. *Consequence*: Bootstrap fails with error "more than one ContainerRuntimeConfig found that matches MCP labels" . *Fix*: Incorrect processing of ContainereRuntimeConfig resource was fixed in performance profile renderer code. *Result*: Bug doesn’t present anymore.
    • Bug Fix
    • Done

      Description of problem:

      Tried to apply ContainerRuntimeConfig on Day 0.
      Manifest:

      apiVersion: machineconfiguration.openshift.io/v1
kind: ContainerRuntimeConfig
metadata:   
  name: enable-crun-master
spec:   
  containerRuntimeConfig:     
    defaultRuntime: crun
  machineConfigPoolSelector:     
    matchLabels: 
       pools.operator.machineconfiguration.openshift.io/master: ""

      Result:

      Feb 18 16:21:54 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[6238]: Rendering Node Tuning core manifests...
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.452084       1 render.go:83] Rendering files into: /assets/node-tuning-bootstrap (ownerRefMode=label-name)
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.501344       1 render.go:143] skipping "/assets/manifests/99_feature-gate.yaml" [1] manifest because of unhandled *v1.FeatureGate
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.505615       1 render.go:143] skipping "/assets/manifests/cluster-dns-02-config.yml" [1] manifest because of unhandled *v1.DNS
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.515601       1 render.go:143] skipping "/assets/manifests/cluster-ingress-02-config.yml" [1] manifest because of unhandled *v1.Ingress
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.515852       1 render.go:143] skipping "/assets/manifests/cluster-network-02-config.yml" [1] manifest because of unhandled *v1.Network
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.516011       1 render.go:143] skipping "/assets/manifests/cluster-proxy-01-config.yaml" [1] manifest because of unhandled *v1.Proxy
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.516303       1 render.go:143] skipping "/assets/manifests/cluster-scheduler-02-config.yml" [1] manifest because of unhandled *v1.Scheduler
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.519692       1 render.go:143] skipping "/assets/manifests/cvo-overrides.yaml" [1] manifest because of unhandled *v1.ClusterVersion
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.529447       1 render.go:143] skipping "/assets/manifests/enable-cgroups-v1.yaml" [1] manifest because of unhandled *v1.Node
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.536292       1 render.go:352] 01_01-master-cpu-partitioning_workload_pinning_machineconfig.yaml
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: I0218 16:22:00.536724       1 render.go:352] 01_01-worker-cpu-partitioning_workload_pinning_machineconfig.yaml
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com bootkube.sh[9992]: F0218 16:22:00.536980       1 cmd.go:54] render: could not determine high-performance runtime class container-runtime for profile "openshift-node-performance-profile"; more than one ContainerRuntimeConfig found that matches MCP labels pools.operator.machineconfiguration.openshift.io/master= that associated with performance profile "openshift-node-performance-profile"
Feb 18 16:22:00 cnfdf12.telco5gran.eng.rdu2.redhat.com systemd[1]: bootkube.service: Main process exited, code=exited, status=255/EXCEPTION

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

          4.15-ci with following PRs (for enabling performance profile on day-0): 
        openshift/installer#8007
        openshift/cluster-node-tuning-operator#935

      How reproducible:

          100%

      Steps to Reproduce:

          1.Apply the manifest above on Day 0     
    2.
    3.

      Actual results:

          bootkube fails

      Expected results:

          ContainerRuntimeConfig is applied on day 0

      Additional info:
      This is done as a part of the effort to reduce reboots
      Full log: https://drive.google.com/file/d/1JeCIByq2dR8_XpRsxTn-i7oirY8xzBwu/view?usp=drive_link
      Contents of /opt/openshift folder when the problem occurs:
      https://drive.google.com/file/d/11rVojGr75vopUF9CQaXsvtAThsY5TTy8/view?usp=drive_link

              vgrinber@redhat.com Vitaly Grinberg
              vgrinber@redhat.com Vitaly Grinberg
              Mallapadi Niranjan Mallapadi Niranjan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: