Skip to content

Conversation

@abhinavdahiya
Copy link
Contributor

@abhinavdahiya abhinavdahiya commented Jun 7, 2019

With installer PR 1, the installer will automatically gather the logs from bootstrap in case of bootstrap failure.
It uses the ~/.ssh directlory to load the private SSH keys for authentication, when not specifically invoked using gather bootstrap --key <>

/cc @smarterclayton
^^-- because we was concerned with changes to templates wrt 4.2 and 4.1.x
/cc @wking

@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 7, 2019
…ogs on bootstrap failure

With installer PR [1], the installer will automatically gather the logs from bootstrap in case of bootstrap failure.
It uses the `~/.ssh` directlory to load the private SSH keys for authentication, when not specifically invoked using `gather bootstrap --key <>`

[1]: openshift/installer#1822
@abhinavdahiya
Copy link
Contributor Author

ping @smarterclayton @wking

@wking
Copy link
Member

wking commented Jun 12, 2019

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@openshift-merge-robot openshift-merge-robot merged commit 82f176f into openshift:master Jun 12, 2019
@openshift-ci-robot
Copy link
Contributor

@abhinavdahiya: Updated the following 6 configmaps:

  • 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-launch-installer-console configmap in namespace ci using the following files:
    • key cluster-launch-installer-console.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-console.yaml
  • prow-job-cluster-launch-installer-console configmap in namespace ci-stg using the following files:
    • key cluster-launch-installer-console.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-console.yaml
  • 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
Details

In response to this:

With installer PR 1, the installer will automatically gather the logs from bootstrap in case of bootstrap failure.
It uses the ~/.ssh directlory to load the private SSH keys for authentication, when not specifically invoked using gather bootstrap --key <>

/cc @smarterclayton
^^-- because we was concerned with changes to templates wrt 4.2 and 4.1.x
/cc @wking

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.

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