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

Update openshift ca redeploy to use correct node client-ca #10034

Merged
merged 1 commit into from
Sep 13, 2018

Conversation

mtnbikenc
Copy link
Member

Corrected redeploy-openshift-ca.yml playbook to reference the correct
node client certificate file, node/client-ca.crt.

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1585978

@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 12, 2018
Corrected redeploy-openshift-ca.yml playbook to reference the correct
node client certificate file, node/client-ca.crt.

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1585978
Copy link
Contributor

@michaelgugino michaelgugino left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 12, 2018
@mtnbikenc
Copy link
Member Author

/cherrypick release-3.10

@openshift-cherrypick-robot

@mtnbikenc: once the present PR merges, I will cherry-pick it on top of release-3.10 in a new PR and assign it to you.

In response to this:

/cherrypick release-3.10

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.

@mtnbikenc
Copy link
Member Author

/cherrypick release-3.11

@openshift-cherrypick-robot

@mtnbikenc: once the present PR merges, I will cherry-pick it on top of release-3.11 in a new PR and assign it to you.

In response to this:

/cherrypick release-3.11

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.

@sdodson
Copy link
Member

sdodson commented Sep 12, 2018

/priority p0
/lgtm

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: michaelgugino, mtnbikenc, sdodson

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:
  • OWNERS [michaelgugino,mtnbikenc,sdodson]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-cherrypick-robot

@mtnbikenc: new pull request created: #10041

In response to this:

/cherrypick release-3.11

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.

@openshift-cherrypick-robot

@mtnbikenc: #10034 failed to apply on top of branch "release-3.10":

error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	playbooks/openshift-master/private/redeploy-openshift-ca.yml
Falling back to patching base and 3-way merge...
Auto-merging playbooks/openshift-master/private/redeploy-openshift-ca.yml
CONFLICT (content): Merge conflict in playbooks/openshift-master/private/redeploy-openshift-ca.yml
Patch failed at 0001 Update openshift ca redeploy to use correct node client-ca

In response to this:

/cherrypick release-3.10

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. priority/P0 size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants