Skip to content

dnm test pipelines 3#2687

Open
jmguzik wants to merge 1 commit intoopenshift:masterfrom
jmguzik:pipe-test3
Open

dnm test pipelines 3#2687
jmguzik wants to merge 1 commit intoopenshift:masterfrom
jmguzik:pipe-test3

Conversation

@jmguzik
Copy link

@jmguzik jmguzik commented Feb 3, 2026

PR Type

Other


Description

  • Add extra whitespace in error message string

  • Add extra whitespace in Dockerfile FROM statement

  • Insert whitespace within word in test name

  • Add blank line in YAML manifest file


Diagram Walkthrough

flowchart LR
  A["Source Files"] -- "Add whitespace" --> B["features.go"]
  A -- "Add whitespace" --> C["Dockerfile.ocp"]
  A -- "Add whitespace" --> D["consoleplugins test YAML"]
  A -- "Add blank line" --> E["featureGate manifest"]
Loading

File Walkthrough

Relevant files
Formatting
features.go
Add extra whitespace in error message                                       

features/features.go

  • Add extra space in error message between "found" and "for"
  • Changes error message formatting in FeatureSets function
+1/-1     
Dockerfile.ocp
Add extra whitespace in FROM statement                                     

Dockerfile.ocp

  • Add extra spaces after FROM keyword in base image declaration
  • Affects builder image reference line
+1/-1     
AAA_ungated.yaml
Insert whitespace within test name word                                   

console/v1/tests/consoleplugins.console.openshift.io/AAA_ungated.yaml

  • Insert whitespace within test name, breaking "create" into "cr eate"
  • Affects test description for ConsolePlugin creation
+1/-1     
featureGate-Hypershift-Default.yaml
Add blank line in manifest structure                                         

payload-manifests/featuregates/featureGate-Hypershift-Default.yaml

  • Add blank line between spec and status sections
  • Affects JSON manifest structure formatting
+1/-0     

Signed-off-by: Jakub Guzik <jguzik@redhat.com>
@openshift-ci-robot
Copy link

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

Hello @jmguzik! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 3, 2026
@jmguzik
Copy link
Author

jmguzik commented Feb 3, 2026

/pipeline auto

@openshift-ci-robot
Copy link

Pipeline controller notification

The pipeline-auto label has been added to this PR. Second-stage tests will be triggered automatically when all first-stage tests pass.

@openshift-ci openshift-ci bot requested a review from everettraven February 3, 2026 14:19
@coderabbitai
Copy link

coderabbitai bot commented Feb 3, 2026

📝 Walkthrough

Walkthrough

This pull request includes four file modifications. The Dockerfile.ocp receives a minor formatting change with additional spacing in the FROM instruction. A test case label in the consoleplugins YAML file gains internal spacing. An error message string in the features.go file adds extra spacing. The featureGate-Hypershift-Default.yaml manifest receives a new top-level status field containing featureGates configuration with disabled and enabled lists. These changes span formatting adjustments and a configuration addition to the feature gate manifest.

🚥 Pre-merge checks | ✅ 1 | ❌ 2
❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check ❓ Inconclusive The title 'dnm test pipelines 3' is vague and does not convey meaningful information about the actual changeset, which involves whitespace additions across multiple files. Use a more descriptive title that summarizes the changes, such as 'Add formatting changes for test pipeline' or 'Update whitespace in multiple files for testing'.
✅ Passed checks (1 passed)
Check name Status Explanation
Description check ✅ Passed The description clearly documents the whitespace additions across four files and provides a detailed file walkthrough with examples of each change type.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.5.0)

Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented
The command is terminated due to an error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented

Important

Action Needed: IP Allowlist Update

If your organization protects your Git platform with IP whitelisting, please add the new CodeRabbit IP address to your allowlist:

  • 136.113.208.247/32 (new)
  • 34.170.211.100/32
  • 35.222.179.152/32

Failure to add the new IP will result in interrupted reviews.


Comment @coderabbitai help to get the list of available commands and usage tips.

@qodo-code-review
Copy link

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🎫 No ticket provided
  • Create ticket/issue
Codebase Duplication Compliance
Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance
🟢
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

🔴
Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status:
Unclear test name: The test name contains an unintended internal whitespace split (cr eate) which reduces
readability and makes the identifier less self-documenting.

Referred Code
- name: Should be able to cr  eate a minimal ConsolePlugin
  initial: |

Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

@openshift-merge-robot
Copy link
Contributor

/override ci/prow/unit ci/prow/minor-images ci/prow/minor-e2e-upgrade-minor ci/prow/lint ci/prow/integration

@qodo-code-review
Copy link

PR Code Suggestions ✨

Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Impact
Possible issue
Fix invalid JSON syntax

Add a missing comma between the spec and status fields to fix the invalid JSON
syntax in the manifest.

payload-manifests/featuregates/featureGate-Hypershift-Default.yaml [10-12]

 "spec": {},
-
 "status": {
  • Apply / Chat
Suggestion importance[1-10]: 9

__

Why: The suggestion correctly identifies a critical syntax error (a missing comma) that makes the JSON content invalid, which would cause parsing to fail. This is a much more significant issue than the newline added by the PR.

High
General
Correct typo in test name

Correct the typo "cr eate" to "create" in the test name for improved
readability and to prevent potential parsing issues.

console/v1/tests/consoleplugins.console.openshift.io/AAA_ungated.yaml [7]

-- name: Should be able to cr  eate a minimal ConsolePlugin
+- name: Should be able to create a minimal ConsolePlugin
  • Apply / Chat
Suggestion importance[1-10]: 5

__

Why: The suggestion correctly identifies and proposes a fix for a typo introduced in a test name, which improves code readability and maintainability.

Low
Remove extra space in error

Remove the extra space between "found" and "for" in the error message for
correct formatting.

features/features.go [12]

-return nil, fmt.Errorf("no information found  for ClusterProfile=%q", clusterProfile)
+return nil, fmt.Errorf("no information found for ClusterProfile=%q", clusterProfile)
  • Apply / Chat
Suggestion importance[1-10]: 4

__

Why: The suggestion correctly points out and fixes an extra space in an error message, which is a minor but valid correction for code consistency and quality.

Low
  • More

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

@openshift-merge-robot: Overrode contexts on behalf of openshift-merge-robot: ci/prow/integration, ci/prow/lint, ci/prow/minor-e2e-upgrade-minor, ci/prow/minor-images, ci/prow/unit

Details

In response to this:

/override ci/prow/unit ci/prow/minor-images ci/prow/minor-e2e-upgrade-minor ci/prow/lint ci/prow/integration

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-robot
Copy link
Contributor

/override ci/prow/build ci/prow/verify-feature-promotion ci/prow/verify-deps ci/prow/verify ci/prow/images ci/prow/okd-scos-images ci/prow/verify-crdify

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

@openshift-merge-robot: Overrode contexts on behalf of openshift-merge-robot: ci/prow/build, ci/prow/images, ci/prow/okd-scos-images, ci/prow/verify, ci/prow/verify-crdify, ci/prow/verify-deps, ci/prow/verify-feature-promotion

Details

In response to this:

/override ci/prow/build ci/prow/verify-feature-promotion ci/prow/verify-deps ci/prow/verify ci/prow/images ci/prow/okd-scos-images ci/prow/verify-crdify

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-robot
Copy link
Contributor

/override ci/prow/verify-client-go ci/prow/verify-crd-schema

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🤖 Fix all issues with AI agents
In `@console/v1/tests/consoleplugins.console.openshift.io/AAA_ungated.yaml`:
- Line 7: The test name string "Should be able to cr  eate a minimal
ConsolePlugin" contains a double space inside "create"; update the YAML value
for the test's name (the string value currently set to that exact phrase) to
"Should be able to create a minimal ConsolePlugin" by removing the extra space
so test reports and searches show the correct name.

In `@Dockerfile.ocp`:
- Line 1: The FROM instruction in the Dockerfile has extraneous spaces ("FROM  
registry...") causing non-standard formatting; update the Dockerfile's FROM
instruction by removing the extra spaces so it reads "FROM registry..." (locate
and edit the FROM line in the Dockerfile.ocp/ Dockerfile and adjust the FROM
instruction accordingly) to follow standard Dockerfile formatting.

In `@features/features.go`:
- Line 12: Fix the typo in the error string used in the fmt.Errorf call that
returns when no data exists: locate the fmt.Errorf(...) invocation that formats
"no information found  for ClusterProfile=%q" (which uses the clusterProfile
variable) and remove the extra space so it reads "no information found for
ClusterProfile=%q".

tests:
onCreate:
- name: Should be able to create a minimal ConsolePlugin
- name: Should be able to cr eate a minimal ConsolePlugin
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Typo: double space in test name.

The test name contains an extra space in "create" ("cr eate" → should be "create"). This will appear in test reports and affects searchability.

✏️ Proposed fix
-    - name: Should be able to cr  eate a minimal ConsolePlugin
+    - name: Should be able to create a minimal ConsolePlugin
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Should be able to cr eate a minimal ConsolePlugin
- name: Should be able to create a minimal ConsolePlugin
🤖 Prompt for AI Agents
In `@console/v1/tests/consoleplugins.console.openshift.io/AAA_ungated.yaml` at
line 7, The test name string "Should be able to cr  eate a minimal
ConsolePlugin" contains a double space inside "create"; update the YAML value
for the test's name (the string value currently set to that exact phrase) to
"Should be able to create a minimal ConsolePlugin" by removing the extra space
so test reports and searches show the correct name.

@@ -1,4 +1,4 @@
FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.24-openshift-4.22 AS builder
FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.24-openshift-4.22 AS builder
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Extraneous whitespace in FROM instruction.

The FROM instruction contains extra spaces (FROM registry... instead of FROM registry...). While Docker tolerates this, it deviates from standard formatting conventions and may indicate an unintended edit.

🧹 Proposed fix
-FROM   registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.24-openshift-4.22 AS builder
+FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.24-openshift-4.22 AS builder
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.24-openshift-4.22 AS builder
FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.24-openshift-4.22 AS builder
🤖 Prompt for AI Agents
In `@Dockerfile.ocp` at line 1, The FROM instruction in the Dockerfile has
extraneous spaces ("FROM   registry...") causing non-standard formatting; update
the Dockerfile's FROM instruction by removing the extra spaces so it reads "FROM
registry..." (locate and edit the FROM line in the Dockerfile.ocp/ Dockerfile
and adjust the FROM instruction accordingly) to follow standard Dockerfile
formatting.

byFeatureSet, ok := allFeatureGates[clusterProfile]
if !ok {
return nil, fmt.Errorf("no information found for ClusterProfile=%q", clusterProfile)
return nil, fmt.Errorf("no information found for ClusterProfile=%q", clusterProfile)
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Typo: double space in error message.

The error message contains an extra space ("no information found for" → should be "no information found for"). This affects the quality of error output.

✏️ Proposed fix
-		return nil, fmt.Errorf("no information found  for ClusterProfile=%q", clusterProfile)
+		return nil, fmt.Errorf("no information found for ClusterProfile=%q", clusterProfile)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
return nil, fmt.Errorf("no information found for ClusterProfile=%q", clusterProfile)
return nil, fmt.Errorf("no information found for ClusterProfile=%q", clusterProfile)
🤖 Prompt for AI Agents
In `@features/features.go` at line 12, Fix the typo in the error string used in
the fmt.Errorf call that returns when no data exists: locate the fmt.Errorf(...)
invocation that formats "no information found  for ClusterProfile=%q" (which
uses the clusterProfile variable) and remove the extra space so it reads "no
information found for ClusterProfile=%q".

@openshift-ci-robot
Copy link

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

@openshift-merge-robot: Overrode contexts on behalf of openshift-merge-robot: ci/prow/verify-client-go, ci/prow/verify-crd-schema

Details

In response to this:

/override ci/prow/verify-client-go ci/prow/verify-crd-schema

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-robot
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-merge-robot
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

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

Details 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
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

@jmguzik: The following tests 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/e2e-aws-ovn d427b3e link true /test e2e-aws-ovn
ci/prow/e2e-gcp d427b3e link true /test e2e-gcp
ci/prow/e2e-aws-ovn-hypershift-conformance d427b3e link true /test e2e-aws-ovn-hypershift-conformance
ci/prow/e2e-aws-ovn-techpreview d427b3e link true /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-serial-1of2 d427b3e link true /test e2e-aws-serial-1of2
ci/prow/e2e-aws-serial-techpreview-1of2 d427b3e link true /test e2e-aws-serial-techpreview-1of2
ci/prow/e2e-aws-ovn-hypershift d427b3e link true /test e2e-aws-ovn-hypershift
ci/prow/e2e-upgrade-out-of-change d427b3e link true /test e2e-upgrade-out-of-change
ci/prow/e2e-azure d427b3e link true /test e2e-azure
ci/prow/e2e-aws-serial-techpreview-2of2 d427b3e link true /test e2e-aws-serial-techpreview-2of2
ci/prow/e2e-aws-serial-2of2 d427b3e link true /test e2e-aws-serial-2of2
ci/prow/e2e-upgrade d427b3e link true /test e2e-upgrade

Full PR test history. Your PR dashboard.

Details

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.

@jmguzik
Copy link
Author

jmguzik commented Feb 3, 2026

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. pipeline-auto Review effort 1/5 size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants