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/step-registry/ipi/install: Drop TF_LOG from 'create manifests' #8299

Conversation

wking
Copy link
Member

@wking wking commented Apr 13, 2020

No Terraform involved in creating manifests. Cleans up after d11bca7 (#8075). Also removes trailing whitespace from the YAML documentation.

Also backgrounds the create manifests call and immediately waits for it, so we can gracefully handle TERM as described in 4472ace (#2680).

…ests'

No Terraform involved in creating manifests.  Cleans up after
d11bca7 (create a hybrid cluster and run the e2e tests on it,
2020-04-01, openshift#8075).  Also removes trailing whitespace from the YAML
documentation.

Also backgrounds the 'create manifests' call and immediately waits for
it, so we can gracefully handle TERM as described in 4472ace
(ci-operator/templates/openshift/installer: Restore backgrounded
'create cluster', 2019-01-23, openshift#2680).
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 13, 2020
@openshift-ci-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/rehearse/cri-o/cri-o/release-1.13/e2e-aws 847cfbc link /test pj-rehearse
ci/prow/pj-rehearse 847cfbc link /test pj-rehearse

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.

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.

Copy link
Contributor

@staebler staebler left a comment

Choose a reason for hiding this comment

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

These changes look to good to me.

@@ -35,16 +35,15 @@ cp "${SHARED_DIR}/install-config.yaml" "${dir}/"
mkdir -p ~/.ssh
cp "${SSH_PRIV_KEY_PATH}" ~/.ssh/


TF_LOG=debug openshift-install --dir="${dir}" create manifests
openshift-install --dir="${dir}" create manifests &
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 a change that we should make in all of the places where openshift-install create manifests is called?

$ grep -rnE ./ci-operator/ -e "openshift-install (.* )?create manifests"
./ci-operator/templates/openshift/installer/cluster-launch-installer-ovirt-e2e.yaml:439:        TF_LOG=debug openshift-install --dir=/tmp/artifacts/installer create manifests --log-level=debug
./ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml:1136:          openshift-install --dir=/tmp/artifacts/installer create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml:1163:          openshift-install --dir=/tmp/artifacts/installer create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml:1221:            openshift-install --dir=/tmp/artifacts/installer create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml:1267:            openshift-install --dir=/tmp/artifacts/installer create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml:770:            openshift-install --dir=/tmp/artifacts/installer/ create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml:779:          openshift-install --dir=/tmp/artifacts/installer/ create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml:555:            openshift-install --dir=/tmp/artifacts/installer/ create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-metal-e2e.yaml:402:        openshift-install --dir=/tmp/artifacts/installer/ create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml:644:            openshift-install --dir=/tmp/artifacts/installer/ create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-openstack-e2e.yaml:385:        TF_LOG=debug openshift-install --dir=/tmp/artifacts/installer create manifests --log-level=debug
./ci-operator/templates/openshift/installer/cluster-launch-installer-upi-src.yaml:417:          openshift-install --dir=/tmp/artifacts/installer create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-upi-src.yaml:442:          openshift-install --dir=/tmp/artifacts/installer create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-upi-src.yaml:501:            openshift-install --dir=/tmp/artifacts/installer create manifests
./ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml:518:        mock-nss.sh openshift-install create manifests --dir=/tmp/artifacts/installer
./ci-operator/step-registry/ipi/install/install/ipi-install-install-commands.sh:39:TF_LOG=debug openshift-install --dir="${dir}" create manifests

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 20, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: staebler, 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-merge-robot openshift-merge-robot merged commit b47d355 into openshift:master Apr 20, 2020
@openshift-ci-robot
Copy link
Contributor

@wking: Updated the following 2 configmaps:

  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key ipi-install-install-commands.sh using file ci-operator/step-registry/ipi/install/install/ipi-install-install-commands.sh
    • key ipi-install-install-ref.yaml using file ci-operator/step-registry/ipi/install/install/ipi-install-install-ref.yaml
  • step-registry configmap in namespace ci at cluster api.ci using the following files:
    • key ipi-install-install-commands.sh using file ci-operator/step-registry/ipi/install/install/ipi-install-install-commands.sh
    • key ipi-install-install-ref.yaml using file ci-operator/step-registry/ipi/install/install/ipi-install-install-ref.yaml

In response to this:

No Terraform involved in creating manifests. Cleans up after d11bca7 (#8075). Also removes trailing whitespace from the YAML documentation.

Also backgrounds the create manifests call and immediately waits for it, so we can gracefully handle TERM as described in 4472ace (#2680).

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 drop-terraform-debug-from-create-manifests branch June 18, 2020 17:38
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants