kubernetes/kops · error

found subnet without properties

Error message

found subnet without properties

What it means

Malformed-API-object guard in the Azure subnet reconciler: the matched subnet has no Properties block in the API response, so its address space/provisioning state cannot be read. kOps refuses to adopt an object it cannot fully describe.

Source

Thrown at upup/pkg/fi/cloudup/azuretasks/subnet.go:92

		}
	}

	var found *network.Subnet
	for _, v := range l {
		if *v.Name == *s.Name {
			found = v
			break
		}
	}
	if found == nil {
		return nil, nil
	}

	if found.ID == nil {
		return nil, fmt.Errorf("found subnet without ID")
	}
	if found.Properties == nil {
		return nil, fmt.Errorf("found subnet without properties")
	}
	if found.Properties.ProvisioningState != nil && *found.Properties.ProvisioningState == network.ProvisioningStateFailed {
		klog.Warningf("found subnet %q in failed provisioning state", *s.Name)
		return nil, nil
	}

	s.ID = found.ID

	fs := &Subnet{
		Name:      s.Name,
		Lifecycle: s.Lifecycle,
		Shared:    s.Shared,
		ResourceGroup: &ResourceGroup{
			Name: s.ResourceGroup.Name,
		},
		VirtualNetwork: &VirtualNetwork{
			Name: s.VirtualNetwork.Name,
		},

View on GitHub (pinned to 4c8573c808)

Solutions

  1. Retry in case of a transient partial API response
  2. Check the subnet state in the Azure portal
  3. Recreate the subnet if it appears corrupted
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/azuretasks/subnet.go:92 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/f98da452faae5777. Report an issue: GitHub.