Certificate CN is not getting updated within the cert-migration playbook

[Marcelo de Castro Loebens]

Brief Description
-----------------
The playbook that migrates certificates to cert-manager support a field provided by the user (subject_CN) to define the CommonName (CN) of the cert . However, the OAM IP is being used instead of the value provided by the user.

Severity
--------
Minor.

Steps to Reproduce
------------------
Follow the steps in https://docs.starlingx.io/security/kubernetes/migrate-platform-certificates-to-use-cert-manager-c0b1727e4e5d.html. Provide the 'subject_CN' field in the inventory file.

Expected Behavior
------------------
After the execution of the playbook, the CommonName (CN) field for the certificate should be updated.

Actual Behavior
----------------
The CN is created as the OAM IP value.

Reproducibility
---------------
100%.

System Configuration
--------------------
Simplex.

Branch/Pull Time/Commit
-----------------------
Master.

Last Pass
---------
NA.

Timestamp/Logs
--------------
NA

Test Activity
-------------
Developer Testing

Workaround
----------
Not really needed, shoudn't cause more significant problems.

If required, the command:

kubectl patch certificate <CERTIFICATE> -n <NAMESPACE> --type 'json' -p='[{"op": "add", "path": "/spec/commonName", "value": "<SUBJECT_CN>"}]'

can edit the certificate after the playbook is executed.

[Ghada Khalil (gkhalil)]

Review: https://review.opendev.org/c/starlingx/ansible-playbooks/+/874249

[Ghada Khalil (gkhalil)]

Marking as Fix Released as the above review merged on Feb 27. Unclear why the LP was not automatically updated.