bradh352 opened a new issue, #227:
URL: https://github.com/apache/cloudstack-terraform-provider/issues/227

   I'm attempting to perform a port forward from an IP address in a VPC to an 
instance.
   
   When applying a configuration, I get:
   ```
   2025-09-21T17:08:21.172Z [ERROR] vertex "cloudstack_port_forward.bastion" 
error: Provider produced inconsistent result after apply
   cloudstack_network_acl_rule.su: Modifications complete after 18s 
[id=ccd32c6a-0e56-4725-ae77-101aa2a796da]
   ╷
   │ Error: Provider produced inconsistent result after apply
   │
   │ When applying changes to cloudstack_port_forward.bastion, provider 
"provider[\"registry.terraform.io/cloudstack/cloudstack\"]" produced an 
unexpected new value: Root object was
   │ present, but now absent.
   │
   │ This is a bug in the provider, which should be reported in the provider's 
own issue tracker.
   ╵
   2025-09-21T17:08:28.251Z [INFO]  provider: plugin process exited: 
plugin=.terraform/providers/registry.terraform.io/cloudstack/cloudstack/0.5.0/linux_amd64/terraform-provider-cloudstack_v0.5.0
 id=1934598
   ```
   
   The configuration is indeed applied and working, but obviously its not 
saving state and therefore on subsequent runs it also errors out since the rule 
already exists.
   
   The basic configuration I'm applying is:
   ```
   resource "cloudstack_ipaddress" "bastion" {
     vpc_id = cloudstack_vpc.infra_vpc.id
     zone   = var.cloudstack_zone
   }
   
   resource "cloudstack_port_forward" "bastion" {
     ip_address_id = cloudstack_ipaddress.bastion.id
   
     forward {
       protocol           = "tcp"
       private_port       = 22
       public_port        = 5022
       virtual_machine_id = cloudstack_instance.bastion.id
     }
   }
   ```
   
   The full configuration I'm using if needed is hosted here: 
https://github.com/bradh352/terraform-config
   
   This is just a test lab I'm setting up, nothing sensitive.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to