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

Use "default-ingress-cert", not "router-ca" #3380

Conversation

Miciah
Copy link
Contributor

@Miciah Miciah commented Mar 30, 2020

As of OpenShift 4.4.0, the router-ca configmap is deprecated, and the default-ingress-cert configmap should be used instead.

  • cmd/openshift-install/create.go (addRouterCAToClusterCA): Replace use of router-ca with use of default-ingress-cert. Return not-found errors to caller.
  • docs/user/troubleshooting.md: Update references to "router-ca".

Thanks @stlaz for finding the issue! openshift/cluster-ingress-operator#377 (comment)

@ironcladlou
Copy link
Contributor

@Miciah If this needs backported to 4.4, might as well open the 4.5 bug and associate it with this PR.

@Miciah
Copy link
Contributor Author

Miciah commented Mar 30, 2020

@Miciah If this needs backported to 4.4, might as well open the 4.5 bug and associate it with this PR.

We can either backport to 4.4 or keep the deprecated router-ca configmap around for an extra release. We have a similar situation with the console (see openshift/cluster-ingress-operator#377 and openshift/console-operator#403).

@abhinavdahiya
Copy link
Contributor

qq: moving not found from move ahead to failure for the router cert, is there a case where the default ca cert will not be created?

@abhinavdahiya
Copy link
Contributor

qq: moving not found from move ahead to failure for the router cert, is there a case where the default ca cert will not be created?

ping @Miciah

@Miciah
Copy link
Contributor Author

Miciah commented Mar 31, 2020

qq: moving not found from move ahead to failure for the router cert, is there a case where the default ca cert will not be created?

The ingress operator always creates default-ingress-cert as of 4.4.0. If the configmap does not exist, then ingress is broken.

@abhinavdahiya
Copy link
Contributor

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya

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 Mar 31, 2020
As of OpenShift 4.4.0, the "router-ca" configmap is deprecated, and the
"default-ingress-cert" configmap should be used instead.

* cmd/openshift-install/create.go (addRouterCAToClusterCA): Replace use of
"router-ca" with use of "default-ingress-cert".  Return not-found errors to
caller.
* docs/user/troubleshooting.md: Update references to "router-ca".
@Miciah
Copy link
Contributor Author

Miciah commented Apr 1, 2020

Rebased.

@Miciah Miciah force-pushed the use-default-ingress-cert-not-router-ca branch from 76ff340 to 81a0904 Compare April 1, 2020 23:40
@abhinavdahiya
Copy link
Contributor

/lgtm

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

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit e023f63 into openshift:master Apr 2, 2020
@openshift-ci-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/prow/e2e-libvirt 81a0904 link /test e2e-libvirt
ci/prow/e2e-openstack 81a0904 link /test e2e-openstack
ci/prow/e2e-ovirt 81a0904 link /test e2e-ovirt
ci/prow/e2e-aws-scaleup-rhel7 81a0904 link /test e2e-aws-scaleup-rhel7

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.

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.

None yet

6 participants