"Add deployed machines" feature does not add interfaces into MAAS

Bug #2097374 reported by maasuser1
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned

Bug Description

Describe the bug:
So, whatever, I manually deployed an Ubuntu server using Ubuntu's official ISO 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:

Revision history for this message
maasuser1 (maasuser1) wrote :

The "commission" button is grayed out.

Revision history for this message
maasuser1 (maasuser1) wrote :

Commission scripts are shown as "Pending".

Revision history for this message
Jacopo Rota (r00ta) wrote :

Without additional information such as logs it’s impossible to reproduce this bug. I have to mark this as incomplete until additional investigation or information are provided

Changed in maas:
status: New → Incomplete
Revision history for this message
maasuser1 (maasuser1) wrote :

Hi r00ta, I checked the `journalctl` on MAAS and did not see anything suspicious. May I ask you to manually deploy an Ubuntu server using the official ISO and then add it to MAAS to see what happened?

```
Feb 04 17:39:23 maas maas-log[1513]: maas.api: [info] ritchie: Enlisted new machine
```

Except for this line, other logs are either `named` `dhcpd` and `pebble`.

maasuser1 (maasuser1)
description: updated
Revision history for this message
Jacopo Rota (r00ta) wrote :

> May I ask you to manually deploy an Ubuntu server using the official ISO and then add it to MAAS to see what happened?

We'll give a try

Changed in maas:
status: Incomplete → New
status: New → Incomplete
status: Incomplete → New
Revision history for this message
Jacopo Rota (r00ta) wrote :

I think you simply used `maas-run-scripts register-machine`. You should also enable HW sync in order to get your hardware info into MAAS

Changed in maas:
status: New → Invalid
Revision history for this message
maasuser1 (maasuser1) wrote :

Hello r00ta, shall I follow [this](https://maas.io/docs/how-to-provision-machines#p-9078-set-hardware-sync) guide? Thanks

Revision history for this message
maasuser1 (maasuser1) wrote :

It doesn't work - there it no option provided to enable HW sync for a machine already deployed out of maas.

Revision history for this message
Jacopo Rota (r00ta) wrote :

You can run the hw sync on a deployed machine. You just need to run

```
maas-run-scripts report-results --config maas-creds.yaml
```

from the deployed machine - see https://maas.io/docs/reference-release-notes-maas-3-1#p-11417-how-to-update-hardware-information-for-a-deployed-machine

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.