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

Update NTO images to be consistent with ART

    XMLWordPrintable

Details

    • Important
    • PSAP Sprint 231
    • 1
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Bug Fix
    • Done

    Description

      Description of problem:

              
        
        
          
            Updating cluster-node-tuning-operator images to be consistent with ART
      
      TLDR:
      
      Component owners, please ensure that this PR merges as it impacts the fidelity
      
      of your CI signal. Patch-manager / leads, this PR is a no-op from a product
      
      perspective -- feel free to manually apply any labels (e.g. jira/valid-bug) to help the
      
      PR merge as long as tests are passing. If the PR is labeled "needs-ok-to-test", this is
      
      to limit costs for re-testing these PRs while they wait for review. Issue /ok-to-test
      
      to remove this tag and help the PR to merge.
      Detail:
      
      This repository is out of sync with the downstream product builds for this component.
      
      One or more images differ from those being used by ART to create product builds. This
      
      should be addressed to ensure that the component's CI testing is accurately
      
      reflecting what customers will experience.
      The information within the following ART component metadata is driving this alignment
      
      request: cluster-node-tuning-operator.yml.
      The vast majority of these PRs are opened because a different Golang version is being
      
      used to build the downstream component. ART compiles most components with the version
      
      of Golang being used by the control plane for a given OpenShift release. Exceptions
      
      to this convention (i.e. you believe your component must be compiled with a Golang
      
      version independent from the control plane) must be granted by the OpenShift
      
      architecture team and communicated to the ART team.
      Roles & Responsibilities:
      
      Component owners are responsible for ensuring these alignment PRs merge with passing
      
      tests OR that necessary metadata changes are reported to the ART team: @release-artists
      
      in #aos-art on Slack. If necessary, the changes required by this pull request can be
      
      introduced with a separate PR opened by the component team. Once the repository is aligned,
      
      this PR will be closed automatically.
      Patch-manager or those with sufficient privileges within this repository may add
      
      any required labels to ensure the PR merges once tests are passing. Downstream builds
      
      are already being built with these changes. Merging this PR only improves the fidelity
      
      of our CI.
      
      ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image).
      
      In order for your upstream .ci-operator.yaml configuration to be 
      honored, you must set the following in your openshift/release 
      ci-operator configuration file:
      build_root:
        from_repository: true
      
      If you have any questions about this pull request, please reach out to @release-artists in the #aos-art coreos slack channel.
          
        
        
      
      
            

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

       

      How reproducible:

       

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

      https://github.com/openshift/cluster-node-tuning-operator/pull/477

      Attachments

        Issue Links

          Activity

            People

              jmencak Jiri Mencak
              jmencak Jiri Mencak
              Liquan Cui Liquan Cui
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: