Skip to content
This repository was archived by the owner on Sep 28, 2022. It is now read-only.

Conversation

@sallyom
Copy link
Contributor

@sallyom sallyom commented Feb 14, 2020

  • removed openshift-tests-kubernetes suite from extended-platform-tests
  • pulled in recent changes to origin
  • added origin/examples from master branch (some tests rely on examples)
  • update Dockerfile to add extended-platform-tests to tests image (depends on add tests-kubernetes image build outside of tests image release#7215 ) to create an image:
    registry.svc.ci.openshift.org/ocp/4.4:extended-platform-tests that includes the openshift-tests-kubernetes + extended-platform-tests binaries - and for transition time also include the openshift-tests binary (this image will be renamed to become the release:tests image and the openshift-tests binary will be removed)

need to merge in this order:

  1. bug 1797788: add openshift-tests as a future delegation binary origin#24450 Bug 1797788: add openshift-tests as a future delegation binary origin#24560
  2. add tests-kubernetes image build outside of tests image release#7215 release PR to build tests-kubernetes image
  3. this PR - will result in extended-platform-tests image w/ 3 binaries listed above
  4. add template to run extended-platform-tests image release#7190 adds a new template to test the new binaries from extended-platform-tests image built here.
  5. add extended-platform-tests binary to e2e template, run e2e-extended-platform in kcmo release#6789 test job to openshift/release in any component to run new template, to confirm all suites run.
  6. rename extended-platform-tests image to become the release:tests (remove the current tests image build from ci-operator/config/openshfit/origin/*.yaml and rename image built in ci-operator/config/openshift/openshift-tests/*yaml
  7. edit all ci-operator/openshfit/installer/* templates to run new binaries
  8. remove openshift-tests binary from the image built in this repo.

this is how i understand what needs to happen

/cc @deads2k

@openshift-ci-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Feb 14, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sallyom
To complete the pull request process, please assign bparees
You can assign the PR to them by writing /assign @bparees in a comment when ready.

The full list of commands accepted by this bot can be found 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

@sallyom sallyom force-pushed the remove-openshift-tests-kubernetes branch from 07a3ca4 to e65ed83 Compare February 15, 2020 00:59
sallyom and others added 25 commits February 15, 2020 18:36
This resource is new in 4.4 and is created by openshift-apiserver.
We noticed a 2x CPU regression in e2e runs, and these are unfortunately
the culprit.
It is expensive to perform 100 checks against 1k names on every
startup. Instead, move these to generated files that can be reviewed
out of bounds on change. Add them to generated-bindata for verification
and regen.
Also move skip logic into provider initialization, and buffer a
small amount of suite output. GCP tests are excluded from core
infra, they are not used.
Change to use centos:7 which is more consistent.
Test that both ends of the range are available. Verify point to
point connectivity across the whole cluster.
The --provider argument for openshift-tests accepts a string (the type)
which triggers discovery, or JSON, which previously meant "use exactly
these values". However, we have more tests which depend on logic from
implicit fields (multimaster, region, zone, and number of nodes) that
we don't want to have accidentally off. This was recently triggered
when refactoring the methods in that numNodes was lost in CI, causing
certain networking tests not to run.

This commit changes openshift-tests run/run-upgrade to attempt to fill
all fields of the config even when JSON is passed to --provider by
invoking the cloud config load method, then updating provider for
the subsequent exec'd test command so that it is accurate. The run-test
command does not perform discovery, which forces the suite runner to
be accurate.
The multi-node PV test creates a PV, starts a pod that writes data to a file on
the PV, then kills the pod and starts another with node anti-affinity to read
the data from the PV attached to a different node. This is problematic on
multi-AZ clusters: there may only be one node in a zone and for volumes that
can't be transferred among zones (AWS EBS, GCE PD, ...) the test would fail.
- Changes similar to openshift/origin@4a31327 as `--config` is deprecated and the replacement for the same is `--kubeconfig`
- https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_jenkins/1015/pull-ci-openshift-jenkins-master-e2e-aws-jenkins/756 is a failed build where we are getting the error.
```
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_jenkins/1015/pull-ci-openshift-jenkins-master-e2e-aws-jenkins/756
```
- Updating this would allow for the Jenkins tests to be done by using the --kubeconfig flag with oc instead of --config
@sallyom sallyom force-pushed the remove-openshift-tests-kubernetes branch 3 times, most recently from 886f836 to 842bc8b Compare February 16, 2020 21:26
@sallyom sallyom force-pushed the remove-openshift-tests-kubernetes branch 4 times, most recently from ec01345 to 218ad05 Compare February 17, 2020 17:17
@openshift-ci-robot openshift-ci-robot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Feb 17, 2020
@sallyom sallyom force-pushed the remove-openshift-tests-kubernetes branch 4 times, most recently from 4561dc7 to 90ce9c9 Compare February 18, 2020 18:06
@sallyom sallyom force-pushed the remove-openshift-tests-kubernetes branch from 90ce9c9 to 1cfa27b Compare February 18, 2020 18:13
@openshift-ci-robot
Copy link

The following users are mentioned in OWNERS file(s) but are not members of the openshift org.

Once all users have been added as members of the org, you can trigger verification by writing /verify-owners in a comment.

  • jboyd01
    • examples/service-catalog/OWNERS
  • jpeeler
    • examples/service-catalog/OWNERS

reviewers:
- bparees
- pmorie
- jboyd01
Copy link
Member

Choose a reason for hiding this comment

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

@sallyom I guess the jboyd01/jpeeler left.

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 copied this OWNERS from origin/examples. i'll check on it

@jianzhangbjz
Copy link
Member

/test images

1 similar comment
@jianzhangbjz
Copy link
Member

/test images

@openshift-ci-robot
Copy link

@sallyom: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/images 1cfa27b link /test images

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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. I understand the commands that are listed here.

@sallyom
Copy link
Contributor Author

sallyom commented Apr 3, 2020

openshift-tests-kubernetes is going in a different direction, closing

@sallyom sallyom closed this Apr 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.