No more IP addresses available on network error during migrate-ovn-db action, and other data migration problems...
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charms Deployment Guide |
Fix Released
|
High
|
Frode Nordahl | ||
OpenStack Neutron API OVN Plugin Charm |
New
|
Undecided
|
Unassigned |
Bug Description
Following instructions at https:/
The migrate-ovn-db action fails with an error "No more IP addresses available on network e50ff198-
$ juju run-action --wait neutron-
unit-neutron-
UnitId: neutron-
id: "39990"
message: Execution failed, please investigate output.
results:
Stderr: |+
migrate-
/
result = self._query(query)
Stdout: "migrate-ovn-db: OUTPUT FROM SYNC ON STDOUT:\n2020-11-25 11:06:17.760
413761 INFO neutron.
db sync\e[00m\n
[snip]
11:06:56.892 413761 WARNING neutron.
[
but not in OVN DB, network_
11:06:57.026 413761 WARNING neutron.
- - - - -] No revision row found for e50ff198-
networks) when bumping the revision number. Creating one.\e[
11:06:57.227 413761 INFO neutron.
- - - - -] Successfully bumped revision number for resource e50ff198-
(type: networks) to 10\e[00m\
[
No more IP addresses available on network e50ff198-
11:06:57.565 413761 ERROR neutron_
last)
\
138, in _ipam_allocate_
\ ip_address, subnet_id = ipam_allocator.
11:06:57.565 413761 ERROR neutron_
line 240, in allocate\
\ raise ipam_exc.
413761 ERROR neutron_
No more IP addresses available.
\n2020-11-25 11:06:57.565 413761 ERROR neutron_
of the above exception, another exception occurred:
413761 ERROR neutron_
Changed in charm-deployment-guide: | |
status: | In Progress → Fix Committed |
Changed in charm-deployment-guide: | |
status: | Fix Committed → Fix Released |
Thank you for the bug.
Could you attach the complete output from the action, the charm log and the neutron-server log?
I wonder if the sync util is attempting to allocate a port for the OVN metadata service and that the subnet is indeed depleted of free IP addresses.
Would you happen to have any surplus ports that could be removed to free up an IP address in the network/subnet in question? Or would it be possible to extend one of the full subnets?
You should be able to interact with the Neutron API reverting the change in step 8 and 9. If you have followed the guide that should be safe to do at this point in time.
If you are successful in freeing an address or extending the subnet you could repeat step 8, 9 and 10 again.