Skip to content
This repository has been archived by the owner on Jun 24, 2020. It is now read-only.

Run the upgrade and downgrade tests in the upgrade prow job #300

Merged
merged 5 commits into from
Mar 3, 2020

Conversation

houshengbo
Copy link

@houshengbo houshengbo commented Feb 17, 2020

Fixes #310

Proposed Changes

  • This PR adds the execution of upgrade and downgrade tests into the operator prow job.
  • This PR refactors the e2e-common script, to accommodate the changes in upgrade tests.
  • This PR adds the deployment verification for Knative in operator's upgrade tests.

Release Note


@houshengbo houshengbo changed the title Add the upgrade tests in Serving WIP: Add the upgrade tests in Serving Feb 17, 2020
Copy link
Contributor

@knative-prow-robot knative-prow-robot left a comment

Choose a reason for hiding this comment

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

@houshengbo: 0 warnings.

In response to this:

Fixes #

Proposed Changes

Release Note


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.

@googlebot googlebot added the cla: yes Author(s) signed a CLA. label Feb 17, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: houshengbo

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@houshengbo houshengbo force-pushed the move-upgrade-tests branch 12 times, most recently from d222648 to 1141562 Compare February 18, 2020 02:21
@houshengbo houshengbo changed the title WIP: Add the upgrade tests in Serving Run the upgrade tests in the upgrade prow job Feb 26, 2020
@houshengbo houshengbo changed the title Run the upgrade tests in the upgrade prow job Run the upgrade and downgrade tests in the upgrade prow job Feb 26, 2020
@houshengbo houshengbo force-pushed the move-upgrade-tests branch 3 times, most recently from 2ad80e7 to 28ad711 Compare February 26, 2020 23:02
Vincent Hou added 4 commits February 27, 2020 09:38
We change the test namespace, because all the tests in serving repository
are running under the namespace knative-serving. We will call the upgrade
and downgrade tests directly in serving. We need to make sure all the tests
are running under the same namespace.
* We do not need to delete the operator CR, becuase we will verify the
services in serving.
* We do not need to create the opertor CR, because we will install a
previous version of the operator and create CR before reaching this
test.
* We need to verify the status of all the deployments, making sure
they match the expected deployments in terms of number and names,
and reach the ready status.
readonly TEST_NAMESPACE="operator-tests"
readonly TEST_NAMESPACE="knative-serving"

OPERATOR_DIR=$(dirname $0)/..
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
OPERATOR_DIR=$(dirname $0)/..
OPERATOR_DIR=$(cd $(dirname "$0")/.. && pwd)

OPERATOR_DIR=$(dirname $0)/.. resolves to ./...
Changing it with OPERATOR_DIR=$(cd $(dirname "$0")/.. && pwd) results in OPERATOR_DIR being e.g. /home/ali/go/src/knative.dev/

@aliok
Copy link
Member

aliok commented Mar 2, 2020

@houshengbo any instructions to run this test locally? I couldn't on Minikube and on OpenShift

@houshengbo
Copy link
Author

@aliok this is good question, but it seems to me that running the tests against GKE is the ONLY way to verify the tests.

@aliok
Copy link
Member

aliok commented Mar 3, 2020

but it seems to me that running the tests against GKE is the ONLY way to verify the tests.

then it lgtm as things pass on GKE. I created #317 so that I don't forget it and hopefully make things working later.

/lgtm

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Run the upgrade and downgrade tests in serving repo
5 participants