kubernetes/kops · error

error creating server %v: %v

Error message

error creating server %v: %v

What it means

Server creation failed and the error was not the recoverable port-in-use case (or no port ID was given), so the raw Nova create error is surfaced. The message includes the create options and the API error; root cause is in the wrapped error.

Source

Thrown at upup/pkg/fi/cloudup/openstack/instance.go:123

		if err != nil {
			if IsPortInUse(err) && portID != "" {
				port, err := c.GetPort(portID)
				if err != nil {
					return false, fmt.Errorf("error finding port %s: %v", portID, err)
				}
				// port is attached to deleted instance, we need reset the status of the DeviceID
				// this is bug in OpenStack APIs
				if port.DeviceID != "" && port.DeviceOwner == "" {
					klog.Warningf("Port %s is attached to Device that does not exist anymore, reseting the status of DeviceID", portID)
					_, err := c.UpdatePort(portID, ports.UpdateOpts{
						DeviceID: new(""),
					})
					if err != nil {
						return false, fmt.Errorf("error updating port %s deviceid: %v", portID, err)
					}
				}
			}
			return false, fmt.Errorf("error creating server %v: %v", opt, err)
		}
		server = v

		err = waitForStatusActive(c, server.ID, nil)
		if err != nil {
			return true, err
		}

		return true, nil
	})
	if err != nil {
		return server, err
	} else if done {
		return server, nil
	} else {
		return server, wait.ErrWaitTimeout
	}
}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Read the wrapped Nova error to identify quota, image, flavor, network or scheduler failures
2. Fix the reported resource issue and retry the operation
3. Check openstack server create manually with the same options to reproduce

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/openstack/instance.go:123 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/6816cb430f0735be. Report an issue: GitHub.