Custom Images - Memory Deploy

vasartori · 16 October 2025 14:53

Hello all,

I’m trying to deploy a custom Ubuntu 22.04 image in memory.

The custom image was generated using the packer at canonical repo: GitHub - canonical/packer-maas: Packer templates to create MAAS deployable images without any modifications, just executed the command make custom-ubuntu.tar.gz

During the boot process, this error was raised:

If I press a key, a grub menu is launched, but nothing works

Images where uploaded through maas cli, with the command:

maas admin boot-resources create name='custom/test-memory-4' title='test memory 4'     architecture='amd64/generic' filetype='tgz' content@=custom-ubuntu.tar.gz`

Looking at logs, we see this error:

If I deploy an ubuntu image provided by maas, everything works as well.

r00ta · 16 October 2025 15:13

what MAAS version are you using?

vasartori · 16 October 2025 16:37

Sorry, we are using maas 3.5.7

r00ta · 16 October 2025 17:04

screenshot of the images page? The commissioning image must be fully synchronized, and from the logs it looks like it is not

vasartori · 16 October 2025 17:19

I re-run the image creation and upload.

It seems the image was synchronized

r00ta · 16 October 2025 19:05

can you retry and extract the rackd logs?

vasartori · 16 October 2025 19:31

I just found this…

Oct 16 19:26:21 maas-rackd02 dhcpd[74085]: DHCPDISCOVER from 00:25:b5:00:00:03 via ens160
Oct 16 19:26:21 maas-rackd02 dhcpd[74085]: DHCPOFFER on 10.107.72.24 to 00:25:b5:00:00:03 via ens160
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[0] = /usr/sbin/maas-dhcp-helper
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[1] = notify
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[2] = --action
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[3] = commit
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[4] = --mac
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[5] = 0:25:b5:0:0:3
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[6] = --ip-family
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[7] = ipv4
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[8] = --ip
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[9] = 10.107.72.24
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[10] = --lease-time
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[11] = 30
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[12] = --hostname
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[13] = (none)
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[14] = --socket
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: execute_statement argv[15] = /var/lib/maas/dhcpd.sock
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: DHCPREQUEST for 10.107.72.24 (10.107.72.11) from 00:25:b5:00:00:03 via ens160
Oct 16 19:26:25 maas-rackd02 dhcpd[74085]: DHCPACK on 10.107.72.24 to 00:25:b5:00:00:03 via ens160
Oct 16 19:26:25 maas-rackd02 rackd[821]: provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 10.107.72.24
Oct 16 19:26:25 maas-rackd02 rackd[821]: provisioningserver.rackdservices.http: [info] /images/bootx64.efi requested by 127.0.0.1
Oct 16 19:26:25 maas-rackd02 rackd[821]: provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 10.107.72.24
Oct 16 19:26:25 maas-rackd02 rackd[821]: provisioningserver.rackdservices.http: [info] /images/bootx64.efi requested by 127.0.0.1
Oct 16 19:26:26 maas-rackd02 rackd[821]: provisioningserver.rackdservices.tftp: [info] grubx64.efi requested by 10.107.72.24
Oct 16 19:26:26 maas-rackd02 rackd[821]: provisioningserver.rackdservices.http: [info] /images/grubx64.efi requested by 127.0.0.1
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/command.lst requested by 10.107.72.24
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.http: [info] /images/grub/x86_64-efi/command.lst requested by 127.0.0.1
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/fs.lst requested by 10.107.72.24
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.http: [info] /images/grub/x86_64-efi/fs.lst requested by 127.0.0.1
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/crypto.lst requested by 10.107.72.24
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.http: [info] /images/grub/x86_64-efi/crypto.lst requested by 127.0.0.1
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/terminal.lst requested by 10.107.72.24
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.http: [info] /images/grub/x86_64-efi/terminal.lst requested by 127.0.0.1
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg requested by 10.107.72.24
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg-00:25:b5:00:00:03 requested by 10.107.72.24
Oct 16 19:26:30 maas-rackd02 rackd[821]: provisioningserver.rackdservices.http: [info] /images/boot-kernel requested by 10.107.72.24

we are running with only one rackd (maas-rackd01), but it was shut down.

vasartori · 17 October 2025 13:56

@r00ta
I instaslled a new maas 3.5.8 on a single server.
Using the same image…
Same behavior…
See the logs:

Oct 17 10:51:03 router01 maas-log[11957]: maas.node: [info] server01: allocated to user admin
Oct 17 10:51:03 router01 maas-log[11957]: maas.preseed: [info] got bootres <BootResource name=teste-1, arch=amd64/generic, kflavor=None, base=ubuntu/jammy rtype=2>
Oct 17 10:51:03 router01 regiond[11939]: maasserver.preseed: [warn] WARNING: '/etc/maas/preseeds/curtin_userdata_custom' contains deprecated preseed variables. Please remove: main_archive_directory, ports_archive_directory
Oct 17 10:51:03 router01 maas-log[11957]: maas.node: [info] server01: Status transition from ALLOCATED to DEPLOYING
Oct 17 10:51:04 router01 regiond[11939]: maasserver.dhcp: [info] Successfully configured DHCPv4 on rack controller 'router01 (dxspcq)'.
Oct 17 10:51:04 router01 regiond[11939]: maasserver.dhcp: [info] Successfully configured DHCPv6 on rack controller 'router01 (dxspcq)'.
Oct 17 10:51:07 router01 named[859]: client @0x702e3001e7a8 127.0.0.1#35461/key maas: signer "maas" approved
Oct 17 10:51:07 router01 named[859]: client @0x702e3001e7a8 127.0.0.1#35461/key maas: updating zone 'maas/IN': adding an RR at 'server01.maas' A 172.16.3.6
Oct 17 10:51:07 router01 named[859]: client @0x702e3001e7a8 127.0.0.1#35461/key maas: updating zone 'maas/IN': deleting an RR at server01.maas A
Oct 17 10:51:07 router01 named[859]: client @0x702e3001e7a8 127.0.0.1#35461/key maas: updating zone 'maas/IN': adding an RR at 'server01.maas' A 172.16.3.6
Oct 17 10:51:07 router01 named[859]: client @0x702e3001e7a8 127.0.0.1#35461/key maas: updating zone 'maas/IN': adding an RR at 'maas' SOA maas. nobody.example.com. 221 600 1800 604800 30
Oct 17 10:51:07 router01 named[859]: client @0x702e38006d78 127.0.0.1#37727/key maas: signer "maas" approved
Oct 17 10:51:07 router01 named[859]: client @0x702e38006d78 127.0.0.1#37727/key maas: updating zone 'lab.int/IN': adding an RR at 'lab.int' SOA lab.int. nobody.example.com. 221 600 1800 604800 30
Oct 17 10:51:07 router01 named[859]: zone lab.int/IN: sending notifies (serial 221)
Oct 17 10:51:07 router01 named[859]: client @0x702e30009578 127.0.0.1#36464/key maas: signer "maas" approved
Oct 17 10:51:07 router01 named[859]: client @0x702e30009578 127.0.0.1#36464/key maas: updating zone 'maas-internal/IN': adding an RR at 'maas-internal' SOA maas-internal. nobody.example.com. 221 600 1800 604800 15
Oct 17 10:51:07 router01 named[859]: zone maas-internal/IN: sending notifies (serial 221)
Oct 17 10:51:07 router01 named[859]: client @0x702e3c012308 127.0.0.1#54529/key maas: signer "maas" approved
Oct 17 10:51:07 router01 named[859]: client @0x702e3c012308 127.0.0.1#54529/key maas: updating zone '0.168.192.in-addr.arpa/IN': adding an RR at '0.168.192.in-addr.arpa' SOA 0.168.192.in-addr.arpa. nobody.example.com. 221 600 1800 604800 30
Oct 17 10:51:07 router01 named[859]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 221)
Oct 17 10:51:07 router01 named[859]: client @0x702e4802b708 127.0.0.1#43049/key maas: signer "maas" approved
Oct 17 10:51:07 router01 named[859]: client @0x702e4802b708 127.0.0.1#43049/key maas: updating zone '0.16.172.in-addr.arpa/IN': adding an RR at '0.16.172.in-addr.arpa' SOA 0.16.172.in-addr.arpa. nobody.example.com. 221 600 1800 604800 30
Oct 17 10:51:07 router01 named[859]: zone 0.16.172.in-addr.arpa/IN: sending notifies (serial 221)
Oct 17 10:51:07 router01 named[859]: client @0x702e3c012308 127.0.0.1#53519/key maas: signer "maas" approved
Oct 17 10:51:07 router01 named[859]: client @0x702e3c012308 127.0.0.1#53519/key maas: updating zone '1.16.172.in-addr.arpa/IN': adding an RR at '1.16.172.in-addr.arpa' SOA 1.16.172.in-addr.arpa. nobody.example.com. 221 600 1800 604800 30
Oct 17 10:51:07 router01 named[859]: zone 1.16.172.in-addr.arpa/IN: sending notifies (serial 221)
Oct 17 10:51:07 router01 named[859]: client @0x702e30009578 127.0.0.1#40432/key maas: signer "maas" approved
Oct 17 10:51:07 router01 named[859]: client @0x702e30009578 127.0.0.1#40432/key maas: updating zone '2.16.172.in-addr.arpa/IN': adding an RR at '2.16.172.in-addr.arpa' SOA 2.16.172.in-addr.arpa. nobody.example.com. 221 600 1800 604800 30
Oct 17 10:51:07 router01 named[859]: zone 2.16.172.in-addr.arpa/IN: sending notifies (serial 221)
Oct 17 10:51:07 router01 named[859]: client @0x702e38018f48 127.0.0.1#33903/key maas: signer "maas" approved
Oct 17 10:51:07 router01 named[859]: client @0x702e38018f48 127.0.0.1#33903/key maas: updating zone '3.16.172.in-addr.arpa/IN': adding an RR at '6.3.16.172.in-addr.arpa' PTR server01.maas.
Oct 17 10:51:07 router01 named[859]: client @0x702e38018f48 127.0.0.1#33903/key maas: updating zone '3.16.172.in-addr.arpa/IN': deleting an RR at 6.3.16.172.in-addr.arpa PTR
Oct 17 10:51:07 router01 named[859]: client @0x702e38018f48 127.0.0.1#33903/key maas: updating zone '3.16.172.in-addr.arpa/IN': adding an RR at '6.3.16.172.in-addr.arpa' PTR server01.maas.
Oct 17 10:51:07 router01 named[859]: client @0x702e38018f48 127.0.0.1#33903/key maas: updating zone '3.16.172.in-addr.arpa/IN': adding an RR at '3.16.172.in-addr.arpa' SOA 3.16.172.in-addr.arpa. nobody.example.com. 221 600 1800 604800 30
Oct 17 10:51:07 router01 named[859]: zone 3.16.172.in-addr.arpa/IN: sending notifies (serial 221)
Oct 17 10:51:07 router01 regiond[11939]: maasserver.dhcp: [info] Successfully configured DHCPv4 on rack controller 'router01 (dxspcq)'.
Oct 17 10:51:07 router01 regiond[11939]: maasserver.dhcp: [info] Successfully configured DHCPv6 on rack controller 'router01 (dxspcq)'.
Oct 17 10:51:09 router01 regiond[11855]: maasserver.region_controller: [info] Reloaded DNS configuration; ip 172.16.3.6 allocated
Oct 17 10:51:46 router01 dhcpd[15183]: DHCPDISCOVER from 20:12:13:68:09:5a via enp5s0
Oct 17 10:51:46 router01 dhcpd[15183]: DHCPOFFER on 172.16.3.6 to 20:12:13:68:09:5a via enp5s0
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[0] = /usr/sbin/maas-dhcp-helper
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[1] = notify
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[2] = --action
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[3] = commit
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[4] = --mac
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[5] = 20:12:13:68:9:5a
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[6] = --ip-family
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[7] = ipv4
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[8] = --ip
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[9] = 172.16.3.6
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[10] = --lease-time
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[11] = 30
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[12] = --hostname
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[13] = (none)
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[14] = --socket
Oct 17 10:51:54 router01 dhcpd[15183]: execute_statement argv[15] = /var/lib/maas/dhcpd.sock
Oct 17 10:51:54 router01 dhcpd[15183]: DHCPREQUEST for 172.16.3.6 (172.16.0.1) from 20:12:13:68:09:5a via enp5s0
Oct 17 10:51:54 router01 dhcpd[15183]: DHCPACK on 172.16.3.6 to 20:12:13:68:09:5a via enp5s0
Oct 17 10:51:54 router01 rackd[11854]: provisioningserver.rackdservices.tftp: [info] lpxelinux.0 requested by 172.16.3.6
Oct 17 10:51:54 router01 rackd[11854]: provisioningserver.rackdservices.http: [info] /images/lpxelinux.0 requested by 127.0.0.1
Oct 17 10:51:54 router01 rackd[11854]: provisioningserver.rackdservices.tftp: [info] lpxelinux.0 requested by 172.16.3.6
Oct 17 10:51:54 router01 rackd[11854]: provisioningserver.rackdservices.http: [info] /images/lpxelinux.0 requested by 127.0.0.1
Oct 17 10:51:54 router01 maas-log[11957]: maas.interface: [info] enp5s0 (physical) on router01: New MAC, IP binding observed: 20:12:13:68:09:5a, 172.16.3.6
Oct 17 10:51:54 router01 regiond[11939]: maasserver.rpc.leases: [info] Lease update: commit for 172.16.3.6 on 20:12:13:68:09:5a at 2025-10-17 10:51:54 (lease time: 30s)
Oct 17 10:51:57 router01 rackd[11854]: provisioningserver.rackdservices.http: [info] ldlinux.c32 requested by 172.16.3.6
Oct 17 10:51:57 router01 rackd[11854]: provisioningserver.rackdservices.http: [info] /images/ldlinux.c32 requested by 127.0.0.1
Oct 17 10:51:57 router01 rackd[11854]: provisioningserver.rackdservices.http: [info] pxelinux.cfg/01-20-12-13-68-09-5a requested by 172.16.3.6
Oct 17 10:51:57 router01 maas-log[11957]: maas.rpc.boot: [warn] failed to compute a bootable amd64/ga-22.04 system for custom/teste-1
Oct 17 10:51:57 router01 rackd[11854]: provisioningserver.rackdservices.http: [info] /images/boot-kernel requested by 172.16.3.6
Oct 17 10:51:57 router01 maas-log[11957]: maas.node: [info] server01: Status transition from DEPLOYING to FAILED_DEPLOYMENT
Oct 17 10:51:58 router01 maas-log[11957]: maas.node: [info] server01: Status transition from DEPLOYING to FAILED_DEPLOYMENT
Oct 17 10:51:58 router01 maas-log[11957]: maas.node: [error] server01: Marking node failed: Missing boot image ubuntu/amd64/ga-22.04/jammy.
Oct 17 10:51:58 router01 regiond[11939]: regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

vasartori · 17 October 2025 17:31

@r00ta another test. This time I installed a new maas using snap, on version 3.6.2. Same image, same behavior.

2025-10-17T17:27:28Z maas-log[3405]: maas.node: [info] equal-osprey: allocated to user admin
2025-10-17T17:27:28Z maas-log[3405]: maas.preseed: [info] got bootres <BootResource name=teste-1, alias=None, arch=amd64/generic, kflavor=None, base=ubuntu/noble rtype=2>
2025-10-17T17:27:28Z maas-regiond[3364]: maasserver.preseed: [warn] WARNING: '/snap/maas/40614/etc/maas/preseeds/curtin_userdata_custom' contains deprecated preseed variables. Please remove: main_archive_directory, ports_archive_directory
2025-10-17T17:27:28Z maas-log[3405]: maas.node: [info] equal-osprey: Status transition from ALLOCATED to DEPLOYING
2025-10-17T17:27:28Z maas.pebble[3249]: 2025-10-17T17:27:28.403Z [pebble] GET /v1/services?names=dhcpd 72.088µs 200
2025-10-17T17:27:28Z maas-regiond[3364]: maasserver.dhcp: [info] Successfully configured DHCPv4 on rack controller 'maas (b67pfd)'.
2025-10-17T17:27:28Z maas.pebble[3249]: 2025-10-17T17:27:28.406Z [pebble] GET /v1/services?names=dhcpd6 81.477µs 200
2025-10-17T17:27:28Z maas-regiond[3364]: maasserver.dhcp: [info] Successfully configured DHCPv6 on rack controller 'maas (b67pfd)'.
2025-10-17T17:27:31Z maas-temporal-worker[3374]: {"message": "Starting workflow DeployManyWorkflow.run", "taskName": "run (workflow: deploy-many, id: f96c6ef0-b646-4d12-97bc-0091bacdd628, run: 4d512c60-eaba-4149-ae07-633c11fc0012)", "context_id": "20609e1e-a670-4019-b8cc-35df1ab67eb6", "timestamp": "2025-10-17T17:27:31.378261Z", "logger": "maastemporalworker.workflow.utils:51", "level": "INFO", "thread": "temporal_workflow__0:133810175866560"}
2025-10-17T17:27:31Z maas-temporal-worker[3374]: {"message": "Starting workflow DeployWorkflow.run", "taskName": "run (workflow: deploy, id: deploy:sk6fqk, run: 281c9f5e-72d2-485f-97d1-28bf67d74185)", "context_id": "99ac6ed2-dd69-455f-a7aa-8c7565f3a16d", "timestamp": "2025-10-17T17:27:31.433174Z", "logger": "maastemporalworker.workflow.utils:51", "level": "INFO", "thread": "temporal_workflow__0:133810175866560"}
2025-10-17T17:27:31Z maas.pebble[3249]: 2025-10-17T17:27:31.502Z [pebble] GET /v1/services?names=dhcpd 172.198µs 200
2025-10-17T17:27:31Z maas.pebble[3249]: 2025-10-17T17:27:31.505Z [pebble] GET /v1/services?names=dhcpd 39.638µs 200
2025-10-17T17:27:31Z maas-regiond[3364]: maasserver.dhcp: [info] Successfully configured DHCPv4 on rack controller 'maas (b67pfd)'.
2025-10-17T17:27:31Z maas.pebble[3249]: 2025-10-17T17:27:31.518Z [pebble] GET /v1/services?names=dhcpd6 40.641µs 200
2025-10-17T17:27:31Z maas-regiond[3364]: maasserver.dhcp: [info] Successfully configured DHCPv6 on rack controller 'maas (b67pfd)'.
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.524 client @0x7d26c0023ba8 127.0.0.1#46007/key maas: signer "maas" approved
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.527 client @0x7d26c0023ba8 127.0.0.1#46007/key maas: updating zone 'maas/IN': adding an RR at 'equal-osprey.maas' A 172.16.32.4
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.527 client @0x7d26c0023ba8 127.0.0.1#46007/key maas: updating zone 'maas/IN': deleting an RR at equal-osprey.maas A
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.527 client @0x7d26c0023ba8 127.0.0.1#46007/key maas: updating zone 'maas/IN': adding an RR at 'equal-osprey.maas' A 172.16.32.4
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.527 client @0x7d26c0023ba8 127.0.0.1#46007/key maas: updating zone 'maas/IN': adding an RR at 'maas' SOA maas. nobody.example.com. 74 600 1800 604800 30
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.562 client @0x7d26c806de78 127.0.0.1#42884/key maas: signer "maas" approved
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.562 client @0x7d26c806de78 127.0.0.1#42884/key maas: updating zone 'maas-internal/IN': adding an RR at 'maas-internal' SOA maas-internal. nobody.example.com. 74 600 1800 604800 15
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.574 zone maas-internal/IN: sending notifies (serial 74)
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.591 client @0x7d26c004ea68 127.0.0.1#37188/key maas: signer "maas" approved
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.591 client @0x7d26c004ea68 127.0.0.1#37188/key maas: updating zone '0.168.192.in-addr.arpa/IN': adding an RR at '0.168.192.in-addr.arpa' SOA 0.168.192.in-addr.arpa. nobody.example.com. 74 600 1800 604800 30
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.609 zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 74)
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.632 client @0x7d26c9b940e8 127.0.0.1#40869/key maas: signer "maas" approved
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.632 client @0x7d26c9b940e8 127.0.0.1#40869/key maas: updating zone '32.16.172.in-addr.arpa/IN': adding an RR at '4.32.16.172.in-addr.arpa' PTR equal-osprey.maas.
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.632 client @0x7d26c9b940e8 127.0.0.1#40869/key maas: updating zone '32.16.172.in-addr.arpa/IN': deleting an RR at 4.32.16.172.in-addr.arpa PTR
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.632 client @0x7d26c9b940e8 127.0.0.1#40869/key maas: updating zone '32.16.172.in-addr.arpa/IN': adding an RR at '4.32.16.172.in-addr.arpa' PTR equal-osprey.maas.
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.632 client @0x7d26c9b940e8 127.0.0.1#40869/key maas: updating zone '32.16.172.in-addr.arpa/IN': adding an RR at '32.16.172.in-addr.arpa' SOA 32.16.172.in-addr.arpa. nobody.example.com. 74 600 1800 604800 30
2025-10-17T17:27:31Z named[5627]: 17-Oct-2025 17:27:31.637 zone 32.16.172.in-addr.arpa/IN: sending notifies (serial 74)
2025-10-17T17:27:33Z maas-agent[3828]: ERR Activity error. ActivityType=power-on Attempt=1 Error="BMC is in the wrong power state" Namespace=default RunID=281c9f5e-72d2-485f-97d1-28bf67d74185 TaskQueue=b67pfd@agent:power WorkerID=b67pfd@agent:3828 WorkflowID=deploy:sk6fqk
2025-10-17T17:27:33Z maas-regiond[3286]: maasserver.region_controller: [info] Reloaded DNS configuration; ip 172.16.32.4 allocated
2025-10-17T17:27:34Z maas-agent[3828]: ERR Activity error. ActivityType=power-on Attempt=2 Error="BMC is in the wrong power state" Namespace=default RunID=281c9f5e-72d2-485f-97d1-28bf67d74185 TaskQueue=b67pfd@agent:power WorkerID=b67pfd@agent:3828 WorkflowID=deploy:sk6fqk
2025-10-17T17:27:37Z maas-agent[3828]: ERR Activity error. ActivityType=power-on Attempt=3 Error="BMC is in the wrong power state" Namespace=default RunID=281c9f5e-72d2-485f-97d1-28bf67d74185 TaskQueue=b67pfd@agent:power WorkerID=b67pfd@agent:3828 WorkflowID=deploy:sk6fqk
2025-10-17T17:27:42Z maas-agent[3828]: ERR Activity error. ActivityType=power-on Attempt=4 Error="BMC is in the wrong power state" Namespace=default RunID=281c9f5e-72d2-485f-97d1-28bf67d74185 TaskQueue=b67pfd@agent:power WorkerID=b67pfd@agent:3828 WorkflowID=deploy:sk6fqk
2025-10-17T17:27:42Z dhcpd[4038]: DHCPDISCOVER from 08:00:27:c4:2a:92 via enp0s8
2025-10-17T17:27:42Z dhcpd[4038]: DHCPOFFER on 172.16.32.4 to 08:00:27:c4:2a:92 via enp0s8
2025-10-17T17:27:43Z maas.pebble[3249]: 2025-10-17T17:27:43.094Z [pebble] GET /v1/services?names=dhcpd6 46.481µs 200
2025-10-17T17:27:43Z maas.pebble[3249]: 2025-10-17T17:27:43.095Z [pebble] GET /v1/services?names=dhcpd 17.016µs 200
2025-10-17T17:27:43Z maas.pebble[3249]: 2025-10-17T17:27:43.095Z [pebble] GET /v1/services?names=agent 9.792µs 200
2025-10-17T17:27:43Z maas.pebble[3249]: 2025-10-17T17:27:43.095Z [pebble] GET /v1/services?names=http 30.197µs 200
2025-10-17T17:27:43Z dhcpd[4038]: DHCPDISCOVER from 08:00:27:c4:2a:92 via enp0s8
2025-10-17T17:27:43Z dhcpd[4038]: DHCPOFFER on 172.16.32.4 to 08:00:27:c4:2a:92 via enp0s8
2025-10-17T17:27:44Z maas.pebble[3249]: 2025-10-17T17:27:44.415Z [pebble] GET /v1/services?names=temporal-worker 49.155µs 200
2025-10-17T17:27:44Z maas.pebble[3249]: 2025-10-17T17:27:44.415Z [pebble] GET /v1/services?names=temporal 11.715µs 200
2025-10-17T17:27:44Z maas.pebble[3249]: 2025-10-17T17:27:44.415Z [pebble] GET /v1/services?names=http 9.497µs 200
2025-10-17T17:27:44Z maas.pebble[3249]: 2025-10-17T17:27:44.415Z [pebble] GET /v1/services?names=syslog 7.772µs 200
2025-10-17T17:27:44Z maas.pebble[3249]: 2025-10-17T17:27:44.415Z [pebble] GET /v1/services?names=ntp 7.696µs 200
2025-10-17T17:27:44Z maas.pebble[3249]: 2025-10-17T17:27:44.415Z [pebble] GET /v1/services?names=bind9 10.035µs 200
2025-10-17T17:27:44Z maas.pebble[3249]: 2025-10-17T17:27:44.417Z [pebble] GET /v1/services?names=proxy 31.274µs 200
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[0] = /snap/maas/40614/usr/sbin/maas-dhcp-helper
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[1] = notify
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[2] = --action
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[3] = commit
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[4] = --mac
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[5] = 8:0:27:c4:2a:92
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[6] = --ip-family
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[7] = ipv4
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[8] = --ip
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[9] = 172.16.32.4
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[10] = --lease-time
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[11] = 30
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[12] = --hostname
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[13] = (none)
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[14] = --socket
2025-10-17T17:27:45Z dhcpd[4038]: execute_statement argv[15] = /var/snap/maas/common/maas/dhcpd.sock
2025-10-17T17:27:45Z dhcpd[4038]: DHCPREQUEST for 172.16.32.4 (172.16.32.1) from 08:00:27:c4:2a:92 via enp0s8
2025-10-17T17:27:45Z dhcpd[4038]: DHCPACK on 172.16.32.4 to 08:00:27:c4:2a:92 via enp0s8
2025-10-17T17:27:45Z maas-log[3405]: maas.interface: [info] enp0s8 (physical) on maas: New MAC, IP binding observed: 08:00:27:c4:2a:92, 172.16.32.4
2025-10-17T17:27:45Z maas-rackd[3291]: provisioningserver.rackdservices.http: [info] ipxe.cfg requested by 172.16.32.4
2025-10-17T17:27:45Z maas-http[3405]:  172.16.32.4 - - [17/Oct/2025:17:27:45 +0000] "GET /ipxe.cfg HTTP/1.1" 200 233 "-" "iPXE/1.21.1+ (g5c49e)"
2025-10-17T17:27:45Z maas-rackd[3291]: provisioningserver.rackdservices.http: [info] ipxe.cfg-08:00:27:c4:2a:92 requested by 172.16.32.4
2025-10-17T17:27:45Z maas-log[3405]: maas.rpc.boot: [warn] failed to compute a bootable amd64/ga-24.04 system for custom/teste-1
2025-10-17T17:27:45Z maas-http[3405]:  172.16.32.4 - - [17/Oct/2025:17:27:45 +0000] "GET /ipxe.cfg-08:00:27:c4:2a:92 HTTP/1.1" 200 467 "-" "iPXE/1.21.1+ (g5c49e)"
2025-10-17T17:27:45Z maas-rackd[3291]: provisioningserver.rackdservices.http: [info] /images/boot-kernel requested by 172.16.32.4
2025-10-17T17:27:45Z maas-http[3405]:  172.16.32.1 - - [17/Oct/2025:17:27:45 +0000] "GET /MAAS/boot-resources/boot-kernel HTTP/1.1" 404 134 "-" "iPXE/1.21.1+ (g5c49e)"
2025-10-17T17:27:45Z maas-http[3405]:  172.16.32.4 - - [17/Oct/2025:17:27:45 +0000] "GET /images/boot-kernel HTTP/1.1" 404 173 "-" "iPXE/1.21.1+ (g5c49e)"
2025-10-17T17:27:45Z maas-rackd[3291]: provisioningserver.rackdservices.http: [info] ipxe.cfg-default-amd64 requested by 172.16.32.4
2025-10-17T17:27:45Z maas-log[3405]: maas.node: [info] equal-osprey: Status transition from DEPLOYING to FAILED_DEPLOYMENT
2025-10-17T17:27:45Z maas-log[3405]: maas.node: [info] equal-osprey: Status transition from DEPLOYING to FAILED_DEPLOYMENT
2025-10-17T17:27:45Z maas-log[3405]: maas.node: [error] equal-osprey: Marking node failed: Missing boot image ubuntu/amd64/ga-24.04/noble.
2025-10-17T17:27:45Z maas-temporal-worker[3374]: {"message": "Workflow has completed", "taskName": "run (workflow: deploy-many, id: f96c6ef0-b646-4d12-97bc-0091bacdd628, run: 4d512c60-eaba-4149-ae07-633c11fc0012)", "elapsed_time_seconds": 14.499726057052612, "context_id": "20609e1e-a670-4019-b8cc-35df1ab67eb6", "timestamp": "2025-10-17T17:27:45.877980Z", "logger": "maastemporalworker.workflow.utils:53", "level": "INFO", "thread": "temporal_workflow__0:133810175866560"}
2025-10-17T17:27:45Z maas-http[3405]:  172.16.32.4 - - [17/Oct/2025:17:27:45 +0000] "GET /ipxe.cfg-default-amd64 HTTP/1.1" 200 616 "-" "iPXE/1.21.1+ (g5c49e)"
2025-10-17T17:27:45Z maas-rackd[3291]: provisioningserver.rackdservices.http: [info] /images/9a674ed/ubuntu/amd64/ga-22.04/jammy/stable/boot-kernel requested by 172.16.32.4
2025-10-17T17:27:45Z maas-http[3405]:  172.16.32.4 - - [17/Oct/2025:17:27:45 +0000] "GET /images/9a674ed/ubuntu/amd64/ga-22.04/jammy/stable/boot-kernel HTTP/1.1" 200 11710472 "-" "iPXE/1.21.1+ (g5c49e)"
2025-10-17T17:27:45Z maas-rackd[3291]: provisioningserver.rackdservices.http: [info] /images/7388520/ubuntu/amd64/ga-22.04/jammy/stable/boot-initrd requested by 172.16.32.4
2025-10-17T17:27:46Z maas-http[3405]:  172.16.32.4 - - [17/Oct/2025:17:27:46 +0000] "GET /images/7388520/ubuntu/amd64/ga-22.04/jammy/stable/boot-initrd HTTP/1.1" 200 115868197 "-" "iPXE/1.21.1+ (g5c49e)"
2025-10-17T17:27:49Z maas-apiserver[3290]: {"message": "Start processing request", "taskName": "Task-1918", "request_method": "POST", "request_path": "/MAAS/a/v3internal/leases", "request_query": "", "request_remote_ip": null, "context_id": "3045b44d-1b88-4f61-90a3-9eba8897ea2b", "timestamp": "2025-10-17T17:27:49.158919Z", "logger": "maasapiserver.v3.middlewares.context:34", "level": "INFO", "thread": "MainThread:139694884775744"}
2025-10-17T17:27:49Z maas-apiserver[3290]: {"message": "Lease update: commit for 172.16.32.4 on 08:00:27:c4:2a:92 at 2025-10-17 17:27:45 (lease time: 30s)", "taskName": "starlette.middleware.base.BaseHTTPMiddleware.__call__.<locals>.call_next.<locals>.coro", "context_id": "3045b44d-1b88-4f61-90a3-9eba8897ea2b", "timestamp": "2025-10-17T17:27:49.162463Z", "logger": "maasservicelayer.services.leases:83", "level": "INFO", "thread": "MainThread:139694884775744"}
2025-10-17T17:27:49Z maas-apiserver[3290]: {"message": "End processing request", "taskName": "Task-1918", "status_code": 204, "elapsed_time_seconds": 0.005640268325805664, "context_id": "3045b44d-1b88-4f61-90a3-9eba8897ea2b", "timestamp": "2025-10-17T17:27:49.164523Z", "logger": "maasapiserver.v3.middlewares.context:43", "level": "INFO", "thread": "MainThread:139694884775744"}

vasartori · 21 October 2025 11:58

@r00ta any news about this?

r00ta · 22 October 2025 09:29

Sorry I’m actually busy with some other stuff, I might be able to try that in the next days

andre-ruiz · 29 October 2025 14:28

I think you are missing pointing the base image used for the custom image (base option in the maas upload command).

vasartori · 30 October 2025 14:14

Hi @andre-ruiz are you talking about the option base_image=ubuntu/jammy in boot-resources create ?

For example:

maas admin boot-resources create name='custom/test-memory-4' title='test memory 4'     architecture='amd64/generic' filetype='tgz' base_image=ubuntu/jammy  content@=custom-ubuntu.tar.gz

If it was, I tested in versions: 3.5.7 and 3.6.2. Same error.

BTW, If I install the same image on disk, everythings works…