Commissioning fails when BIOS reports floppy drive, but there is none installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse | ||
1.9 |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
When commissioning a server it consistently "Failed commissioning"
Looking at the console logs we see a conspicous log: "blk_update_
http://
After disabling the "floppy drive" in the BIOS (there wasn't a physical floppy drive installed) the problem goes away and commissioning is successful!
Thanks to kiko for the help debugging
ubuntu@maas:~$ dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.0.0~beta3+
ii maas-cli 2.0.0~beta3+
un maas-cluster-
ii maas-common 2.0.0~beta3+
ii maas-dhcp 2.0.0~beta3+
ii maas-dns 2.0.0~beta3+
ii maas-proxy 2.0.0~beta3+
ii maas-rack-
ii maas-region-api 2.0.0~beta3+
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.0.0~beta3+
ii python3-maas-client 2.0.0~beta3+
ii python3-
Related branches
- Gavin Panella (community): Approve
-
Diff: 57 lines (+14/-7)2 files modifiedsrc/provisioningserver/refresh/node_info_scripts.py (+5/-3)
src/provisioningserver/refresh/tests/test_node_info_scripts.py (+9/-4)
- Blake Rouse (community): Approve
-
Diff: 57 lines (+14/-7)2 files modifiedsrc/metadataserver/models/commissioningscript.py (+5/-3)
src/metadataserver/models/tests/test_commissioningscript.py (+9/-4)
summary: |
- commissioning fails - related to "blk_update_request: I/O error, dev - fd0, sector 0" + Commissioning fails when BIOS reports floppy drive, but there is none + installed |
Changed in maas: | |
milestone: | none → 2.0.0 |
importance: | Undecided → Critical |
Changed in maas: | |
status: | New → In Progress |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Note the related question: http:// askubuntu. com/questions/ 213512/ buffer- i-o-error- on-device- fd0-logical- block-0- error
I'm not sure why blkid returns an error if fd0 is missing; I guess the problem may be that floppies are not really probeable -- i.e. the only way to tell if they are there is to go and read from them.
At any rate, there's an easy big hammer, which is blacklisting the floppy module during the commissioning run, or we could be more subtle and not really mind blkid's return code.