Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-9064

[DOCS] Carriage Return / Newline in Custom Ingress Certificate

XMLWordPrintable

    • Moderate
    • None
    • 2
    • OSDOCS Sprint 241, OSDOCS Sprint 242, OSDOCS Sprint 243, OSDOCS Sprint 244, OSDOCS Sprint 245, OSDOCS Sprint 246, OSDOCS Sprint 247, OSDOCS Sprint 248, OSDOCS Sprint 249, OSDOCS Sprint 250, OSDOCS Sprint 251
    • 11
    • Unspecified
    • N/A
    • Release Note Not Required

      Document URL: https://docs.openshift.com/container-platform/4.8/security/certificates/replacing-default-ingress-certificate.html

      Section Number and Name:
      1. Replacing the default ingress certificate
      1a. Prerequisites

      Describe the issue:
      The documentation does not mention that the .key and .pem files will need a newline at the end, or else you'll face the issue described in https://access.redhat.com/solutions/5220571

      Suggestions for improvement:
      Mention that the .pem and .key should have one newline after the "----END CERTIFICATE----" line.

      Additional information:
      When lacking the newline ending, the authentication clusterOperator will have an issue like "failed to load SNI cert and key: tls: failed to find PEM block", preventing logging into the cluster.

              rhn-support-jbrigman James Brigman
              rhn-support-jorbell Jordan Bell
              Latha Sreenivasa Murthy Latha Sreenivasa Murthy
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 week
                  1w