Precreated Public Address shouldn’t be deleted by terraform destroy/apply

Bug #1784955 reported by Senthilnathan Murugappan
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
Fix Committed
High
Paweł Kopka

Bug Description

We precreate the Public Address in Azure to allow IPSec traffic from lab to Azure and these precreated resources shouldnt be deleted by terraform destroy/apply.

Sanju Abraham (asanju)
Changed in juniperopenstack:
importance: Undecided → High
status: New → In Progress
Revision history for this message
Paweł Kopka (pkopka) wrote :

You mean, create public ip, before You used multicloud?
Currently we only support import public ip only for AWS, for GCP and Azure we are planning add this in nearest future.

Revision history for this message
Paweł Kopka (pkopka) wrote :

There is bug in terraform, we have workaround for for AWS.
We are planning to make same workaround for other public cloud.
https://github.com/hashicorp/terraform/issues/13018

no longer affects: juniperopenstack/r5.0
tags: added: beta-blocker
Revision history for this message
Sanju Abraham (asanju) wrote :

The support for importing public_ip, already created and reserved by tenants is possible after the pull request - https://github.com/Juniper/contrail-multi-cloud/pull/195.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.