Skip to content

OPNET-678: Bump openshift/api#10097

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
cybertron:dns-records-api-bump
Nov 18, 2025
Merged

OPNET-678: Bump openshift/api#10097
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
cybertron:dns-records-api-bump

Conversation

@cybertron
Copy link
Copy Markdown
Member

Pulling in the internalDNSRecords field from
openshift/api#2460

@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 17, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Nov 17, 2025

@cybertron: This pull request references OPNET-678 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 epic to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Pulling in the internalDNSRecords field from
openshift/api#2460

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.

@tthvo
Copy link
Copy Markdown
Member

tthvo commented Nov 18, 2025

/retest

Pulling in the internalDNSRecords field from
openshift/api#2460
@cybertron cybertron force-pushed the dns-records-api-bump branch from e178a87 to a0dd35f Compare November 18, 2025 14:24
@cybertron
Copy link
Copy Markdown
Member Author

Just ran go mod tidy to fix the verify jobs.

@patrickdillon
Copy link
Copy Markdown
Contributor

/approve

Ready to go with testing.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Nov 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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 Nov 18, 2025
Copy link
Copy Markdown
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Nov 18, 2025
@tthvo
Copy link
Copy Markdown
Member

tthvo commented Nov 18, 2025

well, this shouldn't break anything 🤣

/verified by e2e-aws-ovn

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 18, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@tthvo: This PR has been marked as verified by e2e-aws-ovn.

Details

In response to this:

well, this shouldn't break anything 🤣

/verified by e2e-aws-ovn

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 merged commit ccad892 into openshift:main Nov 18, 2025
21 of 26 checks passed
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Nov 18, 2025

@cybertron: 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/okd-scos-e2e-vsphere-ovn a0dd35f link false /test okd-scos-e2e-vsphere-ovn

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