UCS chassis enlist Failed to probe and enlist UCS nodes: list index out of range

Bug #1469846 reported by David Britton on 2015-06-29
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Andres Rodriguez
Andres Rodriguez

Bug Description

I have 3/8 unconfigured blades, and this error shows up in the maas.log

Jun 29 14:22:41 localhost maas.rpc.cluster: [ERROR] Failed to probe and enlist UCS nodes: list index out of range

There is no other error. Nothing in the UI, nothing in any other logs. I'm guessing it's because of unassociated blades, but I wouldn't expect (as a user) to get an error in that case.

Related branches

Changed in maas:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Andres Rodriguez (andreserl)
milestone: none → 1.9.0
milestone: 1.9.0 → none
David Britton (davidpbritton) wrote :

in ucsm.py, adding the following method:

def lan_boot_options(api, server):
    service_profile = get_service_profile(api, server)
    boot_profile_dn = service_profile.get('operBootPolicyName')
    response = api.config_resolve_children(boot_profile_dn)
    return response.xpath('//outConfigs/lsbootLan')

and changing 'probe_servers' to:

def probe_servers(api):
    """Retrieve the UUID and MAC addresses for servers from the UCS Manager."""
    servers = get_servers(api)
    server_list = []
    for s in servers:
        if not get_macs(api, s):
        if not lan_boot_options(api, s):
    return server_list

Works around the issue.

Changed in maas:
assignee: Andres Rodriguez (andreserl) → nobody
Changed in maas:
status: Confirmed → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers