kubernetes/kops · error
found virtual network without properties
Error message
found virtual network without properties
What it means
Malformed-API-object guard in the Azure VNet Find: the matched virtual network has no Properties block, so provisioning state and address space cannot be inspected. kOps fails rather than guessing the network configuration.
Source
Thrown at upup/pkg/fi/cloudup/azuretasks/virtualnetwork.go:75
if err != nil {
return nil, err
}
var found *network.VirtualNetwork
for _, v := range l {
if *v.Name == *n.Name {
found = v
break
}
}
if found == nil {
return nil, nil
}
if found.ID == nil {
return nil, fmt.Errorf("found virtual network without ID")
}
if found.Properties == nil {
return nil, fmt.Errorf("found virtual network without properties")
}
if found.Properties.ProvisioningState != nil && *found.Properties.ProvisioningState == network.ProvisioningStateFailed {
klog.Warningf("found virtual network %q in failed provisioning state", *n.Name)
return nil, nil
}
if found.Properties.AddressSpace == nil {
return nil, fmt.Errorf("found virtual network without address space")
}
addrPrefixes := found.Properties.AddressSpace.AddressPrefixes
if len(addrPrefixes) != 1 {
return nil, fmt.Errorf("expecting exactly 1 address prefix for %q, found %d: %+v", *n.Name, len(addrPrefixes), addrPrefixes)
}
return &VirtualNetwork{
Name: n.Name,
Lifecycle: n.Lifecycle,
Shared: n.Shared,
ResourceGroup: &ResourceGroup{View on GitHub (pinned to 4c8573c808)
Solutions
- Retry in case of a partial API response
- Verify the VNet's state in the Azure portal
- Recreate the VNet if corrupted
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at upup/pkg/fi/cloudup/azuretasks/virtualnetwork.go:75 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/2c59b351209dc687.
Report an issue: GitHub.