Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

stack activation digest fails to be retrieved due to certificate issues - ingress cert should be trusted by default #728

Closed
bconey opened this issue May 21, 2020 · 2 comments
Assignees

Comments

@bconey
Copy link

bconey commented May 21, 2020

The stack activation digest is not being retrieved from stack images in the internal OCP registry due to error x509: certificate signed by unknown authority.

.....
status:
  summary: '[ 0.3.29: active ]'
  versions:
  - images:
    - digest:
        message: 'Unable to retrieve stack activation digest for image: default-route-openshift-image-registry.apps.bfcjicpa.cp.fyre.ibm.com/kabanero/java-spring-boot2:0.3.29.
          Associated stack: java-spring-boot2 0.3.29. Error: Get https://default-route-openshift-image-registry.apps.bfcjicpa.cp.fyre.ibm.com/v2/:
          x509: certificate signed by unknown authority'
      id: Spring Boot®
      image: default-route-openshift-image-registry.apps.bfcjicpa.cp.fyre.ibm.com/kabanero/java-spring-boot2
.....

After some discussion, the thought is that the Ingress certificate should be trusted by default and this error should not be seen for this setup using the internal registry.

@bconey
Copy link
Author

bconey commented May 29, 2020

Verified

@bconey bconey closed this as completed May 29, 2020
@tkulik
Copy link

tkulik commented Jun 4, 2020

I still see the problem with ICPA 4.2.0-rc.2 build.

root@stark-client:/cp4apps420_stack_curation# oc get stacks
NAME                         AGE    SUMMARY
java-openliberty             6d3h   [ 0.2.12: error ]
java-spring-boot2            6d3h   [ 0.3.29: error ]
java-websphere-traditional   2d2h   [ 0.3.1: error ]
nodejs                       6d3h   [ 0.3.6: error ]
nodejs-express               6d3h   [ 0.4.8: error ]
quarkus                      6d3h   [ 0.3.6: error ]

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants