There are some notes in the bug below, but for anyone looking at the list this was due to a mismatch between the x509 front-proxy-ca certificates/keys on the two controller nodes.  It was fixed by https://bugs.launchpad.net/starlingx/+bug/1855915 Chris On 12/27/2019 2:40 PM, Lemus Contreras, Cristopher J wrote:

Hello All,

I created a launchpad to track an error found during the CNCF K8s conformance procedure: https://bugs.launchpad.net/starlingx/+bug/1857716

Conformance was executed using sonobuoy tool, instructions here: https://github.com/cncf/k8s-conformance/blob/master/instructions.md

This is the summary:

Ran 276 of 4897 Specs in 9316.930 seconds

FAIL! -- 275 Passed | 1 Failed | 0 Pending | 4621 Skipped

--- FAIL: TestE2E (9316.96s)

FAIL

It looks like there’s an issue with the self-signed certificate that might have caused the failures and skips.

E1226 13:31:14.402186       1 authentication.go:63] Unable to authenticate the request due to an error: [x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "front-proxy-ca"), x509: certificate signed by unknown authority]

Some additional details can be found on launchpad, including the full tar.gz file created by sonobuoy. Hopefully somebody can take a look at it.

Regards,

Cristopher

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss