Skip to content

Conversation

@pacevedom
Copy link
Contributor

No description provided.

@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 Jan 12, 2026
@openshift-ci-robot
Copy link

@pacevedom: This pull request references Jira Issue OCPBUGS-72360, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED 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.

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

Details

In response to 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from pmtk and vanhalenar January 12, 2026 11:19
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 12, 2026
@pacevedom pacevedom changed the title OCPBUGS-72360: Update openshift-tests-private commit NO-ISSUE: Update openshift-tests-private commit Jan 12, 2026
@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 Jan 12, 2026
@openshift-ci-robot
Copy link

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

Details

In response to 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 openshift-eng/jira-lifecycle-plugin repository.

@pacevedom
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

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

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.

@agullon
Copy link
Contributor

agullon commented Jan 12, 2026

/lgtm

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

/retest

@pmtk
Copy link
Member

pmtk commented Jan 13, 2026

2026-01-12 16:44:19,672 INFO     [generate_common_versions.py:304] Updating test/bin/common_versions.sh file
++ 16:44:19.710798598 microshift/test/bin/common_versions_verify.sh:25 	git diff --exit-code /home/ec2-user/microshift/test/bin/common_versions.sh
diff --git a/test/bin/common_versions.sh b/test/bin/common_versions.sh
index d22a0417e..0f70192c0 100644
--- a/test/bin/common_versions.sh
+++ b/test/bin/common_versions.sh
@@ -164,6 +164,6 @@ export BREW_LREL_RELEASE_VERSION
 
 # Branch and commit for the openshift-tests-private repository
 OPENSHIFT_TESTS_PRIVATE_REPO_BRANCH="release-4.${MINOR_VERSION}"
-OPENSHIFT_TESTS_PRIVATE_REPO_COMMIT="ed0dc50bfaf9b301d175b7035b8c0192ab113db9"
+OPENSHIFT_TESTS_PRIVATE_REPO_COMMIT="b28bd22e0778a177887dfafe556c61ab354e9bfe"
 export OPENSHIFT_TESTS_PRIVATE_REPO_BRANCH
 export OPENSHIFT_TESTS_PRIVATE_REPO_COMMIT
++ 16:44:19.724456833 microshift/test/bin/common_versions_verify.sh:26 	echo 'ERROR: Discovered that common_versions.sh was updated on the branch under test, but the regenerated version is different'
ERROR: Discovered that common_versions.sh was updated on the branch under test, but the regenerated version is different

checkmate

You need to update common_version.sh.template

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2026
@pmtk
Copy link
Member

pmtk commented Jan 13, 2026

/lgtm

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

agullon commented Jan 13, 2026

/lgtm

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

openshift-ci bot commented Jan 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, pacevedom, pmtk

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 [agullon,pacevedom,pmtk]

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

@agullon
Copy link
Contributor

agullon commented Jan 13, 2026

/test e2e-aws-tests-release-arm

@agullon
Copy link
Contributor

agullon commented Jan 13, 2026

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 13, 2026
@openshift-ci-robot
Copy link

@agullon: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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

/retest-required

Remaining retests: 0 against base HEAD f17724c and 2 for PR HEAD 924a506 in total

@pacevedom
Copy link
Contributor Author

/test e2e-aws-tests-release-arm

@pacevedom
Copy link
Contributor Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 13, 2026

@pacevedom: 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-tests-periodic 924a506 link true /test e2e-aws-tests-periodic
ci/prow/e2e-aws-tests-bootc-periodic 924a506 link true /test e2e-aws-tests-bootc-periodic
ci/prow/e2e-aws-tests 924a506 link true /test e2e-aws-tests
ci/prow/e2e-aws-tests-bootc-periodic-arm 924a506 link true /test e2e-aws-tests-bootc-periodic-arm
ci/prow/e2e-aws-tests-arm 924a506 link true /test e2e-aws-tests-arm
ci/prow/e2e-aws-tests-release-arm 924a506 link true /test e2e-aws-tests-release-arm

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.

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