Repository navigation
db/v1/instances: remove hardcoded 300GB upper limit for CreateOpts.Size #3733
Description
In openstack/db/v1/instances/requests.go, CreateOpts.ToInstanceCreateMap() rejects sizes above 300 GB.
This appears to be environment-specific (Trove/OpenStack deployment limits vary), not a universal API constraint.
Because of this client-side validation, valid requests for deployments with larger limits cannot be sent at all.
Proposal: validate only Size >= 1 in gophercloud and let the API enforce deployment-specific maximums.
Activity
winiciusallan commentedon May 6, 2026
This looks like a valid bug indeed.
The only validation that I've found is this
https://github.com/openstack/trove/blob/master/trove/instance/models.py#L123
which compares the passed volume size with the threshold configured by the operator via
CONF.max_accepted_volume_sizehttps://docs.openstack.org/trove/latest/reference/conf.html#DEFAULT.max_accepted_volume_size