Skip to content

[release-4.12] OCPBUGS-16696: Wait for DNS DS pods to be ready #28083

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
openshift-merge-robot merged 1 commit into from
Aug 23, 2023
Merged

[release-4.12] OCPBUGS-16696: Wait for DNS DS pods to be ready #28083

openshift-merge-robot merged 1 commit into from
Aug 23, 2023

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jul 24, 2023

This is an automated cherry-pick of #27715

/assign Miciah

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jul 24, 2023
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 24, 2023

@openshift-cherrypick-robot: Jira Issue OCPBUGS-6902 has been cloned as Jira Issue OCPBUGS-16696. Will retitle bug to link to clone.
/retitle [release-4.12] OCPBUGS-16696: Wait for DNS DS pods to be ready

Details

In response to this:

This is an automated cherry-pick of #27715

/assign Miciah

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/test-infra repository.

@openshift-ci openshift-ci bot changed the title [release-4.12] OCPBUGS-6902: Wait for DNS DS pods to be ready [release-4.12] OCPBUGS-16696: Wait for DNS DS pods to be ready Jul 24, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jul 24, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 24, 2023

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-6902 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-6902 targets the "4.13.0" version, which is one of the valid target versions: 4.13.0, 4.13.z
  • bug has dependents

Requesting review from QA contact:
/cc @pamoedom

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

Details

In response to this:

This is an automated cherry-pick of #27715

/assign Miciah

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/test-infra repository.

@openshift-ci openshift-ci bot requested review from deads2k, mfojtik and pamoedom July 24, 2023 13:44
@Miciah Miciah mentioned this pull request Jul 24, 2023
Merged
@Miciah
Copy link
Contributor

Miciah commented Jul 24, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2023
@Miciah
Copy link
Contributor

Miciah commented Jul 24, 2023

@soltysh, are you fine with this backport?

soltysh
soltysh approved these changes Aug 16, 2023
View reviewed changes
Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/approve
/label backport-risk-assessed

@soltysh
Copy link
Contributor

soltysh commented Aug 16, 2023

/retest-required

@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 Aug 16, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 16, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miciah, openshift-cherrypick-robot, soltysh

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 Aug 16, 2023
@wangke19
Copy link
Contributor

wangke19 commented Aug 23, 2023

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Aug 23, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 23, 2023 •
edited
Loading

@openshift-cherrypick-robot: 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-agnostic-ovn-cmd a8b0efa link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-gcp-csi a8b0efa link false /test e2e-gcp-csi
ci/prow/e2e-aws-ovn-upgrade a8b0efa link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-single-node-serial a8b0efa link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node-upgrade a8b0efa link false /test e2e-aws-ovn-single-node-upgrade

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/test-infra repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 23, 2023

/retest-required

Remaining retests: 0 against base HEAD e89dca7 and 2 for PR HEAD a8b0efa in total

@openshift-merge-robot openshift-merge-robot merged commit fc7f9ec into openshift:release-4.12 Aug 23, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 23, 2023

@openshift-cherrypick-robot: Jira Issue OCPBUGS-16696: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-16696 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #27715

/assign Miciah

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/test-infra repository.

@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Aug 27, 2023

Fix included in accepted release 4.12.0-0.nightly-2023-08-26-180408

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pamoedom pamoedom Awaiting requested review from pamoedom

@deads2k deads2k Awaiting requested review from deads2k

@mfojtik mfojtik Awaiting requested review from mfojtik

1 more reviewer

@soltysh soltysh soltysh approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@dgoodwin dgoodwin

@stbenjam stbenjam

@Miciah Miciah

@kasturinarra kasturinarra

@jadhaj jadhaj

@sunilcio sunilcio

@pamoedom pamoedom

@jitendar-singh jitendar-singh

@prietyc123 prietyc123

@gangwgr gangwgr

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.