Floating IP creation unexpectedly moved from custom workflow to install workflow

[laurentganne]

Using alien4cloud-yorc-provider 2.2.0-SM9, uploading this topology template in Alien4Cloud catalog:
topology_delegate.zip
where:

• the install workflow is creating a compute instance,
• a custom workflow is creating another compute instance attached to a network.

Attempting to deploy an application from this template on an OpenStack location configured with on-demand resources yorc.nodes.openstack.Compute and yorc.nodes.openstack.PublicNetwork,
has an unexpected effect on workflows :

the delegate operation creating a floating IP address is moved from the custom workflow to the install workflow.