Skip to content

Run upstream e2e test with net-istio#1014

Merged
openshift-merge-robot merged 2 commits intoopenshift-knative:mainfrom
nak3:add-net-istio-test
Jul 13, 2021
Merged

Run upstream e2e test with net-istio#1014
openshift-merge-robot merged 2 commits intoopenshift-knative:mainfrom
nak3:add-net-istio-test

Conversation

@nak3
Copy link
Contributor

@nak3 nak3 commented Jun 10, 2021

/cc

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 10, 2021

@nak3: GitHub didn't allow me to request PR reviews from the following users: nak3.

Note that only openshift-knative members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc

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.

@nak3
Copy link
Contributor Author

nak3 commented Jun 10, 2021

/retest
istio-operator did not start.

@nak3
Copy link
Contributor Author

nak3 commented Jun 15, 2021

/test 4.7-upstream-e2e-aws-ocp-47

@nak3
Copy link
Contributor Author

nak3 commented Jun 15, 2021

domainmapping test hits this issue knative/serving@26c93b9

    stream.go:*54: E 07:41:55.348 domain-mapping-744987c5fb-zl6xs [knative.dev.serving.pkg.reconciler.domainmapping.Reconciler] [serving-tests/domain-mapping-bgboydtt.apps.ci-op-mcifrq*q-fbf8c.origin-ci-int-aws.dev.rhcloud.com] Returned an error err=failed to create Ingress: Ingress.networking.internal.knative.dev "domain-mapping-bgboydtt.apps.ciefb90bedf33484b06ac7d3ba94496ca7" is invalid: metadata.labels: Invalid value: "domain-mapping-bgboydtt.apps.ci-op-mcifrq*q-fbf8c.origin-ci-int-aws.dev.rhcloud.com": must be no more than 63 characters

@nak3
Copy link
Contributor Author

nak3 commented Jun 16, 2021

TestCustomOpenShiftRoute fails because it has fixed kourier and knative-serving-ingress values.

@nak3
Copy link
Contributor Author

nak3 commented Jun 17, 2021

grpc_test.go must be removed. It hangs and got timeout.

@nak3
Copy link
Contributor Author

nak3 commented Jun 23, 2021

The original CRtest/v1alpha1/resources/operator.knative.dev_v1alpha1_knativeserving_cr.yaml sets to prometheus so we need to override.

@nak3
Copy link
Contributor Author

nak3 commented Jun 23, 2021

The test passed. Now trying to remove GODEBUG="x509ignoreCN=0".

@nak3
Copy link
Contributor Author

nak3 commented Jun 25, 2021

/retest

New failure with TestActivatorHAGraceful . I think it is flake.

@nak3
Copy link
Contributor Author

nak3 commented Jun 25, 2021

TestActivatorHAGraceful failed again due to Failed to delete pod activator-85d6cdc89-dr8bg: pods "activator-85d6cdc89-dr8bg" not found.

It will be improved by knative/serving@9054d8b 🤔

@nak3
Copy link
Contributor Author

nak3 commented Jun 27, 2021

/retest

TestActivatorHAGraceful works on my local even with openshift/release-v0.22.0 branch.

@nak3
Copy link
Contributor Author

nak3 commented Jun 28, 2021

@nak3
Copy link
Contributor Author

nak3 commented Jun 28, 2021

/retest

Test passed once. One more time.

@nak3 nak3 changed the title wip - Run e2e test with net-istio wip - Run upstream e2e test with net-istio Jun 29, 2021
@nak3
Copy link
Contributor Author

nak3 commented Jun 30, 2021

Serving 0.22 didn't have h2c issue but 0.23 got the issue log:

    http2_test.go:67: The endpoint http://hello-http2-with-por-fwbdxyth-serving-tests.apps.ci-op-17k619p9-fbf8c.origin-ci-int-aws.dev.rhcloud.com for Route hello-http2-with-por-fwbdxyth didn't serve the expected text "Hello, New World! How about donuts and coffee?": response: status: 426, body: , headers: map[Content-Length:[0] Date:[Wed, 30 Jun 2021 04:54:46 GMT] Server:[istio-envoy] X-Envoy-Upstream-Service-Time:[2] Zipkin_trace_id:[d47245bee119f7711504b28250809ca0]] did not pass checks: status = 426 426 Upgrade Required, want one of: [200]

I experienced it in openshift/knative-serving#751 but still not sure why only serving 0.23 happens this problem.

@nak3
Copy link
Contributor Author

nak3 commented Jun 30, 2021

/retest

TestRouteCreation failed. (It is the first time to fail it.)

    route_test.go:158: CheckSLO() error SLI for "TestRouteCreation" = 0.915663, wanted >= 1.000000

log

@nak3
Copy link
Contributor Author

nak3 commented Jul 1, 2021

Only two HA tests failed.
TestDomainMappingHA ... patch command overrides domainmapping's HA so needs to fix script.
TestControllerHA ... it needs openshift/knative-serving#836

@nak3
Copy link
Contributor Author

nak3 commented Jul 1, 2021

Umm... TestControllerHA still failed. openshift/knative-serving#836 might not be applied.

@nak3
Copy link
Contributor Author

nak3 commented Jul 1, 2021

/retest

infra

@nak3
Copy link
Contributor Author

nak3 commented Jul 2, 2021

/cc @markusthoemmes @mgencur @maschmid

This is ready for review. Could you please take a look?

@skonto
Copy link
Collaborator

skonto commented Jul 2, 2021

@nak3 should we run downstream tests with this setup as well? Is this coming next? I would like to test metrics (ideally tracing too).

@nak3
Copy link
Contributor Author

nak3 commented Jul 2, 2021

Yes, I am going to add the mesh test for downstream with follow up PR. (Because it messes up script and hard to review I guess
😅 )

Makefile Outdated
Comment on lines +82 to +84
# This is to run with FULL_MESH to verify the PR. Remove this and use "test-upstream-e2e-mesh".
FULL_MESH=true TEST_KNATIVE_KAFKA=false TEST_KNATIVE_E2E=true TEST_KNATIVE_UPGRADE=false ./test/upstream-e2e-tests.sh
# INSTALL_KAFKA=true TEST_KNATIVE_KAFKA=true TEST_KNATIVE_E2E=true TEST_KNATIVE_UPGRADE=false ./test/upstream-e2e-tests.sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this go away before a merge?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, correct. This is a temporary as pre-submit PR always run test-upstream-e2e-no-upgrade. I will revert it and trigger job against test-upstream-e2e-mesh.

Comment on lines +60 to +64
# TODO: SRVKS-211: Can not run grpc and http2 tests.
rm ./test/e2e/grpc_test.go
rm ./test/e2e/http2_test.go
# Remove h2c test
sed -ie '46,50d' ./test/conformance/runtime/protocol_test.go
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This means that we'll have to document gRPC/HTTP2 not working for mesh for now, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I will open the JIRA.

Comment on lines +189 to +191
config:
observability:
metrics.backend-destination: "none"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this required? Don't we do that "automatically"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Umm... we have the default as "prometheus"


so I think we need to override it with none. Sorry if I misunderstood the meaning of "automatically".

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ahhhh we explicitly set it. Nevermind then, I was thinking in our Golang code, where we default to none currently, if istio is enabled.

Comment on lines +187 to +188
- name: domain-mapping
replicas: 2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need this? Don't we also need that in "usual" setups?

Copy link
Contributor Author

@nak3 nak3 Jul 12, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we have the replicas: 2 in "usual" setups.


But the spec.deployments is an array. So when we patch the annotation (inject and rewriteAppHTTPProbers) to spec.deployments for activator and autoscaler, domain-mapping's replicas: 2 is dropped 😓

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha, makes sense!

Comment on lines +55 to +58
# Use x509ignoreCN=0.
# This should not be necesssary if we could ceate certs with SAN. However, openssl command in the CI
# seems old version and so it does not have "-addext" option to add SAN.
export GODEBUG="x509ignoreCN=0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried but the base image of registry.ci.openshift.org/openshift/release:golang-1.15 is CentOS 7 and the latest openssl command was still 1.10.

$ docker run build-image rpm -qf `which openssl`
openssl-1.0.2k-21.el7_9.x86_64

Copy link
Contributor

@markusthoemmes markusthoemmes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

/hold

Please revert the "old" make target and then we're good to go here :)

@openshift-ci openshift-ci bot removed the lgtm label Jul 12, 2021
@nak3 nak3 changed the title wip - Run upstream e2e test with net-istio Run upstream e2e test with net-istio Jul 12, 2021
Copy link
Contributor

@markusthoemmes markusthoemmes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm label Jul 12, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 12, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: markusthoemmes, nak3

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

The pull request process is described here

Details 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

@nak3
Copy link
Contributor Author

nak3 commented Jul 13, 2021

/hold cancel

@openshift-merge-robot openshift-merge-robot merged commit 3eab11c into openshift-knative:main Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants