Skip to content

NO-JIRA: Update to track 5.0#1930

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
tlbueno:branching_5.0
Apr 30, 2026
Merged

NO-JIRA: Update to track 5.0#1930
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
tlbueno:branching_5.0

Conversation

@tlbueno

@tlbueno tlbueno commented Apr 16, 2026

Copy link
Copy Markdown
Member

Updates to track 5.0

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

Copy link
Copy Markdown

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

Details

In response to this:

Updates to track 5.0

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.

@tlbueno

tlbueno commented Apr 16, 2026

Copy link
Copy Markdown
Member Author

/draft

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

@dustymabe dustymabe left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@dustymabe

Copy link
Copy Markdown
Member

once this merges we need to make sure that this commit doesn't get synced to https://github.com/openshift/os/tree/release-4.22

@ravanelli ravanelli left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We also need to change base-4-22-rhel102.ocp.svc.cluster.local, since it is tied to prow, we will also need more steps:

  • First we need to create a new repo for ocp-5.0-rhel102.repo see ocp-5.0-rhel101.repo, in order to create it, we need to have it first for 5.0 branch, basically copy the rhel-102 repos from the 4.22 branch

@tlbueno

tlbueno commented Apr 16, 2026

Copy link
Copy Markdown
Member Author

We also need to change base-4-22-rhel102.ocp.svc.cluster.local, since it is tied to prow, we will also need more steps:

* First we need to create a new repo  for  ocp-5.0-rhel102.repo see ocp-5.0-[rhel101.repo](https://github.com/openshift/release/blob/main/core-services/release-controller/_repos/ocp-5.0-rhel101.repo), in order to create it, we need  to have it first for 5.0 branch, basically copy the [rhel-102](https://redhat.atlassian.net/browse/rhel-102) repos from the [4.22](https://github.com/openshift-eng/ocp-build-data/tree/openshift-4.22/repos) branch

ok. let me start to work on that

@tlbueno

tlbueno commented Apr 17, 2026

Copy link
Copy Markdown
Member Author

/retest

1 similar comment
@tlbueno

tlbueno commented Apr 18, 2026

Copy link
Copy Markdown
Member Author

/retest

@ravanelli

ravanelli commented Apr 18, 2026

Copy link
Copy Markdown
Member

conmon-rs and cri-o we are still missing these 2 packages in plashets

@ravanelli

Copy link
Copy Markdown
Member

The okd repos still missing as well.

Comment thread packages-openshift.yaml
@tlbueno

tlbueno commented Apr 22, 2026

Copy link
Copy Markdown
Member Author

/retest

@tlbueno

tlbueno commented Apr 22, 2026

Copy link
Copy Markdown
Member Author

/test images

@tlbueno

tlbueno commented Apr 22, 2026

Copy link
Copy Markdown
Member Author

/retest

2 similar comments
@tlbueno

tlbueno commented Apr 22, 2026

Copy link
Copy Markdown
Member Author

/retest

@tlbueno

tlbueno commented Apr 23, 2026

Copy link
Copy Markdown
Member Author

/retest

@tlbueno

tlbueno commented Apr 24, 2026

Copy link
Copy Markdown
Member Author

/retest

5 similar comments
@ravanelli

Copy link
Copy Markdown
Member

/retest

@tlbueno

tlbueno commented Apr 28, 2026

Copy link
Copy Markdown
Member Author

/retest

@tlbueno

tlbueno commented Apr 29, 2026

Copy link
Copy Markdown
Member Author

/retest

@tlbueno

tlbueno commented Apr 29, 2026

Copy link
Copy Markdown
Member Author

/retest

@ravanelli

Copy link
Copy Markdown
Member

/retest

@ravanelli

Copy link
Copy Markdown
Member

/test images

@tlbueno tlbueno force-pushed the branching_5.0 branch 3 times, most recently from d57a798 to 46dda01 Compare April 30, 2026 01:08
Comment thread extensions/rhel-10.2.yaml Outdated
Comment thread build-node-image.sh Outdated
Comment thread packages-openshift.yaml Outdated
Signed-off-by: Tiago Bueno <tiago.bueno@gmail.com>
@ravanelli

Copy link
Copy Markdown
Member

/override okd-scos-images

@openshift-ci

openshift-ci Bot commented Apr 30, 2026

Copy link
Copy Markdown
Contributor

@ravanelli: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • okd-scos-images

Only the following failed contexts/checkruns were expected:

  • ci/prow/images
  • ci/prow/okd-scos-images
  • pull-ci-openshift-os-master-images
  • pull-ci-openshift-os-master-okd-scos-images
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override okd-scos-images

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.

@ravanelli

Copy link
Copy Markdown
Member

/override ci/prow/okd-scos-images

@openshift-ci

openshift-ci Bot commented Apr 30, 2026

Copy link
Copy Markdown
Contributor

@ravanelli: Overrode contexts on behalf of ravanelli: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images

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-ci

openshift-ci Bot commented Apr 30, 2026

Copy link
Copy Markdown
Contributor

@tlbueno: 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.

@ravanelli

Copy link
Copy Markdown
Member

/lgtm

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

openshift-ci Bot commented Apr 30, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustymabe, ravanelli, tlbueno

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:
  • OWNERS [dustymabe,ravanelli,tlbueno]

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

@ravanelli

Copy link
Copy Markdown
Member

/label verified

@openshift-ci openshift-ci Bot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 30, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 1636879 into openshift:master Apr 30, 2026
3 checks passed
openshift-merge-bot Bot pushed a commit that referenced this pull request May 19, 2026
This didn't get updated in [1], but [2], which created
these files, was also in flight at the same time.

[1] #1930
[2] #1919
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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants