Skip to content
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.

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

[release-4.15] OCPBUGS-33368: monitor test fix to wait before connecting to a non-existent dns on PowerVS and IBMCloud platforms #28776

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #28739

/assign prb112

jcho02 added 2 commits May 7, 2024 17:44
…istent dns

Signed-off-by: Jason Cho <jason.cho2@ibm.com>

go fmt fix

Signed-off-by: Jason Cho <jason.cho2@ibm.com>

add timeout to checkHostnameReady function

Signed-off-by: Jason Cho <jason.cho2@ibm.com>

switch to use oc

Signed-off-by: Jason Cho <jason.cho2@ibm.com>
Signed-off-by: Jason Cho <jason.cho2@ibm.com>
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-18534 has been cloned as Jira Issue OCPBUGS-33368. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-33368: monitor test fix to wait before connecting to a non-existent dns on PowerVS and IBMCloud platforms

In response to this:

This is an automated cherry-pick of #28739

/assign prb112

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 changed the title [release-4.15] OCPBUGS-18534: monitor test fix to wait before connecting to a non-existent dns on PowerVS and IBMCloud platforms [release-4.15] OCPBUGS-33368: monitor test fix to wait before connecting to a non-existent dns on PowerVS and IBMCloud platforms May 7, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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 May 7, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-33368, 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"
  • expected dependent Jira Issue OCPBUGS-18534 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
  • expected dependent Jira Issue OCPBUGS-18534 to target a version in 4.16.0, but it targets "4.16" 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.

In response to this:

This is an automated cherry-pick of #28739

/assign prb112

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 bparees and mfojtik May 7, 2024 17:46
Copy link
Contributor

openshift-ci bot commented May 7, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign bparees for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

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

@prb112
Copy link
Contributor

prb112 commented May 7, 2024

/retest-required

4 similar comments
@prb112
Copy link
Contributor

prb112 commented May 7, 2024

/retest-required

@prb112
Copy link
Contributor

prb112 commented May 8, 2024

/retest-required

@prb112
Copy link
Contributor

prb112 commented May 8, 2024

/retest-required

@prb112
Copy link
Contributor

prb112 commented May 8, 2024

/retest-required

@prb112
Copy link
Contributor

prb112 commented May 9, 2024

/retest

Copy link
Contributor

openshift-ci bot commented May 9, 2024

@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-aws-etcd-recovery 3e3e8ee link false /test e2e-aws-etcd-recovery
ci/prow/e2e-aws-ovn-cgroupsv2 3e3e8ee link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-agnostic-ovn-cmd 3e3e8ee link false /test e2e-agnostic-ovn-cmd
ci/prow/verify 3e3e8ee link true /test verify
ci/prow/e2e-aws-ovn-single-node-serial 3e3e8ee link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node-upgrade 3e3e8ee link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-serial 3e3e8ee link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-csi 3e3e8ee link false /test e2e-aws-csi
ci/prow/e2e-metal-ipi-sdn 3e3e8ee link false /test e2e-metal-ipi-sdn
ci/prow/e2e-aws-ovn-fips 3e3e8ee link true /test e2e-aws-ovn-fips
ci/prow/images 3e3e8ee link true /test images
ci/prow/e2e-metal-ipi-ovn-ipv6 3e3e8ee link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/unit 3e3e8ee link true /test unit
ci/prow/e2e-openstack-ovn 3e3e8ee link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node 3e3e8ee link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-upgrade 3e3e8ee link false /test e2e-aws-ovn-upgrade

Full PR test history. Your PR dashboard.

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.

@prb112
Copy link
Contributor

prb112 commented May 15, 2024

/cherry-pick release-4.14

@openshift-cherrypick-robot
Copy link
Author

@prb112: once the present PR merges, I will cherry-pick it on top of release-4.14 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.14

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.

@prb112
Copy link
Contributor

prb112 commented May 15, 2024

/cherry-pick release-4.15

@openshift-cherrypick-robot
Copy link
Author

@prb112: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.15

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-merge-bot bot added a commit that referenced this pull request May 16, 2024
#28776 FIX [release-4.15] OCPBUGS-33368: monitor test fix to wait before connecting to a non-existent dns on PowerVS and IBMCloud platforms
@openshift-merge-bot openshift-merge-bot bot merged commit 3e3e8ee into openshift:release-4.15 May 16, 2024
2 of 24 checks passed
@openshift-ci-robot
Copy link

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

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

In response to this:

This is an automated cherry-pick of #28739

/assign prb112

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-cherrypick-robot
Copy link
Author

@prb112: new pull request created: #28805

In response to this:

/cherry-pick release-4.14

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-cherrypick-robot
Copy link
Author

@prb112: base branch (release-4.15) needs to differ from target branch (release-4.15)

In response to this:

/cherry-pick release-4.15

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.15.0-0.nightly-2024-06-06-005800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants