test/extended: skip "Services should be rejected when no endpoints exist" for OVNKubernetes #24147
Conversation
…ist" for OVNKubernetes Not expected to work yet. Only recently was re-enabled for SDN too, so clearly it's not a huge issue that the test fails (at least for now).
openshift-ci-robot
added
the
size/XS
|
/test e2e-aws-ovn-kubernetes |
|
/lgtm |
|
/test e2e-gcp |
|
/test e2e-aws-ovn-kubernetes |
|
/approve
…On Wed, Nov 13, 2019, 5:59 PM Dan Williams ***@***.***> wrote:
/test e2e-aws-ovn-kubernetes
level=info msg="Waiting up to 30m0s for the cluster at https://api.ci-op-3yht71y7-469c7.origin-ci-int-aws.dev.rhcloud.com:6443 to initialize..."
level=info msg="Cluster operator console Progressing is True with SyncLoopRefreshProgressingInProgress: SyncLoopRefreshProgressing: Working toward version 0.0.1-2019-11-13-213600"
level=info msg="Cluster operator console Available is False with DeploymentAvailableFailedUpdate: DeploymentAvailable: 1 replicas ready at version 0.0.1-2019-11-13-213600"
level=info msg="Cluster operator insights Disabled is False with : "
level=info msg="Cluster operator insights UploadDegraded is True with UploadFailed: Unable to report: unable to build request to connect to Insights server"
level=fatal msg="failed to initialize the cluster: Cluster operator console has not yet reported success"
2019/11/13 22:44:10 Container setup in pod e2e-aws-ovn-kubernetes failed, exit code 1, reason Error
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24147?email_source=notifications&email_token=ACMRVPNS3DCYZDJAERVMDNDQTSBGBA5CNFSM4JNBSXGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED763TQ#issuecomment-553643470>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACMRVPJZJMITRFKEYAWCQJTQTSBGBANCNFSM4JNBSXGA>
.
|
openshift-ci-robot
added
the
approved
|
/lgtm
…On Wed, Nov 13, 2019, 5:59 PM Dan Williams ***@***.***> wrote:
/test e2e-aws-ovn-kubernetes
level=info msg="Waiting up to 30m0s for the cluster at https://api.ci-op-3yht71y7-469c7.origin-ci-int-aws.dev.rhcloud.com:6443 to initialize..."
level=info msg="Cluster operator console Progressing is True with SyncLoopRefreshProgressingInProgress: SyncLoopRefreshProgressing: Working toward version 0.0.1-2019-11-13-213600"
level=info msg="Cluster operator console Available is False with DeploymentAvailableFailedUpdate: DeploymentAvailable: 1 replicas ready at version 0.0.1-2019-11-13-213600"
level=info msg="Cluster operator insights Disabled is False with : "
level=info msg="Cluster operator insights UploadDegraded is True with UploadFailed: Unable to report: unable to build request to connect to Insights server"
level=fatal msg="failed to initialize the cluster: Cluster operator console has not yet reported success"
2019/11/13 22:44:10 Container setup in pod e2e-aws-ovn-kubernetes failed, exit code 1, reason Error
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24147?email_source=notifications&email_token=ACMRVPNS3DCYZDJAERVMDNDQTSBGBA5CNFSM4JNBSXGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED763TQ#issuecomment-553643470>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACMRVPJZJMITRFKEYAWCQJTQTSBGBANCNFSM4JNBSXGA>
.
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, dcbw, knobunc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test e2e-cmd |
|
/test e2e-gcp-builds |
1 similar comment
|
/test e2e-gcp-builds |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
Ooh, the test failure might be https://bugzilla.redhat.com/show_bug.cgi?id=1765280, so we have a chance to debug. Let's see. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/override ci/prow/e2e-gcp-builds |
|
@knobunc: Overrode contexts on behalf of knobunc: ci/prow/e2e-gcp-builds 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 kubernetes/test-infra repository. |
|
/refresh |
|
What's the eta on a fix? |
|
I for instance would call this a blocker for GA. |
@smarterclayton next week. Note that this test was skipped for openshift-sdn until 2 days ago in #23370 because it was broken there as well for a long time. It appears that the 1.16 rebase may have fixed the test due to fixes in 1.16's kube-proxy. Point being, it's been broken for long enough in SDN that I can't see how it being broken for a week or so more in OVN is a problem :) |
|
If I had known it was broken I would have blocked 4.1 :) This is a foundational reliability / sanity thing for services on the cluster (the difference between blackhole and reject is massive in debugability). |
|
Please make sure there is a release blocker bug open for this. |
@smarterclayton https://bugzilla.redhat.com/show_bug.cgi?id=1772655 |
Not expected to work yet. Only recently was re-enabled for SDN too, so clearly
it's not a huge issue that the test fails (at least for now).
@danwinship