This fix must be published for the 17.1.5 release, which is Feb 26.

We need to add a conditional step in case of the servers are "pre-provisioned" (non ironic ones) to add the ctlplane_virtual_ip manually in the virtual_ips.yaml before adopt the virtual_ips on step  5.1[1] in  step 6. 

Create a backup of the file /home/stack/overcloud-deploy/{{ overcloud_stack_name }}/tripleo-{{ overcloud_stack_name }}-virtual-ips.yaml and include the following lines at the end of the file:

[Begin of the lines]

• dns_name: overcloud

  ip_address: {{ctlplane_virtual_ip{}}}

  name: control_virtual_ip

  network: ctlplane

  subnet: ctlplane-subnet

[end of the lines](I had issue with the format so this might not be seen accurated, attached a file {attached_virtual_ips.yaml} to show an example)

Once the Virtual IP is added into the file, the operator should continue running the command on step 6, and continue with the process.

My example of this step:

" 5. If your environment has pre-provisioned nodes, create a backup of the file /home/stack/overcloud-deploy/{{ overcloud_stack_name }}/tripleo-{{ overcloud_stack_name }}-virtual-ips.yaml and include the following lines at the end of the file: 
<code block>"

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html-single/framework_for_upgrades_16.2_to_17.1/index#running-the-overcloud-upgrade-preparation_overcloud-adoption