yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1980673@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

Posting here because the issue seems to be related to Designate quotas.
Looks like Neutron is only a victim here.

OpenStack fails when creating a floating IP address with a DNS name and
zone. Designate logs do not show anything interesting but neutron server
reports "designateclient.exceptions.OverQuota: over_quota" when creating
floating IP" and the CLI command outputs "Request Failed: internal
server error while processing your request." and exists with non-zero
value.

The floating IP is created but the new DNS name cannot be resolved. The
floating IP cannot be removed until the CLI command to remove it is run
again.

This fails when creating a floating IP within 10.18.75.x, but it works
for addresses within 10.18.86.x. The second range has been working just
fine to this day, and creating an IP address within this range works as
expected.

The logs suggest that the project hits some quota for the reverse zone.
However I fail to check how much resource under quota the project uses.
Since the project has just been created (beside a few similar attempts
that fails), I expect such usage to be near 0.

I cannot find any helpful direction on internet for a corner to look at
with. I attached the logs I collected for neutron server and all
designate services, as well as the command I run and their output.

This is OpenStack Xena running on Rocky 8.5-based nodes.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
Neutron hits "designateclient.exceptions.OverQuota: over_quota" when creating floating IP
https://bugs.launchpad.net/bugs/1980673
You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron.