Check the SSL certificates before generating the supportconfig

[cbosdo]

A lot of issues are due to SSL certificates errors. Generating the supportconfig only in the SSL certificates and their chain are valid would limit the number of those problems

[aaannz]

I am little confused. Is it supposed to be "generating the supportconfig only if SSL certificates are valid" or "generating the supportconfig with SSL certificate check in it"?

[cbosdo]

I was thinking about generating the supportconfig only if the certs are valid to push that kind of debugging as much as possible to the user. But maybe this is not a good idea.

[rjmateus]

I don't think we should block the support config generation. We want to make it as resilient as possible and survive as many scenarios as possible so we can get the data.
Another topic would be around having the health check tool available to customers (or a subset of it) to make an analysis on the customer side and give hints about possible issues and help them fixing it instead of hitting SUSE support.

[juliogonzalez]

I don't think we should block the support config generation. We want to make it as resilient as possible and survive as many scenarios as possible so we can get the data.

I agree to some extent. If the system is fundamentally broken, it's not the worst idea to tell the user and abort.

But if not, at the very least we need information at the supportconfig about the certificates being working or not and/or the certificates, so this can be then parsed later y the health check too.

Another topic would be around having the health check tool available to customers (or a subset of it) to make an analysis on the customer side and give hints about possible issues and help them fixing it instead of hitting SUSE support.

Keep in mind we are discussing SUSE internals here, but yes, why not. However we need to also do this for support.