Skip to content

NO-JIRA: Add unit test for renderManifest #1173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 27, 2025

Conversation

hongkailiu
Copy link
Member

The diff makes sense, of course.

$ cat ./install/0000_00_cluster-version-operator_03_deployment.yaml | grep '{{'
        image: {{.ReleaseImage}}
          - "--release-image={{.ReleaseImage}}"
            value: {{ .ClusterProfile }}

$ diff -Naupr install/0000_00_cluster-version-operator_03_deployment.yaml pkg/payload/testdata/TestRenderManifest_expected_cvo_deployment.yaml    
--- install/0000_00_cluster-version-operator_03_deployment.yaml 2024-11-06 13:30:42
+++ pkg/payload/testdata/TestRenderManifest_expected_cvo_deployment.yaml        2025-03-27 09:59:50
@@ -25,11 +25,11 @@ spec:
       automountServiceAccountToken: false
       containers:
       - name: cluster-version-operator
-        image: {{.ReleaseImage}}
+        image: quay.io/cvo/release:latest
         imagePullPolicy: IfNotPresent
         args:
           - "start"
-          - "--release-image={{.ReleaseImage}}"
+          - "--release-image=quay.io/cvo/release:latest"
           - "--enable-auto-update=false"
           - "--listen=0.0.0.0:9099"
           - "--serving-cert-file=/etc/tls/serving-cert/tls.crt"
@@ -70,7 +70,7 @@ spec:
               fieldRef:
                 fieldPath: spec.nodeName
           - name: CLUSTER_PROFILE
-            value: {{ .ClusterProfile }}
+            value: some-profile
       # this pod is hostNetwork and uses the internal LB DNS name when possible, which the kubelet also uses.
       # this dnsPolicy allows us to use the same dnsConfig as the kubelet, without access to read it ourselves.
       dnsPolicy: Default

/cc @petr-muller

@openshift-ci openshift-ci bot requested a review from petr-muller March 27, 2025 14:06
Copy link
Member

@petr-muller petr-muller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/label no-qe
/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added no-qe Allows PRs to merge without qe-approved label acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. labels Mar 27, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 27, 2025
Copy link
Contributor

openshift-ci bot commented Mar 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu, petr-muller

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 27, 2025
@petr-muller
Copy link
Member

/retitle NO-JIRA: Add unit test for renderManifest

@openshift-ci openshift-ci bot changed the title Add unit test for renderManifest NO-JIRA: Add unit test for renderManifest Mar 27, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 27, 2025
@openshift-ci-robot
Copy link
Contributor

@hongkailiu: This pull request explicitly references no jira issue.

In response to this:

The diff makes sense, of course.

$ cat ./install/0000_00_cluster-version-operator_03_deployment.yaml | grep '{{'
       image: {{.ReleaseImage}}
         - "--release-image={{.ReleaseImage}}"
           value: {{ .ClusterProfile }}

$ diff -Naupr install/0000_00_cluster-version-operator_03_deployment.yaml pkg/payload/testdata/TestRenderManifest_expected_cvo_deployment.yaml    
--- install/0000_00_cluster-version-operator_03_deployment.yaml 2024-11-06 13:30:42
+++ pkg/payload/testdata/TestRenderManifest_expected_cvo_deployment.yaml        2025-03-27 09:59:50
@@ -25,11 +25,11 @@ spec:
      automountServiceAccountToken: false
      containers:
      - name: cluster-version-operator
-        image: {{.ReleaseImage}}
+        image: quay.io/cvo/release:latest
        imagePullPolicy: IfNotPresent
        args:
          - "start"
-          - "--release-image={{.ReleaseImage}}"
+          - "--release-image=quay.io/cvo/release:latest"
          - "--enable-auto-update=false"
          - "--listen=0.0.0.0:9099"
          - "--serving-cert-file=/etc/tls/serving-cert/tls.crt"
@@ -70,7 +70,7 @@ spec:
              fieldRef:
                fieldPath: spec.nodeName
          - name: CLUSTER_PROFILE
-            value: {{ .ClusterProfile }}
+            value: some-profile
      # this pod is hostNetwork and uses the internal LB DNS name when possible, which the kubelet also uses.
      # this dnsPolicy allows us to use the same dnsConfig as the kubelet, without access to read it ourselves.
      dnsPolicy: Default

/cc @petr-muller

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 4ec8c48 and 2 for PR HEAD e543674 in total

@petr-muller
Copy link
Member

/override ci/prow/e2e-agnostic-ovn

Single unrelated test failed:

: [bz-etcd][invariant] alert/etcdHighCommitDurations should not be at or above 

Copy link
Contributor

openshift-ci bot commented Mar 27, 2025

@petr-muller: Overrode contexts on behalf of petr-muller: ci/prow/e2e-agnostic-ovn

In response to this:

/override ci/prow/e2e-agnostic-ovn

Single unrelated test failed:

: [bz-etcd][invariant] alert/etcdHighCommitDurations should not be at or above 

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-merge-bot openshift-merge-bot bot merged commit ddb11b3 into openshift:main Mar 27, 2025
14 of 15 checks passed
Copy link
Contributor

openshift-ci bot commented Mar 27, 2025

@hongkailiu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn e543674 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-version-operator
This PR has been included in build cluster-version-operator-container-v4.20.0-202503271738.p0.gddb11b3.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. no-qe Allows PRs to merge without qe-approved label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants