+++ This bug was initially created as a clone of Bug #1962205 +++

Description of problem:

When executing the pre-upgrade validation group the validation overcloud-service-status is triggered. However, the execution of this group takes currently place right before starting with the Overcloud Upgrade FFU 13 -> 16.1 : https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/framework_for_upgrades_13_to_16.1/index#proc-validating-the-pre-upgrade-requirements_initial-steps

At this point, the Undercloud is upgraded to OSP16.1 while the Overcloud is still in OSP13, therefore the validation fails with:

{
    "hosts": {
        "undercloud": {
            "_ansible_no_log": false,
            "action": "fail",
            "changed": false,
            "failed": true,
            "msg": "At least one of the assertion failed.\n            nova-consoleauth should be removed on controller-2.redhat.local\n                      nova-consoleauth should be removed on controller-1.redhat.local\n                      nova-consoleauth should be removed on controller-0.redhat.local\n                  \n"              
        }
    },
    "name": "Asserted failure",
    "status": "FAILED"
}

But this situation is correct, as the nodes haven't been upgraded yet. For this reason, the pre-upgrade group should be removed from the validation: 

https://github.com/openstack/tripleo-validations/blob/stable/train/playbooks/overcloud-service-status.yaml#L11-L16

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: