kubernetes/kops · error
failed to extract dns recordsets pages: %s
Error message
failed to extract dns recordsets pages: %s
What it means
listDNSRecordsets wraps the gophercloud ExtractRecordsets error after a successful page fetch, i.e. the Designate response pages could not be parsed into RecordSet objects. It fires on malformed API responses and is retried with backoff.
Source
Thrown at upup/pkg/fi/cloudup/openstack/dns.go:95
return deleteDNSRecordset(c, zoneID, rrsetID)
}
// ListDNSRecordsets will list DNS recordsets
func (c *openstackCloud) ListDNSRecordsets(zoneID string, opt recordsets.ListOptsBuilder) ([]recordsets.RecordSet, error) {
return listDNSRecordsets(c, zoneID, opt)
}
func listDNSRecordsets(c OpenstackCloud, zoneID string, opt recordsets.ListOptsBuilder) ([]recordsets.RecordSet, error) {
var rrs []recordsets.RecordSet
done, err := vfs.RetryWithBackoff(readBackoff, func() (bool, error) {
allPages, err := recordsets.ListByZone(c.DNSClient(), zoneID, opt).AllPages(context.TODO())
if err != nil {
return false, fmt.Errorf("failed to list dns recordsets: %s", err)
}
r, err := recordsets.ExtractRecordSets(allPages)
if err != nil {
return false, fmt.Errorf("failed to extract dns recordsets pages: %s", err)
}
rrs = r
return true, nil
})
if err != nil {
return rrs, err
} else if done {
return rrs, nil
} else {
return rrs, wait.ErrWaitTimeout
}
}
View on GitHub (pinned to 4c8573c808)
Solutions
- Retry; the operation already runs inside RetryWithBackoff
- Check gophercloud/Designate version compatibility
- Inspect the wrapped error for response-format anomalies
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at upup/pkg/fi/cloudup/openstack/dns.go:95 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/73890cf329f3ce82.
Report an issue: GitHub.