[2.3] 500 error from maas metadata while running hardware tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
Undecided
|
Unassigned |
Bug Description
I'm trying to deploy multiple servers with 24+ drives. During the hardware tests I'm seeing the attempted posts to the MAAS metadata server getting 500 errors as per:
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: message repeated 12 times: [ request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: message repeated 10 times: [ request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: message repeated 6 times: [ request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:53 hostname cloud-init[3382]: request to http://
Feb 5 23:37:54 hostname cloud-init[3382]: message repeated 5 times: [ request to http://
Feb 5 23:37:54 hostname cloud-init[3382]: FAIL: HTTP error [500]FAIL: HTTP error [500]FAIL: HTTP error [500]FAIL: HTTP error [500]FAIL: HTTP error [500]FAIL: HTTP error [500]Downloading and extracting http://
This is causing the drives to fail hardware validation, as they are unable to complete in time. I can't find any details in the logs as to what is going on to cause the 500 errors.
How can I stop this from occurring, or debug what is going on here?
Please let me know if you need any further information.
$ dpkg-query -W maas
maas 2.3.0-6434-
$ lsb_release -d
Description: Ubuntu 17.10
Changed in maas: | |
importance: | Undecided → High |
Changed in maas: | |
milestone: | 2.4.0rc1 → 2.4.0rc2 |
Hi Brad,
Can you confirm that your storage devices have been discovered successfully? Please attach the following:
1. all commissioning script output
2. all maas logs
3. confirm whether the disks were discovered during commissioning
4. how many nodes at the time are you commissioning?