OVH Terraform Provider Version

Oct 13, 2025 by talynt.org 147 views

Describe the Bug

The healthMonitor attribute in the ovh_cloud_project_loadbalancer resource is documented as optional. However, when creating a load balancer with a listener and a pool, the healthMonitor.delay attribute is required, even if healthMonitor is set to null. This results in an error when attempting to create the load balancer.

Terraform Version

Terraform v1.11.2
on linux_amd64
+ provider registry.terraform.io/ovh/ovh v2.0.0
+ provider registry.terraform.io/terraform-provider-openstack/openstack v3.0.0

OVH Terraform Provider Version

Initializing the backend...
Initializing provider plugins...
- Reusing previous version of terraform-provider-openstack/openstack from the dependency lock file
- Reusing previous version of ovh/ovh from the dependency lock file
- Using previously-installed terraform-provider-openstack/openstack v3.0.0
- Using previously-installed ovh/ovh v2.0.0

Affected Resource(s)

ovh_cloud_project_loadbalancer

Terraform Configuration Files

listeners = [
    {
      port     = 443
      protocol = "https"

      description         = "terminated https, Terraform managed"
      name                = "tf_https"
      secret_id           = "<redacted>"
      timeout_client_data = 20000
      timeout_member_data = 20000
      tls_versions        = ["TLSv1.2", "TLSv1.3"]
      pool = {
        algorithm      = "roundRobin"
        health_monitor = null
        name           = "tf_http_pool"
        protocol       = "http"
        members = [
          {
            name          = "web"
            protocol_port = 80
          }
        ]
      }
    }
]

Expected Behavior

The terraform apply command should create a load balancer with a listener and a pool, without a health monitor, without any errors.

Actual Behavior

When running terraform apply, the following error is encountered:

ovh_cloud_project_loadbalancer.lb_v2: Creating...
╷
│ Error: Error calling Post /cloud/project/d0a27a2826254d28adb4006554f48f1a/region/GRA11/loadbalancing/loadbalancer
│ 
│   with ovh_cloud_project_loadbalancer.lb_v2,
│   on lb.tf line 27, in resource "ovh_cloud_project_loadbalancer" "lb_v2":
│   27: resource "ovh_cloud_project_loadbalancer" "lb_v2" {
│ 
│ OVHcloud API error (status code 400): Client::BadRequest: "[listeners.0.pool.healthMonitor.delay] Property cannot be null" (X-OVH-Query-Id:
│ EU.ext-1.67d2ff08.2380923.cc23fed534b91a814a9f18fb2433c028)

Steps to Reproduce

To reproduce this issue, follow these steps:

Set up a public cloud load balancer with a listener and a pool.
Do not set a health monitor in the pool.
Run terraform apply.

References

Workaround

As a workaround, you can set the healthMonitor.delay attribute to a valid value, even if healthMonitor is set to null. This will allow the load balancer to be created without errors.

listeners = [
    {
      port     = 443
      protocol = "https"

      description         = "terminated https, Terraform managed"
      name                = "tf_https"
      secret_id           = "<redacted>"
      timeout_client_data = 20000
      timeout_member_data = 20000
      tls_versions        = ["TLSv1.2", "TLSv1.3"]
      pool = {
        algorithm      = "roundRobin"
        health_monitor = null
        name           = "tf_http_pool"
        protocol       = "http"
        members = [
          {
            name          = "web"
            protocol_port = 80
          }
        ]
        healthMonitor = {
          delay = 10
        }
      }
    }
]

However, this workaround is not ideal, as it requires setting a valid value for healthMonitor.delay, even if healthMonitor is not being used.

Conclusion

Q: What is the issue with the healthMonitor.delay attribute in the OVH Terraform Provider?

A: The healthMonitor.delay attribute is required, even if healthMonitor is set to null, resulting in an error when creating a load balancer with a listener and a pool.

Q: Why is this an issue?

A: This is an issue because it prevents users from creating a load balancer with a listener and a pool without a health monitor, even if they want to do so.

Q: What are the steps to reproduce this issue?

A: To reproduce this issue, follow these steps:

Set up a public cloud load balancer with a listener and a pool.
Do not set a health monitor in the pool.
Run terraform apply.

Q: What is the expected behavior?

A: The expected behavior is that the terraform apply command should create a load balancer with a listener and a pool, without a health monitor, without any errors.

Q: What is the actual behavior?

A: The actual behavior is that the terraform apply command results in an error, with the message "Client::BadRequest: '[listeners.0.pool.healthMonitor.delay] Property cannot be null'".

Q: Is there a workaround for this issue?

A: Yes, there is a workaround for this issue. You can set the healthMonitor.delay attribute to a valid value, even if healthMonitor is set to null. However, this is not an ideal solution, as it requires setting a valid value for healthMonitor.delay, even if healthMonitor is not being used.

Q: What is the impact of this issue?

A: The impact of this issue is that users are unable to create a load balancer with a listener and a pool without a health monitor, which may be a requirement for certain use cases.

Q: How can this issue be resolved?

A: This issue can be resolved by updating the OVH Terraform Provider to allow the healthMonitor.delay attribute to be optional, even if healthMonitor is set to null.

Q: Is this issue specific to the OVH Terraform Provider?

A: No, this issue is not specific to the OVH Terraform Provider. It is a general issue with the Terraform Provider, and can occur with any provider that has a similar configuration.

Q: How can users report this issue?

A: Users can report this issue by submitting a bug report to the Terraform Provider team, along with a detailed description of the issue and any relevant configuration files.

Q: What is the estimated time to resolve this issue?

A: The estimated time to resolve this issue is unknown, as it depends on the complexity of the issue and the availability of the Terraform Provider team.

Q: Will this issue be fixed in the next version of the Terraform Provider?

A: It is possible that this issue will be fixed in the next version of the Terraform Provider, but it is not guaranteed. The Terraform Provider team will need to review and prioritize the issue before making any changes.

Q: Can users work around this issue by using a different Terraform Provider?

A: Yes, users can work around this issue by using a different Terraform Provider that does not have this configuration issue. However, this may require significant changes to the user's configuration files and may not be a viable solution for all users.