I recently have seen at a customer a SSL profile which was referencing a certificate signing request and key + CA rather than the real certificate.
While this seems strange, my question is if is there any impact in the functionality in having a CSR + root CA rather than the real one?
I have the same situation, showing me "RSA Certificate, Key & Certificate Signing Request" for a specific certificate. I have no other Content like that on our LB but only "RSA Certificate, Key " . What I've done was just to renew a certificate which was going to expire, sent it to be signed by our PKI and import the new certificate. I don't understand why the CSR is still there and how can I get rid of it. Is this happening because something wrong on my side when I generated the CSR or by my colleague who signed the certificate on PKI?
It is likely that your colleague who generated the csr did it from the LB directly then uploaded the signed csr (the certificate - which include the cert+key) with the same name to the system identifies it as a "bundle".
You can simply remove it by clicking on the "bundle", go to the CSR tab and delete from there.