Hi,

I have a problem while deploying StarlingX 2.0, and I found the management subnet-pool was not enough for context. Here is the log.

[sysadmin@controller-1 ~(keystone_admin)]$ system host-update 12 personality=worker hostname=compute-7

Remote error: AddressPoolExhausted Address pool management has no available addresses

[u'Traceback (most recent call last):\n', u'  File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py", line 438, in _process_data\n    **args)\n', u'  File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py", line 172, in dispatch\n    result = getattr(proxyobj, method)(ctxt, **kwargs)\n', u'  File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 1643, in configure_ihost\n    self._configure_worker_host(context, host)\n', u'  File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 1505, in _configure_worker_host\n    self._allocate_addresses_for_host(context, host)\n', u'  File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 1100, in _allocate_addresses_for_host\n    address_name).address\n', u'  File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 1055, in _allocate_pool_address\n    interface_id, pool_uuid, address_name, dbapi=self.dbapi\n', u'  File "/usr/lib64/python2.7/site-packages/sysinv/api/controllers/v1/address_pool.py", line 416, in assign_address\n    ip_address = cls.allocate_address(pool, dbapi)\n', u'  File "/usr/lib64/python2.7/site-packages/sysinv/api/controllers/v1/address_pool.py", line 399, in allocate_address\n    raise exception.AddressPoolExhausted(name=pool.name)\n', u'AddressPoolExhausted: Address pool management has no available addresses\n'].

And I have to extend the management address pool.

[sysadmin@controller-0 sow(keystone_admin)]$ system addrpool-show d6ed7b27-4037-42db-97c7-676256b1c883

+---------------------+--------------------------------------+

| Property            | Value                                |

+---------------------+--------------------------------------+

| uuid                | d6ed7b27-4037-42db-97c7-676256b1c883 |

| name                | management                           |

| network             | 192.168.204.0                        |

| prefix              | 28                                   |

| order               | random                               |

| ranges              | ['192.168.204.2-192.168.204.14']     |

| floating_address    | 192.168.204.2                        |

| controller0_address | 192.168.204.3                        |

| controller1_address | 192.168.204.4                        |

| gateway_address     | None                                 |

+---------------------+--------------------------------------+

I am trying to extend the ranges by ‘system addrpool-modify’, but it reminds the prefix can only be modified during bootstrap phase,

[sysadmin@controller-0 sow(keystone_admin)]$ system help addrpool-modify

usage: system addrpool-modify [--name <name>] [--ranges <ranges>]

                              [--order <sequential | random>]

                              [--prefix <prefix>]

                              <address_pool uuid>

Modify interface attributes.

Positional arguments:

  <address_pool uuid>   UUID of IP address pool entry

Optional arguments:

  --name <name>         Name of the Address Pool]

  --ranges <ranges>     The inclusive range of addresses to allocate

                        <startaddr1-endaddr1>[,<startaddr2-endaddr2>,...]

  --order <sequential | random>

                        The allocation order within the start/end range

  --prefix <prefix>     CIDR prefix, only modifiable during bootstrap phase.

Anybody can tell me how to make the controller node and the compute node into bootstrap phase or I should redeploy the whole context from start, thanks in advance.