Closed gcs278 closed 8 months ago
@gcs278: This pull request references NE-1324 which is a valid jira issue.
@gcs278: This pull request references NE-1324 which is a valid jira issue.
@gcs278: This pull request references NE-1324 which is a valid jira issue.
@gcs278: This pull request references NE-1324 which is a valid jira issue.
/assign
/test e2e-aws-shared-vpc-phz-operator
/retest
An error occurred (HostedZoneAlreadyExists) when calling the CreateHostedZone operation: A hosted zone has already been created with the specified caller reference.
: Seems like the last failed job didn't clean up after itself. Will look into it.
/test e2e-aws-shared-vpc-phz-operator
Round 1 - Success: /test e2e-aws-shared-vpc-phz-operator
cluster install fail /test e2e-azure-operator
https://github.com/openshift/release/pull/43517 merged. testing again. /test e2e-aws-shared-vpc-phz-operator
@gcs278: 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-azure-operator | d04af909927c7c9f47d308ae14e9744b7842c238 | link | true | /test e2e-azure-operator |
ci/prow/verify | d04af909927c7c9f47d308ae14e9744b7842c238 | link | true | /test verify |
ci/prow/e2e-azure-infoblox-operator | d04af909927c7c9f47d308ae14e9744b7842c238 | link | true | /test e2e-azure-infoblox-operator |
ci/prow/e2e-aws-operator | d04af909927c7c9f47d308ae14e9744b7842c238 | link | true | /test e2e-aws-operator |
ci/prow/images | d04af909927c7c9f47d308ae14e9744b7842c238 | link | true | /test images |
ci/prow/e2e-aws-shared-vpc-phz-operator | d04af909927c7c9f47d308ae14e9744b7842c238 | link | true | /test e2e-aws-shared-vpc-phz-operator |
ci/prow/ci-index-external-dns-operator-bundle | d04af909927c7c9f47d308ae14e9744b7842c238 | link | true | /test ci-index-external-dns-operator-bundle |
Full PR test history. Your PR dashboard.
@alebedev87 I should have addressed everything in your review, but I still need to work confirming that DNS records are deleted.
@alebedev87 Addressed latest comments, I also made couple of clean ups: https://github.com/openshift/external-dns-operator/compare/e2330ab8695bfd3d3e0fd803bc95a547772e230a..cd5ab109630a647b08c711a96e5ba12e0e39a699
waitForDeletion
)KubeClient
in common, not really necessary to pass it around.GetPlatformType
had error
return type firstt.Logf
or t.Fatalf
when they could have been t.Log
or t.Fatal
@alebedev87 ready for another round. Fixed your review comments, but also added a make test-e2e-sharedvpc
alias for easy run of sharedvpc e2e tests.
Also, I renamed the directory name from e2e_awssharedvpc
to e2e_sharedvpc
. The package name was already e2e_sharedvpc
and I think it's probably better to be platform generic in hopes maybe it will be supported on other platforms.
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alebedev87
The full list of commands accepted by this bot can be found here.
The pull request process is described here
* 2023-10-12T22:10:23Z 3x kubelet: Failed to create pod sandbox: rpc error: code = DeadlineExceeded desc = context deadline exceeded
/test unit /test verify
test "verify" failed: pod pending for more than 30m0s: containers have not started in 32m26.844693716s: ci-scheduling-dns-wait, place-entrypoint, sidecar, test:
/test verify /test unit
cluster install /test e2e-azure-infoblox-operator
/lgtm
Applying the labels myself as:
/label docs-approved /label px-approved /label qe-approved
@gcs278: This pull request references NE-1324 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 story to target the "4.15.0" version, but no target version was set.
@gcs278: all tests passed!
Full PR test history. Your PR dashboard.
Add E2E tests for AssumeRole functionality added in https://github.com/openshift/external-dns-operator/pull/195/. It creates a ExternalDNS object with AssumeRole configured inside of a Shared VPC cluster. It then confirms that an example DNS record gets created in a targeted AWS account's hosted zone as well as it queries the DNS record inside the cluster to test end-to-end DNS record functionality.
This E2E test update is also dependent on https://github.com/openshift/release/pull/42894 which adds a new CI test job
e2e-aws-shared-vpc-phz-operator
to this repo. Without this, this new E2E test will be skipped.Dependent on https://github.com/openshift/external-dns-operator/pull/195/ and will need rebase when it merges.