ARs in OpenNebula for any VNET are numbered starting from 0. Setting the IP parameter in the reservation template requires also AR_ID to be provided. In the current implementation setting reservation_ar_id=0 is just the same as implying reservation_ar_id=null, thus the reservation_first_ip parameter cannot be with the first AR in a VNET. This is not reflected in unit tests as the AR used there is never the first one (AR_ID=0).
Terraform and Provider version
Terraform v1.6.5
on linux_amd64
+ provider registry.terraform.io/opennebula/opennebula v1.3.1
Description
ARs in OpenNebula for any VNET are numbered starting from 0. Setting the
IP
parameter in the reservation template requires alsoAR_ID
to be provided. In the current implementation settingreservation_ar_id=0
is just the same as implyingreservation_ar_id=null
, thus thereservation_first_ip
parameter cannot be with the first AR in a VNET. This is not reflected in unit tests as the AR used there is never the first one (AR_ID=0).Terraform and Provider version
Affected resources and data sources
opennebula_virtual_network
Terraform configuration
Expected behavior
Reservation is created without errors.
Actual behavior
OpenNebula returns error:
The
AR_ID
is actually missing from the reservation template.Steps to Reproduce
It's just enough the take any VNET and try to create reservation with both
reservation_first_ip="A.B.C.D"
andreservation_ar_id=0
.Debug output
Not sure if this is required, the issue is really easy to reproduce.
Panic output
N/A
Important factoids
N/A
References
https://docs.opennebula.io/stable/integration_and_development/system_interfaces/api.html#one-vn-reserve