MAAS 2.5 won't PXE Qlogic 10G nic HP model# NC523SFP


#1

Hi,

Trying MAAS 2.5 on bare metal, notice maas 2.5 won’t PXE boot this type of nic card’s Model: NC523SFP running firmware version 4.20.1 the servers are HP DL380e G8 System ROM P73 05/21/2018. If anyone know how to fix this issue I’d be really grateful Thanks.

Here’s an image on where the systems han

g


PXE not working after upgrading to 2.5.0
#2

What method did you use to install MAAS? Installing Via Snap currently has a bug which breaks pxebooting.


#3

Packages.
sudo apt-add-repository ppa:maas/stable
sudo apt install maas

Just to let you know the 2.4 version work fine!


#4

Hi,
I’ve the same issue with Mellanox Technologies MT27500 Family [ConnectX-3] cards.

Stuck at the same point


#5

Hi all,

a full console log would be helpful to try to understand what could be going wrong.

That said, I wouldn’t be surprised if this is firmware related, but a full console log (or video) might just help.


#6

We had same problem with couple servers only when we switched to 2.5 (we were @ 2.4), we have fixed getting the latest firmware and replacing the DACs.

We replaced the DACs as after the firmware upgrade as we started to see errors and warnings coming from the NIC driver, then switched back to 2.4 and then no errors! So we hear guy was blaming Chrony causing some problems with some switches in a different deployment, so we decided to check the DACs and as we suspect those were different than the others in that cab. We replaced with Mellanox, after the replacement everything worked fine.

Regards,


#7

Has anyone solved this without swapping DAC cables?


#8

Hello guys,

Sorry for the delay, this is another maas and server same issues find bellow the logs of the maas/rackd/regiond. thanks

maas.log
$ sudo cat maas.log
2019-03-13T08:40:19.057411-04:00 cltnaxmaas01 maas.networks.monitor: [info] Networks monitoring service: Process ID 1251 assumed responsibility.
2019-03-13T08:40:22.558005-04:00 cltnaxmaas01 maas.service_monitor: [info] Service ‘maas-syslog’ has been restarted. Its current state is ‘on’ and ‘running’.
2019-03-13T08:40:22.890237-04:00 cltnaxmaas01 maas.refresh: [info] Refreshing rack controller hardware information.
2019-03-13T08:40:24.180828-04:00 cltnaxmaas01 maas.service_monitor: [info] Service ‘chrony’ has been restarted. Its current state is ‘on’ and ‘running’.
2019-03-13T08:40:25.791631-04:00 cltnaxmaas01 maas.import-images: [info] Downloading image descriptions from http://images.maas.io/ephemeral-v3/daily/
2019-03-13T08:40:25.792115-04:00 cltnaxmaas01 maas.import-images: [info] Region downloading image descriptions from ‘http://images.maas.io/ephemeral-v3/daily/’.
2019-03-13T08:40:26.771307-04:00 cltnaxmaas01 maas.rpc.rackcontrollers: [info] Existing rack controller ‘cltnaxmaas01’ running version 2.5.1-7508-gb70537f3d-0ubuntu1~18.04.1 has connected to region ‘cltnaxmaas01’.
2019-03-13T08:40:28.057092-04:00 cltnaxmaas01 maas.rpc.rackcontrollers: message repeated 2 times: [ [info] Existing rack controller ‘cltnaxmaas01’ running version 2.5.1-7508-gb70537f3d-0ubuntu1~18.04.1 has connected to region ‘cltnaxmaas01’.]
2019-03-13T08:40:30.124685-04:00 cltnaxmaas01 maas.service_monitor: [info] Service ‘maas-dhcpd’ has been restarted. Its current state is ‘on’ and ‘running’.
2019-03-13T08:40:35.808526-04:00 cltnaxmaas01 maas.import-images: [warn] I/O error while syncing boot images. If this problem persists, verify network connectivity and disk usage.
2019-03-13T08:40:35.808642-04:00 cltnaxmaas01 maas.bootsources: [error] Failed to import images from http://images.maas.io/ephemeral-v3/daily/: HTTPConnectionPool(host=‘images.maas.io’, port=80): Max retries exceeded with url: /ephemeral-v3/daily/streams/v1/index.sjson (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x7f4a6af12e10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution’,))
2019-03-13T08:40:35.951437-04:00 cltnaxmaas01 maas.bootsources: [error] Unable to update boot sources cache.
2019-03-13T08:40:36.016121-04:00 cltnaxmaas01 maas.rpc.rackcontrollers: [info] Existing rack controller ‘cltnaxmaas01’ running version 2.5.1-7508-gb70537f3d-0ubuntu1~18.04.1 has connected to region ‘cltnaxmaas01’.
2019-03-13T08:40:36.085957-04:00 cltnaxmaas01 maas.bootresources: [info] Started importing of boot images from 1 source(s).
2019-03-13T08:40:36.091343-04:00 cltnaxmaas01 maas.import-images: [info] Downloading image descriptions from http://images.maas.io/ephemeral-v3/daily/
2019-03-13T08:40:36.091619-04:00 cltnaxmaas01 maas.import-images: [info] Region downloading image descriptions from ‘http://images.maas.io/ephemeral-v3/daily/’.
2019-03-13T08:40:43.033337-04:00 cltnaxmaas01 maas.bootresources: [info] Importing images from source: http://images.maas.io/ephemeral-v3/daily/
2019-03-13T08:40:44.460601-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:ga-18.04 20190307
2019-03-13T08:40:44.515902-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:ga-18.04-lowlatency 20190307
2019-03-13T08:40:44.570648-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:hwe-18.04 20190307
2019-03-13T08:40:44.624699-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:hwe-18.04-edge 20190307
2019-03-13T08:40:44.679722-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:hwe-18.04-lowlatency 20190307
2019-03-13T08:40:44.734096-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:hwe-18.04-lowlatency-edge 20190307
2019-03-13T08:40:45.152573-04:00 cltnaxmaas01 maas.bootresources: [info] Finished importing of boot images from 1 source(s).
2019-03-13T08:40:45.164156-04:00 cltnaxmaas01 maas.import-images: [info] Starting rack boot image import
2019-03-13T08:40:45.174170-04:00 cltnaxmaas01 maas.import-images: [info] Downloading image descriptions from http://10.1.0.1:5240/MAAS/images-stream/streams/v1/index.json
2019-03-13T08:40:45.174646-04:00 cltnaxmaas01 maas.import-images: [info] Rack downloading image descriptions from ‘http://10.1.0.1:5240/MAAS/images-stream/streams/v1/index.json’.
2019-03-13T08:40:45.394913-04:00 cltnaxmaas01 maas.import-images: [info] Finished importing boot images, the region does not have any new images.
2019-03-13T08:40:45.397260-04:00 cltnaxmaas01 maas.import-images: [info] Starting rack boot image import
2019-03-13T08:42:50.824480-04:00 cltnaxmaas01 maas.import-images: [info] Downloading image descriptions from http://images.maas.io/ephemeral-v3/daily/
2019-03-13T08:42:50.824874-04:00 cltnaxmaas01 maas.import-images: [info] Region downloading image descriptions from ‘http://images.maas.io/ephemeral-v3/daily/’.
2019-03-13T08:42:53.133227-04:00 cltnaxmaas01 maas.bootsources: [info] Updated boot sources cache.
2019-03-13T08:42:53.165215-04:00 cltnaxmaas01 maas.bootresources: [info] Started importing of boot images from 1 source(s).
2019-03-13T08:42:53.166782-04:00 cltnaxmaas01 maas.import-images: [info] Downloading image descriptions from http://images.maas.io/ephemeral-v3/daily/
2019-03-13T08:42:53.166895-04:00 cltnaxmaas01 maas.import-images: [info] Region downloading image descriptions from ‘http://images.maas.io/ephemeral-v3/daily/’.
2019-03-13T08:42:56.680491-04:00 cltnaxmaas01 maas.bootresources: [info] Importing images from source: http://images.maas.io/ephemeral-v3/daily/
2019-03-13T08:42:58.087580-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:ga-18.04 20190307
2019-03-13T08:42:58.142743-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:ga-18.04-lowlatency 20190307
2019-03-13T08:42:58.197189-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:hwe-18.04 20190307
2019-03-13T08:42:58.251257-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:hwe-18.04-edge 20190307
2019-03-13T08:42:58.305302-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:hwe-18.04-lowlatency 20190307
2019-03-13T08:42:58.359561-04:00 cltnaxmaas01 maas.bootresources: [warn] Ignoring unsupported filetype(manifest) from com.ubuntu.maas.daily:v3:boot:18.04:amd64:hwe-18.04-lowlatency-edge 20190307
2019-03-13T08:42:59.121974-04:00 cltnaxmaas01 maas.bootresources: [info] Finished importing of boot images from 1 source(s).
2019-03-13T08:42:59.145998-04:00 cltnaxmaas01 maas.import-images: [info] Starting rack boot image import
2019-03-13T08:42:59.151469-04:00 cltnaxmaas01 maas.import-images: [info] Downloading image descriptions from http://10.1.0.1:5240/MAAS/images-stream/streams/v1/index.json
2019-03-13T08:42:59.151616-04:00 cltnaxmaas01 maas.import-images: [info] Rack downloading image descriptions from ‘http://10.1.0.1:5240/MAAS/images-stream/streams/v1/index.json’.
2019-03-13T08:42:59.437952-04:00 cltnaxmaas01 maas.import-images: [info] Finished importing boot images, the region does not have any new images.
2019-03-13T08:42:59.440356-04:00 cltnaxmaas01 maas.import-images: [info] Starting rack boot image import
2019-03-13T08:52:41.247621-04:00 cltnaxmaas01 maas.service_monitor: [info] Service ‘maas-dhcpd’ has been restarted. Its current state is ‘on’ and ‘running’.

#################

rack.log

$ sudo cat rackd.log
2019-03-13 08:40:19 twisted.scripts: [info] twistd 17.9.0 (/usr/bin/python3 3.6.7) starting up.
2019-03-13 08:40:19 twisted.scripts: [info] reactor class: twisted.internet.asyncioreactor.AsyncioSelectorReactor.
2019-03-13 08:40:19 provisioningserver.utils.services: [info] Starting beaconing for interfaces: {‘enp3s0’, ‘bond0’}
2019-03-13 08:40:19 provisioningserver.utils.services: [info] Beaconing process for enp3s0 started.
2019-03-13 08:40:19 provisioningserver.utils.services: [info] Beaconing process for bond0 started.
2019-03-13 08:40:19 provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://10.1.0.1:5240/MAAS).
2019-03-13 08:40:20 provisioningserver.utils.services: [info] observe-beacons[bond0]: tcpdump: listening on bond0, link-type EN10MB (Ethernet), capture size 16384 bytes
2019-03-13 08:40:20 provisioningserver.utils.services: [info] observe-beacons[enp3s0]: tcpdump: listening on enp3s0, link-type EN10MB (Ethernet), capture size 16384 bytes
2019-03-13 08:40:20 provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://10.1.0.1:5240/MAAS).
2019-03-13 08:40:21 provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://10.1.0.1:5240/MAAS).
2019-03-13 08:40:22 provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://10.1.0.1:5240/MAAS).
2019-03-13 08:40:23 provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://10.1.0.1:5240/MAAS).
2019-03-13 08:40:24 provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://10.1.0.1:5240/MAAS).
2019-03-13 08:40:25 provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://10.1.0.1:5240/MAAS).
2019-03-13 08:40:26 provisioningserver.rpc.clusterservice: [info] Making connections to event-loops: cltnaxmaas01:pid=1779, cltnaxmaas01:pid=1780, cltnaxmaas01:pid=1782, cltnaxmaas01:pid=1783
2019-03-13 08:40:26 Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(TCP, ‘::ffff:10.200.200.4’, 38882) PEER:IPv6Address(TCP, ‘::ffff:10.200.200.4’, 5250))
2019-03-13 08:40:26 Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(TCP, ‘::ffff:10.200.200.4’, 46158) PEER:IPv6Address(TCP, ‘::ffff:10.200.200.4’, 5251))
2019-03-13 08:40:26 Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(TCP, ‘::ffff:10.200.100.4’, 48450) PEER:IPv6Address(TCP, ‘::ffff:10.200.100.4’, 5253))
2019-03-13 08:40:26 Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(TCP, ‘::ffff:10.1.0.1’, 58102) PEER:IPv6Address(TCP, ‘::ffff:10.1.0.1’, 5252))
2019-03-13 08:40:26 provisioningserver.rpc.clusterservice: [info] Event-loop ‘cltnaxmaas01:pid=1780’ authenticated.
2019-03-13 08:40:26 provisioningserver.rpc.clusterservice: [info] Event-loop ‘cltnaxmaas01:pid=1782’ authenticated.
2019-03-13 08:40:26 provisioningserver.rpc.clusterservice: [info] Event-loop ‘cltnaxmaas01:pid=1783’ authenticated.
2019-03-13 08:40:26 provisioningserver.rpc.clusterservice: [info] Fully connected to all 4 event-loops on all 1 region controllers (cltnaxmaas01).
2019-03-13 08:40:28 provisioningserver.rpc.clusterservice: [info] Rack controller ‘nm3pn7’ registered (via cltnaxmaas01:pid=1780) with MAAS version 2.5.1-7508-gb70537f3d-0ubuntu1~18.04.1.
2019-03-13 08:40:28 provisioningserver.rpc.clusterservice: [info] Rack controller ‘nm3pn7’ registered (via cltnaxmaas01:pid=1782) with MAAS version 2.5.1-7508-gb70537f3d-0ubuntu1~18.04.1.
2019-03-13 08:40:28 provisioningserver.rpc.clusterservice: [info] Rack controller ‘nm3pn7’ registered (via cltnaxmaas01:pid=1783) with MAAS version 2.5.1-7508-gb70537f3d-0ubuntu1~18.04.1.
2019-03-13 08:40:30 provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: enp3s0, bond0.2130, bond0.2600, bond0.666, bond0.140, bond0.2610, bond0.2110, bond0.888, bond0.2120, bond0.141.
2019-03-13 08:40:31 provisioningserver.utils.services: [info] New interface monitoring state: {‘enp3s0’: {‘neighbour’: False, ‘mdns’: False}, ‘enp5s0’: {‘neighbour’: False, ‘mdns’: False}, ‘ens1f0’: {‘neighbour’: False, ‘mdns’: False}, ‘ens1f1’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0.140’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0.141’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0.2110’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0.2120’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0.2130’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0.2600’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0.2610’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0.666’: {‘neighbour’: False, ‘mdns’: False}, ‘bond0.888’: {‘neighbour’: False, ‘mdns’: False}}
2019-03-13 08:40:35 provisioningserver.rpc.clusterservice: [info] Event-loop ‘cltnaxmaas01:pid=1779’ authenticated.
2019-03-13 08:40:37 provisioningserver.rpc.clusterservice: [info] Rack controller ‘nm3pn7’ registered (via cltnaxmaas01:pid=1779) with MAAS version 2.5.1-7508-gb70537f3d-0ubuntu1~18.04.1.
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:centos:amd64:generic:centos70: to_add=[‘20180901_02’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:grub-efi-signed:amd64:generic:uefi: to_add=[‘20190209.0’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:grub-efi:arm64:generic:uefi: to_add=[‘20190209.0’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:grub-ieee1275:ppc64el:generic:open-firmware: to_add=[‘20181212.0’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:pxelinux:i386:generic:pxe: to_add=[‘20180807.0’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-18.04-lowlatency:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-18.04:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-edge:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-lowlatency-edge:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-lowlatency:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:40:45 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:42:10 provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete.
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:centos:amd64:generic:centos70: to_add=[‘20180901_02’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:grub-efi-signed:amd64:generic:uefi: to_add=[‘20190209.0’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:grub-efi:arm64:generic:uefi: to_add=[‘20190209.0’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:grub-ieee1275:ppc64el:generic:open-firmware: to_add=[‘20181212.0’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:pxelinux:i386:generic:pxe: to_add=[‘20180807.0’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-18.04-lowlatency:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-18.04:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-edge:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-lowlatency-edge:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-lowlatency:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:42:59 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04:bionic: to_add=[‘20190307’] to_remove=[]
2019-03-13 08:46:27 provisioningserver.rackdservices.tftp: [info] lpxelinux.0 requested by 10.1.255.12
2019-03-13 08:46:27 provisioningserver.rackdservices.tftp: [info] lpxelinux.0 requested by 10.1.255.12
2019-03-13 08:50:19 provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: enp3s0, bond0.2130, bond0.2600, bond0.666, bond0.140, bond0.2610, bond0.2110, bond0.888, bond0.2120, bond0.141.
2019-03-13 08:51:59 provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete.
2019-03-13 08:55:43 provisioningserver.rackdservices.tftp: [info] lpxelinux.0 requested by 10.1.255.12
2019-03-13 08:55:43 provisioningserver.rackdservices.tftp: [info] lpxelinux.0 requested by 10.1.255.12

#######################
here last 30 lines of the regiond.log

$ tail -n 30 regiond.log
2019-03-13 08:50:21 maasserver.regiondservices.active_discovery: [info] Active network discovery: Passive discovery is disabled. Skipping periodic scan.
2019-03-13 08:50:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:51:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:51:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:52:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:52:41 maasserver.dhcp: [info] Successfully configured DHCPv4 on rack controller ‘cltnaxmaas01 (nm3pn7)’.
2019-03-13 08:52:41 maasserver.dhcp: [info] Successfully configured DHCPv6 on rack controller ‘cltnaxmaas01 (nm3pn7)’.
2019-03-13 08:52:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:53:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:53:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:54:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:54:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:55:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:55:21 maasserver.regiondservices.active_discovery: [info] Active network discovery: Passive discovery is disabled. Skipping periodic scan.
2019-03-13 08:55:43 maasserver.rpc.leases: [info] Lease update: commit for 10.1.255.12 on 2c:27:d7:50:f5:b0 at 2019-03-13 08:55:43 (lease time: 30s)
2019-03-13 08:55:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:56:13 maasserver.rpc.leases: [info] Lease update: expiry for 10.1.255.12 on 2c:27:d7:50:f5:b0 at 2019-03-13 08:56:13
2019-03-13 08:56:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:56:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:57:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:57:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:58:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:58:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:59:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 08:59:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 09:00:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 09:00:21 maasserver.regiondservices.active_discovery: [info] Active network discovery: Passive discovery is disabled. Skipping periodic scan.
2019-03-13 09:00:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 09:01:19 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2019-03-13 09:01:49 regiond: [info] 10.1.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)


#9

here the screenshot of the server


#10

Hi,

Any news on this issue?
I have a sort of similar issue, my machines getting stuck at grub screen during commission.

It started happening when i changed the PXE nic to our 10G.
We are using Intel Ethernet Converged Network Adapter X710 on Dell R630 hardware.

Thanks!


#11

I haven’t heard anything yet I’m willing to let mass developer team to log into my environment and troubleshoot one of those machine.


#12

i had th same issue but with a different network card.

couple things we found
Wrong SPF install
Dirty fiber pairs

Best one was we had to reboot a nexus 5k to fix it.


#13

We’ve seen this behavior in some older Dell blades with QLogic NICs. Newer Dell blades with Intel NICs do not see the issue. Comparing boots in network captures between the models against various MAAS versions (2.4.2, 2.5.1, 2.6a1/2) we see everything appears to be identical up to the point of the machine requesting a file over http (as MAAS versions increase, http is used earlier and earlier in the boot process). On the QLogic, no response is seen after the http request. On the Intels, an [HTTP/1.1 200 OK] response is recorded. DHCP and tftp appear to work just fine. It’s when it switches to http that we see the process hang up.


#14

Further testing shows that switching to an EFI boot process rather than BIOS boot appears to resolve the issue on our end. We are using QMD8262-k NICs. We noticed that the BIOS boot process sends an HTTP/1.0 GET request, whereas the EFI boot process sends an HTTP/1.1 GET request, but it’s also a request for a different file.


#15

I see, well HP DL G8 series don’t support EFI bios