Skip to content

[release-4.17] OCPBUGS-90609: Bump origin - #270

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.17from
shiftstack:bump-origin-4.17
Jun 30, 2026
Merged

[release-4.17] OCPBUGS-90609: Bump origin#270
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.17from
shiftstack:bump-origin-4.17

Conversation

@winiciusallan

Copy link
Copy Markdown
Member

The 4.17 release is out dated with regarding to the Origin package. This PR bumps the origin vendored version to the 4.17 branch HEAD commit (5abe37f)

Other changes were needed since some imported packages don't exist anymore.

  • Added a standard_suite.go file to point out to our openshift/openstack suite
  • Bumped cluster-api-actuator-pkg to the HEAD of release-4.17

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@winiciusallan: This pull request references Jira Issue OCPBUGS-90609, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-90609 to depend on a bug targeting a version in 4.18.0, 4.18.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

The 4.17 release is out dated with regarding to the Origin package. This PR bumps the origin vendored version to the 4.17 branch HEAD commit (5abe37f)

Other changes were needed since some imported packages don't exist anymore.

  • Added a standard_suite.go file to point out to our openshift/openstack suite
  • Bumped cluster-api-actuator-pkg to the HEAD of release-4.17

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
openshift-ci Bot requested review from mandre and rlobillo June 24, 2026 18:57
@mandre

mandre commented Jun 29, 2026

Copy link
Copy Markdown
Member

/test test

@mandre mandre 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
/approve

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

openshift-ci Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mandre

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-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 29, 2026
@mandre

mandre commented Jun 29, 2026

Copy link
Copy Markdown
Member

The test suite failed, but it was started successfully which is what matters.
/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jun 29, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mandre: The verified label has been added.

Details

In response to this:

The test suite failed, but it was started successfully which is what matters.
/verified bypass

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.

@mandre

mandre commented Jun 29, 2026

Copy link
Copy Markdown
Member

Let's just get this CI run go to completion. If it fails again due to unrelated issue, I'll override.

@mandre

mandre commented Jun 29, 2026

Copy link
Copy Markdown
Member

The cluster failed installation, because the CI was overloaded. Let's get this in, we already saw it solved the issue it was supposed to solve.
/override ci/prow/test

@openshift-ci

openshift-ci Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

@mandre: Overrode contexts on behalf of mandre: ci/prow/test

Details

In response to this:

The cluster failed installation, because the CI was overloaded. Let's get this in, we already saw it solved the issue it was supposed to solve.
/override ci/prow/test

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 Jun 29, 2026

Copy link
Copy Markdown
Contributor

@winiciusallan: 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/test 0922d47 link true /test test

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.

@mandre

mandre commented Jun 30, 2026

Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@mandre: This pull request references Jira Issue OCPBUGS-90609, which is invalid:

  • expected dependent Jira Issue OCPBUGS-94075 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Obsolete) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@mandre

mandre commented Jun 30, 2026

Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 30, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mandre: This pull request references Jira Issue OCPBUGS-90609, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-94075 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-94075 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents
Details

In response to this:

/jira refresh

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 openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jun 30, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 017ff83 into openshift:release-4.17 Jun 30, 2026
5 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@winiciusallan: Jira Issue Verification Checks: Jira Issue OCPBUGS-90609
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-90609 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

The 4.17 release is out dated with regarding to the Origin package. This PR bumps the origin vendored version to the 4.17 branch HEAD commit (5abe37f)

Other changes were needed since some imported packages don't exist anymore.

  • Added a standard_suite.go file to point out to our openshift/openstack suite
  • Bumped cluster-api-actuator-pkg to the HEAD of release-4.17

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-merge-bot
openshift-merge-bot Bot deleted the bump-origin-4.17 branch June 30, 2026 09:27
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-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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants