Comment 2 for bug 1990724

Not sure whart you mean,
I created 3 seperate spaces now (via juju add-space -m controller)

$ juju spaces -m controller
Name Space ID Subnets
alpha 0
oam-space 1 10.33.27.0/24
storage-access-space 2 10.33.28.0/24
fan-network-space 3 252.0.0.0/8

Yet, still presume machines 0 does not have oam-space. But it has, see the below

$ juju controller-config juju-ha-space=oam-space
ERROR invalid config "juju-ha-space"="oam-space": machines with no addresses in this space: 0

$ juju show-machine -m controller 0
model: controller
machines:
  "0":
    juju-status:
      current: started
      since: 01 Dec 2023 00:44:10Z
      version: 3.1.6
    hostname: k8sddev-juju-0
    dns-name: k8sddev-juju-0
    ip-addresses:
    - k8sddev-juju-0
    - 10.33.27.71
    - 252.16.0.1
    instance-id: 'manual:'
    machine-status:
      current: running
      message: Manually provisioned machine
      since: 01 Dec 2023 00:46:39Z
    modification-status:
      current: idle
      since: 30 Nov 2023 23:53:44Z
    base:
      name: ubuntu
      channel: "22.04"
    network-interfaces:
      ens160:
        ip-addresses:
        - 10.33.27.71
        mac-address: 00:50:56:01:41:94
        gateway: 10.33.27.254
        space: oam-space
        is-up: true
      fan-252:
        ip-addresses:
        - 252.16.0.1
        mac-address: 5e:30:82:9f:ef:be
        space: fan-network-space
        is-up: true
    constraints: arch=amd64 mem=3584M
    hardware: arch=amd64 cores=8 mem=15988M
    controller-member-status: has-vote

$ juju version
3.1.6-genericlinux-amd64

So adding extra spaces does not help