Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci-operator/templates/openshift: Use IMAGE_TESTS for teardown gzip #2911

Merged

Conversation

wking
Copy link
Member

@wking wking commented Feb 20, 2019

The teardown container requires oc (for retrieving cluster logs), gzip (for compressing those logs), and openshift-install (for destroying the cluster). We were already copying in oc from another container; with this commit we copy in the statically-linked openshift-install too. That leaves gzip, which we will be built in to IMAGE_TESTS as "a command needed in the CI-test context". Using IMAGE_TESTS for teardown means we no longer need to copy oc into the shared volume for the teardown container (although we may need to copy it in for other containers, e.g. the src template's test container).

I've also dropped an unnecessary /bin/ prefix from the create cluster invocations, which we'd been dragging around from the pre-shell days of 3f2f01c (#1677).

This will allow us to walk back openshift/installer#1262, but we'll still need gzip in the tests image.

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 20, 2019
@openshift-ci-robot openshift-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 20, 2019
@wking
Copy link
Member Author

wking commented Feb 20, 2019

We can lift the hold if/when openshift/origin#22094 lands adding gzip to the tests image.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 23, 2019
@wking
Copy link
Member Author

wking commented Feb 26, 2019

We can lift the hold if/when openshift/origin#22094...

Landed. CC @sdodson

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 26, 2019
The teardown container requires oc (for retrieving cluster logs), gzip
(for compressing those logs), and openshift-install (for destroying
the cluster).  We were already copying in oc from another container;
with this commit we copy in the statically-linked openshift-install
too.  That leaves gzip, which we will be built in to IMAGE_TESTS as "a
command needed in the CI-test context".  Using IMAGE_TESTS for
teardown means we no longer need to copy oc into the shared volume for
the teardown container (although we may need to copy it in for other
containers, e.g. the src template's test container).

I've also dropped an unnecessary /bin/ prefix from the 'create
cluster' invocations, which we'd been dragging around from the
pre-shell days of 3f2f01c
(ci-operator/config/openshift/installer/master: Move to
openshift-install, 2018-09-26, openshift#1677).
@wking wking force-pushed the copy-installer-to-teardown branch from 545f4ce to 00d7b3f Compare February 26, 2019 10:12
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 26, 2019
@wking
Copy link
Member Author

wking commented Feb 26, 2019

Rebased around #2884 with 545f4ce -> 00d7b3f.

@sdodson
Copy link
Member

sdodson commented Feb 26, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 26, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sdodson, wking

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 26, 2019
@openshift-merge-robot openshift-merge-robot merged commit 7920792 into openshift:master Feb 26, 2019
@openshift-ci-robot
Copy link
Contributor

@wking: Updated the following 6 configmaps:

  • prow-job-cluster-launch-installer-e2e configmap in namespace ci using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci-stg using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci-stg using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-scaleup-e2e-40 configmap in namespace ci using the following files:
    • key cluster-scaleup-e2e-40.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-scaleup-e2e-40.yaml
  • prow-job-cluster-scaleup-e2e-40 configmap in namespace ci-stg using the following files:
    • key cluster-scaleup-e2e-40.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-scaleup-e2e-40.yaml

In response to this:

The teardown container requires oc (for retrieving cluster logs), gzip (for compressing those logs), and openshift-install (for destroying the cluster). We were already copying in oc from another container; with this commit we copy in the statically-linked openshift-install too. That leaves gzip, which we will be built in to IMAGE_TESTS as "a command needed in the CI-test context". Using IMAGE_TESTS for teardown means we no longer need to copy oc into the shared volume for the teardown container (although we may need to copy it in for other containers, e.g. the src template's test container).

I've also dropped an unnecessary /bin/ prefix from the create cluster invocations, which we'd been dragging around from the pre-shell days of 3f2f01c (#1677).

This will allow us to walk back openshift/installer#1262, but we'll still need gzip in the tests image.

/hold

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.

@wking wking deleted the copy-installer-to-teardown branch February 27, 2019 16:52
wking added a commit to wking/openshift-installer that referenced this pull request Mar 4, 2019
… gzip"

This reverts commit 71d199c, openshift#1262

Since openshift/release@00d7b3f31 (ci-operator/templates/openshift:
Use IMAGE_TESTS for teardown gzip, 2019-02-19,
openshift/release#2911), the release repository no longer users the
installer image for the teardown containers.
wking added a commit to wking/openshift-release that referenced this pull request Feb 7, 2020
…nstaller to shared volume

I started doing this in 00d7b3f (ci-operator/templates/openshift:
Use IMAGE_TESTS for teardown gzip, 2019-02-19, openshift#2911), but the
teardown container doesn't need an installer injected if it running an
installer image.

  $ git grep -A1 'name: teardown' ci-operator/templates/openshift/installer | grep image:
  ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml-      image: ${IMAGE_TESTS}
  ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml-      image: ${IMAGE_TESTS}
  ci-operator/templates/openshift/installer/cluster-launch-installer-libvirt-e2e.yaml-      image: ${IMAGE_LIBVIRT_INSTALLER}
  ci-operator/templates/openshift/installer/cluster-launch-installer-metal-e2e.yaml-      image: ${IMAGE_UPI_INSTALLER}
  ci-operator/templates/openshift/installer/cluster-launch-installer-openstack-e2e.yaml-      image: ${IMAGE_OPENSTACK_INSTALLER}
  ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml-      image: "${IMAGE_LIBVIRT_INSTALLER}"
  ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml-      image: ${IMAGE_TESTS}
  ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml-      image: ${IMAGE_UPI_INSTALLER}
  ci-operator/templates/openshift/installer/cluster-launch-installer-upi-src.yaml-      image: ${IMAGE_UPI_INSTALLER}

So this commit removes the openshift-installer copy from the templates
that use installer images, and leaves it for templates that use test
images.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants