Hide Forgot
Description of problem: The cert data in the configmap not update when signing CA secret recreated(service-serving-cert-signer-signing-key) Version-Release number of selected component (if applicable): $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-02-26-125216 True False 26h Cluster version is 4.0.0-0.nightly-2019-02-26-125216 How reproducible: always Steps to Reproduce: 1. create a configmap and annotate it with service.alpha.openshift.io/inject-cabundle=true 2. check the cert data in the configmap 3. delete secret service-serving-cert-signer-signing-key in openshift-service-cert-signer project, the service pod service-serving-cert-signer- will restarted automatically 4. waiting the pod ready, check the cert data in the configmap, not updated, the same as step 2 Actual results: The cert data in the configmap, not updated Expected results: The cert data in the configmap should be updated. Additional info: https://jira.coreos.com/browse/AUTH-109
Have checked alpha build, the issue still not fix. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.alpha-2019-03-12-005310 True False 4h20m Cluster version is 4.0.0-0.alpha-2019-03-12-005310
Could you please help check if it has been fixed?
The latest Accepted build 4.0.0-0.nightly-2019-04-05-165550 not include this fix.
Please check if the fix is in 4.0.0-0.nightly-2019-04-08-225815
Verified. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-04-10-182914 True False 171m Cluster version is 4.0.0-0.nightly-2019-04-10-182914
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758