Skip to content

NE-2788: add haproxy28 weekly nightly periodic jobs - #83066

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
gcs278:haproxy28-nightly-periodics
Aug 12, 2026
Merged

NE-2788: add haproxy28 weekly nightly periodic jobs#83066
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
gcs278:haproxy28-nightly-periodics

Conversation

@gcs278

@gcs278 gcs278 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Add five weekly nightly periodic jobs to validate HAProxy 2.8 (the non-default, pinnable version) against the 5.0 release payload, as described in the enhancement test plan.

Job Config Cadence
e2e-aws-ovn-haproxy28 __nightly-5.0.yaml Weekly
e2e-aws-ovn-serial-haproxy28 __nightly-5.0.yaml Weekly
e2e-aws-ovn-upgrade-haproxy28 __nightly-5.0.yaml Weekly
e2e-aws-ovn-fips-haproxy28 __nightly-5.0.yaml Weekly
e2e-aws-ovn-upgrade-from-stable-haproxy28 __nightly-5.0-upgrade-from-stable-4.22.yaml Weekly

Why

The multi-HAProxy version feature (NE-2215) supports HAProxy 2.8 as a pinnable alternative to the default 3.2. Currently only optional presubmits exist for haproxy28 — TRT requires nightly periodics for proper CI signal.

All jobs run on AWS only — HAProxy behavior is platform-agnostic. FIPS is included because HAProxy 2.8 uses OpenSSL 1.1/pcre1 while 3.2 uses OpenSSL 3.x/pcre2, which may behave differently in FIPS mode.

Jobs use the ingress-conf-haproxy-version CI step to annotate ingresses.config.openshift.io/cluster post-install, setting HAProxy 2.8 as the default for all IngressControllers.

Test plan

  • Verify nightly periodics appear in the release controller after merge
  • Verify first weekly run completes successfully

🤖 Generated with Claude Code

Summary by CodeRabbit

Adds five weekly AWS jobs for the OpenShift 5.0 release payload. The jobs validate HAProxy 2.8 through conformance, serial, upgrade, FIPS conformance, and stable 4.22 upgrade workflows.

Each job sets HAProxy 2.8 as the default for all IngressControllers and uses AWS IPI installation with the applicable upgrade, observer, and FIPS checks.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 6, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

@gcs278: This pull request references NE-2788 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Add five weekly nightly periodic jobs to validate HAProxy 2.8 (the non-default, pinnable version) against the 5.0 release payload.

Job Config Cadence
e2e-aws-ovn-haproxy28 __nightly-5.0.yaml Weekly
e2e-aws-ovn-serial-haproxy28 __nightly-5.0.yaml Weekly
e2e-aws-ovn-upgrade-haproxy28 __nightly-5.0.yaml Weekly
e2e-aws-ovn-fips-haproxy28 __nightly-5.0.yaml Weekly
e2e-aws-ovn-upgrade-from-stable-haproxy28 __nightly-5.0-upgrade-from-stable-4.22.yaml Weekly

Why

The multi-HAProxy version feature (NE-2215) supports HAProxy 2.8 as a pinnable alternative to the default 3.2. Currently only optional presubmits exist for haproxy28 — TRT requires nightly periodics for proper CI signal.

All jobs run on AWS only — HAProxy behavior is platform-agnostic. FIPS is included because HAProxy 2.8 uses OpenSSL 1.1/pcre1 while 3.2 uses OpenSSL 3.x/pcre2, which may behave differently in FIPS mode.

Jobs use the ingress-conf-haproxy-version CI step to annotate ingresses.config.openshift.io/cluster post-install, setting HAProxy 2.8 as the default for all IngressControllers.

Dependencies

Test plan

  • Verify nightly periodics appear in the release controller after merge
  • Verify first weekly run completes successfully

🤖 Generated with Claude Code

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.

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: c352a462-8820-429e-a673-525874619bc7

📥 Commits

Reviewing files that changed from the base of the PR and between 81f8e4d and a6e7004.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/release/openshift-release-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (2)
  • ci-operator/config/openshift/release/openshift-release-main__nightly-5.0-upgrade-from-stable-4.22.yaml
  • ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml
🚧 Files skipped from review as they are similar to previous changes (2)
  • ci-operator/config/openshift/release/openshift-release-main__nightly-5.0-upgrade-from-stable-4.22.yaml
  • ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml

Walkthrough

The change adds AWS test configurations for HAProxy 2.8. It covers standard, serial, upgrade, FIPS, and stable-version upgrade-conformance workflows.

Changes

AWS HAProxy 2.8 testing

Layer / File(s) Summary
Nightly workflow variants
ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml
Adds standard, serial, upgrade, and FIPS AWS jobs with HAProxy 2.8 and their respective workflows.
Stable-version upgrade-conformance
ci-operator/config/openshift/release/openshift-release-main__nightly-5.0-upgrade-from-stable-4.22.yaml
Adds a weekly AWS upgrade-conformance job with AWS IPI setup, ingress HAProxy configuration, and the upgrade workflow.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels: lgtm, approved

Suggested reviewers: petr-muller, wking

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: adding weekly nightly periodic jobs for HAProxy 2.8.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The diff adds only static CI YAML targets and generated periodic job names; it changes no Ginkgo It/Describe/Context/When titles or dynamic test-title values.
Test Structure And Quality ✅ Passed The diff adds only three YAML CI configuration files and contains no Ginkgo test code or It/Eventually/BeforeEach/AfterEach blocks to assess.
Microshift Test Compatibility ✅ Passed The parent diff changes only three YAML CI configuration files and adds no Ginkgo test declarations or test source, so MicroShift test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The commit changes only three YAML configuration/job files and adds no Ginkgo declarations or test source, so the SNO test-compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The diff only adds CI test configuration and Prow periodic job registrations; it adds no deployment/operator/controller scheduling constraints or topology-dependent fields.
Ote Binary Stdout Contract ✅ Passed The PR changes only three YAML configuration files; the diff adds no OTE source, suite setup, logging, or stdout writes that could violate the contract.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The diff adds only YAML CI job declarations and generated Prow jobs; it adds no Ginkgo test declarations, IPv4 literals, URL operations, or external connectivity code.
No-Weak-Crypto ✅ Passed The diff adds YAML job definitions and generated Prow entries only; added code has no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or secret comparisons.
Container-Privileges ✅ Passed The PR adds CI job definitions and generated Prow specs only; added lines contain no privileged, hostPID/Network/IPC, SYS_ADMIN, allowPrivilegeEscalation, or root settings.
No-Sensitive-Data-In-Logs ✅ Passed The diff adds only CI job YAML and standard secret mounts; no logging commands or sensitive literals. The referenced HAProxy step logs only its version and status values.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci
openshift-ci Bot requested review from petr-muller and wking August 6, 2026 19:42

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml`:
- Around line 3263-3321: Regenerate the missing periodic Prow jobs by running
make update, covering the source entries in
ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml
lines 3263-3321 and
ci-operator/config/openshift/release/openshift-release-main__nightly-5.0-upgrade-from-stable-4.22.yaml
lines 234-248, then commit the resulting changes to
ci-operator/jobs/openshift/release/openshift-release-main-periodics.yaml.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 440a0fdc-40e4-4628-bc13-8d296ba55680

📥 Commits

Reviewing files that changed from the base of the PR and between 6085899 and 52c15f3.

📒 Files selected for processing (2)
  • ci-operator/config/openshift/release/openshift-release-main__nightly-5.0-upgrade-from-stable-4.22.yaml
  • ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 6, 2026
@gcs278
gcs278 force-pushed the haproxy28-nightly-periodics branch from 52c15f3 to eaef395 Compare August 6, 2026 19:50
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@openshift-merge-bot openshift-merge-bot Bot removed the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 6, 2026
@gcs278

gcs278 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@gcs278

gcs278 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jcmoraisjr

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 6, 2026
@gcs278

gcs278 commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

/hold

We need an update to https://github.com/openshift/origin/blob/main/test/extended/operators/operators.go#L99 to add an exception for haproxy28 upgradeable=false condition which is expected

@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 Aug 7, 2026
@gcs278

gcs278 commented Aug 9, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@gcs278

gcs278 commented Aug 9, 2026

Copy link
Copy Markdown
Contributor Author

I need to wait for the next accepted nightly for openshift/origin#31494 to take effect

@gcs278

gcs278 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@gcs278

gcs278 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade-from-stable-haproxy28

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@gcs278

gcs278 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-fips-haproxy28

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@gcs278

gcs278 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-serial-haproxy28-2of2

@gcs278

gcs278 commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jcmoraisjr

Copy link
Copy Markdown
Member

Just step reorder.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 11, 2026
@gcs278

gcs278 commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade-from-stable-haproxy28

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@gcs278

gcs278 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

base='https://prow.ci.openshift.org/job-history/gs/test-platform-results/pr-logs/directory/rehearse-83066-periodic-ci-openshift-release-main-nightly-5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade-from-stable-haproxy28'

echo '=== Job history page ==='
curl -fsSL "$base" | sed -n '1,240p'

echo
echo '=== Object listing candidates ==='
for url in \
  'https://storage.googleapis.com/test-platform-results/pr-logs/directory/rehearse-83066-periodic-ci-openshift-release-main-nightly-5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade-from-stable-haproxy28/' \
  'https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/directory/rehearse-83066-periodic-ci-openshift-release-main-nightly-5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade-from-stable-haproxy28/'
do
  echo "--- $url"
  curl -fsSL "$url" | sed -n '1,160p' || true
done

Length of output: 13151


🏁 Script executed:

#!/bin/bash
set -euo pipefail

job='rehearse-83066-periodic-ci-openshift-release-main-nightly-5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade-from-stable-haproxy28'
build='2087221719243689984'
root="https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_release/83066/$job/$build"
spyglass="https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/83066/$job/$build"

echo '=== Spyglass page: artifact links ==='
curl -fsSL "$spyglass" |
  grep -Eo 'href="[^"]+"|[^<]{0,120}(Fail|FAIL|Error|ERROR|upgradeable|Upgradeable|haproxy|HAProxy)[^<]{0,160}' |
  sed -n '1,260p' || true

echo
echo '=== GCS artifact index ==='
curl -fsSL "$root/" | sed -n '1,360p'

echo
echo '=== Top-level build log failure excerpts ==='
curl -fsSL "$root/build-log.txt" |
  grep -Ein -C 4 '(^|[^[:alnum:]])(fail|failure|error|upgradeable|haproxy|panic|timed out|timeout)([^[:alnum:]]|$)' |
  tail -n 360 || true

echo
echo '=== JUnit failure excerpts, if present ==='
curl -fsSL "$root/artifacts/junit_operator.xml" 2>/dev/null |
  grep -Ein -C 3 '(failure|error|upgradeable|haproxy)' |
  tail -n 160 || true

Length of output: 60645


🏁 Script executed:

#!/bin/bash
set -euo pipefail

job='rehearse-83066-periodic-ci-openshift-release-main-nightly-5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade-from-stable-haproxy28'
for build in 2085462306837237760 2086862157772754944 2087177198606749696 2087221719243689984; do
  url="https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_release/83066/$job/$build/build-log.txt"
  echo "===== Build $build ====="
  curl -fsSL "$url" |
    grep -Ein -C 2 \
      'Bootstrap failed to complete|bootkube service failed|etcd-bootstrap|Failed waiting for Kubernetes API|Step .*ipi-install-install failed|upgradeable=false|Upgradeable' |
    tail -n 80 || true
done

Length of output: 17351


@gcs278 The four rehearsals fail before the upgrade starts.

Each run fails in:

e2e-aws-ovn-upgrade-from-stable-haproxy28-ipi-install-install

The initial AWS 4.22 cluster does not complete bootstrap. The common error is:

The bootkube service failed at stage "etcd-bootstrap"
Failed waiting for Kubernetes API

The installer container then exits with code 5.

This is not the expected HAProxy 2.8 upgradeable=false condition. The cluster never becomes available, so the HAProxy post-install configuration and the upgrade workflow do not run.

The top-level logs do not contain the underlying etcd-bootstrap error. The bootstrap-machine logs in the install artifacts are required to identify that error.

You are interacting with an AI system.

Add five weekly nightly periodic jobs to validate HAProxy 2.8 (the
non-default, pinnable version) against the 5.0 release payload:

- e2e-aws-ovn-haproxy28 (conformance)
- e2e-aws-ovn-serial-haproxy28 (serial, 2 shards)
- e2e-aws-ovn-upgrade-haproxy28 (z-stream upgrade)
- e2e-aws-ovn-fips-haproxy28 (FIPS conformance)
- e2e-aws-ovn-upgrade-from-stable-haproxy28 (4.22 to 5.0 upgrade)

All jobs run weekly on AWS using the ingress-conf-haproxy-version CI
step to set HAProxy 2.8 as the cluster-wide default post-install.
HAProxy behavior is platform-agnostic so single-platform coverage is
sufficient.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@gcs278
gcs278 force-pushed the haproxy28-nightly-periodics branch from 0f3416c to a6e7004 Compare August 12, 2026 15:29
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 12, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@gcs278: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-serial-haproxy28-2of2 N/A periodic Periodic changed
periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-fips-haproxy28 N/A periodic Periodic changed
periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-upgrade-haproxy28 N/A periodic Periodic changed
periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-serial-haproxy28-1of2 N/A periodic Periodic changed
periodic-ci-openshift-release-main-nightly-5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade-from-stable-haproxy28 N/A periodic Periodic changed
periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-haproxy28 N/A periodic Periodic changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@gcs278

gcs278 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade-from-stable-haproxy28

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@neisw

neisw commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

/approve

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 12, 2026
@gcs278

gcs278 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@jcmoraisjr

Copy link
Copy Markdown
Member

Another step reorder.

/lgtm

@gcs278

gcs278 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

@jcmoraisjr can you provide one last lgtm please? I've tested all of the periodics, and got everything to pass at least once.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 12, 2026
@gcs278

gcs278 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

oh nvm you are too quick thanks!

@openshift-ci

openshift-ci Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gcs278, jcmoraisjr, neisw

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

The pull request process is described 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-merge-bot

Copy link
Copy Markdown
Contributor

@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 12, 2026
@gcs278

gcs278 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 12, 2026
@openshift-ci

openshift-ci Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

@gcs278: all tests passed!

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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 46d6024 into openshift:main Aug 12, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants