kubernetes/kops · error

error creating volume %v: %v

Error message

error creating volume %v: %v

What it means

The Cinder volume create call failed after retry-with-backoff. The wrapped error carries the API reason; common causes are quota exhaustion, invalid size/type, or unavailable availability zone.

Source

Thrown at upup/pkg/fi/cloudup/openstack/volume.go:69

		return volumes, err
	} else if done {
		return volumes, nil
	} else {
		return volumes, wait.ErrWaitTimeout
	}
}

func (c *openstackCloud) CreateVolume(opt cinder.CreateOptsBuilder) (*cinder.Volume, error) {
	return createVolume(c, opt)
}

func createVolume(c OpenstackCloud, opt cinder.CreateOptsBuilder) (*cinder.Volume, error) {
	var volume *cinder.Volume

	done, err := vfs.RetryWithBackoff(writeBackoff, func() (bool, error) {
		v, err := cinder.Create(context.TODO(), c.BlockStorageClient(), opt, nil).Extract()
		if err != nil {
			return false, fmt.Errorf("error creating volume %v: %v", opt, err)
		}
		volume = v
		return true, nil
	})
	if err != nil {
		return volume, err
	} else if done {
		return volume, nil
	} else {
		return volume, wait.ErrWaitTimeout
	}
}

func (c *openstackCloud) AttachVolume(serverID string, opts volumeattach.CreateOpts) (attachment *volumeattach.VolumeAttachment, err error) {
	return attachVolume(c, serverID, opts)
}

func attachVolume(c OpenstackCloud, serverID string, opts volumeattach.CreateOpts) (attachment *volumeattach.VolumeAttachment, err error) {

View on GitHub (pinned to 4c8573c808)

Solutions

1. Inspect the wrapped error for the rejected option
2. Check volume quotas and the volume type/availability zone
3. Fix the configuration and retry

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/openstack/volume.go:69 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of kubernetes/kops@4c8573c808 (2026-09-05). Data as JSON: /api/errors/f27eaf8714f9f3e2. Report an issue: GitHub.