The current 3.9 centos paas repos are at v3.9.0-alpha.4. However, I cannot deploy origin 3.9.0-alpha.4 using ansible (openshift-ansible latest release-3.9 branch) because I run into this issue:
TASK [openshift_master : Wait for API to become available] ********************* "* NSS error -8054 (SEC_ERROR_REUSED_ISSUER_AND_SERIAL)", "* You are attempting to import a cert with the same issuer/serial as an existing cert, but that is not the same cert.",
This was fixed by 95e262011438642410959914c3db9868c57739ff
But that's at commit v3.9.0-alpha.4-426-g95e2620114
I realize the PaaS SIG is trying to stay in sync with official origin tags/releases, but I think that origin 3.9.0-alpha.4 simply isn't deployable using ansible.
Alternately, is there a workaround?
Except for the master branch (currently at origin-3.10), our rpm building automation isn't designed for individual commits. We are setup to only pull on git tags, or the latest master commit.
Please talk to upstream about doing an alpha5, or rc0, or whatever they feel is next.
Troy
On Wed, Mar 7, 2018 at 2:33 PM, Rich Megginson rmeggins@redhat.com wrote:
The current 3.9 centos paas repos are at v3.9.0-alpha.4. However, I cannot deploy origin 3.9.0-alpha.4 using ansible (openshift-ansible latest release-3.9 branch) because I run into this issue:
TASK [openshift_master : Wait for API to become available]
"* NSS error -8054 (SEC_ERROR_REUSED_ISSUER_AND_SERIAL)", "* You are attempting to import a cert with the same issuer/serialas an existing cert, but that is not the same cert.",
This was fixed by 95e262011438642410959914c3db9868c57739ff
But that's at commit v3.9.0-alpha.4-426-g95e2620114
I realize the PaaS SIG is trying to stay in sync with official origin tags/releases, but I think that origin 3.9.0-alpha.4 simply isn't deployable using ansible.
Alternately, is there a workaround?
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Rich Megginson -
Troy Dawson