Mellonx MT28800 Family [ConnectX-5 Ex] does not report 100G as max interface speed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Lee Trager | ||
2.7 |
Fix Released
|
High
|
Lee Trager | ||
lxd |
Fix Released
|
Unknown
|
Bug Description
Failing the comissioning because of smartctl-validate failure.
MAAS server Ubuntu release: 18.04
MAAS v. 2.7.0 (8235-g.fea3a1678)
Commissioning OS: 18.04 & 20.04 same results.
Status
Failed
Exit Status
2
logs combined:
Unable to run 'smartctl-
Given parameters:
{'storage': {'argument_format': '{path}', 'type': 'storage', 'value': 'all'}}Discovered storage devices:[{'NAME': 'sda', 'MODEL': 'MTFDDAK480TDC-1A', 'SERIAL': '500a0751249c23
Discovered interfaces:
{'bc:97:
Running the smartctl-validate device or smarctl -xa device on the server (accessing by ssh avoiding power off the server) works fine.
Last lines on cloud-init-
Starting testing scripts...
Installing apt packages for smartctl-validate (id: 871, script_version_id: 1)
Starting smartctl-validate (id: 871, script_version_id: 1)
Failed to execute smartctl-validate (id: 871, script_version_id: 1): 2
1 test scripts failed to run
Cloud-init v. 20.1-10-
summary: |
- Smart-validate failure on Lenovo RS635 with LSI MegaRaid 730-9i + Smart-validate failure on Lenovo RS635 with LSI MegaRaid 730-8i |
Changed in maas: | |
assignee: | nobody → Lee Trager (ltrager) |
importance: | Undecided → High |
Changed in lxd: | |
status: | Unknown → New |
Changed in lxd: | |
status: | New → Fix Released |
Changed in maas: | |
milestone: | 2.8.0rc1 → 2.8.0 |
Changed in maas: | |
status: | Incomplete → Confirmed |
Changed in maas: | |
status: | Confirmed → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in lxd: | |
status: | Fix Released → Unknown |
Changed in lxd: | |
status: | Unknown → Fix Released |
Can you confirm no storage devices were discovered? You can do this by clicking on the storage tab on the machine details page.
Please upload the following to the bug: 01-commissionin g from the failing machine
* The MAAS logs for each controller, stored in /var/log/maas
* The output of the commissioning script 50-maas-