Comment 7 for bug 1980731

db snippet for machine 14

- _id: cb1ff1db-2ec1-48b1-8421-f4b9ccc6ce40:14
  addresses: [] <- should not be empty, but have 2 entries
  agent-started-at: "2022-07-04T15:11:31.957Z"
  clean: false
  containertype: ""
  hostname: ip-10-x-x-112
  jobs:
  - 1
  life: 0
  machineaddresses: <- missing the public ip entry
  - addresstype: ipv4
    networkscope: local-cloud
    origin: machine
    value: 10.x.x.112
  - addresstype: ipv4
    networkscope: local-machine
    origin: machine
    value: 127.0.0.1
  - addresstype: ipv6
    networkscope: local-machine
    origin: machine
    value: ::1
  machineid: "14"
  model-uuid: cb1ff1db-2ec1-48b1-8421-f4b9ccc6ce40
  nonce: machine-0:a37fc6a6-99bb-446f-8efa-0846daad5306
  preferredprivateaddress:
    addresstype: ipv4
    networkscope: local-cloud
    origin: provider
    spaceid: "0"
    value: 10.x.x.112
  preferredpublicaddress:
    addresstype: ipv4
    networkscope: local-cloud
    origin: machine <- expected "provider"
    spaceid: <- missing data
    value: 10.x.x.112 <- expected the public ip here
  principals:
  - content-cache/0
  series: bionic
  supportedcontainers:
  - lxd
  supportedcontainersknown: true
  tools:
    sha256: ""
    size: 0
    url: ""
    version: 2.9.32-ubuntu-amd64
  txn-queue: []
  txn-revno: 132

The above explains the juju status output, but not how we got there.