Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Floating IP creation unexpectedly moved from custom workflow to install workflow #11

Open
laurentganne opened this issue Oct 21, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@laurentganne
Copy link
Contributor

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.

@laurentganne laurentganne added the bug Something isn't working label Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant