Skip to content

Conversation

@rh-roman
Copy link

Promote streaming list encoding from only being on by default in Hypershift to being on by default everywhere.

@openshift-ci-robot
Copy link

Pipeline controller notification
This repository 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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 21, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 21, 2025

@rh-roman: This pull request references CNTRLPLANE-1980 which is a valid jira issue.

In response to this:

Promote streaming list encoding from only being on by default in Hypershift to being on by default everywhere.

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

coderabbitai bot commented Nov 21, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

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

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

@rh-roman
Copy link
Author

/hold

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

Hello @rh-roman! 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 do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 21, 2025
@openshift-ci openshift-ci bot requested review from deads2k and sjenning November 21, 2025 19:07
@rh-roman
Copy link
Author

rh-roman commented Dec 2, 2025

/payload 4.18 nightly blocking

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 2, 2025

@rh-roman: trigger 12 job(s) of type blocking for the nightly release of OCP 4.18

  • periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6
  • periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-ovn-ocp-conformance
  • periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-ovn-ocp-conformance-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9b27fa40-cfa4-11f0-81ff-2e60786fb27c-0

@rh-roman
Copy link
Author

rh-roman commented Dec 2, 2025

/retest-required

@rh-roman
Copy link
Author

rh-roman commented Dec 3, 2025

/payload-job periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

@rh-roman: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/482aea20-d092-11f0-83f6-2851a233d398-0

@rh-roman
Copy link
Author

rh-roman commented Dec 4, 2025

On the initial run, 3 jobs failed

periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance
periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-ovn-ocp-conformance
periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-ovn-ocp-conformance-serial

Microshift payload jobs don't work #2597 (comment)

aws-ovn-conformance failed with a transient error and succeeded when run again

* could not run steps: step e2e-aws-ovn-conformance failed: failed to acquire lease for "hypershift-quota-slice": status 502 Bad Gateway, status code 502

jluhrsen added a commit to jluhrsen/release that referenced this pull request Dec 4, 2025
Change ovn-kubernetes master build_root from golang-1.22 to
rhel-9-release-golang-1.24-openshift-4.18 to provide dev tools
(git, jq, ssh) needed by microshift conformance tests when they
run as payload qualifiers.

When microshift periodic tests run as payload qualifiers (via /payload
or release-controller), ci-operator merges configs:
  Base: openshift/ovn-kubernetes@master (provides build_root)
  Injected: openshift/[email protected]__periodics:e2e-aws-ovn-ocp-conformance-serial

The microshift workflow steps use "from: root" which resolves to the
merged config's build_root. The plain golang-1.22 image lacks dev tools
that microshift test scripts require, causing "unknown image root" errors.

The rhel-9-release-golang image provides both golang and dev tools,
working for both ovn-kubernetes's own tests (which use "from: src")
and injected microshift tests (which use "from: root").

Fixes:
- periodic-ci-openshift-microshift-release-4.21-periodics-e2e-aws-ovn-ocp-conformance
- periodic-ci-openshift-microshift-release-4.21-periodics-e2e-aws-ovn-ocp-conformance-serial

Related: openshift/ovn-kubernetes#2887
Related: openshift/api#2598
@rh-roman
Copy link
Author

rh-roman commented Dec 4, 2025

/hold cancel

@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 Dec 4, 2025
@JoelSpeed
Copy link
Contributor

/lgtm
/label jira/valid-bug
/override ci/prow/verify

/hold Should we wait for 4.19 to hit a green payload before merging this?

@openshift-ci openshift-ci bot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Dec 4, 2025
@JoelSpeed
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Dec 4, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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 Dec 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 4, 2025

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify

In response to this:

/lgtm
/label jira/valid-bug
/override ci/prow/verify

/hold Should we wait for 4.19 to hit a green payload before merging this?

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.

@benluddy
Copy link
Contributor

Should we wait for 4.19 to hit a green payload before merging this?

I see it in https://amd64.ocp.releases.ci.openshift.org/releasestream/4-stable/release/4.19.19 now.

/hold cancel

@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 Dec 10, 2025
@rh-roman
Copy link
Author

/retest-required

@liangxia
Copy link
Member

/pipeline required

@liangxia
Copy link
Member

/test e2e-aws-ovn-hypershift-conformance

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 12, 2025

@liangxia: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test build
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial
/test e2e-aws-serial-techpreview
/test e2e-upgrade
/test images
/test integration
/test minor-e2e-upgrade-minor
/test minor-images
/test okd-scos-images
/test unit
/test verify
/test verify-client-go
/test verify-crd-schema
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-azure
/test e2e-gcp
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-api-release-4.18-build
pull-ci-openshift-api-release-4.18-e2e-aws-ovn
pull-ci-openshift-api-release-4.18-e2e-aws-ovn-hypershift
pull-ci-openshift-api-release-4.18-e2e-aws-ovn-techpreview
pull-ci-openshift-api-release-4.18-e2e-aws-serial
pull-ci-openshift-api-release-4.18-e2e-aws-serial-techpreview
pull-ci-openshift-api-release-4.18-e2e-azure
pull-ci-openshift-api-release-4.18-e2e-gcp
pull-ci-openshift-api-release-4.18-e2e-upgrade
pull-ci-openshift-api-release-4.18-images
pull-ci-openshift-api-release-4.18-integration
pull-ci-openshift-api-release-4.18-minor-e2e-upgrade-minor
pull-ci-openshift-api-release-4.18-minor-images
pull-ci-openshift-api-release-4.18-okd-scos-images
pull-ci-openshift-api-release-4.18-unit
pull-ci-openshift-api-release-4.18-verify
pull-ci-openshift-api-release-4.18-verify-client-go
pull-ci-openshift-api-release-4.18-verify-crd-schema
pull-ci-openshift-api-release-4.18-verify-deps

In response to this:

/test e2e-aws-ovn-hypershift-conformance

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.

@liangxia
Copy link
Member

/test e2e-aws-serial

@liangxia
Copy link
Member

/test e2e-aws-serial-techpreview

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 12, 2025

@rh-roman: all tests passed!

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants