Legacy bios boot from second nic

Hi,
I have the following MAAS setup.
MAAS and Postgres are on the same server. The server is connected to a network (net0) providing internet access (with router and gateway), and to another network (net1) used only for MAAS commissioning and booting machines (with no router and no gateway). MAAS has DHCP active on net1, and (from what I could see) it correctly assign ip addresses to the NIC designated for PXE booting. However, I keep getting “No boot filename received” errors. This happens on all machines. The same machines were able to be commissioned some time ago when I was only using one network net1. As I need to have now two network for keeping some degree of isolation, I would be grateful is anyone could help me at debugging this issue. Attached you can find some logs.
Thanks in advance.

Regards,
Filippo

From MAAS

root@maas001:~# snap logs maas -n 100 -f
2023-12-09T00:12:33Z dhcpd[57936]: execute_statement argv[5] = e4:11:5b:d5:14:e4
2023-12-09T00:12:33Z dhcpd[57936]: execute_statement argv[6] = --ip-family
2023-12-09T00:12:33Z dhcpd[57936]: execute_statement argv[7] = ipv4
2023-12-09T00:12:33Z dhcpd[57936]: execute_statement argv[8] = --ip
2023-12-09T00:12:33Z dhcpd[57936]: execute_statement argv[9] = 10.10.10.52
2023-12-09T00:12:33Z dhcpd[57936]: execute_statement argv[10] = --socket
2023-12-09T00:12:33Z dhcpd[57936]: execute_statement argv[11] = /var/snap/maas/common/maas/dhcpd.sock
2023-12-09T00:22:11Z dhcpd[57936]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:22:11Z dhcpd[57936]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:22:12Z dhcpd[57936]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:22:12Z dhcpd[57936]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:22:14Z dhcpd[57936]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:22:14Z dhcpd[57936]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:22:18Z dhcpd[57936]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:22:18Z dhcpd[57936]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:26:43Z dhcpd[59431]: Internet Systems Consortium DHCP Server 4.4.1
2023-12-09T00:26:43Z dhcpd[59431]: Copyright 2004-2018 Internet Systems Consortium.
2023-12-09T00:26:43Z dhcpd[59431]: All rights reserved.
2023-12-09T00:26:43Z dhcpd[59431]: For info, please visit https://www.isc.org/software/dhcp/
2023-12-09T00:26:43Z dhcpd[59431]: Config file: /var/snap/maas/common/maas/dhcpd.conf
2023-12-09T00:26:43Z dhcpd[59431]: Database file: /var/snap/maas/common/maas/dhcp/dhcpd.leases
2023-12-09T00:26:43Z dhcpd[59431]: PID file: /var/snap/maas/common/maas/dhcp/dhcpd.pid
2023-12-09T00:26:43Z dhcpd[59431]: Wrote 0 class decls to leases file.
2023-12-09T00:26:43Z dhcpd[59431]: Wrote 0 deleted host decls to leases file.
2023-12-09T00:26:43Z dhcpd[59431]: Wrote 0 new dynamic host decls to leases file.
2023-12-09T00:26:43Z dhcpd[59431]: Wrote 1 leases to leases file.
2023-12-09T00:26:43Z dhcpd[59431]: Listening on LPF/enp6s0/00:1b:24:b3:74:a5/vlan-5002
2023-12-09T00:26:43Z dhcpd[59431]: Sending on   LPF/enp6s0/00:1b:24:b3:74:a5/vlan-5002
2023-12-09T00:26:43Z dhcpd[59431]: Sending on   Socket/fallback/fallback-net
2023-12-09T00:26:43Z dhcpd[59431]: Server starting service.
2023-12-09T00:31:47Z dhcpd[59893]: Internet Systems Consortium DHCP Server 4.4.1
2023-12-09T00:31:47Z dhcpd[59893]: Copyright 2004-2018 Internet Systems Consortium.
2023-12-09T00:31:47Z dhcpd[59893]: All rights reserved.
2023-12-09T00:31:47Z dhcpd[59893]: For info, please visit https://www.isc.org/software/dhcp/
2023-12-09T00:31:47Z dhcpd[59893]: Config file: /var/snap/maas/common/maas/dhcpd.conf
2023-12-09T00:31:47Z dhcpd[59893]: Database file: /var/snap/maas/common/maas/dhcp/dhcpd.leases
2023-12-09T00:31:47Z dhcpd[59893]: PID file: /var/snap/maas/common/maas/dhcp/dhcpd.pid
2023-12-09T00:31:47Z dhcpd[59893]: Wrote 0 class decls to leases file.
2023-12-09T00:31:47Z dhcpd[59893]: Wrote 0 deleted host decls to leases file.
2023-12-09T00:31:47Z dhcpd[59893]: Wrote 0 new dynamic host decls to leases file.
2023-12-09T00:31:47Z dhcpd[59893]: Wrote 1 leases to leases file.
2023-12-09T00:31:48Z dhcpd[59893]: Listening on LPF/enp6s0/00:1b:24:b3:74:a5/vlan-5002
2023-12-09T00:31:48Z dhcpd[59893]: Sending on   LPF/enp6s0/00:1b:24:b3:74:a5/vlan-5002
2023-12-09T00:31:48Z dhcpd[59893]: Sending on   Socket/fallback/fallback-net
2023-12-09T00:31:48Z dhcpd[59893]: Server starting service.
2023-12-09T00:32:07Z dhcpd[59893]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:32:07Z dhcpd[59893]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:32:09Z dhcpd[59893]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:32:09Z dhcpd[59893]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:32:11Z dhcpd[59893]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:32:11Z dhcpd[59893]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:32:15Z dhcpd[59893]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:32:15Z dhcpd[59893]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:33:58Z dhcpd[60156]: Internet Systems Consortium DHCP Server 4.4.1
2023-12-09T00:33:58Z dhcpd[60156]: Copyright 2004-2018 Internet Systems Consortium.
2023-12-09T00:33:58Z dhcpd[60156]: All rights reserved.
2023-12-09T00:33:58Z dhcpd[60156]: For info, please visit https://www.isc.org/software/dhcp/
2023-12-09T00:33:58Z dhcpd[60156]: Config file: /var/snap/maas/common/maas/dhcpd.conf
2023-12-09T00:33:58Z dhcpd[60156]: Database file: /var/snap/maas/common/maas/dhcp/dhcpd.leases
2023-12-09T00:33:58Z dhcpd[60156]: PID file: /var/snap/maas/common/maas/dhcp/dhcpd.pid
2023-12-09T00:33:58Z dhcpd[60156]: Wrote 0 class decls to leases file.
2023-12-09T00:33:58Z dhcpd[60156]: Wrote 0 deleted host decls to leases file.
2023-12-09T00:33:58Z dhcpd[60156]: Wrote 0 new dynamic host decls to leases file.
2023-12-09T00:33:58Z dhcpd[60156]: Wrote 1 leases to leases file.
2023-12-09T00:33:58Z dhcpd[60156]: Listening on LPF/enp6s0/00:1b:24:b3:74:a5/vlan-5002
2023-12-09T00:33:58Z dhcpd[60156]: Sending on   LPF/enp6s0/00:1b:24:b3:74:a5/vlan-5002
2023-12-09T00:33:58Z dhcpd[60156]: Sending on   Socket/fallback/fallback-net
2023-12-09T00:33:58Z dhcpd[60156]: Server starting service.
2023-12-09T00:42:07Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:42:07Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:42:09Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:42:09Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:42:11Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:42:11Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:42:15Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:42:15Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:52:07Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:52:07Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:52:09Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:52:09Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:52:11Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:52:11Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:52:15Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T00:52:15Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:02:08Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:02:08Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:02:10Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:02:10Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:02:12Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:02:12Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:02:16Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:02:16Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:12:07Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:12:07Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:12:09Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:12:09Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:12:11Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:12:11Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:12:15Z dhcpd[60156]: DHCPDISCOVER from 00:1b:24:b3:74:a5 via enp6s0
2023-12-09T01:12:15Z dhcpd[60156]: DHCPOFFER on 10.10.10.1 to 00:1b:24:b3:74:a5 via enp6s0

From PostgreSQL

2023-12-07 13:41:58.444 UTC [5911] maas@maasdb ERROR:  could not serialize access due to concurrent delete
2023-12-07 13:41:58.444 UTC [5911] maas@maasdb STATEMENT:  DELETE FROM "maasserver_regionrackrpcconnection" WHERE "maasserver_regionrackrpcconnection"."id" IN (3)
2023-12-07 13:41:58.517 UTC [5866] maas@maasdb ERROR:  could not serialize access due to concurrent delete
2023-12-07 13:41:58.517 UTC [5866] maas@maasdb STATEMENT:  DELETE FROM "maasserver_regionrackrpcconnection" WHERE "maasserver_regionrackrpcconnection"."id" IN (3)
2023-12-07 13:41:58.392 UTC [5909] maas@maasdb ERROR:  could not serialize access due to concurrent delete
2023-12-07 13:41:58.392 UTC [5909] maas@maasdb STATEMENT:  DELETE FROM "maasserver_regionrackrpcconnection" WHERE "maasserver_regionrackrpcconnection"."id" IN (3)
2023-12-07 13:43:17.919 UTC [5864] maas@maasdb ERROR:  could not serialize access due to concurrent delete
2023-12-07 13:43:17.919 UTC [5864] maas@maasdb STATEMENT:  DELETE FROM "maasserver_regionrackrpcconnection" WHERE "maasserver_regionrackrpcconnection"."id" IN (1)
2023-12-07 13:43:44.093 UTC [5885] maas@maasdb ERROR:  could not serialize access due to concurrent delete
2023-12-07 13:43:44.093 UTC [5885] maas@maasdb STATEMENT:  DELETE FROM "maasserver_regionrackrpcconnection" WHERE "maasserver_regionrackrpcconnection"."id" IN (6)
2023-12-07 13:46:44.509 UTC [5864] maas@maasdb ERROR:  could not serialize access due to concurrent update
2023-12-07 13:46:44.509 UTC [5864] maas@maasdb STATEMENT:  UPDATE "maasserver_service" SET "updated" = '2023-12-07T13:46:41.771737'::timestamp, "status_info" = '50% connected to region controllers.' WHERE "maasserver_service"."id" = 10
2023-12-07 13:46:44.509 UTC [5866] maas@maasdb ERROR:  could not serialize access due to concurrent delete
2023-12-07 13:46:44.509 UTC [5866] maas@maasdb STATEMENT:  DELETE FROM "maasserver_regionrackrpcconnection" WHERE "maasserver_regionrackrpcconnection"."id" IN (2)
2023-12-07 13:46:46.913 UTC [5864] maas@maasdb ERROR:  could not serialize access due to concurrent update
2023-12-07 13:46:46.913 UTC [5864] maas@maasdb STATEMENT:  DELETE FROM "maasserver_regionrackrpcconnection" WHERE "maasserver_regionrackrpcconnection"."id" IN (5)
2023-12-07 13:46:47.882 UTC [8863] maas@maasdb ERROR:  could not serialize access due to concurrent update
2023-12-07 13:46:47.882 UTC [8863] maas@maasdb STATEMENT:  UPDATE "maasserver_service" SET "updated" = '2023-12-07T13:46:47.879348'::timestamp, "status" = 'running', "status_info" = '' WHERE "maasserver_service"."id" = 10
2023-12-07 13:46:48.490 UTC [8863] maas@maasdb ERROR:  could not serialize access due to concurrent update
2023-12-07 13:46:48.490 UTC [8863] maas@maasdb STATEMENT:  UPDATE "maasserver_service" SET "updated" = '2023-12-07T13:46:48.145613'::timestamp, "status_info" = '75% connected to region controllers.' WHERE "maasserver_service"."id" = 10
2023-12-07 13:47:03.108 UTC [5899] maas@maasdb ERROR:  could not serialize access due to concurrent delete
2023-12-07 13:47:03.108 UTC [5899] maas@maasdb STATEMENT:  DELETE FROM "maasserver_regionrackrpcconnection" WHERE "maasserver_regionrackrpcconnection"."id" IN (9)
2023-12-07 14:42:54.413 UTC [5885] maas@maasdb ERROR:  could not serialize access due to concurrent update
2023-12-07 14:42:54.413 UTC [5885] maas@maasdb CONTEXT:  SQL statement "UPDATE maasserver_node
	    SET managing_process_id = region_process.id
	    WHERE maasserver_node.id = rack_controller.id"
	PL/pgSQL function sys_core_rpc_delete() line 34 at SQL statement
2023-12-07 14:42:54.413 UTC [5885] maas@maasdb STATEMENT:  DELETE FROM "maasserver_regionrackrpcconnection" WHERE "maasserver_regionrackrpcconnection"."id" IN (17)

Hi @ingfimo .

Do you machines use BIOS or UEFI?

Hi,

it should be BIOS. The machine in object is a HP Proliant DL 360 and uses ILO3

Then if I’m not wrong until MAAS 3.5 (which will be released in the next months) you can boot only from the first NIC.

Could you try to boot from net0 and use net1 for the other network?

Note that you have to add the machine again with the MAC address of the first nic

For reference Bug #2026824 “Enlistment fail for a machine with BIOS Legacy if ...” : Bugs : MAAS

Thanks your advice fixed the issue. Booting from the first NIC worked.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.