Error on arm64 while running autoinstaller

Bug #1926132 reported by Alfonso Sanchez-Beato
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
Fix Released
Undecided
Unassigned

Bug Description

I am installing on an arm64 server using the autoinstaller, with command line:

linux /vmlinuz console=hvc0 console=ttyAMA0 earlycon=pl011,0x01000000 fixrtc ip=dhcp url=http://192.168.100.1/tftp/bluefield.iso autoinstall ds="nocloud-net;s=http://192.168.100.1/tftp/" cloud-config-url=/dev/null

meta-data is an empty file, while user-data has content:

#cloud-config
autoinstall:
  version: 1
  # ubuntu/ubuntu
  identity:
    hostname: mynic
    username: ubuntu
    password: "$6$rounds=4096$PCrfo.ggdf4ubP$REjyaoY2tUWH2vjFJjvLs3rDxVTszGR9P7mhH9sHb2MsELfc53uV/v15jDDOJU/9WInfjjTKJPlD5URhX5Mix0"
  ssh:
    allow-pw: true
    authorized-keys:
      - "ssh-rsa AAAAB3Nz..."
    install-server: true

The error I see on the console is:

connecting...
start: subiquity/Meta/status_GET
finish: subiquity/Network/apply_config: apply_error() missing 1 required positional argument: 'stage'
start: subiquity/ErrorReporter/1616017200.540628672.network_fail/add_info
finish: subiquity/Network/apply_autoinstall_config/wait_for_apply: apply_error() missing 1 required positional argument: 'stage'
finish: subiquity/Network/apply_autoinstall_config: apply_error() missing 1 required positional argument: 'stage'
finish: subiquity/apply_autoinstall_config: apply_error() missing 1 required positional argument: 'stage'
finish: subiquity/ErrorReporter/1616017200.540628672.network_fail/add_info
start: subiquity/Meta/status_GET
start: subiquity/Meta/status_GET
start: subiquity/Meta/status_GET

and things do not move forward. How I could get the error log in this case?

Tags: fr-1334
Dan Bungert (dbungert)
tags: added: fr-1334
Revision history for this message
Matt Simmons (standalonesa) wrote :

I am also hitting this error. I believe that this line is the problem:

https://github.com/canonical/subiquity/blob/main/subiquity/server/controllers/network.py#L259

I believe instead of

super().apply_error()

it should be:

super().apply_error(stage)

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Yes you're completely right that that is the problem: https://github.com/canonical/subiquity/pull/945

However, this is a crash reporting the failure of something that really shouldn't be failing (probably calling netplan apply, although it could be some other less likely things). So let's fix this and get on to debugging the next problem I guess!

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

(does an interactive install work on this system?)

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

This should be fixed in edge now.

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

Thanks, will give it a try! Yeah, interactive installation worked for this system.

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

@Michael, thanks, the installation now moves forward but as you predicted calling netplan apply fails. I have opened LP:#1927695 with more information.

Is there a way to get into the system when this happens? Note that this is a console interface.

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

> Is there a way to get into the system when this happens? Note that this is a console interface.

No, we don't have a good answer here so let's add one: https://github.com/canonical/subiquity/pull/950

I've pushed builds of this branch to the 'latest/edge/mwhudson-hack' channel if you want to try it out.

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

So the change to not crash on netplan apply failure and the change to offer a shell if autoinstall fails are in the current stable release. I'm not sure there's anything else actionable from this bug so I'm going to close it. Feel free to reopen it or file new ones if I've missed something.

Changed in subiquity:
status: New → Fix Released
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.