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.

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

MGMT-11143: Fix missing DNS entry for reclaim test #2525

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

MGMT-11143: Fix missing DNS entry for reclaim test #2525

wants to merge 1 commit into from

Conversation

CrystalChun
Copy link
Contributor

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 6, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 6, 2024 •
edited by openshift-ci bot
Loading

@CrystalChun: This pull request references MGMT-11143 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 sub-task to target the "4.18.0" version, but no target version was set.

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.

@CrystalChun
Copy link
Contributor Author

/test ?

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Sep 6, 2024

@CrystalChun: The following commands are available to trigger required jobs:

  • /test e2e-metal-assisted
  • /test e2e-metal-assisted-bond-4-14
  • /test e2e-metal-assisted-kube-api-net-suite
  • /test e2e-metal-assisted-static-ip-suite-4-14
  • /test e2e-metal-single-node-live-iso
  • /test e2e-metal-single-node-with-worker-live-iso
  • /test images
  • /test lint

The following commands are available to trigger optional jobs:

  • /test e2e-metal-assisted-4-12
  • /test e2e-metal-assisted-4-13
  • /test e2e-metal-assisted-4-14
  • /test e2e-metal-assisted-4-15
  • /test e2e-metal-assisted-4-16
  • /test e2e-metal-assisted-bond
  • /test e2e-metal-assisted-cnv-4-16
  • /test e2e-metal-assisted-day2
  • /test e2e-metal-assisted-day2-arm-workers
  • /test e2e-metal-assisted-day2-single-node
  • /test e2e-metal-assisted-external
  • /test e2e-metal-assisted-external-4-16
  • /test e2e-metal-assisted-ha-kube-api
  • /test e2e-metal-assisted-ha-kube-api-ipv4
  • /test e2e-metal-assisted-ha-kube-api-ipv6
  • /test e2e-metal-assisted-ipv4v6
  • /test e2e-metal-assisted-ipv6
  • /test e2e-metal-assisted-ipxe
  • /test e2e-metal-assisted-kube-api-late-binding-single-node
  • /test e2e-metal-assisted-kube-api-late-unbinding-single-node
  • /test e2e-metal-assisted-kube-api-reclaim
  • /test e2e-metal-assisted-kube-api-reclaim-single-node
  • /test e2e-metal-assisted-lvm
  • /test e2e-metal-assisted-mce
  • /test e2e-metal-assisted-mce-sno
  • /test e2e-metal-assisted-metallb
  • /test e2e-metal-assisted-none
  • /test e2e-metal-assisted-odf-4-16
  • /test e2e-metal-assisted-onprem
  • /test e2e-metal-assisted-single-node
  • /test e2e-metal-assisted-static-ip-suite
  • /test e2e-metal-assisted-tang
  • /test e2e-metal-assisted-tpmv2
  • /test e2e-metal-assisted-upgrade-agent
  • /test e2e-metal-ctlplane-scaleup
  • /test e2e-nutanix-assisted
  • /test e2e-nutanix-assisted-4-14
  • /test e2e-nutanix-assisted-4-15
  • /test e2e-nutanix-assisted-4-16
  • /test e2e-oci-assisted
  • /test e2e-oci-assisted-4-16
  • /test e2e-oci-assisted-iscsi
  • /test e2e-vsphere-assisted
  • /test e2e-vsphere-assisted-4-14
  • /test e2e-vsphere-assisted-4-15
  • /test e2e-vsphere-assisted-4-16
  • /test e2e-vsphere-assisted-kube-api
  • /test e2e-vsphere-assisted-umn
  • /test opct-oci-assisted

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-assisted-test-infra-master-e2e-metal-assisted
  • pull-ci-openshift-assisted-test-infra-master-e2e-metal-assisted-kube-api-late-binding-single-node
  • pull-ci-openshift-assisted-test-infra-master-e2e-metal-assisted-kube-api-net-suite
  • pull-ci-openshift-assisted-test-infra-master-e2e-metal-single-node-live-iso
  • pull-ci-openshift-assisted-test-infra-master-images
  • pull-ci-openshift-assisted-test-infra-master-lint

In response to this:

/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 requested review from avishayt and eliorerz September 6, 2024 18:59
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 6, 2024
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Sep 6, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: CrystalChun
Once this PR has been reviewed and has the lgtm label, please assign eranco74 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

@CrystalChun
Copy link
Contributor Author

/test e2e-metal-assisted-kube-api-reclaim e2e-metal-assisted-kube-api-reclaim-single-node

@CrystalChun CrystalChun mentioned this pull request Sep 6, 2024
Closed
@CrystalChun CrystalChun marked this pull request as draft September 6, 2024 19:03
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 6, 2024
@CrystalChun
Copy link
Contributor Author

/test e2e-metal-assisted-kube-api-reclaim e2e-metal-assisted-kube-api-reclaim-single-node

@CrystalChun
MGMT-11143: Fix missing DNS entry for reclaim test
eb17fd4 
During the reclaim test, the error `Get
\"https://api.test-infra-cluster-8102e86e.redhat.com:6443/api/v1\":
dial tcp: lookup api.test-infra-cluster-8102e86e.redhat.com on
10.96.0.10:53: no such host"` was observed in assisted-service.
This adds the spoke cluster's DNS entry to `/etc/hosts` so
assisted-service can resolve the spoke cluster API DNS.
@CrystalChun
Copy link
Contributor Author

/test e2e-metal-assisted-kube-api-reclaim e2e-metal-assisted-kube-api-reclaim-single-node

1 similar comment
@CrystalChun
Copy link
Contributor Author

/test e2e-metal-assisted-kube-api-reclaim e2e-metal-assisted-kube-api-reclaim-single-node

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Sep 10, 2024

@CrystalChun: 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-metal-assisted 8476301 link true /test e2e-metal-assisted
ci/prow/e2e-metal-assisted-kube-api-late-binding-single-node 8476301 link false /test e2e-metal-assisted-kube-api-late-binding-single-node
ci/prow/lint 8476301 link true /test lint
ci/prow/e2e-metal-assisted-kube-api-net-suite 8476301 link true /test e2e-metal-assisted-kube-api-net-suite
ci/prow/e2e-metal-assisted-kube-api-reclaim-single-node eb17fd4 link false /test e2e-metal-assisted-kube-api-reclaim-single-node
ci/prow/e2e-metal-assisted-kube-api-reclaim eb17fd4 link false /test e2e-metal-assisted-kube-api-reclaim

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.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@avishayt avishayt Awaiting requested review from avishayt

@eliorerz eliorerz Awaiting requested review from eliorerz

Assignees
No one assigned
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@CrystalChun @openshift-ci-robot @openshift-bot