Describe the bug: So, whatever, I manually deployed an Ubuntu server and used the [instruction](https://maas.io/docs/how-to-provision-machines#p-9078-add-deployed-machines:~:text=SYSTEM_ID%20install_kvm%3DTrue-,Add%20deployed%20machines,-MAAS%20can%20add) adding it to the MAAS. However, the "networks", "storage" and "PCI devices" tabs remain empty.
Steps to reproduce: Manually deploy an Ubuntu server instance and add it to the MAAS as a deployed machine.
Expected behavior (what should have happened?): The maas-run-script should perform a commission and collect those specs and report to MAAS.
Actual behavior (what actually happened?): It only creates a machine entry on MAAS.
MAAS version and installation type (deb, snap): 3.5.3 stable
MAAS setup (HA, single node, multiple regions/racks): doesn't matter
Host OS distro and version: ubuntu 22.04
Additional context:
Describe the bug: /maas.io/ docs/how- to-provision- machines# p-9078- add-deployed- machines: ~:text= SYSTEM_ ID%20install_ kvm%3DTrue- ,Add%20deployed %20machines, -MAAS%20can% 20add) adding it to the MAAS. However, the "networks", "storage" and "PCI devices" tabs remain empty.
So, whatever, I manually deployed an Ubuntu server and used the [instruction](https:/
Steps to reproduce:
Manually deploy an Ubuntu server instance and add it to the MAAS as a deployed machine.
Expected behavior (what should have happened?):
The maas-run-script should perform a commission and collect those specs and report to MAAS.
Actual behavior (what actually happened?):
It only creates a machine entry on MAAS.
MAAS version and installation type (deb, snap):
3.5.3 stable
MAAS setup (HA, single node, multiple regions/racks):
doesn't matter
Host OS distro and version:
ubuntu 22.04
Additional context: