Bug 2014710: Fix for Azure dns privateZone degrade e2e test#662
Conversation
|
/test e2e-aws |
|
Thanks! We might as well check that the full test suite passes on Azure: |
|
Tests look good. Thanks! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lmzuccarelli, Miciah The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
In retrospect, we should have a BZ linked to this PR so that we can backport the fix to the release-4.9, where the test was first introduced. |
|
/retitle Bug 2014710: Fix for Azure dns privateZone degrade e2e test |
|
@lmzuccarelli: All pull requests linked via external trackers have merged: Bugzilla bug 2014710 has been moved to the MODIFIED state. DetailsIn 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 kubernetes/test-infra repository. |
|
/cherry-pick release-4.9 |
|
@Miciah: new pull request created: #664 DetailsIn 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 kubernetes/test-infra repository. |
This fix ensures the e2e test for dns privateZone works for Azure , GCP and AWS.
The fix is really simple. Azure uses a "/" naming notation for privateZones, the original "error-" prefix did not cause a failure, the updated prefix injected is simply "/error" which causes the operator status to degrade to TRUE
The change was verified on Azure & AWS via cluster-bot
For Azure
For AWS