Error on CNCF K8s conformance

[Cristopher Lemus]

Brief Description
-----------------
Error found during CNCF K8s conformance certification. Error found during a check "[sig-api-machinery] Aggregator ", however, it might be related to self-signed certificates. "x509: certificate signed by unknown authority" found on the logs.

Severity
--------
TBD

Steps to Reproduce
------------------
On a fresh install of starlingx, with platform-integ-apps and stx-openstack deployed, we followed up these instructions: https://github.com/cncf/k8s-conformance/blob/master/instructions.md

Once the tool sonobuoy completed, it reported the failure.

Expected Behavior
------------------
System should pass CNCF K8s conformance.

Actual Behavior
----------------
Error found during CNCF K8s conformance.

Reproducibility
---------------
Seen once. A fresh install will be deployed and sonobuoy will be re-executed. Once completed, I'll update this section.

System Configuration
--------------------
Duplex.

Branch/Pull Time/Commit
-----------------------
Ran sonobuoy against STX 3.0.0.

Last Pass
---------
New test.

Timestamp/Logs
--------------
Some lines found that indicate an issue with self signed certificate: http://paste.openstack.org/show/787938/

The full output of sonobuoy is attached.

Test Activity
-------------
CNCF K8s conformance certification.

[Ghada Khalil (gkhalil)]

There was a recent fix for stx.3.0 related to certificates being different on both controllers which resulted in conformance testing failing. See the LP below for more details:
https://bugs.launchpad.net/starlingx/+bug/1855915
The fix was merged in r/stx.3.0 on 2019-12-11

As far as I know, once the above issue was addressed, the conformance test suite passed.

@Christopher, can you confirm the build date for the stx.3.0 you are using for your test?

[Cristopher Lemus (cjlemusc)]

Hi Ghada,

Thanks for the detailed information. I verified and confirmed that I was not using the actual RC 3.0, instead, this execution was from an older build (2019-12-08).

I re-ran sonobuoy against the RC, this issue did not happened. I'm verifying results and I'll update the distribution list with some information.

I'll mark this bug as invalid.

[Ghada Khalil (gkhalil)]

Thanks Christopher. I will mark this LP as a duplicate of 1855915 which addressed the issue you saw.